From af93b2a91cc7ce8cd660e3aaa7c9974887c2a232 Mon Sep 17 00:00:00 2001 From: tegwick Date: Tue, 7 Jul 2026 17:04:55 +0200 Subject: [PATCH] REUSE-WP-0018-T05: ecosystem rollout convention drafted and proposed Gate cleared: WP-0017 finished 2026-07-07, federated.yaml now carries 61 real capabilities (was 24). Dogfooded immediately -- plan-check against 'unified interface for issue tracking across Gitea GitHub GitLab' now correctly returns extend/capability.infotech.issue-tracking instead of new. Drafted the query-before-build convention in .claude/rules/workplan-convention.md (gitignored, local -- propagation happens via the custodian rules-template mechanism, not a reuse-surface git commit). Sent State Hub message to custodian-agent proposing it be added to the shared template (13cecd08-14e8-46d9-880c-65b8fef857cb). Added reuse_check frontmatter to REUSE-WP-0018 and REUSE-WP-0019 themselves as the reference implementation, both dogfooded for real against the live federated index (both correctly verdict 'new'). REUSE-WP-0018 is now done except T03 (LLM semantic rerank), deferred pending a running llm-connect instance. Updated IntentScopeGapAnalysis.md priority 29 accordingly. Co-Authored-By: Claude Sonnet 5 --- docs/IntentScopeGapAnalysis.md | 5 +- ...USE-WP-0018-plan-check-consumption-loop.md | 46 +++++++++++-------- ...P-0019-forgejo-automation-and-telemetry.md | 3 +- 3 files changed, 33 insertions(+), 21 deletions(-) diff --git a/docs/IntentScopeGapAnalysis.md b/docs/IntentScopeGapAnalysis.md index 9c6baf9..ce63ef0 100644 --- a/docs/IntentScopeGapAnalysis.md +++ b/docs/IntentScopeGapAnalysis.md @@ -202,7 +202,7 @@ See §4 and archived workplans `workplans/archived/`. | 26 | Federated ID deduplication | Per-owner removal from reuse-surface index | **Closed** (WP-0015-T02) | | 27 | Planning analytics + standardization | Gap report or standardization tracker | **Partial** — gap report shipped (T03); tracker deferred | | 28 | Registry maintenance automation | Interactive `maintain` + `--auto` with llm-connect | **Closed** (WP-0016) | -| 29 | Consumption loop (query-before-build) | `plan-check` command + State Hub capability-request bridge | **Partial** — deterministic matching (T02) and the request bridge (T04) shipped; LLM semantic rerank (T03) and ecosystem session-protocol rollout (T05) remain open, T05 gated on REUSE-WP-0017 coverage reaching the *published* federated index, not just local drafts | +| 29 | Consumption loop (query-before-build) | `plan-check` command + State Hub capability-request bridge | **Partial** — deterministic matching (T02), the request bridge (T04), docs/CI (T06), and the ecosystem session-protocol convention (T05, propagation proposed to custodian-agent 2026-07-07) shipped; only LLM semantic rerank (T03) remains open, deferred pending a running `llm-connect` instance | **Workplan:** `workplans/REUSE-WP-0016-interactive-registry-maintain.md` (priority 28); `workplans/REUSE-WP-0015-federation-polish-and-planning-analytics.md` (25–27); @@ -238,4 +238,5 @@ See §4 and archived workplans `workplans/archived/`. | 2026-06-16 | **SCOPE refresh + full INTENT success-criteria mapping**; priorities 25–27 proposed | | 2026-06-16 | Assessment persisted; **REUSE-WP-0015** created for priorities 25–27 | | 2026-06-16 | **REUSE-WP-0016** closed priority 28 (interactive `maintain`, `--auto`, templates) | -| 2026-07-07 | **REUSE-WP-0018** partially closed priority 29 (`plan-check` deterministic matching + State Hub capability-request bridge; LLM rerank and ecosystem rollout remain open) | \ No newline at end of file +| 2026-07-07 | **REUSE-WP-0018** partially closed priority 29 (`plan-check` deterministic matching + State Hub capability-request bridge; LLM rerank and ecosystem rollout remain open) | +| 2026-07-07 | **REUSE-WP-0018-T05** closed following REUSE-WP-0017 completion (61 published capabilities); only T03 (LLM rerank) remains open under priority 29 | \ No newline at end of file diff --git a/workplans/REUSE-WP-0018-plan-check-consumption-loop.md b/workplans/REUSE-WP-0018-plan-check-consumption-loop.md index df6c52e..32cedfd 100644 --- a/workplans/REUSE-WP-0018-plan-check-consumption-loop.md +++ b/workplans/REUSE-WP-0018-plan-check-consumption-loop.md @@ -8,8 +8,9 @@ status: active owner: claude-code topic_slug: helix-forge created: "2026-07-06" -updated: "2026-07-06" +updated: "2026-07-07" state_hub_workstream_id: "cd8683ff-6e6c-4f6c-a62f-565bd55113ea" +reuse_check: "new — dogfooded 2026-07-07 via reuse-surface plan-check against the full 61-capability federated index; no existing capability covers query-before-build matching" --- # plan-check: close the consumption loop for capability reuse @@ -172,26 +173,31 @@ State Hub HTTP API (`http://127.0.0.1:8000`, confirmed reachable): ```task id: REUSE-WP-0018-T05 -status: wait +status: done priority: high state_hub_task_id: "c232a669-b263-4978-a8b1-3721b8bfaa68" ``` -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. +Gate cleared 2026-07-07: WP-0017 finished, `federated.yaml` composed with +61 real capabilities (up from the original 24). Dogfooded immediately — +`plan-check` against "unified interface for issue tracking across Gitea +GitHub GitLab" now correctly returns `extend` pointing at +`capability.infotech.issue-tracking`, where before WP-0017 published it +would have returned `new`. That's the whole point of sequencing T05 after +WP-0017 landed. -- Draft the one-line convention for the shared session-protocol/workplan - rules: *"Before creating a workplan, run `reuse-surface plan-check` on the - draft and record the verdict in the workplan frontmatter - (`reuse_check: reuse|extend|new — `)"* -- Coordinate propagation with the-custodian rules template mechanism - (fix-consistency / repo-seed) — send State Hub message to custodian agent -- Add `reuse_check` frontmatter to this repo's workplan convention as the - reference implementation +- [x] Drafted the convention in `.claude/rules/workplan-convention.md` + ("Query before building" section): run `plan-check`, record + `reuse_check: reuse|extend|new — ` in frontmatter, + advisory only +- [x] Sent State Hub message to `custodian-agent` proposing propagation + via the fix-consistency/repo-seed shared rules template (message + `13cecd08-14e8-46d9-880c-65b8fef857cb`) — propagation itself depends on + the-custodian's own template mechanism, not something reuse-surface + can push directly into sibling repos +- [x] Added `reuse_check` frontmatter to this repo's own REUSE-WP-0018 and + REUSE-WP-0019 as the reference implementation, both dogfooded for real + (both correctly verdict `new`) ## Docs, CI, SCOPE @@ -218,8 +224,12 @@ state_hub_task_id: "ff0a91eb-cc41-487b-b726-8c2f84860399" - [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 +- [x] Session-protocol convention drafted; propagation *proposed* to custodian-agent + 2026-07-07 (message `13cecd08-14e8-46d9-880c-65b8fef857cb`) — actual + adoption into the shared rules template is the-custodian's call, not + something reuse-surface can complete unilaterally +- [x] reuse-surface itself records `reuse_check` in its own workplans + (REUSE-WP-0018, REUSE-WP-0019) as the reference implementation ## Out of scope diff --git a/workplans/REUSE-WP-0019-forgejo-automation-and-telemetry.md b/workplans/REUSE-WP-0019-forgejo-automation-and-telemetry.md index e1fa28d..cc53162 100644 --- a/workplans/REUSE-WP-0019-forgejo-automation-and-telemetry.md +++ b/workplans/REUSE-WP-0019-forgejo-automation-and-telemetry.md @@ -8,8 +8,9 @@ status: active owner: claude-code topic_slug: helix-forge created: "2026-07-06" -updated: "2026-07-06" +updated: "2026-07-07" state_hub_workstream_id: "569be717-34f8-4039-bb26-497685f60159" +reuse_check: "new — dogfooded 2026-07-07 via reuse-surface plan-check against the full 61-capability federated index; no existing capability covers Forgejo webhook automation or reuse telemetry" --- # Forgejo-native federation automation and reuse telemetry