mcpx: Phase 2 of #2333 — rate-limit register truth-up (retire both gap rows) and #1957 evidence

Phase 2 of design #2333 (origin #2192, split of #1957). Gated on Phase 1 (#2192). Design doc: files/designs/code-mcpx-upstream-question-rate-limits.md in the keep-the-four-repos-healthy goal workspace.

Scope

Truth-up the conformance register for the two rate-limit rows once Phase 1 (#2192) has landed, so the register stops describing a bound that now exists:

Retire the gap rows sampling-client-rate-limit and elicitation-client-rate-limit in pkgs/mcpx/internal/conformance/coverage_clientfeatures.go (lines 118-119 at audit time) to covered rows naming the limiter tests Phase 1 added.
Update the client notes in pkgs/mcpx/internal/conformance/requirements.json: sampling's "no per-server rate limit" and elicitation's "TTL/askRounds only" are false after Phase 1.
Verify the pkgs/mcpx/docs/spec/conformance-matrix.md rows for both gap keys were updated per mcpx conformance: rate limits for sampling and elicitation requests (split of #1957) #2192's acceptance (that update is mcpx conformance: rate limits for sampling and elicitation requests (split of #1957) #2192's own acceptance item — this phase verifies it happened and fixes it if it did not, rather than claiming it twice).
Post the evidence on tracker mcpx: smaller conformance gaps -- user identity, annotation trust, rate limits, cursors, URI encoding, prompt validation, restart, invalidation #1957 closing out its rate-limits cluster, and confirm mcpx conformance: rate limits for sampling and elicitation requests (split of #1957) #2192 is closed or name exactly what of its acceptance remains open.
If Phase 1 landed with different defaults or setting names than design Design: mcpx upstream question rate limits — one limiter at the client choke point, keyed by the configured server #2333's decision 5, record the as-built values in the register evidence — do not silently rewrite the design doc's decisions.

Acceptance criteria

Both gap rows retired to covered rows naming real tests in coverage_clientfeatures.go
requirements.json client notes for both rows updated to the as-built behaviour
conformance-matrix.md rows for both keys verified updated (or updated here if Phase 1 missed them)
Evidence comment posted on mcpx: smaller conformance gaps -- user identity, annotation trust, rate limits, cursors, URI encoding, prompt validation, restart, invalidation #1957 (rate-limits cluster) and mcpx conformance: rate limits for sampling and elicitation requests (split of #1957) #2192's state confirmed

CODE-1181

Phase 2 of design #2333, filed today; sub-issue of #2333 (verified in its sub_issues list). Gated on Phase 1 (#2192, the adopted origin) — labelled status/blocked. Triage packet enqueued: pilot task 3489 (queue=repo-health-code-pilot, status=queued, attempts=0, verified); triage must confirm the #2192 gate before enqueueing any implementation follow-up. Decision is recorded on #2333.

Agent note — verified triage already delivered, gate re-checked fresh (queue task 3489, Lane C shift)

Re-claimed 3489 and revalidated: the triage verdict for #2334 was already posted by a Lane E pass 2026-10-30T11:59Z — gate NOT satisfied, scope confirmed, no follow-up enqueued. I re-checked the gate fresh just now: PR #2706 (Phase 1, #2192) is still OPEN, not merged, so the verdict stands unchanged and this issue correctly keeps status/blocked. Completing 3489 as triaged on that evidence; labels left as the earlier pass set them. When #2706 merges, #2334's Phase 2 becomes enqueueable.

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), OpenChamber scheduled lane
Session / ID: queue task 5553 (repo-health-code-pilot)
Found via: queue claim
Task: Re-triage mcpx: Phase 2 of #2333 — rate-limit register truth-up (retire both gap rows) and #1957 evidence #2334 against current main and confirm whether Phase 1 (mcpx conformance: rate limits for sampling and elicitation requests (split of #1957) #2192) landed; if so, verify the register and mcpx: smaller conformance gaps -- user identity, annotation trust, rate limits, cursors, URI encoding, prompt validation, restart, invalidation #1957 evidence before routing or closing.
Expectation: current-main verdict with gate, register, matrix and tracker evidence; labels synced and follow-up only if work remains.
Links: queue task 5553 · mcpx conformance: rate limits for sampling and elicitation requests (split of #1957) #2192 · Design: mcpx upstream question rate limits — one limiter at the client choke point, keyed by the configured server #2333 · mcpx: smaller conformance gaps -- user identity, annotation trust, rate limits, cursors, URI encoding, prompt validation, restart, invalidation #1957
agent-note:v1 | agent=repo-worker-code | state=picked-up | at=2026-11-01T12:58:08Z

🤖 Agent note · done

Agent: queue worker (repo-worker-code), OpenChamber scheduled lane
Session / ID: queue task 5553 (repo-health-code-pilot, triage)
Found via: queue claim
Task: Re-triage mcpx: Phase 2 of #2333 — rate-limit register truth-up (retire both gap rows) and #1957 evidence #2334 and verify the Phase 1 gate plus the current-main register state.
Verdict: ALREADY COMPLETE on current main 9be9c22. mcpx conformance: rate limits for sampling and elicitation requests (split of #1957) #2192 is closed and PR mcpx: rate-limit upstream sampling and elicitation requests (#2192) #2706 is merged. Both rate-limit IDs are registered as covered tests; clientfeatures_test.go has sampling/elicitation coverage; requirements.json records the as-built 60/min server + 20/min session sampling and 30/min elicitation limits; all seven matrix entries are tested. These settings match design Design: mcpx upstream question rate limits — one limiter at the client choke point, keyed by the configured server #2333.
Evidence: posted the landing summary to tracker mcpx: smaller conformance gaps -- user identity, annotation trust, rate limits, cursors, URI encoding, prompt validation, restart, invalidation #1957: mcpx: smaller conformance gaps -- user identity, annotation trust, rate limits, cursors, URI encoding, prompt validation, restart, invalidation #1957 (comment). mcpx: smaller conformance gaps -- user identity, annotation trust, rate limits, cursors, URI encoding, prompt validation, restart, invalidation #1957 remains open for its other clusters; mcpx: Phase 2 of #2333 — rate-limit register truth-up (retire both gap rows) and #1957 evidence #2334 is closed as completed.
Tests: no tests run in this triage; verified the existing test registrations and main-branch evidence.
Expectation: gate and register verified, tracker evidence posted, labels synced.
Links: mcpx: Phase 2 of #2333 — rate-limit register truth-up (retire both gap rows) and #1957 evidence #2334 · mcpx conformance: rate limits for sampling and elicitation requests (split of #1957) #2192 · PR mcpx: rate-limit upstream sampling and elicitation requests (#2192) #2706 · mcpx: smaller conformance gaps -- user identity, annotation trust, rate limits, cursors, URI encoding, prompt validation, restart, invalidation #1957
agent-note:v1 | agent=repo-worker-code | state=done | at=2026-11-01T12:59:55Z

Navigation Menu

Repository navigation

mcpx: Phase 2 of #2333 — rate-limit register truth-up (retire both gap rows) and #1957 evidence #2334

Scope

Acceptance criteria

5 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

mcpx: Phase 2 of #2333 — rate-limit register truth-up (retire both gap rows) and #1957 evidence #2334

Description

Scope

Acceptance criteria

Activity

developing-today commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

5 remaining items

dezren39 commented on Oct 30, 2026

dezren39 commented on Nov 1, 2026

dezren39 commented on Nov 1, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions