id: design: adapter conformance harness & interop matrix CI (from #5674) #5814

Activity

1. dezren39

   added

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   on Nov 5, 2026
2. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1497
3. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 5, 2026
4. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane code-c
   • Session / ID: task 10217
   • Found via: queue claim
   • Task: Triage issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814 (adapter conformance harness & interop matrix CI design, from issue id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674) at current main: verify state, scope the design path, record blockers/ordering.
   • Expectation: s — triage complete with evidence and ordering recorded on issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814; no implementation in this task.
   • Links: parent issue id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674; programme epic epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056
5. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: queue worker (repo-worker-code), lane code-c
   • Session / ID: task 10217
   • Found via: queue claim
   • Task: Triage of issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814 complete — findings below.
   • Expectation: done for task 10217 (triage); the design work itself remains open on issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814, ordered after its parent.
   • Links: parent issue id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674; programme epic epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056

   Triage findings (task 10217, verified 2026-11-05)

   • State verified fresh: issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814 is OPEN, labels at claim were task/triage, queue/queued, app/id — no hard-stop labels (held, user/owned, do-not-merge, do-not-auto-edit) and no user/review/user/escalated. No PR or branch owns this work; the only prior comment is a tracker link.
   • What this is: a follow-on design ticket from issue id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674, filed 2026-11-04 in the WS-F gap pass. Its deliverable is a recorded decision — the conformance harness every transport adapter must pass, and the interop matrix run in CI ("adapters are certified, not hoped") — not code in the first instance.
   • Blocker / ordering (recorded per acceptance): parent issue id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674 ("Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies") is still OPEN and undecided. Issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814's own body states the parent carries the surrounding decisions this ticket must not re-decide, and that implementation timing is a separate decision, possibly months out. The conformance harness presupposes the adapter model and wire-format family the parent settles — designing it first would silently fork the parent's decisions, which the ticket explicitly forbids.
   • Scoped path once unblocked: (1) parent issue id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674 records its decision; (2) this design settles harness shape (shared test suite vs per-adapter suites), the interop matrix dimensions (adapter × transport × relay/proxy path), and the certification gate for CI, recording alternatives rejected and the invariants implementation must hold, per the ticket's decision-record requirement; (3) implementation splits are filed as separate linked issues rather than growing this one, as the ticket instructs.
   • Disposition: triaged, left OPEN pending the parent decision. No code change, no PR, and no duplicate design/implementation issue filed in this pass.
6. dezren39

   removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 5, 2026
7. github-actions

   assigned

   dezren39

   on Nov 5, 2026
8. dezren39 commented on Nov 8, 2026

   

   dezren39

   on Nov 8, 2026

   MemberAuthor

   More actions

   🤖 Agent note · handed off

   • Agent: queue worker (repo-worker-code), lane code-z
   • Session / ID: task 12315
   • Found via: queue claim
   • Task: Triage of issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814 (id: design: adapter conformance harness & interop matrix CI). Execution-lane assignment for task 12315 returned opencode, so per the worker runbook §1b this lane does not work it directly: task 12315 is checkpointed handed_off and parked 1800s for the opencode claimant.
   • Expectation: the claimant launches a bound opencode session that drives task 12315 to its terminal state under the queue worker id.
   • Links: issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814
9. 7 remaining items

   Load more
10. dezren39

    added

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    and removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 8, 2026
11. developing-today commented on Nov 8, 2026

    

    developing-todayBot

    on Nov 8, 2026 – with developing.today

    Contributor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-p
    • Session / ID: task 12315
    • Found via: queue claim
    • Task: triage issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814 — handed off to the opencode claimant per execution-lane assignment (§1b); this lane does not work it directly. (This note is the rate-limit repair: the original handoff note failed with GitHub's secondary rate limit "submitted too quickly"; the queue checkpoints, parked labels, and 1200s park all landed at handoff time. Reposted under the developing.today GitHub App token per the runbook rate-limit fallback.)
    • Expectation: claimant launches the bound opencode session; task parked 1200s so it returns to the queue if the claimant does not bind.
    • Links: issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814
12. dezren39 commented on Nov 8, 2026

    

    dezren39

    on Nov 8, 2026

    MemberAuthor

    More actions

    🤖 Agent note · triaged (re-triage under the 2026-11-07 triage doctrine, code#7016)

    • Agent: queue worker (repo-worker-code), lane c8b9355e-319a-4640-8096-7ad19480d151 (openchamber scheduled lane)
    • Session / ID: task 12315
    • Found via: queue claim
    • Verdict: real and current — not invalid, so it returns to the queue for real work with a fix packet.
    • Task: re-triage of issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814 after the done-task-only audit found queue task 10217 done with no landed evidence.

    Verification (fresh, 2026-11-08)

    • Issue id: design: adapter conformance harness & interop matrix CI (from #5674) #5814 is OPEN, created 2026-11-05, labels at claim: task/triage, status/parked, queue/parked, app/id, work/assigned. No hard-stop labels (held, user/owned, do-not-merge, do-not-auto-edit), no user/escalated.
    • No PR, branch, or commit owns this work: no open PR references id: design: adapter conformance harness & interop matrix CI (from #5674) #5814, no queue/*5814* branch, no merged commit with a closing keyword. The only cross-reference is measurement PR docs(id): self-hosting and interop stance (#5975) #7602 (id: design: self-hosting & interop stance — own servers, Rust library reuse, what intercompatibility requires #5975), which assigns the conformance proof here rather than doing it.
    • The prior triage note (2026-11-05, task 10217) recorded findings but produced no decision record, which is why the doctrine re-queued it. Its content is still correct and is not contradicted by anything landed since.

    What this issue actually owes

    A recorded design decision for the adapter conformance harness (the test suite every transport adapter must pass) and the interop matrix run in CI ("adapters are certified, not hoped"). It is a decision record, not an implementation: doc/ record linked from this issue, chosen shape, rejected alternatives with reasons, invariants.

    Ordering and dependencies (verified fresh)

    • Parent: id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674 (wire format & transport adapters) — OPEN.
    • Siblings under id: design: Wire format & transport adapters — postcard schema, non-UDP carriers, relays/proxies #5674: id: design: postcard wire schema v1 (from #5674) #5808 (postcard wire schema v1), id: design: versioning, negotiation & forward-compatibility policy (from #5674) #5809 (versioning/negotiation/forward-compat), id: design: framing & fragmentation per carrier class (from #5674) #5810 (framing & fragmentation per carrier), id: design: adapter: WebSocket/WSS + HTTPS fallback (from #5674) #5811–id: design: relay & proxy standard protocol (from #5674) #5813 (the adapters themselves), id: design: security binding review across adapters & relays (from #5674) #5815 (security binding review). All OPEN.
    • id: design: self-hosting & interop stance — own servers, Rust library reuse, what intercompatibility requires #5975 (closed, PR docs(id): self-hosting and interop stance (#5975) #7602) makes this issue load-bearing: its interop contract names the wire format, identity, capability negotiation and registry format as the load-bearing elements, and explicitly assigns "conformance proof" to id: design: adapter conformance harness & interop matrix CI (from #5674) #5814. So this design is the proof obligation for the self-hosting/interop stance, not an optional extra.
    • Consequence for sequencing: the harness can be designed now against the contract shape (certification criteria, matrix axes, CI gate placement, fixture/oracle model), but the matrix cells and assertion set must be filled from id: design: postcard wire schema v1 (from #5674) #5808/id: design: versioning, negotiation & forward-compatibility policy (from #5674) #5809/id: design: framing & fragmentation per carrier class (from #5674) #5810/id: design: adapter: WebSocket/WSS + HTTPS fallback (from #5674) #5811–id: design: relay & proxy standard protocol (from #5674) #5813 as they land. The record must therefore either pin the contract versions it was written against or state that cell population follows the siblings — the same shape used by the id: design: local-dev parity for the serverless edition (from #5681) #5866 decision record (decided half + explicitly blocked remainder with a resume condition).

    Repo state relevant to the design (checked)

    • No conformance harness, interop matrix, or equivalent exists for ID transports: no *conformance* / *interop* files under pkgs/id/, and no interop workflow in .github/workflows/.
    • pkgs/id does have conformance-adjacent precedent to reuse rather than invent: pkgs/id/src/shell_contract.rs + shell_contract/tests.rs and pkgs/id/src/world_session/contract_tests.rs are contract-suite patterns; postcard is already a dependency; pkgs/id/tests/ holds the integration-test conventions.

    Routing

    Real and current → converting the remaining scope to a fix packet (repo-health:v1:fix:developing-today/code:issue:5814) returning it to the queue for the decision record. No blocker on Drew; nothing here needs escalation. Task 12315 completes as triaged.
13. dezren39

    added

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    and removed

    status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

    queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

    on Nov 8, 2026
14. developing-today

    added

    status:in-review

    on Nov 8, 2026
15. dezren39 commented on Nov 8, 2026

    

    dezren39

    on Nov 8, 2026

    MemberAuthor

    More actions

    agent-note:v1 — task 13680 (lane code-l) — pr_opened

    Partial decision record for #5814 is up as PR #7853: doc/2026-11-08T23-22-53Z_design_id_adapter-conformance/, indexed in doc/README.md.

    Decided now: one shared contract harness in pkgs/id (adapters enter through assertion-free bindings); certification criteria C1–C6 pinned to the #5975 load-bearing elements; interop matrix axes adapter × carrier class × platform with cross-pairing and direction as in-cell dimensions; CI gate = pkgs/id flake check in the id workflow (PR) plus the nightly full matrix; fixture/oracle model with per-step declared outcomes so a pass is machine-decidable. Rejected alternatives are recorded with reasons.

    Blocked remainder (record §7): per-sibling fixture content and matrix rows fill in as #5808/#5809/#5810/#5811/#5812/#5813 land — all verified OPEN 2026-11-08. Per the record, #5814 stays open for exactly that remainder; PR #7853 carries no closing keyword. No #5674 or #5975 decision is changed.

    Verification: every relative link in the record resolves (checked programmatically), the README index target exists, git diff --check clean.
16. dezren39

    removed

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    on Nov 8, 2026
17. dezren39

    added 2 commits that reference this issue on Nov 9, 2026

    docs(id): framing and fragmentation decision across carrier classes (#…

    ...

    e2f7e0d

    docs(id): framing and fragmentation decision across carrier classes (#…

    ...

    828d6b3