diff --git a/workplans/STATE-WP-0080-register-project-flavor-awareness.md b/workplans/STATE-WP-0080-register-project-flavor-awareness.md
index a08289d..6ef84a0 100644
--- a/workplans/STATE-WP-0080-register-project-flavor-awareness.md
+++ b/workplans/STATE-WP-0080-register-project-flavor-awareness.md
@@ -251,3 +251,29 @@ standards and representation now sit with `repo-manager`, per decision
 | T05–T08 | 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.