workplans: record classification projection repair

WORK-RECORDS.md

@@ -414,7 +414,7 @@
 | task | CUST-WP-0065-T01 | done | — | workplans/CUST-WP-0065-reclassify-repos-and-guidance-docs-to-the-new-sector-domain.md |
 | task | CUST-WP-0065-T02 | done | — | workplans/CUST-WP-0065-reclassify-repos-and-guidance-docs-to-the-new-sector-domain.md |
 | task | CUST-WP-0065-T03 | progress | — | workplans/CUST-WP-0065-reclassify-repos-and-guidance-docs-to-the-new-sector-domain.md |
-| task | CUST-WP-0065-T04 | todo | — | workplans/CUST-WP-0065-reclassify-repos-and-guidance-docs-to-the-new-sector-domain.md |
+| task | CUST-WP-0065-T04 | progress | — | workplans/CUST-WP-0065-reclassify-repos-and-guidance-docs-to-the-new-sector-domain.md |
 | intake | CUST-IN-0001 | closed | green | intake-legacy-suggestions-migration.md |
 | intake | CUST-IN-0002 | closed | green | intake-legacy-suggestions-migration.md |
 | intake | CUST-IN-0003 | closed | green | intake-legacy-suggestions-migration.md |

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.

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

@@ -87,11 +87,33 @@ and `config-atlas` sentinel proof in message `a5e685c9`; `binky-control`
 received the first missing-source owner handoff in message `15d8f2df`. The
 remaining missing-source repos stay in the baseline for governed owner routing.
 
+**Implementation checkpoint (2026-08-23):** all 24 committed source files now
+project through the State Hub API; the active-fleet projection improved from
+79/117 to 103/117 classified repos. Twenty-one updated through the standard
+registration command. Three server-error cases (`rail-knative`, `rapp-qonto`,
+and `rapp-sbom-nexus`) were recovered with classification-only PATCHes, then
+used to expose and verify a State Hub registration defect. State Hub revision
+`57c3e08` now keeps classification updates separate from Git identity fields,
+honors `domain_slug` changes, and normalizes multi-root histories to one
+fingerprint; focused regression tests and all three live repros pass.
+
+Every remaining missing-source repo has an owner handoff with a suggested
+starting point and an explicit requirement to review, validate, commit, and
+report its revision: `agent-harness` (`b5718a78`), `binect-chrome`
+(`cfe4baa6`), `binect-js` (`3a8358b7`), `binky-control` (`18dc8758`),
+`clay-borg` (`98726021`), `direkt-vermittlung-de` (`f177403a`),
+`polycode-sim` (`b3247d7b`), `railiance-telemetry` (`bf2e2fea`),
+`ralph-workplan` (`186be39c`), `rein-aharness` (`c02a26b9`),
+`rein-openweights` (`24d9e895`), `tele-mcp` (`76e3d0dc`),
+`testdrive-jsui` (`cbefc9a0`), and `timeline-svg` (`d350d2c6`). T03 remains in
+progress because those classification judgments must land in their owning
+repositories; they are not safe Custodian-side mechanical edits.
+
 ## Verify fleet convergence and close
 
 ```task
 id: CUST-WP-0065-T04
-status: todo
+status: progress
 priority: medium
 ```
 
@@ -101,6 +123,11 @@ guidance uses sector domains, and no project identity was destroyed by the
 migration. Record any genuine owner decision as a live residual before
 finishing.
 
+**Started (2026-08-23):** the post-repair fleet check reports 121 registered,
+117 active, 103 classified, and 14 active null-category records. The null set
+exactly matches the 14 governed owner handoffs; no present source file remains
+unprojected. Project names and repository identities were not rewritten.
+
 ## Indexing note
 
 The workplan is indexed as `e2702474-b276-4e15-8337-41bfa344c89c`, but the
@@ -118,5 +145,5 @@ path can bind them.
 - [x] Legacy project identity is distinguished from sector-domain metadata
 - [x] Canonical and agent-facing migration guidance is current
 - [ ] Missing source classifications are owner-reviewed and validated
-- [ ] Present source classifications project into State Hub
+- [x] Present source classifications project into State Hub
 - [ ] Active fleet has zero unexplained null category projections