Restore-truth run (2026-10-25): D47 + D48 recorded (09 §3 decisions 256, 257; CONTEXT); 07 §6.5 (R-1271 cause + the future-date rule), §6.6 (D48 order, the R-698 sentence), §8.2d (D47), §8.2e (R-1270); register 217 -> 219 (R-1278, R-1279 opened; R-1269/1270/1271 VERIFY; notes R-1206, R-1243 dated check done read-only, R-232 moved one day); STATUS D49 + Monday list; evidence (9202)
gates / gates (push) Successful in 13m44s
gates / gates (push) Successful in 13m44s
This commit is contained in:
1 parent
67053335d1
commit
9647f1d158
58 files changed
+1834
-14
No files matched your search
@@ -1089,6 +1089,24 @@ 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 (08:38) — D47: nothing changes an existing backup; D48: a restore downloads first (operator rulings by starting the run; R-1269)
|
||||
|
||||
256. **An existing recovery unit is never changed in part (D47).** A unit's definition (compose, pins, `app.yaml`) and
|
||||
its data are written only together, by a backup of the same install. A new install never adopts, rewrites or
|
||||
deletes a unit that an earlier install left; that unit is set aside whole and stays restorable. *Operator ruling
|
||||
2026-10-25 08:38, taken by starting the R-1269 brief.* Why: on 2026-10-24 the catalog sweep measured three times
|
||||
that a reinstall's own five-minute refresh wrote the new install's database password into the unit „remove — keep
|
||||
backups" had kept; a restore then could not open the old data (R-1269). Built: every install has an identity
|
||||
(`install_id`), the unit records it, and every writer asks first — `07` §8.2a „An earlier install's unit is set
|
||||
aside" (controller, unreleased; rides v0.343.0).
|
||||
257. **Every restore path resolves and pulls every image its definition names before the first change to the app; a
|
||||
failed pull is a refusal with the app untouched (D48).** *Operator ruling 2026-10-25 08:38, taken by starting the
|
||||
brief.* Why: the restore stopped the app and moved its data first and pulled only inside the database-only start;
|
||||
a version that could not be downloaded then ended in the D22 put-back, a full stop-and-pour-back for nothing.
|
||||
Built: `07` §6.6 „The limit — the image is not in the backup" (controller, unreleased; rides v0.343.0).
|
||||
**Confirmed, no change:** `07` §6.6 — a restore brings the app back at its data's version, then the guarded update
|
||||
climbs the ladder; R-698 (a deleted version cannot come back) and R-933 (our own image mirror) are unchanged.
|
||||
|
||||
### 2026-10-15 (07:48–08:20) — bake first; Plex through its own key; HSTS one day (recorded before the media build)
|
||||
|
||||
247. ~~**Bake first.** A controller version is RELEASED only when its golden is baked.~~ **REVERSED by decision 250,
|
||||
|
||||
Reference in new issue
Block a user