From fb681b58f8f86910ac677c82697fcc118f49189f Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 26 Aug 2026 07:49:27 +0200 Subject: [PATCH] =?UTF-8?q?feat(workplan):=20close=20STATE-WP-0083-T06=20?= =?UTF-8?q?=E2=80=94=20tasks=20carry=20canonical=20identity?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Central: 5248 of 5974 tasks identified, 5213 distinct, 35 duplicates. The pre-apply check was uniqueness rather than volume — all 136 pending updates were verified to take identities held by nothing else, which is the lesson from the first attempt where a clean dry run concealed 51 non-unique ids. The 35 remaining duplicates predate this work: 18 from a workplan registered twice, 12 from archived RAILIANCE-WP files left unrenamed by the active-only migration decision, 4 from unqualified ad-hoc ids. Co-Authored-By: Claude Opus 5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006 --- ...-WP-0083-forge-derived-projection-reset.md | 27 ++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/workplans/STATE-WP-0083-forge-derived-projection-reset.md b/workplans/STATE-WP-0083-forge-derived-projection-reset.md index 1e7a7bd..d64be5a 100644 --- a/workplans/STATE-WP-0083-forge-derived-projection-reset.md +++ b/workplans/STATE-WP-0083-forge-derived-projection-reset.md @@ -219,7 +219,7 @@ filesystem. ```task id: STATE-WP-0083-T06 -status: progress +status: done priority: high ``` @@ -306,6 +306,31 @@ repositories — `ADHOC-2026-07-02-T01` exists in three workplans — which is t problem `CUST-WP-0066` closed for new records while existing ones kept their unqualified ids. They need their own disposition. +**Done (2026-08-26).** Corrected backfill applied to central: **5248 of 5974 +tasks identified, 5213 distinct, 35 duplicate identities.** + +The check before applying was uniqueness, not volume — the lesson from the first +attempt, where a clean dry run reporting zero conflicts concealed 51 non-unique +ids. All 136 pending updates were verified to take identities held by nothing +else before a single row was written. + +The 35 remaining duplicates predate this work and fall into three classes: + +| Count | Class | Origin | +|---|---|---| +| 18 | `KONT-WP-0013-T00N` and similar | a workplan registered twice, so both copies claim the same task ids | +| 12 | `RAILIANCE-WP-00NN-T0N` | archived RAILIANCE-WP files, left unrenamed by the owner decision of 2026-08-25 — the same numbers exist in three repositories, so their task ids collide | +| 4 | `ADHOC-*-T0N` | unqualified ad-hoc ids reused across repositories, the class `CUST-WP-0066` closed for new records only | + +The `RAILIANCE-WP` twelve are worth noting as a consequence rather than a +surprise: migrating only the *active* workplans was the right call for blast +radius, and this is the price — the archived copies keep colliding identities +until they are migrated too, and task-level reset cannot act on those workplans +in the meantime. + +**Task-level reset remains blocked**, now on a narrower and better-understood +problem: 35 identities, not 5974 unidentified rows. + ## Restore a migration mechanism for central