docs(recovery): drop agent-harness by owner decision

Superseded by glas-harness and the rein concept, so there is nothing to
restore. Not onboarded to central; its cache-only record is left to disappear
when the cache database is discarded, rather than preserved as a hub-only
record with no backing file.

Successors verified present and classified on central before dropping.
Ten records remain outstanding.

Refs CUST-WP-0067-T05

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

workplans/CUST-WP-0067-hub-authority-target-resolution.md

@@ -294,8 +294,9 @@ written disposition; only then may the local cache database be discarded.
 repositories. The remaining 11 each carry a written disposition in
 `docs/recovery/onboarding-disposition-2026-08-24.md`: nine need a classification
 file authored with their owner, `soul-frame` has unpushed research commits that
-are the owner's to publish, and `agent-harness` has no working copy and must be
-restored or explicitly dropped.
+are the owner's to publish, and `agent-harness` was **dropped on 2026-08-25** by owner decision — superseded by
+`glas-harness` and the `rein` concept, both verified present and classified on
+central first. Ten records remain outstanding.
 
 None were forced. Classification is not mechanical (`CUST-WP-0065-T01`), and a
 confident wrong domain is harder to correct than a missing one.