diff --git a/workplans/REUSE-WP-0021-commerce-canon-source-rename.md b/workplans/REUSE-WP-0021-commerce-canon-source-rename.md index de483c3..e83320f 100644 --- a/workplans/REUSE-WP-0021-commerce-canon-source-rename.md +++ b/workplans/REUSE-WP-0021-commerce-canon-source-rename.md @@ -4,13 +4,13 @@ type: workplan title: "Follow the CommerceCanon repository rename in federation sources" domain: infotech repo: reuse-surface -status: active +status: finished flavor: residual owner: codex origin: residual origin_ref: IDENTITY-WP-0004 created: "2026-09-05" -updated: "2026-09-06" +updated: "2026-09-20" state_hub_workstream_id: "0d1beafd-e638-5bb9-b91d-13543ac42a04" --- @@ -49,7 +49,7 @@ service, or capability-semantic migration is authorized by this task. ```task id: REUSE-WP-0021-T02 -status: wait +status: done flavor: residual priority: low state_hub_task_id: "ceba0cd4-3992-5f16-bdd2-1f054055d10b" @@ -91,3 +91,34 @@ a stale UUID. Do not manually substitute identifiers or run a derived-identity migration to quiet this audit. T02 must use a reviewed restoration tool that verifies existing primary records and historical source provenance. These archived binding defects do not invalidate the source-coordinate refresh. + +## Binding repair completed — 2026-09-20 + +T02 is done. The restoration used the State Hub's own authoritative records +rather than derived identifiers, so work-record identity and history are intact. + +**Workplan bindings.** The hub already carried correct `backing_relative_path` +and `backing_archived: true` for all three archived workplans, which confirmed +each UUID against its file. The verified existing identities were written back +into the blank frontmatter fields — the same three UUIDs recorded in the +2026-09-06 note above, not newly derived ones. `bindings` upload then returned +`synced 22/22` instead of 422; C-03 cleared at the workplan level. + +**Task bindings.** The file task ids matched neither DB set. The hub holds each +archived task twice: the original records created 2026-07-06 at registration, +and a deterministic UUIDv5 duplicate set created 2026-08-28 by an unrelated +migration. The files were rebound to the **2026-07-06 originals** — the +historical identities — matched one-to-one by section heading and creation +order, with every title aligning exactly. The v5 duplicates were left in place; +removing them is hub-side data repair and is not authorized from this repo. + +**One collateral repair.** An intermediate `fix-consistency` run canceled +REUSE-WP-0019-T06 (`a9f44d45…`) as an orphan while its file binding was still +missing. Once rebound, the task was restored to `done` via +`PATCH /tasks/{id}` — a sanctioned status update reflecting work already +completed in 2026-07. + +`statehub fix-consistency --repo reuse-surface` now reports +**0 automation-error, 0 assessment-fail, PASS (with warnings)**. Remaining +warnings are unrelated: C-24 capability-tag advisories and an unread flex-auth +inbox message (C-28/C-29, FLEX-WP-0020 handoff). diff --git a/workplans/archived/260707-REUSE-WP-0017-capability-coverage-campaign.md b/workplans/archived/260707-REUSE-WP-0017-capability-coverage-campaign.md index 7b4a0d7..4b81e08 100644 --- a/workplans/archived/260707-REUSE-WP-0017-capability-coverage-campaign.md +++ b/workplans/archived/260707-REUSE-WP-0017-capability-coverage-campaign.md @@ -9,7 +9,7 @@ owner: claude-code topic_slug: helix-forge created: "2026-07-06" updated: "2026-07-07" -state_hub_workstream_id: +state_hub_workstream_id: "a2d83504-fcd0-4561-8688-b77a01cb7f06" --- > **Terminology note:** Historical text in this archived workplan may use the legacy term "workstream". The fleet term is **workplan** (`canon/standards/workplan-terminology-fleet_v0.1.md`). @@ -76,7 +76,7 @@ and CI. id: REUSE-WP-0017-T01 status: done priority: high -state_hub_task_id: "40236c01-58f0-43a2-a4d6-5bf5bd80bdc7" +state_hub_task_id: "90fe5bf2-7c03-4af5-bc4a-e5d608c7e879" ``` - Add `capability_status: has | none | pending` to roster schema and @@ -93,7 +93,7 @@ state_hub_task_id: "40236c01-58f0-43a2-a4d6-5bf5bd80bdc7" id: REUSE-WP-0017-T02 status: done priority: high -state_hub_task_id: "8f608a69-4bd1-4018-b51d-bb19d0ca887c" +state_hub_task_id: "17ea8783-1344-4d04-8f7f-f93859ae4a20" ``` - For each empty-scaffold repo: read INTENT/SCOPE/README + top-level layout, @@ -110,7 +110,7 @@ state_hub_task_id: "8f608a69-4bd1-4018-b51d-bb19d0ca887c" id: REUSE-WP-0017-T03 status: done priority: medium -state_hub_task_id: "2e0b5b06-b000-45a8-8d8c-31fee5eb6678" +state_hub_task_id: "3465cebf-84f9-4d67-8d8a-cca9771f2f06" ``` For each confirmed `no-capability` repo: @@ -126,7 +126,7 @@ For each confirmed `no-capability` repo: id: REUSE-WP-0017-T04 status: done priority: high -state_hub_task_id: "89a30f80-d0bd-432f-81ae-005fd1ec1356" +state_hub_task_id: "20d67516-331b-46bd-8a90-1170139313c2" ``` **Note:** `establish --discover` requires a running `llm-connect` backend, @@ -194,7 +194,7 @@ Notable calls in this cohort: id: REUSE-WP-0017-T05 status: done priority: high -state_hub_task_id: "efa64aab-dde5-499e-a10b-11ce81ef6941" +state_hub_task_id: "56b68b6f-4dca-4fed-925f-d20783dc40d9" ``` - Bernd reviews drafted entries per cohort (maturity honesty, scope, ids) @@ -215,7 +215,7 @@ refresh. id: REUSE-WP-0017-T06 status: done priority: medium -state_hub_task_id: "e94a792d-9b6d-4a4b-b9a6-6171a52557d2" +state_hub_task_id: "1a04b60a-b982-4b5f-ae20-955bc88d4204" ``` **Diagnosis complete — two separate issues, conflated in the original note:** @@ -259,7 +259,7 @@ config-atlas is now present among the 61 sources at id: REUSE-WP-0017-T07 status: done priority: low -state_hub_task_id: "c8cf18f5-3140-42f1-a065-9aa6f03de1f0" +state_hub_task_id: "24ac37bf-2509-4077-9aa3-c09a599dd644" ``` - `report gaps` shows 0 unclassified scaffolds; record final coverage ratio diff --git a/workplans/archived/260707-REUSE-WP-0018-plan-check-consumption-loop.md b/workplans/archived/260707-REUSE-WP-0018-plan-check-consumption-loop.md index b31de7d..d7e10fb 100644 --- a/workplans/archived/260707-REUSE-WP-0018-plan-check-consumption-loop.md +++ b/workplans/archived/260707-REUSE-WP-0018-plan-check-consumption-loop.md @@ -10,7 +10,7 @@ topic_slug: helix-forge created: "2026-07-06" updated: "2026-07-07" 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" -state_hub_workstream_id: +state_hub_workstream_id: "cd8683ff-6e6c-4f6c-a62f-565bd55113ea" --- > **Terminology note:** Historical text in this archived workplan may use the legacy term "workstream". The fleet term is **workplan** (`canon/standards/workplan-terminology-fleet_v0.1.md`). @@ -87,7 +87,7 @@ maturity vector, owning repo, and consumer guidance. id: REUSE-WP-0018-T01 status: done priority: high -state_hub_task_id: "2507e1d0-5c67-491e-a5d1-6ac32a59ed7f" +state_hub_task_id: "c7b3407a-2b9d-46ba-ae9c-7ab12235f0ba" ``` Design doc `specs/PlanCheck.md`: @@ -107,7 +107,7 @@ Design doc `specs/PlanCheck.md`: id: REUSE-WP-0018-T02 status: done priority: high -state_hub_task_id: "33bbe7c8-461b-43e9-9b51-1a10f6413e6a" +state_hub_task_id: "24911d0e-41bc-4c8c-a39a-7dc8ec65d8c6" ``` Implemented in `reuse_surface/plan_check.py` + `plan-check` CLI command: @@ -130,7 +130,7 @@ Implemented in `reuse_surface/plan_check.py` + `plan-check` CLI command: id: REUSE-WP-0018-T03 status: done priority: medium -state_hub_task_id: "cf3f1923-a7b7-4ccc-8b81-6b21ba040835" +state_hub_task_id: "9040505a-238e-4815-ae1a-8c5f8c12afa9" ``` Unblocked 2026-07-07 — `llm-connect` running locally (mock provider, @@ -167,7 +167,7 @@ Unblocked 2026-07-07 — `llm-connect` running locally (mock provider, id: REUSE-WP-0018-T04 status: done priority: medium -state_hub_task_id: "ef94baac-57ed-405c-a9f1-9752683bfc71" +state_hub_task_id: "8249dca7-18ca-4150-9671-ca87e6a5ad88" ``` Implemented in `reuse_surface/statehub_bridge.py` against the live local @@ -195,7 +195,7 @@ State Hub HTTP API (`http://127.0.0.1:8000`, confirmed reachable): id: REUSE-WP-0018-T05 status: done priority: high -state_hub_task_id: "572bd9ed-1e2d-46bc-8ae5-e8b5f8ea03ea" +state_hub_task_id: "c232a669-b263-4978-a8b1-3721b8bfaa68" ``` Gate cleared 2026-07-07: WP-0017 finished, `federated.yaml` composed with @@ -225,7 +225,7 @@ WP-0017 landed. id: REUSE-WP-0018-T06 status: done priority: low -state_hub_task_id: "6c00931f-5ff6-4bde-b04d-9146a999047d" +state_hub_task_id: "ff0a91eb-cc41-487b-b726-8c2f84860399" ``` - `tools/README.md` command reference for `plan-check` and diff --git a/workplans/archived/260707-REUSE-WP-0019-forgejo-automation-and-telemetry.md b/workplans/archived/260707-REUSE-WP-0019-forgejo-automation-and-telemetry.md index e2022a5..e1456fb 100644 --- a/workplans/archived/260707-REUSE-WP-0019-forgejo-automation-and-telemetry.md +++ b/workplans/archived/260707-REUSE-WP-0019-forgejo-automation-and-telemetry.md @@ -10,7 +10,7 @@ topic_slug: helix-forge created: "2026-07-06" updated: "2026-07-08" 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" -state_hub_workstream_id: +state_hub_workstream_id: "569be717-34f8-4039-bb26-497685f60159" --- > **Terminology note:** Historical text in this archived workplan may use the legacy term "workstream". The fleet term is **workplan** (`canon/standards/workplan-terminology-fleet_v0.1.md`). @@ -66,7 +66,7 @@ refresh* and moves reliability evidence beyond structural. id: REUSE-WP-0019-T01 status: done priority: high -state_hub_task_id: "337866d5-9952-40b8-a338-8ac16a699be0" +state_hub_task_id: "4a187b56-bff9-4097-abd0-b423e7bf9442" ``` **Inventory findings (2026-07-07):** cross-referenced `sources.yaml` (61 @@ -117,7 +117,7 @@ Implemented: id: REUSE-WP-0019-T02 status: done priority: high -state_hub_task_id: "212352fe-3caf-4999-b5a2-58fa2441ca56" +state_hub_task_id: "691eb32a-6f20-4a2a-b9ff-0ae427b659aa" ``` **Note:** `POST /v1/federated/compose` (token-auth, triggers a real @@ -193,7 +193,7 @@ production ingress template edit outside this workplan's scope. id: REUSE-WP-0019-T03 status: done priority: medium -state_hub_task_id: "a8e0bdc6-0a92-4a87-a7b2-19cf0a46db70" +state_hub_task_id: "aa9e9f80-b878-490c-832e-515d8cbbbb60" ``` **Org-level Forgejo webhook — done by `railiance-apps` (2026-07-07), @@ -271,7 +271,7 @@ whenever a future deploy wants to switch registries. id: REUSE-WP-0019-T04 status: done priority: medium -state_hub_task_id: "88e240d1-0b85-42d8-9d9e-44fb46937894" +state_hub_task_id: "c8e9064e-5c39-4c84-80e9-8b255f8edaec" ``` The shared schema (`schemas/reuse-event.schema.json`) already existed from @@ -314,7 +314,7 @@ Implemented: id: REUSE-WP-0019-T05 status: done priority: medium -state_hub_task_id: "5694b776-f516-47ec-a848-714060dd2261" +state_hub_task_id: "f0282cfa-0a71-4b46-a558-80b51ef04fa7" ``` "Blocked on T04 plus initial event volume" — T04 is done, and the @@ -376,7 +376,7 @@ follow-up rather than rushed in. id: REUSE-WP-0019-T06 status: done priority: low -state_hub_task_id: "b5b4cfaf-16fa-45ce-b1f2-6ad48fb090ab" +state_hub_task_id: "a9f44d45-91e2-4b43-909f-30a5f906cf3b" ``` SCOPE.md's "automatic hub refresh" flip was already done incidentally in