docs(observatory): record cache activation and Docker memory recovery

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

@@ -83,8 +83,11 @@ See the [repair evidence and rollback boundary](../../experiments/perception/OBS
 
 ## Third increment: exact published-result cache (2026-09-03)
 
-Implemented in source; activation of the matching backend/frontend release is
-pending the local resource gate. This does not claim a completed recorded run.
+Implemented and activated as a matching backend/frontend release on canonical8000
+on 2026-09-03 after an owner-approved Docker VM restart recovered memory headroom.
+Full typecheck,714 frontend tests and production build passed sequentially;
+API catalogs and in-app UI were checked without creating inference jobs.
+All queue row hashes are preserved. This does not claim a completed recorded run.
 
 The portable catalog now joins successful **published** queue receipts to the
 current per-source catalog snapshot, immutable definition, Session publication
@@ -112,6 +115,10 @@ return the original job. Verified corruption permits a new request.
 The frontend's existing portable decoder now accepts only bound, internally
 consistent cached results. No per-LAB page, renderer or selector implementation
 was introduced. Full selector/progress/product acceptance remains stage 2.
+Browser QA confirms that source/setup-only job selection can still display a
+legacy completion status against a current definition. Exact-version status
+binding and separating archives from executable choices remain required;
+the activated backend cache does not prove those UI changes complete.
 See [verification and activation status](../../experiments/perception/OBSERVATORY_PUBLISHED_CACHE_2026-09-03.md).
 
 ## Boundaries