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,5 +1,45 @@
|
||||
# Typed RootHelper bridge contract (implementation, not native acceptance)
|
||||
|
||||
## Configure-only partial recovery (schema 4, local implementation)
|
||||
|
||||
This is a **new, separately WebUI-approved** dev-test native action. Schema 4
|
||||
requires `native_recovery = {schema_version:1, previous_grant_id,
|
||||
previous_attempt_id, partial_proof_sha256}` and forbids `native_retry`.
|
||||
Resolved transaction schema 2 adds `operation:"configure_only"`; only the
|
||||
existing `rmm-apt-fixture-install-1.0` recipe/version 1, pinned fixture archive,
|
||||
and old/new version `1.0` are eligible. Schema 1 retains its exact encoding.
|
||||
|
||||
The helper first requires the original saved signed request, immutable SQLite
|
||||
partial proof, definitive `APT_PARTIAL_UNCONFIGURED_VERIFIED` outcome, and closed
|
||||
consumed row. `recovery-planning` receives exactly `{native_recovery, proof}`;
|
||||
Python rechecks the original still-active witnesses and complete current partial
|
||||
snapshot. It seals only the content-addressed baseline and returns the normal
|
||||
planning projection plus `native_recovery`. Ordinary planning continues to reject
|
||||
unconfigured packages. This passive projection creates no job or authorization.
|
||||
|
||||
For execution the helper archives the definitive old active directory, stages
|
||||
the exact proof as `active/partial-proof.json`, and binds its hash in the new
|
||||
signed manifest. Python independently checks history, original target, full
|
||||
partial baseline and installed fixture bytes. APT receives only
|
||||
`install -- rmm-mvp-test=1.0`; the actual v3 hook must contain exactly one
|
||||
equal-version `**CONFIGURE**` action. Unpack, removal, foreign packages and pending
|
||||
configuration remain forbidden. The same native sandbox, grant deadlines,
|
||||
locked-store handoff and complete postcondition/audit checks apply.
|
||||
|
||||
Create-once markers are `recovery-attempt-<previous_grant>.json`,
|
||||
`pending-recovery-<previous_grant>.json`, and `recovery-<previous_grant>.json`.
|
||||
Original/retry markers, signed histories and the original unknown proof remain
|
||||
intact. Recovery produces `native_recovery:true`, `recovery_record_sha256` and
|
||||
`partial_proof_sha256`; it creates no fresh-install acceptance record or
|
||||
`native_record_sha256`. A later separately approved native 1.1 upgrade must
|
||||
provide the ordinary acceptance evidence for the changed provider/runtime.
|
||||
|
||||
Local actual APT 2.6.2, with a vetoing collector and independently guarded fake
|
||||
dpkg, emitted only the exact configure action/target; real and copied package
|
||||
status stayed unchanged. This is **local regression evidence**, not Cloud-VM
|
||||
recovery acceptance. Native deployment, UI approval and execution remain the
|
||||
parent's next acceptance step.
|
||||
|
||||
## Explicit one-attempt recovery (schema 3, 2026-11-13)
|
||||
|
||||
Schema 2 keeps its exact old encoding (the optional field is omitted). Schema 3
|
||||
|
||||
Reference in New Issue
Block a user