REUSE-WP-0018 T01/T02/T04/T06: plan-check deterministic matching + State Hub bridge

T01: specs/PlanCheck.md design doc, plan-check-result.schema.json and
reuse-event.schema.json (the latter shared with WP-0019's reuse telemetry).

T02: reuse_surface/plan_check.py + 'reuse-surface plan-check' CLI command.
Deterministic token-Jaccard matching against registry/indexes/federated.yaml
(reuses overlaps.py's TOKEN_RE rather than a second scoring method), with
reuse/extend/new verdicts, markdown and --format json output, staleness
warning, and --record-outcome JSONL telemetry.

T04: reuse_surface/statehub_bridge.py bridges plan-check 'new' verdicts to
State Hub capability requests (--file-request) and surfaces open requests
with no matching capability (report gaps --check-capability-requests, opt-in
to stay offline-safe). Verified against the live local State Hub API;
status field (not catalog_entry_id presence) is the correct open/closed
signal, and the list endpoint needs a longer timeout than the health check
(~7s observed with 5 rows).

T06: docs (tools/README.md, RegistryFederation.md, SCOPE.md,
IntentScopeGapAnalysis.md priority 29) and an informational CI smoke step.

T03 (LLM rerank) not started -- llm-connect isn't running on this
workstation. T05 (ecosystem rollout) remains blocked: WP-0017 has drafted
entries for all 61 repos but they're still local-only pending its own T05
push/publish pass, so the federated index isn't yet worth rolling out
plan-check as ecosystem convention.

16 new tests, all mocked -- no network calls in the default test run.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

workplans/REUSE-WP-0018-plan-check-consumption-loop.md

@@ -82,7 +82,7 @@ maturity vector, owning repo, and consumer guidance.
 
 ```task
 id: REUSE-WP-0018-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "c7b3407a-2b9d-46ba-ae9c-7ab12235f0ba"
 ```
@@ -102,17 +102,24 @@ Design doc `specs/PlanCheck.md`:
 
 ```task
 id: REUSE-WP-0018-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "24911d0e-41bc-4c8c-a39a-7dc8ec65d8c6"
 ```
 
-- `reuse_surface/plan_check.py` + CLI command per T01 spec, no-LLM path
-- Reads `registry/indexes/federated.yaml` (fall back to local index; warn on
-  stale `updated`)
-- Markdown report for TTY; `--format json` for agents
-- Pytest: fixture index with known reuse/extend/new cases; workplan-file and
-  intent-text inputs
+Implemented in `reuse_surface/plan_check.py` + `plan-check` CLI command:
+
+- Reuses `overlaps.py`'s `TOKEN_RE`/Jaccard approach rather than a second
+  scoring method (per spec §4)
+- Reads `registry/indexes/federated.yaml`, falls back to the local index,
+  warns when the composed index is >14 days stale
+- Markdown (TTY default) and `--format json` (validated against
+  `schemas/plan-check-result.schema.json`)
+- 11 pytest cases: verdict thresholds, workplan-file parsing, intent-text
+  parsing, tie-window vector ranking, staleness warning, CLI wiring
+- `--record-outcome` appends to `registry/telemetry/plan-check-events.jsonl`
+  per the shared `schemas/reuse-event.schema.json` (WP-0019-T04 will post the
+  same shape to the hub)
 
 ## Add llm-connect Semantic Rerank
 
@@ -123,6 +130,11 @@ priority: medium
 state_hub_task_id: "9040505a-238e-4815-ae1a-8c5f8c12afa9"
 ```
 
+**Not started** — `llm-connect` is not running on this workstation
+(same gap noted in REUSE-WP-0017-T04's drafting cohorts). Deterministic
+`plan-check` (T02) is fully usable without it; this task adds the optional
+rerank on top when a backend is available.
+
 - Optional rerank/expansion stage via `LLM_CONNECT_URL` (reuse
   `llm_bridge.py`); schema-constrained JSON, graceful skip when unset
 - Confidence surfaced per match; deterministic matches always listed first
@@ -132,20 +144,29 @@ state_hub_task_id: "9040505a-238e-4815-ae1a-8c5f8c12afa9"
 
 ```task
 id: REUSE-WP-0018-T04
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "8249dca7-18ca-4150-9671-ca87e6a5ad88"
 ```
 
-Two directions:
+Implemented in `reuse_surface/statehub_bridge.py` against the live local
+State Hub HTTP API (`http://127.0.0.1:8000`, confirmed reachable):
 
-- **new → request:** on a `new` verdict, offer (`--file-request` /
-  interactive prompt) to create a State Hub capability request with the
-  intent text and searched terms
-- **request → gap:** `report gaps` gains a section listing open State Hub
-  capability requests with no matching federated capability (HTTP against
-  `http://127.0.0.1:8000`, degrade gracefully offline)
-- Matched requests can be marked resolved with a pointer to the capability id
+- **new → request:** `plan-check --file-request` files a State Hub
+  capability request (`POST /capability-requests/`) on a `new` verdict
+- **request → gap:** `report gaps --check-capability-requests` lists open
+  requests (`GET /capability-requests/`, filtered on `status` — a request
+  can carry a `catalog_entry_id` while still `requested`/routed, so status
+  is the correct open/closed signal, not `catalog_entry_id` presence).
+  Opt-in flag so `report gaps` stays fast and offline-safe by default
+- Both degrade to `None`/graceful-skip when the hub is unreachable; neither
+  ever blocks the primary command
+- List endpoint observed taking ~7s in production with only 5 rows; uses a
+  20s timeout distinct from the 5s health-check timeout
+- 5 pytest cases with the hub client fully mocked (never hits the network
+  in the default test run)
+- **Not done:** marking matched requests resolved with a pointer to the
+  capability id — deferred, no current caller needs it yet
 
 ## Ecosystem Rollout: Session-Protocol Integration
 
@@ -156,7 +177,12 @@ priority: high
 state_hub_task_id: "c232a669-b263-4978-a8b1-3721b8bfaa68"
 ```
 
-Blocked on WP-0017 coverage (index must be worth querying). 
+Blocked on WP-0017 coverage reaching the *published* federated index, not
+just local drafts. WP-0017-T04 has drafted entries for all 61 roster repos
+(coverage 61/61 locally), but those commits are still local-only in each
+sibling repo pending WP-0017-T05's human review and push — `federated.yaml`
+still only carries the original 24 entries. Re-check this gate once
+WP-0017-T05 pushes and recomposes.
 
 - Draft the one-line convention for the shared session-protocol/workplan
   rules: *"Before creating a workplan, run `reuse-surface plan-check` on the
@@ -171,25 +197,29 @@ Blocked on WP-0017 coverage (index must be worth querying).
 
 ```task
 id: REUSE-WP-0018-T06
-status: todo
+status: done
 priority: low
 state_hub_task_id: "ff0a91eb-cc41-487b-b726-8c2f84860399"
 ```
 
-- `tools/README.md` command reference; `docs/RegistryFederation.md` consumer
-  section; `SCOPE.md` "What Is Possible Now"
+- `tools/README.md` command reference for `plan-check` and
+  `report gaps --check-capability-requests`; `docs/RegistryFederation.md`
+  "Query before building" consumer section; `SCOPE.md` "What Is Possible Now"
 - CI: informational `plan-check --intent "smoke test" --format json` run
-- Gap-analysis note: consumption loop status flips from missing to shipped
+  added to `.gitea/workflows/ci.yml`
+- `docs/IntentScopeGapAnalysis.md`: priority 29 added, marked **Partial**
+  (T02/T04 shipped; T03/T05 remain open — not flipped fully to "shipped"
+  since the ecosystem rollout hasn't happened yet)
 
 ---
 
 ## Acceptance
 
-- [ ] `plan-check` returns reuse/extend/new verdicts for workplan files and intent text, with and without llm-connect
-- [ ] JSON output validates against the published schema
-- [ ] `new` verdicts can file State Hub capability requests; `report gaps` lists unmatched open requests
-- [ ] Session-protocol convention drafted and propagation agreed with the-custodian
-- [ ] reuse-surface itself records `reuse_check` in new workplans (dogfood)
+- [x] `plan-check` returns reuse/extend/new verdicts for workplan files and intent text (without llm-connect — T03 rerank not built, not available on this workstation)
+- [x] JSON output validates against the published schema
+- [x] `new` verdicts can file State Hub capability requests; `report gaps` lists unmatched open requests
+- [ ] Session-protocol convention drafted and propagation agreed with the-custodian (blocked, see T05)
+- [ ] reuse-surface itself records `reuse_check` in new workplans (dogfood) — deferred to T05 rollout
 
 ## Out of scope