workplans: record classification projection repair

docs/repo-classification-sector-migration-baseline-2026-08-23.md

@@ -74,3 +74,30 @@ source file present but unprojected: 24
 Acceptance is zero unexplained null category projections among active repos.
 A governed archived/decommissioned record or an explicit classification
 exclusion is not unexplained.
+
+## Implementation checkpoint
+
+The same query after API reconciliation reports:
+
+```text
+registered: 121
+active: 117
+active with projected classification: 103
+active with null category: 14
+missing source file: 14
+source file present but unprojected: 0
+```
+
+All 24 present source files were validated and projected through State Hub's
+REST API. Twenty-one completed through the existing registration utility.
+`rail-knative`, `rapp-qonto`, and `rapp-sbom-nexus` initially exposed a utility
+defect because classification PATCHes also sent Git identity metadata; their
+multi-root fingerprints exceeded the single-SHA database field. State Hub
+revision `57c3e08` separates those concerns, supports primary-domain updates,
+and uses the same single-root fingerprint projection as token attribution. The
+three live repros subsequently completed without invalid results.
+
+The remaining null set exactly equals the 14 missing-source repositories above.
+Each owner has a State Hub handoff requiring human review, local validation, a
+committed `.repo-classification.yaml`, and revision evidence. This is governed
+pending work rather than an unexplained projection failure.