docs: retain failed stale-baseline noop and require post-upgrade planning evidence
Rust development slice / linux (push) Failing after 6s
Rust development slice / linux (push) Failing after 6s
This commit is contained in:
@@ -109,3 +109,14 @@ upgrade or change outside the harmless fixture is claimed.
|
|||||||
Private verified checkpoint:
|
Private verified checkpoint:
|
||||||
`devstate/cloud-apt-recovery/configured-reconcile-runtime/cases/apt_native_update/checkpoint.json`.
|
`devstate/cloud-apt-recovery/configured-reconcile-runtime/cases/apt_native_update/checkpoint.json`.
|
||||||
The two separate normal1.1-noop plans and remaining MVP gates are still open.
|
The two separate normal1.1-noop plans and remaining MVP gates are still open.
|
||||||
|
|
||||||
|
The first separate `ensure_package` plan subsequently ended **failed** with
|
||||||
|
`STATUS_FINGERPRINT`, grant`b7fbd250-c382-4d2f-950d-ae6001e4c48e`/Root13.
|
||||||
|
Its actual UI audit and counts1/1/1/0 are retained. It reused exactly the
|
||||||
|
pre-upgrade baseline and status fingerprint; the native update's verified
|
||||||
|
post-snapshot was different. The under90-second observation-age check alone
|
||||||
|
therefore did not establish post-update freshness. The immutable failed plan
|
||||||
|
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.
|
||||||
|
|||||||
@@ -1,5 +1,16 @@
|
|||||||
# Tatsächlicher Implementierungsstand
|
# Tatsächlicher Implementierungsstand
|
||||||
|
|
||||||
|
## Erste1.1-Noop-Vorbereitung ehrlich abgewiesen — 2026-11-13
|
||||||
|
|
||||||
|
Separater tatsächlicher UI-`ensure_package`-Plan wurde vor Paketwirkung mit
|
||||||
|
`failed/STATUS_FINGERPRINT` geschlossen, Grantb7fbd250-c382-4d2f-950d-ae6001e4c48e,
|
||||||
|
Root13, eigenes0/0/0→1/1/1/0 und simuliertes Genehmigungsaudit erhalten.
|
||||||
|
Er benutzte exakt die passive Baseline und den Fingerprint VOR dem erfolgreichen
|
||||||
|
Upgrade, nicht dessen verifizierten1.1-Postsnapshot. Alter<90Sekunden genügte
|
||||||
|
hier nicht. Kein bestandener Noop; alter Versuch bleibt unverändert. Ein neuer
|
||||||
|
fester Plan muss frische passive1.1-Daten nach Updateabschluss binden. Provider,
|
||||||
|
Helper und native1.1-Acceptance werden dafür nicht verändert. MVP weiterhin offen.
|
||||||
|
|
||||||
## Native APT1.0→1.1-Acceptance bestanden — 2026-11-13
|
## Native APT1.0→1.1-Acceptance bestanden — 2026-11-13
|
||||||
|
|
||||||
Eigener fester WebUI-Plan auf der qualifizierten Runtimef40c/bbd2/1dc tatsächlich
|
Eigener fester WebUI-Plan auf der qualifizierten Runtimef40c/bbd2/1dc tatsächlich
|
||||||
|
|||||||
Reference in New Issue
Block a user