[V3RON]

Closes #1015

Status

Implement: done (5/5 green, audit 4/4 Done when) Review: passed round 1, 0 open Hardware: n/a Gate: waiting for the stack
Next: merges with the #1013 stack

Assumptions

• Assumption: where does the 0x07 test run? — at the stream module's surface (src/stream/create.test.ts), since the device-lost cases need a real health monitor and an enrolled phone

Done when

• pnpm test passes with the five tests above. — five Tests lines built and green locally (build 5/5, audit probed 6/6); CI pending on head
• The OpenAPI document lists GET /v1/leases/{id}/stream with its statuses. — check-openapi.mjs passes (34 operations)
• watching-the-screen.mdx and access-control.mdx say a lease holder can watch its own lease, and how a stream ends. — pages edited in this PR; website build passes
• src/stream/AGENTS.md and src/http/AGENTS.md describe the lease route. — both edited; audit fixed two stale lines in src/stream/AGENTS.md

Review

Spec review: 1 blocking, 0 fixed, 0 notes. Code review: 0 blocking, 0 fixed, 0 notes. Claims review: 0 blocking, 0 fixed, 0 notes.
Rounds: 1. Tokens: 7.0M.
Runs: 8. Cost USD: 6.3551. Agent seconds: 2518.
Assessment: complete

Rejected:

• spec: unknown tag has no test (ui/src/data/stream.test.ts:517) — [incorrect] the alive frame takes the same unhandled-tag path and the 0x07 after it still arrives (ui/src/data/stream.ts:239-250)

Written by an agent.

[V3RON]

Decision taken

Question: a module's lease route is /v1/leases/{id}/<module name>. Core already has lease sub-routes renew and exec. What happens when a module's name is one of them? Today the host only checks names against core first segments, so such a module would load and the routes would clash.

Options:

1. The host refuses to load the module (taken). A user who loads a module named renew or exec gets a load error, as a name clashing with a core first segment does today. POST /v1/leases/{id}/renew and exec keep working.
2. The module route wins. renew or exec stops working for every lease on that daemon.
3. Core wins silently. The module loads but its lease route is never reached; the user sees no error.

Why 1: it is the rule the host already applies to first segments, it keeps every core route working, and no shipped module has such a name, so nobody sees a change today.

Reverting: drop the names from the host's clash check and the #1015 test that pins it; the ADR 0049 line changes with it.

Raised in the ADR review on #1014; folded into #1015 (Modules touched and Tests), marked pending the maintainer. This PR builds it.

Written by an agent.

[V3RON]

Decision taken

The audit found three branches no test catches and one test away from its named seam. Nothing a user sees changes; these settle what the tests pin.

1. Worker's own 404 UNKNOWN_LEASE (lease missing from the worker's registry, src/stream/worker-link.ts). Options: add a row at the worker's stream lease handler (taken), or leave it untested. Taken because a deleted check would serve a picture for a lease the worker no longer holds. Reverting: delete the row.
2. An unleased device going absent writes no 0x07. Options: add a row to the 0x07 test (taken), or rely on the older follows its device test. Taken so the 0x07 test catches its own condition. Reverting: delete the row.
3. The relay's leaseId has no effect on the stream target yet. Kept as the spec (F5) names it; no test, since nothing reads it here. Input socket for a lease #1017 is its first reader.
4. The 0x07 test runs in src/stream/create.test.ts, not the e2e file the Tests section names: the device-lost cases need a real health monitor and an enrolled phone. Options: keep it there (taken), or move it and fake both in the e2e daemon. Reverting: move the test.

Folded into #1015's Tests, marked pending the maintainer.

Written by an agent.

[V3RON]

Review ledger

Round 1: 0f28cc7
Round fix-check: 46ea88c

Runs: 10. Cost USD: 6.5132. Agent seconds: 2575.
Tokens input 506, output 132153, cache read 20869365, cache write 769626.
- build implementer: claude-sonnet-5-5 841 s $1.9657
- build implementer: claude-sonnet-5-5 134 s $0.2749
- audit implementer: claude-sonnet-5-5 319 s $0.6251
- fix implementer: claude-sonnet-5-5 76 s $0.1696
- review 1 reviewer: claude-sonnet-5-5 552 s $0.3262
- review 1 spec: claude-sonnet-5-5 50 s $0.2935
- review 1 claims: claude-sonnet-5-5 85 s $0.3409
- review 1 code both: claude-opus-5-5 461 s $2.3592
- fix ci implementer: claude-sonnet-5-5 33 s $0.0857
- review fix-check reviewer: claude-sonnet-5-5 24 s $0.0724
Finding outcomes: {"incorrect":1}. Classes: {"testing 3":1}.

{"findings":[{"id":"R1","role":"spec","class":"testing 3","outcome":"incorrect","path":"ui/src/data/stream.test.ts","round":"1"}]}

Written by an agent.