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.
8 lines
233 B
Plaintext
8 lines
233 B
Plaintext
=== demo-felhom BEFORE: still zero registered storage paths? ===
|
|
registered storage paths: 0
|
|
last_proof_result: '<ABSENT>'
|
|
|
|
=== deploy 0.232.0 ===
|
|
deployed
|
|
gitea.dooplex.hu/admin/felhom-controller:0.232.0 Up 26 seconds (healthy)
|