docs(observatory): record claim-v3 repair and preserved queue history

docs/adr/0050-recorded-observatory-first.md

@@ -63,6 +63,24 @@ complete recorded-analysis execution are still pending. This increment does not
 mark stage 1 or the full workflow complete. Tests cover concurrent admission,
 durability, changed source/profile, failure retry and HTTP 409 duplicate handling.
 
+## Second increment: bounded non-binding idle claims
+
+Claim/v3 is active on the backend and both current Worker006 control agents.
+Idle polls do not persist receipts; actual grants are durable and share the
+request-ID namespace with preserved v2 history. Repeating a non-binding v3 idle
+request may later acquire work, unlike an old persisted v2 empty receipt.
+The 50,000-row legacy ledger remains intact; a separate 50,000-positive-grant
+budget does not change the shared 128 MiB database/WAL/SHM storage bound.
+
+Only the imported gateway's request schema literal changes in two pinned child
+images. Compute package identities and model images remain unchanged. The exact
+control-agent create declarations, separate from executor package declarations,
+are now the durable runtime source; old agents remain stopped for rollback.
+126 focused tests and 16 real empty-capability Worker-to-backend probes passed.
+All pre-existing queue row hashes are unchanged. This repairs dispatch polling,
+not published-cache verification or full recorded-workflow acceptance.
+See the [repair evidence and rollback boundary](../../experiments/perception/OBSERVATORY_RECORDED_CLAIM_REPAIR_2026-09-02.md).
+
 ## Boundaries
 
 No Synology deployment, hardware actuation, motor integration, new capture,