night 2026-09-25 (in progress): part 7 shipped as controller v0.271.0 — decisions 31-33, evidence A/B/C/F, register (R-685..R-687; closed R-672 R-673 R-684 R-680 R-678)
gates / gates (push) Successful in 25s

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
2026-09-24 23:04:43 +02:00
parent 75ff26408a
commit a7971c4822
126 changed files with 10324 additions and 9 deletions
+9
View File
@@ -171,6 +171,15 @@ ALLOWLIST = {
"that card. The sibling `offsite.last_integrity_check` is NOT allowlisted and passes on its "
"own — the string already occurs hub-side. **When a hub surface is built, delete this entry.**"),
# ---- controller v0.271.0 (`09` §6.4 part 7): the automatic update leg's nightly summary ----
(_CH, "update_leg"): (
"controller v0.271.0: the operator's ONE summary of the night's automatic update leg (done / undone / "
"held / failed / skipped with reasons) rides the report so it is in the hub's stored raw report; no hub "
"surface reads it yet — a fleet view is §6.3 slice 7 (decision 18), built when the fleet grows. The "
"household's events for an undone or held step are the existing app_update_undone / app_update_held. "
"**When a hub surface is built, delete this entry.**"),
(_CH, "update_leg.ended_at"): "controller v0.271.0: a field of update_leg above — same reason.",
# ---- R-87, controller v0.231.0: the nightly off-site PROOF's verdict ----
#
# Five fields, ONE reason, and it is the SAME reason as the two integrity siblings below: the