fix: bind noop acceptance to post-upgrade passive baseline and preserve failed attempt
Rust development slice / linux (push) Failing after 6s

This commit is contained in:
2026-11-13 20:08:52 +01:00
parent aee9d72d8b
commit 335486cd1f
4 changed files with 264 additions and 3 deletions
+27
View File
@@ -120,3 +120,30 @@ is not a passed noop and is never reactivated. The minimal next preparation
must bind a newly stored passive installed1.1 observation to the accepted
post-snapshot; any new attempt needs its own pending0/0/0 and actual WebUI click.
No provider/helper change or replacement of the accepted1.1 record is needed.
Actual read-only preflight then proved the exact terminal Root13 outcome,
active handoff13 with no launch/hook/prechecks/child result, and retained native12
acceptance plus original31/337 proofs. Root13/0unresolved/0faults. Protected
report`configured-reconcile-runtime/noop-preflight-d140758efc3e421b91550d3dd52d5d7a.json`.
The SDK fix is implemented and locally qualified: **29 pure harness guard
tests passed**. A no-change preparation now independently reads the completed,
verified native upgrade, then waits for a passive observation collected after
that read. It requires installed fixture `1.1` and the exact full baseline hash
from the native upgrade's postconditions. The earlier observation's under
90-second age is insufficient. A saved preparation witness records that time
barrier, observation time and baseline/fingerprint.
The explicit `--new-noop-after-definitive-no-effect` option additionally checks
the old immutable failed plan, its single authoritative grant and a read-only
Root-ledger/context proof that the `STATUS_FINGERPRINT` failure occurred before
launch or hook arming. It creates a separate
`cases/no-change-retry/ensure_package/` directory; the original checkpoint is
retained. The next actual browser flow still creates a new pending plan and
requires its own approval. These commands are **prepared, not executed by this
source qualification**:
```sh
python3 deploy/cloud_apt_recovery.py accept --case ensure_package --new-noop-after-definitive-no-effect
python3 deploy/cloud_apt_recovery.py finish --case ensure_package --new-noop-after-definitive-no-effect
```