canon: distinguish sector domains from project identity

workplans/CUST-WP-0065-reclassify-repos-and-guidance-docs-to-the-new-sector-domain.md

@@ -51,7 +51,7 @@ when the answer is ambiguous.
 
 ```task
 id: CUST-WP-0065-T02
-status: todo
+status: done
 priority: medium
 ```
 
@@ -61,6 +61,13 @@ historical project names and canon references intact. Add a validation example
 that rejects legacy names in `repo_classification.domain` while allowing them
 as project/topic identity.
 
+**Done (2026-08-23):** the active Repo Classification Standard now explicitly
+separates legacy project/estate identities from sector-domain metadata and
+links the governed migration baseline. The contribution convention and all
+four contribution templates now show current sector values. The classification
+validator self-test proves `custodian` is rejected as a classification domain;
+project names remain valid outside that field.
+
 ## Repair source records and authoritative projection
 
 ```task
@@ -109,7 +116,7 @@ path can bind them.
 
 - [x] Live missing-classification baseline is reproducible and split by cause
 - [x] Legacy project identity is distinguished from sector-domain metadata
-- [ ] Canonical and agent-facing migration guidance is current
+- [x] Canonical and agent-facing migration guidance is current
 - [ ] Missing source classifications are owner-reviewed and validated
 - [ ] Present source classifications project into State Hub
 - [ ] Active fleet has zero unexplained null category projections