spec(port): port specs/port/trios/crates/trios-bridge/src/relay.t27 (Closes #8684)

[dmitrii-f-t27]

Summary

Port gHashTag/trios:crates/trios-bridge/src/relay.rs (at 8b229e9489ee, 183 lines) as specs/port/trios/crates/trios-bridge/src/relay.t27 — Roadmap Stage 6 (goal #4548), target t27c gen-rust. Closes #8684.

The original is the HTTP relay with SSE for Comet ↔ agent real-time communication: four endpoints over the bridge.

Per the issue's rule ("Port the decision, not the plumbing"), all six listed functions are ported under their names as pure functions (no transports — the HTTP server, the SSE transport and the router state are the callers' plumbing) with 8 tests (27 runtime asserts, 0 vacuous, 100% function coverage):

• relay_app — the four-route table: /events, /agents, /dispatch (POST), /health (original lines 62-69);
• serve_relay — the relay runs alongside the WebSocket bridge, never replacing it (lines 72-87);
• sse_events — the sidepanel stream: a lagged broadcast message is skipped, not fatal, and the stream keeps alive (lines 96-109);
• list_agents — the registered agents answered as JSON (lines 112-115);
• dispatch_task — the dispatch decisions: the broadcast literal fans to everyone; a specific agent must be registered; when both the issue number and the branch name arrive, the router claims the issue first, then the status moves to Working with the task as the message, and the command rides the broadcast; the confirmation and error shapes (lines 118-174);
• health_check — the ok status with the agent count (lines 177-183).

Verification (all run live from the worktree root, zig 0.16.0)

• t27c parse: OK. t27c spec-status: IMPLEMENTED. t27c typecheck: 0 errors, 0 warnings.
• t27c coverage: 14/14 tested (100%) — no transports in this port.
• t27c test-report: 8 tests / 8 pass / 0 FAIL / 0 BLOCKED, 0 vacuous passes — the route table with methods, the lag-skip and keep-alive, the list pass-through, the broadcast literal, the registration gate, the claim-requires-both rule in all four combinations with the claim-then-status ordering, and the health ok both ways.
• t27c gen | grep -c 'not yet implemented': 0; gen | wc -l: 134 (> 12).
• grep -cE '^\s*(pub )?fn (relay_app|serve_relay|sse_events|list_agents|dispatch_task|health_check)\(': 6. grep -cE '^\s*test\s+(["|[A-Za-z_])': 8 (≥ 6).
• Boundary: git status --short — exactly this one file. The repo's lefthook pre-commit passed.
• dupe_scan: all 8 introduced names unique across 2040 specs (checked before the commit); the bare body scan adds no duplicate group (752 bodies / 221 groups on base, identical with this spec present).

Dmitrii Fedorov (@dmitrii-f-t27)

[dmitrii-f-t27]

@gHashTag Please merge this PR into master via the golden chain — rights on gHashTag/t27 are read-only for me (403), so the merge itself needs your action.

What this is: the #8684 port — crates/trios-bridge/src/relay.rs (gHashTag/trios, at 8b229e9489ee, 183 lines) re-authored as specs/port/trios/crates/trios-bridge/src/relay.t27. One file, one commit, head d0fbc0096, Closes #8684.

What is verified:

• t27c parse OK, spec-status IMPLEMENTED, typecheck 0 errors / 0 warnings, coverage 14/14 (100%) — no transports in this port, t27c test-report 8 tests / 8 pass / 0 FAIL / 0 BLOCKED, 0 vacuous — the four-route table (/events, /agents, /dispatch POST, /health), the SSE rule that a lagged broadcast message is skipped rather than fatal with the stream kept alive, the relay running alongside the bridge, the dispatch decisions (the broadcast literal fanning to everyone; the registration gate; the claim-then-status ordering when both the issue number and the branch name arrive — the claim first, then the status moves to Working with the task as the message), and the health ok with the agent count.
• gen → 134 lines, 0 not yet implemented; the 6 required names count exactly 6; 8 test blocks; boundary exactly the one file.
• dupe_scan: all 8 introduced names unique across 2040 specs (checked before the commit); the bare body scan adds no duplicate group (752/221 unchanged).
• The t27b-native-run artifact of this head (commit d0fbc00, run 39025604259): relay.t27 row — reference pass, t27b pass, tests 8, invariants 0, asserts 29, blockers [], detail empty, reference_disagree: [].

CI (head d0fbc00): required trio green — validate, check-linked-issue, parse-ratchet — Check L1 TRACEABILITY green and Corpus ratchet green; 26 checks pass overall, incl. emit-bitexact, t27b-native-linux, t27b-native-macos.

The 3 reds are the base-red trio, not this change: cli-tri (the #3324 include_str!), duplicate-bodies (only the known base names), t27b-native-ratchet (the same verdict red the Queen's port PRs carry; this spec's own row is reference pass + t27b pass — the registration debt is the UNLISTED class).

After the merge I will: verify the spec file live on the merge SHA, confirm #8684 auto-closed, and file the 14-step report.

Dmitrii Fedorov (@dmitrii-f-t27)