docs(workplan): record STATE-WP-0080's projection state after closing on central
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Central now reads finished, matching the file. Its task projection is still the
pre-retarget draft with four open tasks, because central never saw the
2026-08-16 retarget and none of this file's task identifiers exist there.

Left deliberately: re-registering would add eight records alongside eight stale
ones. Duplicate task identity resolution belongs to CUST-WP-0068.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
This commit is contained in:
tegwick 2026-08-25 16:25:34 +02:00
parent 83fc8c43f5
commit 13ada219eb

View file

@ -251,3 +251,29 @@ standards and representation now sit with `repo-manager`, per decision
| T05T08 | moved to `RMGR-WP-0004-T02/T04/T06`, or superseded |
Nothing in this workplan remains executable here.
## Projection note (2026-08-25)
Closing this on the hub exposed a duplicate registration. The file carried
`03f38314`, minted by the retired local hub; central held a **different** record
for the same file, `bbfce36a``ADR-010`'s "same filename, different UUID"
class. The file now carries central's identifier, because central is
authoritative (`ADR-010` decision 1) and decision 6 says to mitigate by changing
the repository file rather than editing central. The cache-side identifier dies
with the cache.
Central's workplan status is now `finished`, matching this file.
**Its task projection is still the superseded draft.** Central holds the eight
pre-retarget tasks — "Detect repository flavor", "Fix workplan prefix
inference", "Scaffold GOAL.md instead of INTENT.md", "Decide the bootstrap
workplan" — four of them still open, because central never saw the 2026-08-16
retarget. None of this file's own task identifiers exist on central.
That is left deliberately rather than repaired here: re-registering these tasks
would add eight new records alongside the eight stale ones. Resolving duplicate
task identities belongs to `CUST-WP-0068` (T05/T06), which exists for exactly
this class.
**Until then, treat central's open tasks on this workplan as superseded.** The
work they name moved to `RMGR-WP-0004`; nothing here is owed.