docs: record legacy task identity backfill
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 5s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e77b-9d43-7432-9301-e5cb6ad05ef6
This commit is contained in:
tegwick 2026-09-28 12:18:42 +02:00
parent 8b9f599931
commit 1e4c46414e

View file

@ -47,7 +47,11 @@ No release tag, registry publication, or browser acceptance is claimed.
The following blocks restore file backing for the nine **existing** legacy P.1–P.9 The following blocks restore file backing for the nine **existing** legacy P.1–P.9
tasks. Their State Hub UUIDs are preserved verbatim; no task is being created. tasks. Their State Hub UUIDs are preserved verbatim; no task is being created.
The file record IDs provide stable local references. The roadmap retains the The file record IDs provide stable local references. Central reconciliation
initially duplicated the nine rows whose canonical IDs were null; a scoped
transaction removed only those new projections and used State Hub’s
forge-sourced backfill to bind the original UUIDs to these record IDs. All ten
original task identities remain. The roadmap retains the
historical checklist and the current release acceptance criteria. historical checklist and the current release acceptance criteria.
## P.1 — Decide repository structure (monorepo vs standalone) ## P.1 — Decide repository structure (monorepo vs standalone)