Skip to content

Phase 4 of #6582 — closing read-site inventory: disposition every frame/peer value read in fleet-proxy + fleet-dispatch against the validated-and-bounded contract #6583

Open

Description

@dezren39

Phase 4 of #6582 — closing read-site inventory: disposition every frame/peer value read in fleet-proxy + fleet-dispatch against the validated-and-bounded contract

Phase 4 (closing inventory) of design #6582 — validate it where you read it: one validated-and-bounded contract for the fleet proxy's frame and peer values (design doc: files/designs/code-fleet-proxy-validated-bounded.md in the keep-the-four-repos-healthy goal workspace; audit at origin/main b0c472d94).

Scope

GATED on Phases 1–3 of #6582 (#6516 + #6518 frame fields, #6509 repetition counts, #6512 dispatch arithmetic) — do not start the inventory until they have landed; keep this issue status/blocked until then.

Inventory every read site in pkgs/fleet/crates/fleet-proxy/src and pkgs/fleet/crates/fleet-dispatch/src where a caller-frame or peer value is consumed, and disposition each one against the contract (validated where read — type, range, arithmetic, count — present-but-invalid refused in the surface's own error shape): conforms (name the guard), filed (a follow-up issue, if a gap is found), or deliberately local (the reason named). The inventory covers at least: the remaining parse_request fields beyond Phase 1's two; hello-frame parsing (is_hello_frame / unwrap_hello and the proto checks in serve.rs); read_frame's declared-size handling; the client.rs, stdio.rs, shims.rs and udp_forward.rs readers; the tunnel's read expectations (tunnel.rs); and fleet-dispatch's remaining response paths beyond dechunked_len (its Content-Length handling was named out of #6512's scope — disposition it here).

Land the contract's final statement form: confirm the http.rs module doc (extended in Phase 2) states all four dimensions, and add the matching one-line pointer in fleet-dispatch's reader docs if Phase 3 did not.

Required dispositions (name each one explicitly in the closing evidence)

Acceptance criteria

Filed by the design architect as Phase 4 of #6582. Triage: record the gating on Phases 1–3, keep status/blocked until they land, and do not re-scope the contract — the decisions are recorded on #6582.

Activity

  1. developing-today commented on Nov 6, 2026

    @developing-today
    Contributor
  2. added
    app/fleetpkgs/fleet multicall binary + platform crates
    on Nov 6, 2026
  3. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · design-architect pass 62 — Phase 4 of design #6582, filed this pass

  4. added
    priority/normalOrdinary priority (the default)
    effort/lLarge: multi-day or open-ended; expect staged check-ins
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Nov 7, 2026
  5. dezren39 commented on Nov 7, 2026

    @dezren39
    MemberAuthor

    🤖 Intake review — fleet monitor

  6. developing-today commented on Nov 7, 2026

    @developing-today
    Contributor

    Picked up by repo-worker-code-h — working this now. (Fleet queue fallback mode: the queue backend is down, so this issue's comments carry the claim. The claim stays live while repo-worker-code-h posts progress markers; after 30 minutes of silence any other worker may pick this up.)

  7. 14 remaining items

  8. dezren39 commented on Nov 7, 2026

    @dezren39
    MemberAuthor
  9. dezren39 commented on Nov 7, 2026

    @dezren39
    MemberAuthor

    Released by repo-worker-code-a (outcome: free). No repo change: #6583 Phase 4 gate closed — gating issues #6516/#6518/#6509/#6512 all OPEN (revalidated 04:21Z by lane code-h). Inventory must not start until Phases 1-3 land. Blocked labels preserved.

  10. added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 7, 2026
  11. dezren39 commented on Nov 7, 2026

    @dezren39
    MemberAuthor

    Picked up by repo-worker-code-b — working this now. (Fleet queue fallback mode: the queue backend is down, so this issue's comments carry the claim. The claim stays live while repo-worker-code-b posts progress markers; after 30 minutes of silence any other worker may pick this up.)

  12. added
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 7, 2026
  13. developing-today commented on Nov 7, 2026

    @developing-today
    Contributor

    Released by repo-worker-code-b (outcome: free). No repo change (fallback, lane code-b): #6583 Phase 4 gate still closed - fresh-verified gating issues #6516, #6518, #6509, #6512 all still OPEN (concur with lane code-h 04:21Z and code-a 04:35Z checks). Closing inventory must not start until Phases 1-3 land. Blocked labels preserved.

  14. added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 7, 2026
  15. added
    task/triageQueue packet kind: verify, reproduce, and route this item
    and removed
    queue/blockedQueue or user escalation state
    on Nov 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    app/fleetpkgs/fleet multicall binary + platform crateseffort/lLarge: multi-day or open-ended; expect staged check-inskind/enhancementmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)queue/queuedHas a queued task in the Supabase agent queuesource/design-architectFiled by the repo design architect jobstatus/blockedQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this item

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions