feat: qualify bound configure-only recovery runtime on cloud VM
Rust development slice / linux (push) Failing after 6s
Rust development slice / linux (push) Failing after 6s
This commit is contained in:
@@ -1,11 +1,21 @@
|
||||
# Root-helper APT transaction provider / explicit first native acceptance
|
||||
|
||||
**Current 2026-11-13:** Cloud fixture retry reached armed hook and APT exit 0,
|
||||
but independent verification found an unpacked/unconfigured package; outcome
|
||||
remains **unknown**, with all original/retry tombstones and ledger preserved.
|
||||
No native acceptance record, package repair or further retry. Root test policy
|
||||
**Current 2026-11-13:** The Cloud fixture retry reached armed hook and APT exit 0,
|
||||
leaving fixture 1.0 unpacked/unconfigured. An original-bound readonly proof and
|
||||
normal signed RootSync now classified that original attempt as **failed**
|
||||
(`APT_PARTIAL_UNCONFIGURED_VERIFIED`), preserving all histories/tombstones.
|
||||
No native acceptance record or package repair exists. Root test policy remains
|
||||
closed. Detailed real evidence: `../../docs/implementation-status.md`.
|
||||
|
||||
The configure-only recovery path, requiring its own new fixed WebUI approval, is implemented in source
|
||||
(schema 4 manifest, transaction schema 2), with a dedicated passive recovery
|
||||
projection and separate immutable recovery records. Its qualified runtime is now installed and its actual Cloud copied-database
|
||||
sandbox readiness probe passed, preserving original state. **No configure-only
|
||||
package effect or native package acceptance has yet run.** All **75 Python tests passed** in the offline readonly
|
||||
unprivileged container, including actual APT 2.6.2 configure-only protocol and
|
||||
guarded fake-dpkg arguments with unchanged real/copied status. See
|
||||
[`HELPER-CONTRACT.md`](HELPER-CONTRACT.md) for the precise recovery boundary.
|
||||
|
||||
Source configuration now disables APT's `dpkg::selection::remove::approved`
|
||||
rewrite, retaining the exact package's Configure operation while both pending
|
||||
modes remain disabled and hook-pinned. Upstream explanation:
|
||||
@@ -13,8 +23,8 @@ modes remain disabled and hook-pinned. Upstream explanation:
|
||||
Local actual APT 2.6.2 regression in an offline readonly unprivileged container
|
||||
proved unpack + exact `--configure rmm-mvp-test:all`, no `--pending` or foreign
|
||||
target; independent dpkg guard simulated effects, real/copied status unchanged.
|
||||
67 Python tests passed with this opt-in regression. **This source correction
|
||||
is not deployed or natively accepted on the Cloud VM.** No automatic repair,
|
||||
67 Python tests passed with this opt-in regression. **This correction is now installed and sandbox-probed on the Cloud VM;
|
||||
its native package effect remains unaccepted.** No automatic repair,
|
||||
marker reset or implicit unknown-resolution is introduced. Older sections below
|
||||
describe historical increments; current operational status is the linked log.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user