admin
f41a1a0ad8
gates / gates (push) Failing after 18s
Part 2.1's determination is the first artifact: the scratch resolver was consciously OUT OF SCOPE for R-356, not excluded on state-only grounds - established from R-356's own commit 08eb1a6, whose tests say 'the prepared scratch still resolves ... only the DESTINATION moves'. So 07 section 6.3's rule applies and now has a FOURTH consumer, and the section says so. Live evidence: the collision rerun on demo-hp with the sampler positively controlled first (12 locks=1 across a real check, 4 locks=0 quiet), showing unlock --remove-all 0 times where the drill saw it twice; and the proof reaching verdict pass on demo-felhom - the box that could not run it at all - recorded where last_proof_result had been ABSENT every night. Capability map: the off-site proof row now records that the nightly firing IS proven (it ran unattended at 05:30 on demo-hp) and that a driveless box can now be proved. Register: six rows closed and compressed. OPEN 176 -> 170, CLOSED 152 -> 158.
14 lines
757 B
Plaintext
14 lines
757 B
Plaintext
=== VALIDATION 3: an ordinary customer restore on demo-hp, unchanged ===
|
|
--- unit restore ---
|
|
[http=302 wall=0.010338s]
|
|
off-box restore docmost completed (full=false, async)
|
|
--- the scratch it produced ---
|
|
124208399 /mnt/felhom-drives/hdd_1/backups/offsite-restore/docmost
|
|
marker: {"schema":1,"snapshot_id":"b2e059ee","full":false,"finished_at":"2026-09-01T08:33:33Z"}
|
|
--- and the full two-step flow: prepare (which now takes the flag) then confirm ---
|
|
[http=302 wall=5.495803s]
|
|
off-box full-restore prepared for privatebin (size 2.0 MB) — awaiting the customer's confirm; no restore has started
|
|
|
|
--- R-412a live: does a hollow push now say so? (no hollow unit here, so this is the CONTROL) ---
|
|
hollow-push warnings (0 expected, all units sound): 0
|