id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244)

Phase of #2244 (P0-A integration, per the #2033 design in PR #3834). Sequenced AFTER the P0-A core phase issue (shared abuse evaluator + structured refusal + counter registry) lands. Triage record: task 5839 on #2244.

Wire the shared evaluator into the real paths — this phase delivers #2244's Done-when:

Charge counters at the frames.rs seam: read_frame (L150–165) charges after the length prefix and before body allocation/decode; the write path charges via the encode_frame/write_frame funnel (L27–39); adapters thread the remote EndpointId. Retain the 1 MiB MAX_FRAME_BYTES cap — do not duplicate it.
HTTP mapping: existing 429 sites emit the structured refusal with a Retry-After header (web/routes.rs:1218 save limiter — currently 429 with a prose body; web/world_ws.rs:350).
World chat limiter becomes a consumer of the same bucket: world/core.rs chat_rates (L38) and the prose refusal "chat rate exceeded; try again later" (L1000) are replaced by the shared bucket + structured refusal where the caller can expose one; chat semantics/caps unchanged, no limit duplicated.
Counter visibility: surface the registry snapshot via id peers or the existing metrics surface.
A refusal sheds the request/stream, never the whole peer connection (except a permanent operator block, which is id(comms): operator block list by public key, with one-button block in the web UI (P0 of #2032) #2245 scope, not this phase).

Acceptance:

A peer exceeding the bucket is refused with a machine-readable retry value on the frame and HTTP paths.
Counters are visible to an operator.
Tests cover: over-bucket refusal with retry value, request-stream shed without peer disconnect, counters incrementing in both directions.

Parent: #2244 · Design: #2033 (PR #3834) · Program: #2056

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), lane B
Session / ID: queue task 5847
Found via: queue claim
Task: Implement id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882 (Phase B / P0-A integration of id(comms): per-peer frame/byte accounting + structured rate-limit refusal (P0 of #2032) #2244): frame-seam charging, HTTP 429 + Retry-After, chat limiter consumer, counter visibility — wired into the P0-A core evaluator.
Expectation: effort m–l; done = integration PR with the acceptance tests passing in CI.
Links: issue id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882 · core phase id(comms): P0-A core — shared abuse evaluator, token buckets, structured refusal, counter registry (phase of #2244) #3881 (task 5845)

🤖 Agent note · parked

Agent: queue worker (repo-worker-code), lane B
Session / ID: queue task 5847
Found via: queue claim
Task: id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882 (Phase B / P0-A integration of id(comms): per-peer frame/byte accounting + structured rate-limit refusal (P0 of #2032) #2244).
Park reason: Prerequisite not landed. This integration wires into the P0-A core evaluator (Phase A: issue id(comms): P0-A core — shared abuse evaluator, token buckets, structured refusal, counter registry (phase of #2244) #3881), which the triage addendum on id(comms): per-peer frame/byte accounting + structured rate-limit refusal (P0 of #2032) #2244 sequences explicitly — "Phase B … sequenced after task 5845 lands" — and queue task 5845 is claimed right now by another lane (verified fresh this claim). Building the integration before the core's evaluator/bucket/refusal/registry types exist would mean inventing them in parallel with their owner.
Resume condition: task 5845 completed and its PR merged; then build Phase B against the landed core types.
Links: core id(comms): P0-A core — shared abuse evaluator, token buckets, structured refusal, counter registry (phase of #2244) #3881 · origin id(comms): per-peer frame/byte accounting + structured rate-limit refusal (P0 of #2032) #2244

🤖 Agent note · parked

Agent: repo-worker-code (lane C scheduled shift)
Task: queue task 5847 for id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882.
Verified fresh 2026-11-01T18:27Z: id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882 OPEN, no hard-stop labels; prerequisite P0-A core id(comms): P0-A core — shared abuse evaluator, token buckets, structured refusal, counter registry (phase of #2244) #3881 still OPEN — its implementation PR feat(id): shared abuse evaluator core — buckets, structured refusal, counter registry (#3881) #3891 is OPEN but not merged.
Action: parked task 5847 for 30 minutes; no code or worktree changes.
Resume when: PR feat(id): shared abuse evaluator core — buckets, structured refusal, counter registry (#3881) #3891 merges and id(comms): P0-A core — shared abuse evaluator, token buckets, structured refusal, counter registry (phase of #2244) #3881 closes (core task 5845 completes); then wire the integration paths.

🤖 Agent note · parked — dependency gate CLEARED; ready to implement next claim

Agent: queue worker (repo-worker-code), Lane E shift
Session / ID: queue task 5847 (small_fix, id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882 P0-A integration for id(comms): per-peer frame/byte accounting + structured rate-limit refusal (P0 of #2032) #2244)
Found via: queue claim; resuming lane C's park (resume condition: PR feat(id): shared abuse evaluator core — buckets, structured refusal, counter registry (#3881) #3891 merges and id(comms): P0-A core — shared abuse evaluator, token buckets, structured refusal, counter registry (phase of #2244) #3881 closes)
Fresh check (2026-11-01): resume condition now MET — PR feat(id): shared abuse evaluator core — buckets, structured refusal, counter registry (#3881) #3891 MERGED (merge commit bc76a7ed1a44fd056c8f1669dfec78d50de2344e), issue id(comms): P0-A core — shared abuse evaluator, token buckets, structured refusal, counter registry (phase of #2244) #3881 CLOSED, and the P0-A core evaluator is on main at pkgs/id/src/abuse.rs. id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882 OPEN, no hard-stop labels.
Why parked again: the gate cleared minutes ago, but the integration itself (frames.rs charge seam, HTTP 429+Retry-After at the two existing sites, chat limiter consumer, counter visibility, plus CI test cycle) is an m–l implementation that does not fit verifiably in this shift's remaining budget. Parked 30m so the next lane starts implementation immediately from current main — no further gate checks needed beyond the standard revalidation.

Parked: OpenChamber scheduled lane parked task 5847 for 30 minutes, naming the Drew-owned artifacts.

Agent: repo-worker-code
Session / ID: OpenCode session ses_e5e6528192cffeQK5DDqNGg4cM; task 5847
Fresh evidence: id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882 is OPEN and assigned to Drew; canonical PR feat(id): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (#3882) #3960 and prerequisite PR design(id): #2033 abuse-control primitives v1 #3834 are OPEN and Drew-authored. Only issue/PR metadata and labels were checked; no diffs, CI checks, reviews, branches, or worktrees were inspected.
Disposition: Drew-owned PR hard stop applies. No code, branch, worktree, or PR changes. Existing work/assigned label remains; parked labels are set.
Resume condition: After the park interval, freshly revalidate id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882/feat(id): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (#3882) #3960/design(id): #2033 abuse-control primitives v1 #3834; proceed only when ownership/handoff clears the Drew-owned restriction, then verify remaining PR gates.
Links: id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882 · feat(id): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (#3882) #3960 · design(id): #2033 abuse-control primitives v1 #3834

Lane E resumed task 5847: PR #3960 is the queue agent PR for this task (branch queue/5847-3882-p0a-integration; the shared dezren39 author account is not a Drew-owned stop — same pattern as task 5236/PR #4206). Fresh revalidation: PR #3960 MERGEABLE/CLEAN at head 6e868c6, core PR #3891 merged, all 7 Codex findings dispositioned with fix replies (latest P2 fixed in 6e868c6). Proceeding to merge.

Merge pull request #3960 from developing-today/queue/5847-3882-p0a-in…

Done: PR #3960 merged (merge commit 762f32a). All acceptance criteria landed: frame-seam charging with structured refusal + retry value, HTTP 429 sites emit Retry-After, world chat limiter consumes the shared bucket, counters visible via peers/metrics surface. All 7 Codex findings dispositioned with fixes. Closing as complete.

Navigation Menu

Repository navigation

id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882

117 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id(comms): P0-A integration — frame-seam charging, HTTP 429+Retry-After, chat limiter consumer, counter visibility (phase of #2244) #3882

Description

Activity

dezren39 commented on Nov 1, 2026

dezren39 commented on Nov 1, 2026

dezren39 commented on Nov 1, 2026

dezren39 commented on Nov 1, 2026

117 remaining items

dezren39 commented on Nov 2, 2026

dezren39 commented on Nov 2, 2026

dezren39 commented on Nov 2, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions