diff --git a/docs/recovery/onboarding-disposition-2026-08-24.md b/docs/recovery/onboarding-disposition-2026-08-24.md
index bdccaae..c56a0ea 100644
--- a/docs/recovery/onboarding-disposition-2026-08-24.md
+++ b/docs/recovery/onboarding-disposition-2026-08-24.md
@@ -71,3 +71,44 @@ and the variable set — tracked as `CUST-WP-0067-T09`.
 The records are correct and re-derivable in the meantime: the classification
 files are committed and pushed, so re-running onboarding projects them once the
 hub can validate.
+
+
+## Closed 2026-08-25 — all 44 resolved
+
+| Outcome | Count |
+|---|---|
+| Onboarded to central and classified | 43 |
+| Dropped by owner decision (`agent-harness`) | 1 |
+
+`soul-frame`'s three research commits were pushed by owner decision and it
+onboarded cleanly. The nine repositories without a classification file had their
+sector domain and category decided with the owner one at a time; all nine
+validated against canon, were committed, pushed, and onboarded. Central holds
+121 repositories.
+
+Two decisions worth keeping visible:
+
+- **`rein-openweights` moved `infotech` → `agents`**, matching its sibling
+  `rein-aharness` so the rein concept groups coherently.
+- **`railiance-telemetry` moved `financials` → `infotech`** by owner decision,
+  classifying it by what it is rather than the estate it serves. This
+  deliberately splits it from the other Railiance repositories on central.
+
+## The cache database still must not be discarded
+
+Repository records are fully recovered, but that was only this task's scope.
+Measured 2026-08-25:
+
+| Record type | Local cache | Central |
+|---|---|---|
+| `managed_repos` | 122 | 121 |
+| `workplans` | 1075 | 669 |
+| `tasks` | 6073 | 4123 |
+
+Roughly 400 workplans and 1,950 tasks still exist only in the cache. That is
+`ADR-010`'s original divergence, which this workplan never claimed to close —
+it addressed the repository-record subset. `ADR-010` assessed the bulk of those
+as file-backed and therefore re-derivable, but re-derivation has not been run
+or verified.
+
+**Do not discard the cache database until that is resolved.**
diff --git a/workplans/CUST-WP-0067-hub-authority-target-resolution.md b/workplans/CUST-WP-0067-hub-authority-target-resolution.md
index 09862ad..9e18395 100644
--- a/workplans/CUST-WP-0067-hub-authority-target-resolution.md
+++ b/workplans/CUST-WP-0067-hub-authority-target-resolution.md
@@ -310,8 +310,20 @@ All 33 landed with their domain but no classification fields, pending `T09`.
 They are re-derivable: the classification files are committed and pushed, so
 re-running onboarding projects them once the hub can validate.
 
-**The local cache database may not be discarded yet** — 11 records still exist
-only there.
+**Closed 2026-08-25.** All 44 resolved: 43 onboarded to central and classified,
+`agent-harness` dropped by owner decision. `soul-frame`'s research commits were
+pushed by the owner; the nine repositories lacking a classification file had
+their sector and category decided one at a time with the owner, validated
+against canon, committed, pushed, and onboarded. Central holds 121 repositories.
+
+**The cache database still must not be discarded, for a different reason.**
+Repository records are fully recovered, but they were only this task's scope.
+Measured the same day: 1075 workplans and 6073 tasks in the cache against 669
+and 4123 on central — roughly 400 workplans and 1,950 tasks that exist only
+there. That is `ADR-010`'s original divergence, tracked as `T10`. An earlier
+note in this workplan said the cache would hold nothing unique once the 11 were
+resolved; that was wrong, because it generalised a repository-scoped result to
+every record type.
 
 ## Correct the ADR-010 framing and record the retirement
 
@@ -632,3 +644,36 @@ every one returned `updated` with no warnings, where before each returned
 
 The idempotence mattered here: the same command that onboarded them projected
 their classification later, with no separate backfill path to write or trust.
+
+
+## Re-derive the workplan and task divergence
+
+```task
+id: CUST-WP-0067-T10
+status: todo
+priority: high
+```
+
+`ADR-010`'s original finding was about workplans, and it is still open. The
+local cache holds 1075 workplans and 6073 tasks against central's 669 and 4123
+— roughly 400 workplans and 1,950 tasks that exist nowhere else. Until these
+are re-derived or dispositioned, the cache database cannot be discarded, which
+means the retired instance's data is still load-bearing.
+
+`ADR-010` assessed most of the equivalent divergence as file-backed and
+therefore rebuildable, with a smaller orphan set needing case-by-case handling.
+That assessment is from 2026-08-17 and predates this workplan's changes; it
+should be re-measured rather than assumed.
+
+The pattern from `T04`/`T05` applies: identify the authoritative source file,
+confirm it is committed and pushed, re-derive onto central, and disposition in
+writing whatever has no source. `fix-consistency` C-06 and the registrar already
+do this for workplans, so the work is likely driving and verifying them rather
+than writing something new.
+
+This may warrant promotion to its own workplan — it is larger than the
+repository-record subset and touches every repo with work records.
+
+Acceptance: every cache-only workplan and task either exists on central or
+carries a written disposition; the cache database can then be discarded, and
+`ADR-010`'s divergence is closed rather than merely described.