diff --git a/docs/open-collection-gap-analysis/AGENT_GOAL_PROMPTS.md b/docs/open-collection-gap-analysis/AGENT_GOAL_PROMPTS.md
index 4f1f93d..315ce7d 100644
--- a/docs/open-collection-gap-analysis/AGENT_GOAL_PROMPTS.md
+++ b/docs/open-collection-gap-analysis/AGENT_GOAL_PROMPTS.md
@@ -100,8 +100,14 @@ If an agent host does not inject the project-local skills, tell the agent to rea
 /goal Complete OC-090 gRPC streaming support using $missio-agent-coordination, $missio-protocol-implementer, and $missio-demo-server-fixtures without stopping until client-streaming, server-streaming, and bidirectional-streaming execution, schema-native message sequences, validation, cancellation, response streaming UI/tool output, local demo streaming fixtures, AGENT_PROGRESS updates, and complete automated unit, integration, round-trip, failure-path, and cleanup tests are implemented and passing.
 ```
 
+## gRPC Demo Server Reliability
+
+```text
+/goal Complete OC-160 gRPC demo server reliability review using $missio-agent-coordination, $missio-protocol-implementer, and $missio-demo-server-fixtures without stopping until the current failing demo-request behavior is reproduced or concretely explained, every packaged gRPC demo request has a documented local start flow, localhost:50051 is served by a deterministic fixture or all request endpoints are corrected, unary/server-streaming/client-streaming/bidirectional-streaming/error/runtime demo requests pass live smoke tests through Missio execution where applicable, missing-fixture diagnostics are clear, AGENT_PROGRESS updates are complete, and demo collection validation plus complete automated gRPC/demo regression, build, package, and install verification are passing.
+```
+
 ## Final Integration
 
 ```text
