Night 2026-10-25 Parts 1–3: every named artifact still downloads; installer 1.36.1 published (operator yes) and its three refusal sentences seen live; D50 = A recorded (09 §3 262, CONTEXT, build skill); R-1284 and R-1290 closed; R-1261 rig evidence so far

documentation/architecture/09-update-architecture.md

@@ -1099,6 +1099,16 @@ its length, and both fixes cost something the household would notice — operato
      `plex: security fix CVE-2026-96652,CVE-2026-96654,CVE-2026-96655,CVE-2026-96656 taken` and ended `done` in 30.1 s
      after the update's second-drive copy and undo copy. Released as controller 0.341.0, global floor 11:24 UTC.
 
+### 2026-10-25 (evening, attended) — D50: which agent packages the registry keeps
+
+262. **The registry keeps the newest 5 released agent versions, plus the hub's MinAgent floor, plus the version the hub's
+     day-0 manifest names; CI asserts exactly these (D50 = A).** *Operator ruling 2026-10-25 evening.* Options: A) this
+     — cost: a box on a version outside the set cannot fetch its own binary again (none is, on the day); B) the newest 10,
+     never pruned by hand — cost: today's four are gone, so CI stays red until ten new versions exist. Why A: it is what
+     the operator prunes to, and the two pinned versions are the only old ones anything still asks for. Built: agent
+     `scripts/retention-policy.json` (`generic_versions_kept` 5, `pinned`) + `check-published-versions.py`; the pins are
+     copies of hub state, updated by the session that records a vouch or a new MinAgent (R-1290).
+
 ### 2026-10-25 (attended release run) — D49: a restore that does not start keeps both copies; D44–D46: the review picks
 
 258. **A restore whose app does not start keeps the restored data AND the old copy, tells the operator, and never puts the