docs(plans): drop the Maven-only rate-limit mount from S30
What this changes
S30's plan carried Step 16b: S05 rate-limit wiring — mounting the
namespace rate-limit check on the Maven virtual read path alone. That step is
removed, and the plan's step total drops from 25 to 24. The surviving
16a keeps its id: its MR (!2692 (merged)) already merged under it, and a step id is
not renumbered after it lands.
The spec keeps everything it fixed about the refusal — 429,
too_many_requests, Retry-After: 5, measured per namespace per ADR-004,
observe-first rollout — and now names the work item that delivers the check.
Files:
docs/plans/2026-09-10-s30-maven-virtual.mddocs/specs/S30-maven-virtual.mddocs/plans/README.md(the plan's index row: the rate-limit clause is gone and the step count moves to 24)
Why
Every pull arm wants the same check: the Maven and npm remote and virtual arms and the container remote and virtual arms. A mount delivered inside S30 would be Maven's alone, and each sibling arm would then need its own.
That work already has a home:
- #1181 owns the check on all six pull arms, keyed on principal, namespace, and IP. Its acceptance criteria name the Maven virtual arm explicitly.
- #149 owns the S05 Phase 2 primitive. It records that S30's read path is the first workload to need it.
Neither is on this plan's critical path, so no step here waits for the S05 amendment any more.
A design divergence this removal settles
Step 16b wired the primitive as a middleware instance mounted at the
class router, carried through a new Deps field and wire_maven.go.
S05-B runs the check inline in the read arm, after repository resolution, and leaves S01's middleware chain slot 11 reserved and unused. The two texts disagreed about where the check lives, and the removal drops the losing side rather than carrying both.
What this does not change
- The refusal shape, its code, and its
Retry-Aftervalue stay S30's. - The merge memory cap (Step 16) is untouched.
- No step's dependencies move except 16b's own removal.
Follow-ups
- S05-B (!3083 (merged)) carried the same claim. It is updated on that branch at
fa8a72f0f: it keeps the Maven arm as its worked example, states that #1181's plan mounts it, and no longer names S30 as the consumer. - #149 and #1181 both cite "S30 Step 16b" as the Maven virtual mount. Each has a comment recording what replaces it.
- #1181's plan cannot be written yet: its acceptance criteria are full of spec-owner decisions, and it depends on its own spec MR, which in turn waits on !3083 (merged).
Coordination
- !2693 (merged) (open, mine) batch-fills this plan's Status table. It edits the same file and was built against the 25-row table, so it needs a rebase once this lands.
docs/roadmap/beta.mdcarries the old denominator and names16bamong the remaining closed-beta steps. That file is left alone here because !2997 (closed) edits it; its S30 row is re-derived by that sync.
Related to #289 (closed) Related to #1181