-/goal Complete final OpenCollection compatibility integration across all Missio tracks using $missio-agent-coordination without stopping until all OC-000 through OC-150 task rows are Done, all GitButler branches or PRs are linked, the full test suite and required fixture integration tests pass, documentation is consistent, and AGENT_PROGRESS.md contains final verification evidence.
+/goal Complete final OpenCollection compatibility integration across all Missio tracks using $missio-agent-coordination without stopping until all OC-000 through OC-160 task rows are Done, all GitButler branches or PRs are linked, the full test suite and required fixture integration tests pass, documentation is consistent, and AGENT_PROGRESS.md contains final verification evidence.
 ```
diff --git a/docs/open-collection-gap-analysis/AGENT_PROGRESS.md b/docs/open-collection-gap-analysis/AGENT_PROGRESS.md
index fd38764..7017506 100644
--- a/docs/open-collection-gap-analysis/AGENT_PROGRESS.md
+++ b/docs/open-collection-gap-analysis/AGENT_PROGRESS.md
@@ -20,7 +20,7 @@ Status values: `Unclaimed`, `Claimed`, `In Progress`, `Review Ready`, `Blocked`,
 
 | Role | Owner | Scope | Since | Current Focus |
 | --- | --- | --- | --- | --- |
-| Supervisor | Codex | Sanity-check completed tracks, run build/test/package/install verification, preserve GitButler branch hygiene, and append progress reports. | 2026-06-14 22:31 NZT | OC-150 queued as a focused runtime assertion variable UX, WebSocket runtime result visibility, and WebSocket lifecycle contrast follow-up. |
+| Supervisor | Codex | Sanity-check completed tracks, run build/test/package/install verification, preserve GitButler branch hygiene, and append progress reports. | 2026-06-14 22:31 NZT | OC-160 queued as a focused gRPC demo server startup and live verification reliability follow-up. |
 
 ## Test Coverage Rules
 
@@ -73,6 +73,7 @@ Use full branch names for stacking existing branches with `but move <child-branc
 | OC-130 | Protocol-native request editor first paint | Done | Codex | `feature/oc-130-protocol-layout-stability` (g0), stacked on `feature/oc-120-preview-media-controls`; implementation commit `a3d3251` | Satisfied by `test/protocolLayoutStability.test.ts` plus shared request editor/protocol regressions: neutral first-paint shell, host invalid-YAML fallback message, direct HTTP/GraphQL/WebSocket/gRPC hydration, no visible HTTP default or stale non-HTTP controls during hydration, layout-stability CSS assertions, no-op round-trip and protocol-aware validation coverage, and request type UX startup regression. | `npx vitest run test/protocolLayoutStability.test.ts` passed 9 tests; `npm run compile` passed; focused `npx vitest run test/protocolLayoutStability.test.ts test/requestTypeUx.test.ts test/runtimeAuthoringUx.test.ts test/schemaRoundTrip.test.ts test/validationService.test.ts` passed 5 files/34 tests; targeted protocol/editor matrix passed 9 files/89 tests; `node scripts\validate-collection.js examples\demo-api` passed 44/44 files; `npm test` passed 25 files/454 tests; `npm run build` passed. | 2026-06-15 12:03 NZT | OC-130 complete. Preserve parallel/unrelated unassigned OC-140 docs IDs `wp`/`tks`/`tkt`/`uxu` and PDF.js media churn IDs `qp`/`ko`; do not commit them to OC-130. |
 | OC-140 | First-class WebSocket lifecycle UX | Done | Codex | `feature/oc-140-websocket-lifecycle-ux` (g0 after restack), stacked on `supervisor/add-websocket-lifecycle-task`; implementation commit `ec0f014`; supervisor/user follow-up commits `d2b93d4`, `1c918d5`, `401a82e`, `3bfc234`, and `b3ff548` | Satisfied by `test/webSocketSupport.test.ts` plus shared command, CodeLens, Copilot, editor, validation, round-trip, and demo regressions: persistent WebSocket sessions now expose connect/disconnect lifecycle operations through one fixed-width stateful editor button plus a separate send-message flow; retain session state and message history; surface editor controls/history, bottom status bar management, command palette/tree/CodeLens actions, and `missio_websocket_session`; route live send-tool WebSocket execution to lifecycle diagnostics; disconnect on editor/session cleanup; prefer freshly posted WebSocket lifecycle requests over stale debounced YAML; extract send-message payloads from the same resolved lifecycle request; keep Send styled as the primary request action; hide the HTTP-style response placeholder/body pane so WebSocket history fills the response area; show millisecond-precision history timestamps; and add local connect-only, repeated-send, and server-push fixtures. | `npm run compile` passed; `npx vitest run test/webSocketSupport.test.ts test/protocolLayoutStability.test.ts` passed 2 files/35 tests; `node scripts/validate-collection.js examples/demo-api` passed 47/47 files; live local WebSocket lifecycle smoke returned `LIVE_WS_LIFECYCLE_SMOKE ok`; `npm test` passed 25 files/465 tests; `npm run build` passed. | 2026-06-15 14:32 NZT | OC-140 complete. WebSocket lifecycle sessions are file-path scoped for editor/command flows, persist for that request until disconnect/close/editor disposal, and are intentionally not shared across separate request files. Preserve unrelated PDF.js media churn IDs `qp`/`ko`. |
 | OC-150 | Runtime assertion variables and WebSocket runtime results UX | Done | Codex | feature/oc-150-runtime-assertion-variables, stacked on supervisor/add-runtime-assertion-variable-task; implementation commit `55dd694`; completion ledger commit `940a696`; acceptance rework commit `a2e63b4`; WebSocket runtime-tab follow-up commit `0cfc7f8`; lifecycle restyle follow-up commit `608eb19`; no-fill send follow-up commit `3e6cee0`; no-fill cancel follow-up commit `7f021ca` | Satisfied by `test/runtimeAuthoringUx.test.ts` for shared variable-aware assertion expression/value/description inputs and dynamic row overlays; `test/runtimeExecutionService.test.ts` for assertion expression/value/description interpolation, after-response script-produced assertion variables avoiding preflight prompts, deterministic unresolved assertion diagnostics, disabled assertions, and HTTP/GraphQL/WebSocket/gRPC runtime parity; `test/unresolvedVars.test.ts` for preserving request/auth preflight while deferring runtime assertion placeholders to runtime diagnostics; `test/webSocketSupport.test.ts` for WebSocket messages/history inside the existing response tab container plus visible runtime assertion/test/action results, theme-coloured no-fill lifecycle controls, blue no-fill Send controls, and red no-fill Cancel controls; `test/protocolLayoutStability.test.ts` for no HTTP response placeholder flash, no duplicate WebSocket response panel, Runtime tab visibility before WebSocket runtime results exist, and non-WebSocket response layout reset after WebSocket. | Rework verification passed: `npm run compile`; `npx vitest run test/runtimeAuthoringUx.test.ts test/runtimeExecutionService.test.ts test/unresolvedVars.test.ts test/webSocketSupport.test.ts test/protocolLayoutStability.test.ts test/responseProvider.test.ts test/sendRequestTool.test.ts` passed 7 files/91 tests; `node scripts/validate-collection.js examples/demo-api` passed 47/47 files; `npm test` passed 25 files/476 tests; `npm run build` passed. Follow-up verification passed: `npx vitest run test/protocolLayoutStability.test.ts test/webSocketSupport.test.ts` passed 2 files/40 tests; `npm run compile` passed; OC-150 matrix passed 7 files/92 tests; `node scripts/validate-collection.js examples/demo-api` passed 47/47 files; `npm run build` passed. Lifecycle restyle verification passed: `npx vitest run test/webSocketSupport.test.ts` passed 26 tests; `npm run compile` passed; `npx vitest run test/protocolLayoutStability.test.ts test/webSocketSupport.test.ts` passed 2 files/40 tests; `npm run build` passed. Send follow-up verification passed: `npx vitest run test/webSocketSupport.test.ts test/protocolLayoutStability.test.ts` passed 2 files/40 tests; `npm run compile` passed; `npm run build` passed. Cancel follow-up verification passed: `npx vitest run test/webSocketSupport.test.ts test/protocolLayoutStability.test.ts` passed 2 files/40 tests; `npm run compile` passed; `npm run build` passed. Supervisor install pass also packaged `C:\Users\chris\AppData\Local\Temp\missio-0.8.0-oc150-rework.vsix` and installed `missio.missio@0.8.0`. | 2026-06-15 16:43 NZT | OC-150 accepted after WebSocket runtime-tab, lifecycle style, send-button style, and cancel-button style follow-ups; no remaining OC-150 action. |
