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.
20 lines
719 B
Plaintext
20 lines
719 B
Plaintext
=== THE PROOF ON A BOX WITH ZERO REGISTERED DRIVES ===
|
|
{"error":"Nem bekötött","ok":false}
|
|
|
|
[http=501]
|
|
|
|
=== what it recorded (last night this was ABSENT) ===
|
|
last_proof_result '<ABSENT>'
|
|
last_proof_stack '<ABSENT>'
|
|
last_proof_snapshot '<ABSENT>'
|
|
last_proof_reason '<ABSENT>'
|
|
last_proof_run '<ABSENT>'
|
|
proved_snapshots '<ABSENT>'
|
|
|
|
=== the log line (last night: a WARN and nothing else) ===
|
|
Daily job offsite-proof scheduled for 2026-09-02 05:30 CEST
|
|
|
|
=== where did the scratch resolve to, and is it gone? ===
|
|
offsite-proof root: ls: cannot access '/mnt/sys_drive/felhom-data/backups/offsite-proof': No such file or directory
|
|
(empty or absent = the copy was deleted, as it must be)
|