Skip to content

docs(quest): drop suffix-based routing from the wildcard line - #4383

Merged
kixelated merged 1 commit into
quest/m1/wildcard/READMEfrom
chore/wildcard-drop-suffix
Sep 28, 2026
Merged

kixelated merged 1 commit into
quest/m1/wildcard/READMEfrom
chore/wildcard-drop-suffix

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Problem

Maintainer decision: suffix-based routing is no longer planned.

The wildcard line already settled on prefix claims (#4159, #4218, #4279), but its README still describes the rule as specificity tiers and mentions suffix claims in two places. The relay cluster doc also still says non-prefix pattern resolution is coming.

Approach

Text only. The wording matches the main PR (#4382), so the line merges cleanly.

  • quest/m1/wildcard/README.md
    • Goal: the longest covering prefix wins, and prices compete only among claims of the same prefix. The "specificity tier" wording is gone, and so is "the three pattern shapes".
    • Plan: drops "a suffix or catch-all claim is expressed as the widest prefix that covers it". The catch-all is simply the root prefix.
    • Priced decision: the standby floor applies to claims of the same prefix, not "equal specificity".
    • "Where derived output lives": drops the sentence about **/transcode.pro collapsing to the root. The mirrored-prefix layout stays as the plan.
  • doc/bin/relay/cluster.md
    • "Wildcard advertisements" is now "Prefix advertisements".
    • Routing prefers the longest covering prefix, not "the most specific pattern".
    • Drops "Resolving a non-prefix pattern into a subscription is not implemented yet".

Impact

  • Public API: none.
  • Wire: none.
  • Code already on this line (spread hash, reply-named origin) is prefix pooling, not suffix routing, so it is unchanged.

Alternatives

Follow-ups

(Written by Opus 5.5)

🤖 Generated with Claude Code

Maintainer decision: suffix-based routing is no longer planned. Reword the
wildcard README around the longest-prefix rule, drop the leftover suffix
references, and drop the relay cluster doc's promise of non-prefix pattern
resolution.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kixelated
kixelated marked this pull request as ready for review September 28, 2026 17:47
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-28T17:49:16.270295Z f348562 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@kixelated

Copy link
Copy Markdown
Collaborator Author

Merge summary:

  • Text only: the wildcard line's README and doc/bin/relay/cluster.md now describe prefix claims (longest covering prefix wins, prices compete within the same prefix) and drop suffix routing. The wording matches docs(quest): drop suffix-based routing from the plans #4382.
  • CI green. Codex reviewed head f348562 with no findings (thumbs up). No open review threads.
  • quest check fails on this questline branch, but the output is identical on the base (quest/m1/wildcard/README), so this PR adds no errors. The branch predates the newer quest format; it clears when main is merged into the line, which also needs the quest/m1/wildcard to quest/m0/wildcard move from quest: plan cluster routing, update dedupe, and the local origin #4213 resolved.
  • Maintainer approved the merge.

(Written by Opus 5.5)

@kixelated
kixelated merged commit 58c7db8 into quest/m1/wildcard/README Sep 28, 2026
3 checks passed
@kixelated
kixelated deleted the chore/wildcard-drop-suffix branch September 28, 2026 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant