Archive closed workplans with completion-date prefixes
Moves the remaining finished workplans into workplans/archived/. Prefixes use each workplan's own completion date per the convention, not the date the archive sweep ran. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 4609@bnt-lap001 Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
This commit is contained in:
parent
152e88a38e
commit
1df9c19c96
15 changed files with 2 additions and 2 deletions
|
|
@ -0,0 +1,124 @@
|
|||
---
|
||||
id: REUSE-WP-0021
|
||||
type: workplan
|
||||
title: "Follow the CommerceCanon repository rename in federation sources"
|
||||
domain: infotech
|
||||
repo: reuse-surface
|
||||
status: finished
|
||||
flavor: residual
|
||||
owner: codex
|
||||
origin: residual
|
||||
origin_ref: IDENTITY-WP-0004
|
||||
created: "2026-09-05"
|
||||
updated: "2026-09-20"
|
||||
state_hub_workstream_id: "0d1beafd-e638-5bb9-b91d-13543ac42a04"
|
||||
---
|
||||
|
||||
# CommerceCanon source-coordinate handoff
|
||||
|
||||
identity-canon was renamed to commerce-canon under CFED-WP-0001-T03 and
|
||||
IDENTITY-WP-0004. Forge repository ID 46 is unchanged, and the old URL is a
|
||||
redirect. Project task CFED-WP-0001-T09 owns fleet acceptance and consumes this
|
||||
repository's source/refresh evidence.
|
||||
|
||||
## Update source coordinates and verify federation
|
||||
|
||||
```task
|
||||
id: REUSE-WP-0021-T01
|
||||
status: done
|
||||
flavor: residual
|
||||
priority: medium
|
||||
state_hub_task_id: "b7803b7d-0b70-5aac-8f6a-2704794fccf2"
|
||||
```
|
||||
|
||||
Update registry/federation/sources.yaml and local-repo-roster.yaml to the
|
||||
canonical commerce-canon URL/path. Refresh the affected source cache and
|
||||
registry/indexes/federated.yaml through the repository's federation tooling.
|
||||
Preserve capability.identity.subject-resolution and
|
||||
capability.identity.vocabulary-canonicalize identifiers; a repository rename
|
||||
alone does not redefine capabilities. Source owner/URL/cache metadata should
|
||||
match the newly published commerce-canon registry.
|
||||
|
||||
Verify both capability entries remain discoverable with canonical source links,
|
||||
record command/results and commit, and hand evidence back to CFED-WP-0001-T09.
|
||||
Leave historical workplan/completion provenance intact. No credential, runtime
|
||||
service, or capability-semantic migration is authorized by this task.
|
||||
|
||||
|
||||
## Repair archived workplan bindings reported during handoff registration
|
||||
|
||||
```task
|
||||
id: REUSE-WP-0021-T02
|
||||
status: done
|
||||
flavor: residual
|
||||
priority: low
|
||||
state_hub_task_id: "ceba0cd4-3992-5f16-bdd2-1f054055d10b"
|
||||
```
|
||||
|
||||
The 2026-09-05 handoff registration created this workplan and T01 successfully,
|
||||
but the full consistency audit reported pre-existing invalid `None` bindings in
|
||||
archived REUSE-WP-0017, REUSE-WP-0018 and REUSE-WP-0019 (C-03, plus C-08 on their
|
||||
closed DB records); binding upload returned 422. Reconcile these through the
|
||||
supported identifier/projection tooling, preserving work-record identity and
|
||||
history, then rerun the audit. This is an index-repair follow-up, not a failure
|
||||
of the completed commerce-canon Forge/State Hub rename.
|
||||
|
||||
## Source refresh result — 2026-09-06
|
||||
|
||||
T01 passes: source manifest and roster use commerce-canon; the federation
|
||||
composer refreshed that source with no warnings. Both capability.identity ids
|
||||
and vectors are unchanged; 60 unrelated local index rows are preserved.
|
||||
The live reuse service has an enabled commerce-canon registration and retains
|
||||
the old registration disabled with a replacement note. Its fresh composed index
|
||||
serves both ids from canonical URLs and cache paths, with no target warnings.
|
||||
Existing federation tests: 15 passed. CFED-WP-0001-T09 owns consolidated evidence.
|
||||
|
||||
## Binding repair limitation — 2026-09-06
|
||||
|
||||
T02 remains live and waiting for supported legacy-binding restoration. Null
|
||||
frontmatter fields were deliberately cleared in commit 8b04f91. Current primary
|
||||
workplans remain finished under existing UUIDs:
|
||||
|
||||
- REUSE-WP-0017: a2d83504-fcd0-4561-8688-b77a01cb7f06
|
||||
- REUSE-WP-0018: cd8683ff-6e6c-4f6c-a62f-565bd55113ea
|
||||
- REUSE-WP-0019: 569be717-34f8-4039-bb26-497685f60159
|
||||
|
||||
Repo Manager ensure_missing_work_record_identifiers(execute=False) rejects the
|
||||
blank scalar (expected None, found empty string); moreover its deterministic
|
||||
UUIDs differ from all three existing identities. Ordinary assignment is not a
|
||||
restoration mechanism. State Hub stringifies null as None and classifies it as
|
||||
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).
|
||||
Loading…
Add table
Add a link
Reference in a new issue