[12/36] Add OC-080 and OC-090 task tracks

[cjohnsto-nz]

---

This is part 10 of 21 in a stack made with GitButler:

•  21  [22/36] Release 0.8.0 with packaged PDF.js preview #54
•  20  [21/36] Complete OC-070 protocol surface polish #56
•  19  [20/36] Record final OpenCollection supervisor acceptance #53
•  18  [19/36] Add OC-110 runtime authoring UX #52
•  17  [18/36] Add OC-080 runtime lifecycle and OC-110 task setup #51
•  16  [16/36] Record OC-050 OC-090 OC-100 supervisor audit #50
•  15  [15/36] Add OC-050 auth and transport support #49
•  14  [14/36] Add OC-100 request type UX #48
•  13  [13/36] Add OC-100 request type UX task #47
•  12  [12/36] Add OC-080 and OC-090 task tracks #46 <-- current
•  11  [11/36] Record OC-010 through OC-040 supervisor audit #45
•  10  [10/36] Add OC-020 WebSocket support #44
•  9  [09/36] Add OC-010 GraphQL support #43
•  8  [08/36] Require demo server fixtures for parallel tracks #42
•  7  [07/36] Record OC-000 and OC-060 supervisor audit #41
•  6  [06/36] Add OC-060 schema round-trip validation #40
•  5  [05/36] Add OC-040 runtime scripting support #39
•  4  [04/36] Add OC-090 gRPC streaming support #38
•  3  [03/36] Add OC-030 gRPC unary protobuf support #37
•  2  [02/36] Add OC-000 protocol dispatch foundation #36
•  1  [01/36] Add OpenCollection agent plan #35

[APKiwi]

Verdict: approve. Docs only, internally consistent with the audit PR before it: OC-080's stated gap correctly restates the runtime-lifecycle limitation the code actually has, the OC-070 rewrite is coherent with its new dependencies, and numbering lines up across board, dependency map, prompts and README. The renamed "Remaining Gap Evidence" file-path pointers are asserted rather than verified in-diff but nothing contradicts them.

[cjohnsto-nz]

Already addressed; no change is required on this planning branch.

I verified the evidence paths rather than treating them as assertions:

• At the OC-070 planning point, src/commands/requestCommands.ts still creates only an HttpRequest starter.
• src/services/requestExecutionService.ts applies the runtime lifecycle to HTTP and GraphQL, while WebSocket and gRPC dispatch directly to their clients; that is the OC-080 gap this task records.
• The README's snippet path is stale on this historical branch: the implementation file is src/services/snippetExporter.ts, not src/services/snippetService.ts.
• The gRPC streaming statement is a planning snapshot that was superseded by PR [04/36] Add OC-090 gRPC streaming support #38, branch feature/oc-090-grpc-streaming, which owns the streaming implementation and coverage in src/services/grpcClient.ts and test/grpcSupport.test.ts at the currently verified head 5b5164f.

The stale snippet link and open-gap wording are already corrected by PR #53, branch supervisor/final-opencollection-review, in docs/open-collection-gap-analysis/README.md at the currently verified head 72ae2dd. That final-state document links src/services/snippetExporter.ts and records unary/streaming gRPC as implemented. I am not duplicating that descendant-owned final-state rewrite on PR #46.

PR #46 and immediate child PR #47 remain MERGEABLE/CLEAN.

[APKiwi]

Re-review (whole-stack pass, per REVIEW_GUIDE.md)

This is a docs-only task-track PR, so the ledger is the deliverable. Its central claim about OC-090 is wrong against the code already in its own ancestry.

• (high) AGENT_PROGRESS.md:69 logs OC-090 as Unclaimed ("Start after OC-030..."), and tasks/09-grpc-streaming.md:13-18 says streaming calls "are not executed" and the demo "proves unary and unsupported-streaming, not real streaming." Both are false here. feature/oc-090-grpc-streaming ([04/36] Add OC-090 gRPC streaming support #38) is a verified ancestor of this base. At this PR's head, src/services/grpcClient.ts already executes server/client/bidi streaming, test/grpcSupport.test.ts already passes every item in task 09's own suggested-tests table, and examples/demo-api/gRPC/ already has all the streaming fixtures. The dead GrpcStreamingUnsupportedError class is the only trace of the "unsupported" state the doc describes as current. Anyone using this ledger to find open work would spin up a redundant OC-090 implementation agent.
• (medium) Same stale premise repeats in tasks/07-import-export-copilot.md ("If OC-090 lands first...") and tasks/08-runtime-non-http-protocols.md ("Covered by OC-090 after streaming execution exists"). OC-090 is order 04, both of those land later, and per the git evidence it already exists.
• (low) README.md "Remaining Gap Evidence" cites src/services/snippetService.ts, which does not exist. The real file is src/services/snippetExporter.ts.

Verdict: changes-needed. Correct the OC-090 row to done with a pointer to #38 (2ac3bc4/06b8d83), reword task 09 to verification/hardening rather than net-new implementation, and fix the snippet path.

[cjohnsto-nz]

Response to the second review: the stale OC-090 documentation was a valid finding.

I corrected it on stack-tip rework PR #72 in b220ecb, rather than rewriting this historical planning branch. The OC-090 task now records PR #38 and commits 2ac3bc4/06b8d83 as complete, its former "Current Gap" is explicitly historical/closed, OC-070 states that streaming landed first, and OC-080 no longer describes streaming execution as future or unsupported. The nonexistent snippetService.ts pointer was already corrected to src/services/snippetExporter.ts.

The task board's OC-090 row is Done, and the exact full-stack verification passes build, TypeScript compile, 31 files / 539 tests, and 47/47 demo files.