coulomb/reuse-surface
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Track CommerceCanon source rename and archived binding follow-up
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
ci / validate-registry (push) Successful in 1m7s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
This commit is contained in:
tegwick 2026-09-05 20:25:07 +02:00
parent 46919718e2
commit c4c800f4a3
2 changed files with 62 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
WORK-RECORDS.md
View file

@ -20,6 +20,7 @@
| workplan | REUSE-WP-0010 | finished | — | workplans/REUSE-WP-0010-network-federation.md |
| workplan | REUSE-WP-0016 | finished | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md |
| workplan | REUSE-WP-0020 | finished | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
| workplan | REUSE-WP-0021 | ready | — | workplans/REUSE-WP-0021-commerce-canon-source-rename.md |
| task | REUSE-WP-0001-T01 | done | — | workplans/REUSE-WP-0001-statehub-bootstrap.md |
| task | REUSE-WP-0001-T02 | done | — | workplans/REUSE-WP-0001-statehub-bootstrap.md |
| task | REUSE-WP-0001-T03 | done | — | workplans/REUSE-WP-0001-statehub-bootstrap.md |
@ -79,3 +80,4 @@
| task | REUSE-WP-0020-T07 | done | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
| task | REUSE-WP-0020-T08 | done | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
| task | REUSE-WP-0020-T09 | done | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md |
| task | REUSE-WP-0021-T01 | todo | — | workplans/REUSE-WP-0021-commerce-canon-source-rename.md |

60
workplans/REUSE-WP-0021-commerce-canon-source-rename.md Normal file
View file

@ -0,0 +1,60 @@
---
id: REUSE-WP-0021
type: workplan
title: "Follow the CommerceCanon repository rename in federation sources"
domain: infotech
repo: reuse-surface
status: ready
owner: codex
origin: residual
origin_ref: IDENTITY-WP-0004
created: "2026-09-05"
updated: "2026-09-05"
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: todo
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: todo
priority: low
```
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.