docs(observatory): record selector rules and local UI acceptance

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

@@ -121,6 +121,28 @@ 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).
 
+## Selector contract clarification — 2026-09-03
+
+The owner explicitly excludes completion buttons and status badges. A completed
+current profile is represented by its reviewable, profile-marked evidence below,
+not by a “calculation complete” control. The selector now contains compatible
+portable definitions with no verified exact published cache hit. An archived LAB
+or old definition never hides a new version. An empty selector has no Calculate.
+An in-flight computation has only an activity indicator; failed publication
+keeps a separate recovery action and never starts inference again.
+
+Removed the six-card presentation cap; the existing catalog window limit remains
+explicit. Queue reads now filter definition SHA before pagination. Hook snapshots
+are fenced by source/setup/definition so previous jobs cannot flash in the next
+selection. New synthetic tests exercise none/all/partially cached choices,
+unavailable executors, legacy/new-version separation and pre-effect selection
+changes. Sequential validation:720 frontend tests,52 queue/API tests, architecture,
+typecheck, Ruff/mypy and production build PASS. Full recorded-run/product
+acceptance and measured progress counters remain stage2.
+Historical terminal logs do not become a new selection's error. The existing
+responsive selector layout follows workspace width, including restored narrow
+windows, rather than only the browser viewport.
+
 ## Boundaries
 
 No Synology deployment, hardware actuation, motor integration, new capture,