Implement read-only HTTP kernel and actor-owned rate limits #6

New issue

Open

opened 2026-08-03 07:47:27 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-03 07:47:27 +00:00

(Migrated from github.com)

Depends on

Goal

Implement the bounded read-only REST surface required by Profile A with deterministic admission, cancellation, and rate-limit behavior.

Scope

immutable route objects and major-parameter keys
request construction from immutable client context
provisional route queues and server bucket remapping
global, user, shared, and route limit handling
bounded retries and typed HTTP results/conditions
cancellation of queued and submitted work
bounded message-history fetch
individual message lookup
bounded attachment retrieval
response-size and deadline enforcement
telemetry that excludes authorization material

Constraints

read-only endpoints only
the rate-limit registry owns bucket state
worker jobs do not own account credentials
one limited bucket must not block unrelated actors or routes
target/scope cancellation must stop queued and active bounded work

Exit gate

fixture tests cover bucket remapping, 429 responses, global limits, cancellation, deadlines, and response limits
route-to-bucket mapping is deterministic
retry policy is bounded and observable
no raw authorization header appears in logs, conditions, fixtures, or results

## Depends on - #3 - #4 ## Goal Implement the bounded read-only REST surface required by Profile A with deterministic admission, cancellation, and rate-limit behavior. ## Scope - immutable route objects and major-parameter keys - request construction from immutable client context - provisional route queues and server bucket remapping - global, user, shared, and route limit handling - bounded retries and typed HTTP results/conditions - cancellation of queued and submitted work - bounded message-history fetch - individual message lookup - bounded attachment retrieval - response-size and deadline enforcement - telemetry that excludes authorization material ## Constraints - read-only endpoints only - the rate-limit registry owns bucket state - worker jobs do not own account credentials - one limited bucket must not block unrelated actors or routes - target/scope cancellation must stop queued and active bounded work ## Exit gate - fixture tests cover bucket remapping, 429 responses, global limits, cancellation, deadlines, and response limits - route-to-bucket mapping is deterministic - retry policy is bounded and observable - no raw authorization header appears in logs, conditions, fixtures, or results