+| OC-160 | gRPC demo server reliability | Unclaimed | - | suggested branch `feature/oc-160-grpc-demo-server-reliability` | Reproduce or explain the failing gRPC demo requests; verify the local gRPC fixture binds the documented `localhost:50051`/`127.0.0.1:50051` endpoint; align `examples/demo-api/opencollection.yml`, gRPC request files, proto paths, and request descriptions; add automated fixture-start smoke coverage for representative or complete gRPC demo requests, including unary, streaming, runtime, and deterministic error demos; cover missing-fixture diagnostics and run shared gRPC/runtime/send-tool/response-provider/schema/validation regressions. | Not started. | 2026-06-15 16:54 NZT | Claim OC-160, reproduce the user-facing failure, then make the gRPC demo startup and smoke-test path reliable before packaging/installing for user verification. |
 
 ## Dependency Map
 
@@ -94,6 +95,7 @@ Use full branch names for stacking existing branches with `but move <child-branc
 | OC-130 | OC-100 protocol identity, request editor webview startup path, all protocol editor layouts; coordinate with OC-120 if shared CSS changes | Protocol-native editor first paint and layout stability |
 | OC-140 | OC-020 WebSocket client/executor, OC-070 CodeLens/Copilot patterns, OC-080 WebSocket runtime lifecycle, OC-100 WebSocket editor identity, OC-130 request editor startup/layout if shared UI changes overlap | First-class WebSocket session lifecycle management |
 | OC-150 | OC-040 runtime engine, OC-080 protocol runtime lifecycle, OC-110 runtime authoring UX, OC-130 layout stability, OC-140 WebSocket lifecycle UX | Runtime assertion variable parity, WebSocket runtime result discoverability, and WebSocket lifecycle button contrast |
+| OC-160 | OC-030 gRPC unary/protobuf support, OC-080 gRPC runtime lifecycle, OC-090 gRPC streaming, local demo fixture conventions | Reliable user-facing gRPC demo startup and live verification |
 
 ## Shared Decisions
 
@@ -109,6 +111,13 @@ Record cross-cutting decisions here so parallel agents do not rediscover them.
 
 ### Supervisor Reports
 
+- 2026-06-15 16:54 NZT - Codex Supervisor: Added OC-160 as a focused follow-up for gRPC demo server reliability after user reported all gRPC demo requests failing, likely because no local fixture is listening on `localhost:50051`.
+  GitButler: planning branch `supervisor/add-grpc-demo-server-reliability-task`; `but status -fv` was clean before the docs update.
+  Coverage: OC-160 requires reproducing the failure, aligning demo start commands/endpoints/proto paths, adding fixture-start smoke tests for gRPC demo requests, covering missing-fixture diagnostics, running demo collection validation, shared gRPC/runtime/tool/response/schema regressions, build, package, and local install.
+  Changed: `docs/open-collection-gap-analysis/tasks/16-grpc-demo-server-reliability.md`, `docs/open-collection-gap-analysis/AGENT_GOAL_PROMPTS.md`, `docs/open-collection-gap-analysis/README.md`, and this ledger.
+  Verified: docs-only planning change; `rg "OC-160|gRPC Demo Server Reliability|grpc-demo-server-reliability" docs/open-collection-gap-analysis` should confirm the task, prompt, task board, dependency map, and log references before commit.
+  Next: launch OC-160 with the new goal prompt after current OC-150/user-theme work is settled, or run it immediately if the gRPC demo failures are blocking user verification.
+
 - 2026-06-15 10:03 NZT - Codex Supervisor: Completed final integration review for OC-000 through OC-110, accepted OC-070, aligned stale documentation, built, packaged, installed, and live-smoked the reviewed stack.
   GitButler: `but status -fv` showed all implementation branches applied and linked; the verified branches include `feature/oc-000-foundation-dispatch`, `feature/oc-010-graphql-support`, `feature/oc-020-websocket-support`, `feature/oc-030-grpc-unary-protobuf`, `feature/oc-040-runtime-scripting-testing`, `feature/oc-050-auth-transport`, `feature/oc-060-schema-roundtrip-validation`, `feature/oc-070-surface-polish`, `supervisor/add-runtime-authoring-ux-task` for OC-080, `feature/oc-090-grpc-streaming`, `feature/oc-100-request-type-ux`, and `feature/oc-110-runtime-authoring-ux`. Before this final ledger/docs commit, the only unassigned changes were supervisor-owned docs IDs `rl`, `tk`, and this ledger update.
   Findings: no blocking implementation findings remain. OC-070 is accepted from commit `f9a5a55`; the README and gap-analysis wiki no longer describe completed scripting/runtime/type/surface work as missing.
diff --git a/docs/open-collection-gap-analysis/README.md b/docs/open-collection-gap-analysis/README.md
index d2ea2d9..94d66b0 100644
--- a/docs/open-collection-gap-analysis/README.md
+++ b/docs/open-collection-gap-analysis/README.md
@@ -72,6 +72,7 @@ If a scenario truly cannot be automated in this repo, document the reason, manua
 | OC-130 | Protocol Layout Stability | [13-protocol-layout-stability.md](tasks/13-protocol-layout-stability.md) | Protocol-native first paint and layout stability when opening non-HTTP requests. |
 | OC-140 | WebSocket Lifecycle UX | [14-websocket-lifecycle-ux.md](tasks/14-websocket-lifecycle-ux.md) | First-class connect, disconnect, send, status bar, CodeLens, and Copilot lifecycle management for WebSocket sessions. |
 | OC-150 | Runtime Assertion Variables And WebSocket Results UX | [15-runtime-assertion-variables.md](tasks/15-runtime-assertion-variables.md) | Variable-aware assertion fields, assertion interpolation, WebSocket runtime result visibility, and lifecycle button contrast. |
+| OC-160 | gRPC Demo Server Reliability | [16-grpc-demo-server-reliability.md](tasks/16-grpc-demo-server-reliability.md) | User-verifiable gRPC demo startup, localhost fixture reliability, and live smoke coverage. |
 
 ## Project Skills
 
@@ -88,7 +89,7 @@ Project-local skills live in [.agents/skills/](../../.agents/skills/). They are
 
 ## Final Compatibility Evidence
 
-OC-000 through OC-140 are implemented and tracked in [AGENT_PROGRESS.md](AGENT_PROGRESS.md). OC-150 is a focused follow-up for runtime assertion variable parity, WebSocket runtime result visibility, and WebSocket lifecycle button contrast. The table below records the main evidence surfaces that remain useful for maintenance and future audits.
+OC-000 through OC-150 are implemented and tracked in [AGENT_PROGRESS.md](AGENT_PROGRESS.md). OC-160 is a focused follow-up for gRPC demo server startup and live user-verification reliability. The table below records the main evidence surfaces that remain useful for maintenance and future audits.
 
 | Evidence Surface | Location |
 | --- | --- |
@@ -97,6 +98,7 @@ OC-000 through OC-140 are implemented and tracked in [AGENT_PROGRESS.md](AGENT_P
 | Runtime scripting, tests, assertions, actions, and visual authoring. | [src/services/runtimeExecutionService.ts](../../src/services/runtimeExecutionService.ts), [src/webview/requestPanel.ts](../../src/webview/requestPanel.ts) |
 | Protocol execution for GraphQL, WebSocket, and gRPC unary/streaming requests. | [src/services/graphqlSupport.ts](../../src/services/graphqlSupport.ts), [src/services/webSocketClient.ts](../../src/services/webSocketClient.ts), [src/services/grpcClient.ts](../../src/services/grpcClient.ts) |
 | Local fixture API, demo requests, and collection validation. | [examples/demo-api](../../examples/demo-api), [scripts/validate-collection.js](../../scripts/validate-collection.js) |
+| gRPC demo startup and fixture smoke coverage. | [examples/demo-api/grpc-server.js](../../examples/demo-api/grpc-server.js), [examples/demo-api/gRPC](../../examples/demo-api/gRPC) |
 
 ## Definition Of Done For Any Track
 
diff --git a/docs/open-collection-gap-analysis/tasks/16-grpc-demo-server-reliability.md b/docs/open-collection-gap-analysis/tasks/16-grpc-demo-server-reliability.md
new file mode 100644
index 0000000..756173d
--- /dev/null
+++ b/docs/open-collection-gap-analysis/tasks/16-grpc-demo-server-reliability.md
@@ -0,0 +1,120 @@
+# OC-160 gRPC Demo Server Reliability
+
+## Goal
+
+Make every gRPC demo request under `examples/demo-api/gRPC/` work reliably for a user after following the documented local demo start flow. The current user-facing symptom is that gRPC demo requests fail because nothing appears to be serving `localhost:50051`.
+
+This is a demo-fixture and verification task, not a new gRPC protocol feature task. It should preserve the OC-030 unary and OC-090 streaming implementation behavior while making the local example collection trustworthy.
+
+## Current Gap
+
+| Surface | Gap |
+| --- | --- |
+| Demo server lifecycle | `examples/demo-api/server.js` does not make it obvious whether the gRPC fixture is also running, and a user can start the HTTP/WebSocket demo server while `localhost:50051` remains closed. |
+| Demo request endpoints | gRPC request files rely on `{{grpcBaseUrl}}`/`localhost:50051`; those values must match the actual local fixture server. |
+| User guidance | gRPC request descriptions and docs need a clear command sequence for starting every required demo process. |
+| Smoke coverage | Existing automated coverage proves gRPC client behavior, but user-facing demo request startup can regress if the fixture server is not started, not bound to the expected port, or drifts from the proto/request files. |
+| Packaging confidence | Packaged extension verification should include a live gRPC demo smoke so missing fixture startup does not escape review. |
+
+## Implementation Plan
+
+1. Reproduce and document the failure:
+
+| Check | Expected Evidence |
+| --- | --- |
+| Run the documented demo start command. | Record whether it starts only HTTP/WebSocket or also gRPC. |
+| Send each gRPC demo request. | Record current failures, including connection errors for `localhost:50051` and any proto/method mismatch. |
+| Inspect environment variables. | Confirm `examples/demo-api/opencollection.yml` defines `LOCAL.grpcBaseUrl` and related proto paths consistently. |
+
+2. Normalize the local gRPC fixture server:
+
+| Area | Required Work |
+| --- | --- |
+| Server command | Provide a simple deterministic command, such as `node examples/demo-api/grpc-server.js`, that binds `127.0.0.1:50051` or the documented configured port. |
+| Optional aggregate command | If useful, add a repo script or small helper that starts all demo processes needed for HTTP, WebSocket, GraphQL, runtime, and gRPC verification without hiding failures. |
+| Startup diagnostics | Print the bound host/port and available gRPC methods so users can tell the fixture is ready. |
+| Shutdown cleanup | Ensure tests and smoke scripts can start and stop the fixture without leaving a locked port. |
+| Local-only safety | Keep the fixture bound to loopback and independent of internet access. |
+
+3. Align demo requests and collection config:
+
+| Area | Required Work |
+| --- | --- |
+| `opencollection.yml` | Ensure `LOCAL.grpcBaseUrl`, proto file paths, and import paths resolve from a normal checkout. |
+| Request files | Ensure every unary, server-streaming, client-streaming, bidirectional-streaming, metadata, runtime, and error demo points at the local fixture and a real proto method. |
+| Request descriptions | Each gRPC request should tell the user which gRPC fixture command must be running. |
+| Folder guidance | `examples/demo-api/gRPC/folder.yml` should summarize the gRPC demo start requirement. |
+| Validation | Demo request YAML must remain schema-valid and preserve OpenCollection gRPC fields on round trip. |
+
+4. Add automated and live verification:
+
+| Test Surface | Required Work |
+| --- | --- |
+| Fixture integration | Add or extend tests that start the demo gRPC server process, wait for readiness, and execute representative demo requests through the Missio gRPC execution path. |
+| Demo inventory | Cover every committed gRPC demo request or group them by method type with explicit documented exceptions. |
+| Failure diagnostics | Add coverage for the user-facing error when the fixture server is not running, so the message points to the start command instead of a bare connection failure when practical. |
+| Collection validation | Run `node scripts/validate-collection.js examples/demo-api`. |
+| Regression safety | Run existing gRPC, runtime, send-tool, response-provider, schema round-trip, and validation tests touched by the fixture changes. |
+
+5. Update packaging/user verification flow:
+
+| Area | Required Work |
+| --- | --- |
+| README or demo docs | Add concise local demo startup instructions if the current docs do not tell users how to start gRPC. |
+| Build/install | Package and install the extension after the fix so the user can retry the demo requests from VS Code. |
+| Ledger | Record the exact gRPC demo start command, smoke command, request coverage, build/package/install evidence, and any remaining caveats in `AGENT_PROGRESS.md`. |
+
+## Acceptance Criteria
+
+| Requirement | Acceptance |
+| --- | --- |
+| Reproduction | The original failure mode is reproduced or otherwise explained with concrete evidence. |
+| Listening fixture | A documented command starts a local gRPC fixture on the same host/port used by the demo collection, expected to be `127.0.0.1:50051` or `localhost:50051`. |
+| Demo request parity | Every `examples/demo-api/gRPC/*.yml` request either sends successfully against the local fixture or is intentionally a documented failure diagnostic request. |
+| Streaming coverage | Unary, server-streaming, client-streaming, bidirectional-streaming, and deterministic error-stream demos are covered if present in the demo folder. |
+| Runtime coverage | gRPC runtime demo requests, including scripts/assertions/actions where present, execute against the fixture and expose results. |
+| Clear user guidance | Folder/request descriptions and docs tell users exactly which command or script to run before sending gRPC requests. |
+| Automated proof | Tests start/stop the fixture and exercise representative or complete gRPC demo requests without depending on an already-running server. |
+| Packaging proof | `npm run build`, local package/install, demo collection validation, and live gRPC smoke evidence are recorded. |
+
+## Suggested Tests
+
+| Test | Expected Result |
+| --- | --- |
+| Demo server readiness | Starting the fixture process produces a readiness signal and accepts a simple unary call on the documented port. |
+| Demo unary request smoke | `echo-unary.yml` executes through `RequestExecutionService` and returns deterministic response data. |
+| Metadata/defaults smoke | `echo-metadata-defaults.yml` proves metadata/defaults still reach the fixture. |
+| Streaming request smoke | Server, client, and bidirectional streaming demo requests return the expected event summaries. |
+| Runtime lifecycle smoke | `runtime-unary-lifecycle.yml` resolves variables, runs runtime assertions/actions, and surfaces results. |
+| Fixture missing diagnostic | Sending a demo request without the fixture running returns a useful diagnostic that names the gRPC demo start command where feasible. |
+| Demo collection validation | `node scripts/validate-collection.js examples/demo-api` passes with all gRPC demo files included. |
+
+Recommended verification commands:
+
+```powershell
+npm run compile
+npx vitest run test/grpcSupport.test.ts test/runtimeExecutionService.test.ts test/responseProvider.test.ts test/sendRequestTool.test.ts test/schemaRoundTrip.test.ts test/validationService.test.ts
+node scripts/validate-collection.js examples/demo-api
+npm test
+npm run build
+npm run install:local
+```
+
+The implementation agent should add any new focused fixture-smoke test command to this list once it exists.
+
+## Dependencies
+
+| Dependency | Reason |
+| --- | --- |
+| OC-030 | Provides proto loading, unary execution, metadata defaults, and the original local gRPC fixture. |
+| OC-080 | Provides gRPC runtime lifecycle behavior used by runtime demo requests. |
+| OC-090 | Provides gRPC streaming execution and streaming demo fixture expectations. |
+| OC-110/OC-150 | Runtime authoring and assertion behavior may be visible in gRPC runtime demo requests. |
+
+## Out Of Scope
+
+| Area | Reason |
+| --- | --- |
+| New gRPC protocol features | OC-030 and OC-090 own protocol execution capabilities. This task fixes demo reliability and verification. |
+| External gRPC services | Demo requests must remain local-only and deterministic. |
+| Changing OpenCollection schema | Use existing schema fields unless a concrete validation bug is found and separately justified. |