Skip to content

Cleanup umbrella: simplify MVM, reduce dependencies, and improve build performance #4839

Open
0 of 1 issue completed

Description

@auser

Highest-priority delivery objective

Tracking issue — closure rule: Keep this issue OPEN until all body/comment checkboxes are checked and each item has verified supporting evidence. A merged PR, completed subtask, or partial delivery is not grounds to close this issue.

HIGHEST priority: ALL body/comment checkboxes in #4839 and #3731, their child acceptance, and ALL demo-labelled issues. Continue implementation, review, validation, PRs and merges without repeated “continue” prompts. Keep one owner per lane and update both bodies and comments at verified milestones. The overnight/end-of-week target does not waive gates.

Deliver complete parent outcomes, not merely subtask receipts. Preserve unfinished criteria and the HVF-first, library-first, tracing, custody and backend/security requirements below. Source review or scoped tests do not prove end-to-end acceptance. Escalate only a precise unresolved decision with its next executable step. Existing specific approvals govern; this priority adds no signing, publication, paid/live, old-state cleanup or credential authority.

Current demo inventory: 12 open issues, verified 2026-10-30. All twelve owning scopes remain in scope. Unrelated work must not displace these deliveries.

Current implementation and verification batch

Active delivery queue

Prior next-action snapshot

These are active implementation/delivery assignments, not completion claims. Broad acceptance below remains unchanged.

Live delivery ledger — 2026-10-30

Completion includes body AND comment checklists; keep verified states synchronized. One delivery owner per lane; no new authority.

Lane / sole owner Verified progress and next action
Client parity / facade owner #4877 97615b4f: full local/hosted gates passed. Manifest removal/ABI1.12 generation underway; ratchet still 65 files/76 reaches, root exec outside. No native/Studio parity.
CLI teardown / PS-21 owner #4881 d53cc219: scoped/static/gated/hooks +hosted CI pass. Local HOLD: original attestation assertion unresolved; instrumented full run failed earlier on unchanged span wall-clock ceiling. Same-binary failure showed off-CPU time, not its cause. Finite participant build-drain planned; no waiver.
Volume safeguard / volume owner Step1 #4880 landed 511e354e (receipt). Step2 original-FD custody/startup adoption in implementation; Step3 all-path enforcement open. No rollout/cleanup.
Capture exclusion / capture owner V4 landed: #4994 c3fc5831, full gates green. Provider-limited owner handoff pending; no native/all-error claim.
Builder ownership / runtime owner #4879 EOF foundation landed 39afac26. Fresh-owner/terminal/durability +bounded extraction composition active; factory unqualified. First route FlakeImage only; unsupported modes refuse before birth. Reviewed Debug foundation in full validation.
Toolchains / product-specific owners Studio32 c37c2a26, packs86 85ca6897, images73 32bb05ba landed; FC witness skipped. MVM4876 Nix/compiler/two-arch/repro/boot open. ValidationJob design assigned for same-owner implementation, not execution proof.
Application / integration + producer owners 4509 originals1/2/3/4/6 checked; genuine Sigstore positive open. 4510 all7 hermetic criteria checked, producer dependency open. 4511 OCI-fallback fix: RED +58 scoped passes/source clearance; full gates/protected delivery pending.

Published ABI-1 ARM builder assets and the frozen input packet exist. Fresh M4 isolated build and reviewed/tested builder-only test identity are approved; implementation safety gates still apply. dm-verity finalization is not signing. Official signing/publication, live-model acceptance and old-VM cleanup are separate. PS-06, PS-21 and both umbrellas remain open.

  • Land configured local-policy/Dev defaults #4853, 5bb761c5…; verified source/full-validation/queue receipt. Stable Rust API preserved; not public-pack or native demo acceptance.

  • Land signed-budget fold correction #4859, 7a9061aec8fb9d0e71c613a401bd9b062c85d2a0; protected queue40974115784 passed. Budget ordering/transport only; schema, required-egress and no-policy defaults unchanged. No live demo acceptance.

Detailed receipts preserved verbatim for the compact completed milestones below.

Landed bounded milestones (#4843/#4844/#4846/#4849/#4850 and Studio#31) are recorded separately; they do not complete PS-06, PS-21, the <1M-line goal, performance targets, or native acceptance.

Cleanup PR#4854 is landed; validation records below retain their original source bindings. Studio local-first retirement landed in PR#31 at 94a470d36f3120c16dc204c7d196c6e6da19f436 after remote CI passed. Broader acceptance below remains open.

  • Validate consolidated MCP adapter: 38 adapter tests plus 11 tool-gate tests; shared third-party closure retained.
  • Validate removal of the private CaptureRequestBuilder: the 32 commands::deps:: tests passed, with direct named fields replacing unreachable missing-field states and existing tracing/audit preserved.
  • Run pre-Make pair-image tests hermetic and bound macOS validation time #4840 workspace fmt/check/Clippy and Linux capture-test compilation; compilation is not Linux execution.
  • Validate cleanup 98efd394…: full workspace tests/doctests, fmt/check/Clippy and both gated arms passed. #4854 retains exact commands/source and historical failures. Not performance/umbrella acceptance.
  • Review/validate the first Make pair-image tests hermetic and bound macOS validation time #4840 synthetic-checkout slice: five native macOS tests and workspace Clippy passed; production identity/proof logic retained. Remaining Make pair-image tests hermetic and bound macOS validation time #4840 acceptance stays open. Preserved detailed receipt.
  • Land reviewed Studio retirement docs(plan-34): fold 12 cross-cutting considerations into the L7 egress plan #31 at 94a470d: stop/remove and delayed-output regressions passed; current/native parity separate.
  • Correct the independently reviewed HVF snapshot capture concurrency gap before claiming racing requests are nondestructive. Scope includes pause ownership, aliases/handoff, stale-output cleanup and consumption. V3 late-writer reuse was reproduced; V4 landed as #4994 (merge c3fc58315787593305dfc85b8ed0e4f073584460, all checks green): snapshot-vs-resume serialization with pause ownership, aliases/handoff, stale-output cleanup and request-keyed consumption, with regression tests. fix(hvf): a refused snapshot capture no longer kills the guest, and says why #4836 retries, the 30-second deadline, authenticated observations and diagnostics preserved. Post-land scoped reruns 2026-11-02: cargo test -p mvm-runtime --lib instance_snapshot 45/45, cargo test -p mvm-vmm --lib snapshot 31/31. No native/cross-generation safety claim from scoped tests.

Next #4840 implementation is no longer discovery-only: the test-only unbounded child wait has been replaced with the existing event observer, execution deadline, owned-child cleanup and file-backed diagnostic capture. All five helper tests and one existing cache/proof regression pass; Clippy and independent review remain in progress. Commands/results. No production VM lifecycle or dependency changes.

Reproduced footprint at public 511e354e: 2,804 Rust files / 1,235,719 inclusive physical lines / 47,170,593 bytes; strict <1M gap 235,720 lines. Exact method, SHA-256 inventory and independent reproduction: vendored 76,259 lines; header-marked generated 378; dedicated tests/benches 93,254; remainder 1,065,828 includes inline tests/unmarked generation, not production SLOC. Historical dirty 2,807/1,227,238 is not a controlled comparison/savings claim. No category exclusion or formatting compression.

Goal and authority

Outcome over checklist count. The maintainer clarified:

We can expand the checklists where necessary... the goal here is to simplify all the AI crap, the project, make it easier to maintain, faster to develop, easier to use, etc. etc. as documented in the issue so far

Expand acceptance criteria when investigation reveals necessary work; do not freeze scope merely to make the list easier to finish. Each addition should name a concrete problem, an owner or existing issue, and observable completion evidence. Avoid process-only ceremony and duplicate implementations. Small additions can be justified when they remove hidden states, unsafe coupling, or maintenance cost, but measure their cost honestly and keep the overall footprint/dependency goals intact. Preserve protected tracing/security/backend behavior and HVF-first demo priority. Checked items must correspond to achieved outcomes, not optimistic wording.

Substantially clean up and refactor MVM—not merely perform cosmetic edits. Reduce unnecessary code, dependencies, crates, features, and maintenance burden; remove AI-generated-looking narration and architectural ceremony; make shipped binaries small and fast and development/release builds predictable.

The maintainer explicitly authorizes removing crates established to be extraneous. A justified crate deletion does not need another permission request just because it removes a crate. Prove that it is extraneous through production consumers, supported targets/features, released contracts, and active issue ownership; small size or lack of default integration alone is not proof.

This umbrella owns scope, acceptance criteria, dependencies, and progress. Link focused child issues and PRs here as workstreams are established. Do not create another shared cleanup dashboard in specs/.

Priority: working demo and cleanup

Maintainer instruction:

Top priority: deliver the working demo across those repositories alongside this cleanup. Order cleanup so it unblocks or safely simplifies the demo critical path; do not disrupt active demo owners, signed artifact compatibility, or security enforcement for unrelated count reductions. Continue non-overlapping bounded cleanup in parallel.

Required demo backend order — latest maintainer instruction:

HVF is the first backend for the demo that must work

Demo critical-path delivery checklist — all 12 tracked issues

Completion requires: full scope addressed, necessary implementation, reviewed PRs, passing validation, merged commits and required release/live evidence. Existing landed work counts; no redundant PRs. Plans or partial delivery do not. Separate operational/publication approvals still apply.

  • mvm#4764 — Release.
  • mvm#4655 — HVF custody/recovery.
  • mvm#4511 — Signed launch.
  • mvm#4510 — Atomic installation. Closed COMPLETED on 2026-11-09 with all 7 acceptance criteria checked; credential-free signed application acquisition and installation witness in #4510 (2026-11-09, released macOS aarch64 mvmctl 0.27.0, empty private MVM_HOME, pinned descriptor resolved to the independently trusted author key). Limit recorded there: the v0.27.0 release is a prerelease, so this is not final-demo client compatibility evidence; the demo boxes stay open.
  • mvm#4509 — Descriptor verification. Closed COMPLETED on 2026-11-09 with all 6 acceptance criteria checked; credential-free real signed application positive witness in #4509 (2026-11-09, released mvmctl 0.27.0: tar, checksum manifest, Sigstore bundle and provenance attestation verified; pull agent/claude@2.0.1 exited 0 and reported the descriptor and bundle digests). Same limit: prerelease, not final-demo client compatibility evidence.
  • mvm#4508 — Execution baseline.
  • mvm#4507 — Claude demo.
  • mvm#4391 — HVF latency.
  • mvm-packs#84 — Public HVF witness.
  • mvm-packs#77 — Allow/deny rehearsal.
  • mvm-packs#76 — Signed archive publication.
  • mvm-packs#31 — Runnable environments.

Full scope and dependency details. All 12 boxes are umbrella closure requirements; the earlier audit is not delivery acceptance.

  • Reconcile each listed issue against current implementation, PR/release state, active ownership, and missing acceptance evidence; record the critical-path dependency order. Read-only reconciliation and limits. This completes the audit task only; implementation/live acceptance remains unchecked.
  • Complete the current demo contract across producer, registry, paired CLI/runtime consumer, policy enforcement, and installed-artifact execution. Preserve the exact request-budget constraint documented below; historical descriptors and old multi-request wrappers are not current release evidence.
  • Witness the actual supported demo workflow with correlated allow/deny audit evidence and the required platform/artifact/client checks. Unit tests alone do not establish demo readiness. Explicitly record unavailable checks and operator-authorized publication/live/model gates.
  • Close/reconcile demo issues only after their own acceptance criteria are verified; link the evidence here without substituting this umbrella for the owning issue.

The original empty image-repository demo-label inventory is not image readiness evidence. Existing owners retain their scopes.

Required working method and skills

Maintainer instructions:

Use subagents where possible to work on the checkboxes in the cleanup issue

Also update the issue to utilize ponytail and rust-skills.

Remember to refer to a full cleanup prompt at https://gist.githubusercontent.com/auser/d62dde280d75372dff19d8be7c549d2d/raw/4b5bea12e01e4a579a44fb3c642c0f88899bdc2d/cleanup.md

  • Read and apply the complete, version-pinned MVM cleanup runbook. This issue's checklist is a tracking surface, not a replacement for the full charter, coverage matrix, staged prompts, review requirements, or completion report.
  • Use ponytail for cleanup, implementation, refactoring, and review. Prefer deletion, existing helpers, direct control flow, and the smallest coherent change. Remove unnecessary concepts and maintained surface—not meaningful security boundaries or behavior tests.
  • Use rust-skills for all Rust implementation, refactoring, and review. Apply the relevant ownership, error-handling, async/concurrency, unsafe/FFI, API, testing, and dependency guidance; do not merely mention the skill in a report. This is the maintainer's explicit skill requirement alongside the runbook's Rust-review guidance.
  • Delegate independent checkbox work to subagents where useful. Give each agent a precise worktree, file/surface ownership, read/write scope, execution boundaries, validation requirements, and missing-tool fallback. Do not duplicate active assignments or run competing expensive builds against shared mutable state. Use fresh review context where independence matters.
  • Follow the runbook's staged workflow; do not load every stage into one undifferentiated prompt. Current repository instructions and subsequent explicit maintainer decisions take precedence over generic skill/runbook suggestions.
  • Each agent reports concrete changes/findings, exact evidence, commands and results, limitations, and remaining acceptance gaps. Integrate and verify changes before checking completion; an agent report or accepted assignment alone is not a completed checkbox.

Source charter and recovered intent

Use the complete version-pinned cleanup runbook, subject to current repository instructions and subsequent explicit maintainer decisions.

This issue consolidates that runbook, surviving coordination context, and the maintainer's subsequent clarifications. It is not a verbatim recovery of the original long prompt.

Our project is based on security. The more dependencies and supply chain deps that we depend on introduce yet another layer of possible attack surfaces and vulnerabilities. I really want to reduce the number of dependencies to deal with supply chain attacks and reduce the amount of possible security vulnerabilities.

In addition, the fewer dependencies we rely on the fewer external dependencies. I want you to explore the dependencies that we have and how we might be able to reduce them, especially for deps that we're only using a tiny amount of their API surface area.

When I build for release I see we build 1017 dependencies and then the build seems to rebuild? Something is wrong. This binary has to be small and fast. It's required for good UX/DX.

Subsequent explicit clarification:

We have to clean up and refactor this project... it's a deep prompt with a strong refactor and cleanup. Reduce dependencies where possible.

Remove the AI slop (it's awful). You have authority to remove crates where they are extraneous

Subsequent maintainer instructions — execution contract

These instructions supplement the recovered charter and govern this cleanup. Keep this section and the owning acceptance criteria current as the maintainer clarifies scope; use issue comments for dated evidence and implementation updates rather than a separate repository progress ledger.

Rust size and completion

We definitely do not want more than 1M lines of rust code at all

I want you to get started on that work

Your goal is address and check all those checkboxes in the umbrella issue

  • Reduce the Rust footprint below 1,000,000 lines using a declared, reproducible measurement. Report physical lines and executable SLOC distinctly and break out first-party, inline/dedicated tests, generated, and vendored code. Do not meet the target by silently excluding categories, compressing formatting, moving code to another repository, or weakening tests/security.
  • Complete every acceptance item in this umbrella with evidence. A proposal, audit, passing text scan, or one completed cleanup slice is not overall completion; blocked or unverified work remains unchecked.

MvmClient and mvm-studio: library functions, never CLI backfill

We need to make sure that the MvmClient exposes all functionality and never drops into a Command::new() or the same to execute AND that it supports the mvm-studio (../mvm-studio) project's goals through the library functions, NOT through Command

Track implementation with #4415 and the native-lifecycle boundary in #4414. Missing library functionality must be implemented in the library, not replaced by a hidden CLI callback, runtime re-export, or a differently named spawn wrapper. CLI, MCP, Studio, hostlib, and language SDKs must consume the same authoritative services.

  • Build the Studio→MVM capability matrix: 13 requirement rows with pinned sources/tests, distinguishing verified hermetic behavior, unwitnessed runtime parity, unsupported/planned capabilities and missing integration. Current-pin Studio/live parity remains unchecked.
  • Expose the required operations through typed MvmClient/client-library APIs and appropriate hostlib/SDK bindings, including failure, cancellation, cleanup, policy, and audit semantics. Do not claim parity merely because a method exists or returns unsupported.
  • Remove Studio's subprocess-backed operation backfill, CLI discovery, and related legacy adapters after library replacements are functional. Studio's local operations must work without finding or executing mvmctl. Studio #30 records the local-first retirement landed in PR #31 (94a470d36f): gateway/sidecar/CLI-discovery and shell-plugin surfaces removed; existing local machine operations use MvmClient. Native GUI/runtime, missing typed operations, transitive spawn audit and SDK parity remain separate unchecked rows below.
  • Audit the full reachable production call graph, not just literal Command::new sites: std::process, tokio::process, aliases, helper factories, shell/exec/spawn APIs, native process calls, deferred callbacks, and transitive runtime paths. Separate test-only processes from production behavior and record every real spawn's purpose and authority.
  • Resolve the exact backend/process boundary against PS-21: Complete typed VMM lifecycle without shell or utility processes #4414 and the maintainer's stricter instruction. Existing narrowly approved VMM/role-process decisions do not authorize CLI/utility fallbacks. Do not silently preserve an exception that conflicts with this instruction, or collapse signer/parser isolation merely to eliminate a process.
  • Extend regression enforcement to the actual client and consumer surfaces. Combine structural checks with real public-API success/failure tests proving supported operations work with CLI execution unavailable and forbidden spawn paths fail the tests.
  • Validate Studio integration against the resulting library contract, plus matching hostlib/SDK parity. No Studio integration pass is claimed until its build/tests and relevant runtime witnesses actually run.

Updated evidence after attaching Studio: the earlier sibling checkout was stale. The attached Studio worktree has already retired StudioBackend, SubprocessBackend, and CLI discovery; src-tauri/src/machines.rs::build_client calls connect(Target::Local) directly. Accepted Studio ADR 0005 requires library-only machine operations. Do not duplicate that completed removal. Stale source comments and historical sprint entries still describe the retired backfill and need correction. The remaining explicit Studio process launch found in this bounded scan is the gateway sidecar; ADR 0005 distinguishes it from local machine verbs, but the full transitive process audit remains open.

MVM's current xtask check-no-cli-shellout scans SDK and hostlib sources but explicitly excludes mvm-client; mvm-client::secret::source::SourceResolver can invoke password-manager CLIs through helper_command_with(...).spawn(). A clean direct Command::new grep therefore would not establish the requested guarantee. All four ecosystem worktrees are now attached. No library/Studio parity or live-runtime acceptance is claimed from this source inspection.

Host secret storage and future AWS KMS

The maintainer requires a trait-based host secret-storage boundary: local host storage now, with a future AWS KMS-backed key-management/encryption option. AWS KMS is explicitly confirmed, not Secrets Manager or a guest secret service. This is part of the highest-priority joint #3731/#4839 work, coordinated with PS-21/#3730/#4415 and existing secret ownership.

  • Inspect existing SecretStore, SecretService, SecretResolver and KeyProvider boundaries. Reuse them; no duplicate trait/AWS stub. Confined-resolver/provider custody and KMS envelope acceptance remain open. Preserved detailed receipt.

  • Establish the smallest typed, library-owned local-host implementation and provider seam needed by CLI/Studio. Retain authorization, audit, error/refusal semantics, secret-safe types/logging, and host-only material custody. No hidden provider CLI subprocess, guest plaintext, or parallel source of authority.

  • Define the future KMS integration contract explicitly: what is encrypted/stored where, key identity and access policy, ciphertext/context binding, failure/unavailable behavior, and provider configuration. Do not add an AWS SDK, dummy remote implementation, or Secrets Manager dependency merely to claim extensibility. Remote implementation follows reviewed scope and credential/identity decisions.

  • Add meaningful local success/failure and custody tests plus provider-contract tests where justified. Record dependency impact and client/consumer coverage; do not claim live AWS operation or completed KMS integration from an interface alone.

  • Land direct-keyring false-success/index fix #4858: 11517ede496ba2d262861cc0e9aa3bc614fe8545. Canonical receipt: reviewed file hash retained; PR CI and protected merge-group40965475636 passed. Auto fallback unchanged; native keychain, KMS and broader custody acceptance remain open.

PS-21: shared work with product umbrella #3731

Maintainer direction: work both #3731 and #4839. This cleanup umbrella supplements—not replaces—the agent-sandbox product umbrella. Its remaining PS-21: Keep the CLI thin over mvm-client is owned by #3730, with implementation/closure gates in #4412, #4413, #4414, #4415, #4416 and paired image-contract work in tinylabscom/mvm-images#67. Existing PS-21 acceptance remains authoritative; do not open a duplicate implementation track.

CLI recovery lifetime — partner handoff and #4655

The maintainer supplied the partner handoff and asked that it inform CLI work. Live #4655 confirms the blocker: native HVF entrypoint/pack health boots refuse until verified input custody and a held recovery lifetime exist. This is separate from snapshot-exit observability (#4096), from #84 completion/audit observations, and from foreground mock-client diagnostics.

  • Resolve macOS HVF: entrypoint boots (machine run --entrypoint, pack build health boot) are refused until native input custody lands #4655 ownership: PS-21 coordinator explicitly released the historical reservation and confirmed no active implementation/PR. One dedicated owner, “Own HVF entrypoint custody recovery,” now owns the bounded current-source lifecycle/design and subsequent implementation. Reservation and boundaries. Recovery design, implementation and live acceptance remain unchecked.
  • Specify and verify the approved recovery receiver/lifetime contract. The maintainer approved a minimal unprivileged per-VM birth-in-owner role conditional on safety: original handles/resources, authenticated recovery, signing-key isolation, bounded failure/cleanup and independent review. Approval resolves the role-direction decision; exact implementation, authority identity and post-CLI-exit behavior still require verification.
  • Expose that lifecycle through the typed client/library boundary used by CLI and Studio. A process host, if required, needs an approved identity/authority/lifetime contract; no generic command replay, hidden CLI operation backfill, duplicate supervisor, or reuse of another security role without approval.
  • Add failure-path evidence for CLI exit/disconnect during uncertain execution, failed recovery handoff, repeated recovery, stale generation/identity, and eventual authenticated completion/cleanup. Refuse unsupported transitions rather than reporting success or losing the owner.
  • Only after the product custody/lifetime implementation lands, remove both Firecracker-only gates in macOS HVF: entrypoint boots (machine run --entrypoint, pack build health boot) are refused until native input custody lands #4655 and record the actual macOS HVF entrypoint exit-code and pack-health/signing scenarios. Keep the current refusal and counted gates until then. A mock, compile check, snapshot observer, or Firecracker pass cannot close this item.

This handoff guides implementation; it does not itself choose a new supervisor architecture, assign the exclusive writer, authorize live execution, or supply a passing witness.

No legacy support requirement

For any future prompts in this session, make sure the umbrella issue reflects that and contains the content and intent.

Also we don't need to support any legacy paths

The no-legacy instruction removes backward compatibility as a reason to retain an obsolete path; it does not waive security requirements or authorize silently losing required Studio/library functionality. Where it supersedes earlier compatibility-preservation wording in this issue or the runbook, this instruction takes precedence.

Protected core goals — cleanup must preserve these

Latest maintainer instruction:

Make sure we retain all "fire-and-forget" tracing log messages as that's a core goal

Other core goals:

  • Best UX/DX
  • fast startup time -- <300ms cold start, <50ms warm start
  • multiple backends (HVF, Firecracker, libkrun, wasm, WHP (future))
  • tracing everywhere
  • vsock everywhere (microvm to/from host)
  • no secrets leak into a microvm

These are protected product requirements, not candidates for deletion to meet line/dependency/CI budgets:

  • Retain all fire-and-forget tracing messages and observability coverage. Removing AI-like narration means removing unnecessary prose/structure, not useful tracing. Preserve non-blocking tracing behavior and the existing context/correlation, redaction, delivery/loss reporting, and shutdown/flush contracts. Do not invent an unbounded queue or discard events silently to make an operation appear fast.
  • Tracing everywhere: preserve instrumentation of important lifecycle, policy, backend, failure, cleanup, and cross-boundary paths. Payloads must be safe metadata, never secret values. A trace/export change must be reviewed as an observability change, not incidental cleanup.
  • Security audit is not disposable diagnostics. Keep signed-audit integrity, required persistence/flush, and fail-closed behavior. The fire-and-forget requirement does not waive mandatory audit evidence or authorize detaching security work that must finish before success.
  • Best UX/DX: simplify installation, build, library use, diagnostics, and recovery as well as code. No hidden CLI fallback, repeated compilation, misleading success, or new configuration ceremony. Preserve Studio/library parity and typed actionable failures.
  • Startup targets: cold start <300 ms; warm start <50 ms. Use the original invocation-to-ready measurement and declare the exact candidate, backend, host, workload, cache state, and cold/warm definition. Do not exclude authentication, admission, required audit/durability, or other user-visible work to pass. Preserve any stricter existing percentile/per-sample budgets; do not reinterpret these targets as averages or relax the thresholds.
  • Backend coverage: preserve HVF, Firecracker, libkrun, and WASM as supported product paths. WHP remains a future goal, not a current-support claim or a reason to add speculative scaffolding. Retiring optional native Cranelift development compilation is not permission to remove WASM execution. “No legacy paths” does not mean deleting a required backend or its real isolation/platform boundary.
  • MicroVM ↔ host transport: preserve the vsock architecture, authentication, and no-guest-NIC invariant. Do not introduce a guest TCP/NIC/TAP/bridge alternative or fallback to simplify a backend. Keep backend-specific implementations behind the canonical transport contract.
  • No secret values in a microVM: keep secret material and substitution/custody on the host under the approved subsystem. Guest placeholders/references must not become plaintext credentials in environment variables, argv, files, logs, tracing, snapshots, or fixtures. Preserve boundary validation and negative leakage tests; a working demo must satisfy this constraint too.

Acceptance evidence:

Security and product boundaries

  • Preserve the design governed by Agent-sandbox product surface: close every gap (tracking) #3731, security guarantees, traceability, and mailbox designs. Prioritize demo-tagged work while respecting active ownership.
  • Preserve no-guest-NIC architecture, authenticated vsock, host-only secret-value proxying, signed ExecutionPlan enforcement, audit integrity, and meaningful backend/telemetry boundaries.
  • Preserve fail-closed behavior, isolation, authorization, network restrictions, secret handling, update verification, supported platforms, and released contracts.
  • Prefer deletion, std, existing dependencies/helpers, and direct Rust. Do not replace mature cryptography, signature verification, hostile-input parsers, serialization, protocols, or memory-safety-critical code merely to improve a count. Follow required owner decisions, threat analysis, and adversarial testing.
  • Keep real platform, trust, privilege, protocol, lifecycle, unsafe-code, and public-API boundaries. Remove ceremony rather than security structure.
  • Respect repository ownership: MVM runtime/interfaces; mvm-packs application/agent packs and pack policy; mvm-images Linux image layer under the current migration contract; mvm-assurance scanning/assurance; mvm-ops outreach/opportunity workflows.

Additional canonical goals found during documentation audit

The maintainer requested coverage against README, ADRs, issues, and PRs—not just the short core-goals list. The following explicit obligations supplement the existing checklist. Audits distinguish documented intent, landed source, and witnessed behavior; this section does not declare them implemented or validated.

Security posture and installation

  • Map the current shipped claims in MVM README/ADR-001 to retained enforcement and meaningful witnesses: host-filesystem isolation except explicit shares, privilege separation, dm-verity, sealed-production DevOnly/shell/PTY exclusions, bounded/fuzzed hostile-input protocols, signed audited execution plans, content-addressed artifacts, default-deny egress, bound host services, host-held secret substitution, provenance, CVE/SBOM evidence, and release/update signature verification. Keep preview claims visibly separate from shipped guarantees. Done via docs(contracts): claims witness-adequacy matrix and legacy compatibility classification (#4839) #5432 (390c5f6c): specs/contracts/claims-witness-adequacy.md maps ADR-001 claims 1-15, 19, 20 and 21 to enforcement locations and each cited witness, classifying every witness as a behavioural outcome test, a source-text scan, a fixture or mock, or a CI lane, with CI freshness and the documented limits carried through unchanged (no claim was upgraded). Preview rows 16-18 are in a separate section and not promoted. All 154 distinct fn: witnesses resolve and check-claim-catalog passes (21 claims, 174 witnesses). Recorded, not fixed: text-scan and weak witnesses (claim 20 fresh_install_*, claim 2 constant assertions, claim 19 argument parsing, claim 10 ci:single-network-path anchored to a step title) have replacement proposals in section 5 that are not implemented; claim 3 still has no KVM tampered-boot lane.
  • Preserve relocatable installation and the documented no-host-Nix/no-Docker prerequisites, with source-build prerequisites distinguished from installed-release UX. Preserve prepared/cache-only launch semantics rather than hiding download/build work inside measured startup.

Image and application trust are distinct contracts

Canonical sources: mvm-images README, SECURITY.md and REVOCATIONS.md; mvm-packs README/README.packs.md; MVM ADR-054/055 and the linked migration issues.

  • Preserve the Linux-only image producer boundary and generic default/rootless profiles across both architectures. Keep base-contract bytes, fixed identities/boot ABI, full producer-member coverage, and direct VMM/rootless witnesses; do not add application-specific packages, MVM runtime binaries, or MVM-source inputs to mvm-images.
  • Verify the staged image migration and release order through mvm-images#49/feat(mvm-supervisor): plan 37 E1 — false-positive circuit breakers #64 and mvm#4100/Release lane is red: e2e control-plane failures and archive-smoke bootstrap gap block every release witness #4764: a compatible same-version signed CLI/runtime and installed-product boot evidence precede Linux-only publication and consumer image-lock advancement. Source definitions without an MVM input are not completed-release evidence.
  • Keep image-set identity (root/member table, profile, architecture, base contract, release provenance) distinct from application identity (exact descriptor bytes, archive SHA/size, guest architecture, independently enrolled bundle key, runtime compatibility). Consolidate helpers only where semantics truly match; never create competing identity authorities. — Evidence (2026-11-06): test(packs): guard pack catalog, descriptor and revocation trust boundaries #5142 (merged) adds an_image_set_signer_cannot_sign_an_application_descriptor and a_flipped_archive_byte_of_the_same_size_is_a_digest_refusal beside the existing identity refusals; each guarded behaviour was broken locally and its test failed (digest check disabled, publisher trust widened with image-set identities).
  • Preserve one generated pack catalog with exact-byte manifest hashes, independent manifest/signature verification, publisher policy, and separate bundle trust/admission. Catalog discovery or a descriptor naming a key must not enroll or authorize that key. — Evidence (2026-11-06): test(packs): guard pack catalog, descriptor and revocation trust boundaries #5142 (merged) adds catalog_hash_binds_the_exact_manifest_bytes and catalog_discovery_and_a_matching_hash_enroll_and_admit_nothing (fetching the index, searching, and a matching-hash pull that fails on signature leave MVM_HOME with no trust key, policy or pin); mutation-checked (catalog digest check disabled together with a state write).
  • Preserve separate image and pack revocation authority, signer identities, freshness bounds, and consumer enforcement. Immutable historical signed artifacts remain verification evidence; no-legacy execution cleanup does not authorize rewriting or deleting them. — Evidence (2026-11-09): merged #5142 rejects cross-authority feed signatures and image-set/CLI signer substitution; #5216 confines built-in bundle-author keys to authenticated installed applications with revocation checked before lookup; #5217 refreshes the separately signed official registry-pack feed, checks stale/rollback and additive operator feeds at install and launch/admission. On base 3b827982ff, focused image/registry authority, rollback/wrong-signer, official/operator feed, revoked-bundle and distinct-store tests passed (including the published historical image-set fixture under host-state,manifest-verify); xtask check-bundle-trust-sites passed. These PR diffs do not rewrite historical signed fixture artifacts. This is preservation/enforcement evidence only, not a current published/installed product witness or completion of the separate image/pack release boxes.
  • Preserve atomic immutable publication across the required architectures/profiles, reproducibility and SLSA/SBOM subject coverage. Component checks, observer reports, unit tests, version probes, and local reproduction are bounded evidence, not substitutes for final published/installed artifact admission and boot.

Studio and MVMD scope and contract obligations

  • Reconcile Studio#19's explicit single-host/local product scope with accepted legacy fleet ADRs and Studio#30. Record the retirement decision before deleting fleet/auth/observability behavior; do not recreate the absent MVMD client/gateway or claim that sibling symlinks solve a removed API.
  • Coordinate—not duplicate—Studio PR#29's local typed MvmClient telemetry adapter and its proposed ADR0008 acceptance gate. Preserve bounded cursor paging, cancellation, selected-machine attribution, stale-cursor refusal/reset, unavailable/not-provisioned states, and explicit fixture mode. Successful PR CI is not a merged/live product witness.
  • Preserve MVMD V1's independent contract boundaries: no runtime/framework/transport types in authority contracts; hard placement constraints never become score penalties; billing stays integer microunits; connection establishment is not authorization; remote mutations remain audience/generation/time/nonce-bound with a destination-host refusal path; mailbox plaintext remains unavailable to controller/router/store APIs; queues/frames/retries stay bounded.

Conflicts to resolve rather than silently reinterpret: the README's current 300-ms warm refusal ceiling is not evidence of meeting the maintainer's <50-ms warm goal; Studio's old gateway startup model is not its desired local-library architecture; historical migration release numbers are not the current candidate; future WHP and draft roadmap capabilities are not current support claims.

Accepted contracts and roadmap dispositions from the 58-ADR review

The MVM audit inspected all 58 ADR status headings (001–057 plus 110), README, the live issue/PR inventory, and selected owning contracts/issues. Studio/MVMD and images/packs audits supplied their canonical-source matrices separately. This establishes a goal/disposition inventory—not exhaustive implementation verification or a live witness. Historical/proposed architecture must not silently displace shipped behavior.

Disposition rule: preserve current required capabilities; explicitly identify preview/proposed/future work and its owner; retire obsolete execution paths only with the current owner decision and complete caller/test/docs cleanup. This goal inventory does not turn every future roadmap feature into a prerequisite to finishing a bounded cleanup slice.

Workstreams and acceptance checklist

Each category requires evidence-backed findings or an explicit, supported conclusion that no change is warranted. Check items only when the outcome is verified, not merely proposed or locally reviewed.

1. Establish baseline and ownership

  • Verify the runbook's required release baseline and record its exact tag/commit, or obtain an explicit change to that gate before new implementation.
  • Inventory current cleanup diffs, branches, PRs, and active owners; link them here without overwriting unrelated work. Inventory evidence (verified 2026-11-03 at 3d17ff9fdd; 2 open PRs, 75 unmerged cleanup branches reconciled to active lanes).
  • Record supported binaries, guest artifacts, targets/features, released contracts, and security invariants. Use the repository graph and verify its coverage. Done via docs(contracts): record fresh graph coverage and name workstream owners in the cleanup inventory (#4839) #5383 (00cdc7f9): the inventory in specs/contracts/cleanup-inventory.md §1 covers the packages, binaries, guest artifacts, features, released contracts and security invariants, and the graph was reindexed in full mode (2026-11-12, main at aaf74fcb11, 106,437 nodes) and its coverage re-checked: the binary entry points report fresh and the mvm-hostd, mvm-agentd and mvm-builder-guest src/bin scopes are no longer excluded. Remaining gaps are recorded there (two CLI command directories excluded by name, fuzz corpora and virtual environments, five partially parsed files). Coverage is a best-effort signal, not proof of completeness.
  • Split the inventory into atomic child workstreams with owners, dependencies, acceptance criteria, and validation commands. Done via docs(contracts): record fresh graph coverage and name workstream owners in the cleanup inventory (#4839) #5383 (00cdc7f9): the workstream table (W1-W17) carries owner, boxes, dependencies, acceptance and validation commands. Owners are accountable roles (maintainer, runtime owner, producer and consumer owners, PS-21 coordinator), not named individuals, because the issue has no assignees and the repository has no CODEOWNERS; a named person replaces the role.

2. Remove AI slop, duplication, and unnecessary structure

3. Reduce dependencies and extraneous crates/features

4. Explain and fix excessive/repeated release compilation

  • Reproduce the maintainer's actual release-build workflow and identify what the approximately 1,017 entries count; do not assume they are unique third-party packages.
  • Separate unique packages from host/guest targets, profiles, feature-resolved units, procedural macros/build scripts, toolchains, and genuinely duplicated work.
  • Diagnose cache/target-directory mismatches, changing environment inputs, over-broad build-script reruns, repeated hashing/code generation, and redundant packaging/build invocations. Done via docs(deps): record release-build unit counts and repeated compilation (#4839) #4888 and docs(contracts): release-build timings, binary contribution and build diagnosis (#4839) #4988 (specs/contracts/build-dependency-decisions.md, "Diagnosis"): a five-row table covering cache/target-directory mismatch, environment inputs, over-broad build-script rerun, repeated hashing/generation and redundant invocations, backed by timed runs. The over-broad rerun-if-changed on crates and src in mvm-cli's build script is diagnosed and recorded as found, not fixed; fixing it and demonstrating the result in the release workflow is the separate open box below.
  • Record comparable clean release-build time, no-change rebuild time, repeated compilation, and final binary/guest-artifact size, with architecture, target, profile, stripping, compression, and environment.
  • Demonstrate the accepted fixes in that same real release workflow and document remaining necessary repeated work. Done via docs(deps): record release-build unit counts and repeated compilation (#4839) #4888, docs(contracts): release-build timings, binary contribution and build diagnosis (#4839) #4988 and docs(contracts): record the #4839 section 3 applied state #5044 (specs/contracts/build-dependency-decisions.md, "The accepted fix, shown in the same workflow" and "Repeated work that remains necessary"): the accepted fix, the embed content store at ~/.cache/mvm/embed, was shown in the same release-build command, clean target directory and host with only the store differing (r3 against r4: 512.9 s against 372.2 s, 27 percent less; the mvm-cli build script 150.9 s against 0.9 s; identical mvmctl SHA-256). The remaining necessary repeated work is documented: any edit under crates/mvm-cli costs about 160 s (one codegen unit and fat LTO), any file change under crates or src reruns the mvm-cli build script, 343 packages build up to three times (profile and unwind constraints, each recorded), and the first build after the store is lost spends 150 to 180 s cross-compiling five guest binaries. Limits: a warm-store zigbuild run was not taken; the dependency reductions are within the run-to-run spread, so no time saving is claimed for them; the over-broad rerun-if-changed on crates and src was diagnosed and deliberately not changed, because those directories feed the source-dirty stamp, and is listed as remaining work, not as a fix.

5. Simplify toolchain, development, and CI paths

  • Complete bounded macOS fixture/source-identity and owned-child test-performance follow-up Make pair-image tests hermetic and bound macOS validation time #4840, coordinated with Hard gate: restore fast local feedback and bounded CI/release latency #4657 and PS-21: Replace checkout identity and manifest emission with in-process APIs #4412. Require an immutable source baseline, no production identity/custody bypass, identical-feature timing, and a completed native macOS witness; do not treat the interrupted feat(run): finish canonical launch-plan command support #4838 run as a diagnosed regression or a pass.

  • Verify and complete the ordinary-build/CI Rust 1.97.1 pin and Cargo-wrapper/caller consolidation described in surviving work context.

  • Retire the optional native Cranelift development path while preserving WASM execution and required WASM support.

  • Ensure ordinary Cargo and recipes share the intended cache within a worktree without cross-worktree contamination. Evidence/limits.

  • Preserve supported-platform, WASM, fuzz, eBPF, supply-chain, and release coverage; local validation must match the owning CI gates. Done when (maintainer-approved wording, comment): every CI coverage class has a named owning job in a manifest verified by a gate; removing a lane breaks the gate. Done via test(ci): gate CI coverage classes; classify workflow-reading tests (#4839) #5437: xtask check-ci-coverage (in check-all) maps each coverage class (supply-chain, fuzz, eBPF, WASM, release, and the Windows, aarch64 and macOS platforms) to its owning workflow job (10 jobs present), checks the job is a live key with the claims ledger's ci_anchors parser so a commented-out job does not count, and fails on any check-* gate a workflow invokes that check-all does not run. Three negative tests show a removed job, a commented-out job and an unrun gate are each reported. Limit: it checks that the job exists, not that the right step is still inside it.

  • Measure CI against the ≤30-minute goal. Do not remove a slow gate without identifying its invariant and providing equivalent evidence.

  • Coordinate embedded-toolchain/Nix work with its existing owner rather than duplicating it.

6. Simplify capability surface, Rust, tests, and documentation

  • Inventory capabilities, flags, environment/configuration options, modes, backends, compatibility layers, and supported combinations; retire only those shown obsolete.
  • Review ownership, allocation, errors, state transitions, cancellation, lock/task ownership, cleanup/rollback, unsafe/FFI boundaries, and panic paths affected by changes. Done when (maintainer-approved wording, comment): split. Checkable part: clippy::undocumented_unsafe_blocks is deny workspace-wide and clippy is clean, with a reviewed-to-date table recorded. The ongoing part moves to the PR checklist. Done via chore(lints): deny undocumented_unsafe_blocks workspace-wide (#4839) #5438 and docs: lifecycle review ledger and PR checklist item (#4839) #5444: clippy::undocumented_unsafe_blocks is deny workspace-wide and clippy is clean (about 200 SAFETY comments written after reading each site; three packages that silently skipped the lint table now inherit it; Linux cross-check included); the reviewed-to-date table is specs/contracts/lifecycle-review-ledger.md (reviewed areas with the PRs that fixed defects, the files read, a "Files NOT read" section, and the five known-unfixed lifecycle gaps with owner and next step); the ongoing part is item 7 of the PR checklist in AGENTS.md (state the state transitions and resource owners and add a failing-before test). Limit: the review is not exhaustive; the ledger says plainly which files were not read (parts of hvf_restore.rs, kernel_boot.rs, flowmux and libkrun), and Linux-only code behind features outside CI's set, aarch64 and musl arms and the excluded fuzz and eBPF crates were not linted.
  • Replace misleading existence/text/internal-wiring tests with meaningful outcome tests where practical; retain security, compatibility, recovery, platform, and user-visible BDD coverage. Done when (maintainer-approved wording, comment): tests that read workflow, justfile or source text are limited to an allowlist where each entry states the gate it owns. Done via test(ci): gate CI coverage classes; classify workflow-reading tests (#4839) #5437 and test(ci): allowlist tests that read gate text and ratchet new ones (#4839) #5446: xtask check-text-reading-tests (in check-all) fails on a new test file that reads workflow, recipe, script, nix or install.sh text, or a new test in a listed file, unless xtask/data/text-reading-tests.txt has an entry with a maximum test count and the gate it owns (19 files seeded, each with its owned gate; five negative tests); release_assets.rs and github_actions_extended_e2e.rs now carry per-test owner lines. Two pin tests were deleted and one tightened (test(ci): gate CI coverage classes; classify workflow-reading tests (#4839) #5437). Limit: no test under tests/ or crates/*/tests includes Rust source text through include_str! today, and inline unit tests that read source are not scanned; claim 20 fresh_install_* text scans stay and their replacement is a proposal in the claims matrix.
  • Trace affected security claims through reachable enforcement and regression tests; fix gaps or narrow unsupported claims.
  • Synchronize active docs, CLI reference, recipes, CI, release instructions, and actual behavior; remove obsolete scripts/references only after checking consumers. Done when (maintainer-approved wording, comment): the docs gates pass and name every checked surface; prose package counts either match cargo metadata or are removed. Done via docs: sync manifest sizing key, release instructions and recipes with behavior (#4839) #5351, docs(repo): complete root layout inventory (#4839) #5240, docs(repo): inventory third_party, data dirs and nix/packages owners (#4839) #5347 and chore: gate process labels in comments; drop stale package counts (#4839) #5410: check-cli-help-matches-docs, check-doc-links, check-doc-claims, check-documented-env, check-spec-hygiene and check-root-layout are all in check-all and passed in the merge queue; the CLAUDE.md prose package count was removed (chore: gate process labels in comments; drop stale package counts (#4839) #5410); the inventory counts were set to the measured 28 packages and 52 bins and the stale mvm-egress-proxy row removed; the removed vcpus key and just release::image references were fixed (docs: sync manifest sizing key, release instructions and recipes with behavior (#4839) #5351). Limit: the inventory counts are a dated measurement and no gate ties them to cargo metadata.
  • Keep specs limited to active ADRs, stable contracts/security claims, and linked exceptional design attachments; retire obsolete progress ledgers after checking workflow consumers. Done in PR chore(specs): retire the cleanup progress ledgers #5022 (merge commit e4ea8ef, CI green): cleanup-active-work.md and cleanup-preservation-ledger.md retired (history under the specs-archive-2026-11-02 tag), both added to check-spec-hygiene's retired-dashboard list; consumer grep found no workflow/tooling references; check-spec-hygiene and check-root-layout clean.

Demo-policy coordination gate

A subsequent #84-owner report adds this constraint; the repository-qualified issue link and authoritative schema/commit still need confirmation before handoff:

  • The schema field EnvironmentPolicy.request_budget may be optional, but the demo requires exactly {"max_requests":1,"max_spend_microusd":500000,"model":"claude-haiku-4-5-20251001"}. Omission or widening must refuse under the strict Anthropic wire policy.

  • The prior descriptor abbreviated 663e... is historical, not export-ready; this abbreviation is not a usable artifact identifier.

  • Final paired consumer CLI/runtime source must include the contract and enforcement once landed. Coordinate contract/dependency cleanup with that owner.

  • The old three-turn wrapper does not prove client compatibility with beta-header refusal, token caps, or the one-request limit.

  • Link the authoritative demo issue, schema, and landed commit; verify paired CLI/runtime enforcement and required client compatibility before artifact handoff. No live/client/model validation is claimed here.

Current evidence and candidate triage

These are starting points from surviving reports, not completed umbrella acceptance criteria:

  • A scoped review of the compiler/wrapper/cache cleanup reported no actionable regressions and passing targeted Python/shell/guard checks. Full Cargo validation, live VM/Nix execution, release measurements, and CI timing are not established by that review.
  • mvm-fc-lifecycle: deletion candidate reported as an isolated privileged prototype with no default integration. Verify active ownership and deliberate prototype requirements before declaring it extraneous. Its standalone dependency closure is not automatically removable from other shipped artifacts.
  • mvm-mcp: candidate to fold into the CLI while preserving MCP functionality, protocol tests, bounded transport, authorization, and signed-plan/audit behavior. Expect a first-party package-boundary reduction, not removal of its entire shared third-party closure.
  • mvm-net: retain its backend-neutral/default-deny enforcement boundary unless a separately justified architecture change preserves it. Small size alone does not justify removal.
  • network-perf and dev-watch: reported to have live consumers; do not treat them as unused without further evidence.

PS-06 coordination: distinct from the HVF-first demo

The existing PS-06 owner retains #3716 and tinylabscom/mvm-packs#12, including all five stages below. No duplicate source writer, remote validation host, release job, or native lifecycle owner is assigned here.

  • Finish current-source Linux workspace/Clippy/all-target/BDD/format validation. — Evidence (2026-11-06, exact source 40ce000, the v0.27.0-rc.3 release commit): ci-main run 42218673590 succeeded for Test (main), Test Linux and conformance, Test workspace (aarch64), Test workspace (doctests + feature suites), BDD conformance, BDD live PS-11 frozen volume (Linux, Firecracker), Test eBPF telemetry load/attach, Test release profile (overflow + no debug assertions) and the lint feature-coverage matrix; PR release: v0.27.0-rc.3 #5162 CI succeeded for Lint core (fmt + clippy), Lint feature combinations (clippy), Invariant (xtask check-all) and Workspace shard 1. A Release dry-run on the previous main (06a6d7a, run 42186498320) also passed end to end.
  • Establish original-owner persistent Firecracker lifecycle through per-active-VM supervision, detach/stop, and freshly admitted start. Deferred past the demo by maintainer decision (2026-11-14); not complete. Tracked, with the preserved contract and model and what must happen to resume, in Persistent Firecracker lifecycle owner: deferred past the demo (preserve the contract and model) #5522. This is the explicit, linked scope disposition the completion box allows; the box stays unchecked.
  • Preserve original signed metadata, failure cleanup/resource census, and one-way owner-only protected completion projection. Deferred past the demo by maintainer decision (2026-11-14); not complete. Tracked, with the preserved contract and model and what must happen to resume, in Persistent Firecracker lifecycle owner: deferred past the demo (preserve the contract and model) #5522. This is the explicit, linked scope disposition the completion box allows; the box stays unchecked.
  • Witness genuine released Linux producer A plus independent B, authenticated extracted-ELF H, original signed rootfs/verity/metadata/raw hash, accepted base lock, independent current revocations, byte rebuild, signing and attestation. Deferred past the demo by maintainer decision (2026-11-14); not complete. Tracked, with the preserved contract and model and what must happen to resume, in Persistent Firecracker lifecycle owner: deferred past the demo (preserve the contract and model) #5522. This is the explicit, linked scope disposition the completion box allows; the box stays unchecked.
  • Witness transient and persistent consumer lifecycle/refusals/cleanup with exact evidence for the owning checkboxes. Deferred past the demo by maintainer decision (2026-11-14); not complete. Tracked, with the preserved contract and model and what must happen to resume, in Persistent Firecracker lifecycle owner: deferred past the demo (preserve the contract and model) #5522. This is the explicit, linked scope disposition the completion box allows; the box stays unchecked.
  • Resolve the process-host design dependency before supervisor wiring: a typed library-owned lifecycle, exact process-host executable/source/signing identity, original Child custody (no PID-file resurrection), bounded startup data/FD handling, invoking UID/privilege bounds, authenticated generation/refusals, detach/stop/fresh admission, and release effects. The prior hidden-CLI bootstrap codec is groundwork, not approval for a hidden CLI supervisor or operation backfill. PS-21: Complete typed VMM lifecycle without shell or utility processes #4414 does not automatically authorize a new host role; do not repurpose broker/host-agent trust boundaries. The owner is preparing a focused review packet. Deferred past the demo by maintainer decision (2026-11-14); not complete. Tracked, with the preserved contract and model and what must happen to resume, in Persistent Firecracker lifecycle owner: deferred past the demo (preserve the contract and model) #5522. This is the explicit, linked scope disposition the completion box allows; the box stays unchecked.

PS-06 source tests do not close live/artifact acceptance. Preserve its existing isolated validation-host allocation; no competing builds/VMs. Firecracker evidence remains necessary for PS-06 but does not substitute for the first required HVF demo.

Low-priority terminal checklist view

Delivery and definition of done

For each child workstream: identify callers/contracts, classify compatibility and security effects, make the smallest coherent change, update behavior tests/docs, conduct independent reviews, resolve findings, and record exact validation and measurements. Keep skipped/unavailable/failing checks explicit.

  • All child workstreams have verified completion or an explicit, linked scope disposition; no unfinished checklist item is silently checked or deleted to close this umbrella.
  • Required validation is recorded: cargo fmt --all --check, cargo test --workspace, cargo clippy --workspace -- -D warnings, cargo check --workspace, and just check::gated where shared type shapes change, plus affected BDD/platform/security/integration/image/release gates.
  • Final before/after dependency/build/binary/CI evidence demonstrates the outcome; remaining risks and retained complexity are documented.
  • Active instructions/docs match the final behavior and repository boundaries.

Respect builder-VM and long-operation rules, worktree isolation, and unrelated changes. This issue authorizes tracking the requested cleanup; it does not independently authorize publishing branches, landing changes, billable infrastructure, destructive external operations, or weakening security contracts.

Coordinated runtime → pack → M4 delivery

The single governing checklist records accountable runtime/artifact/consumer owners, landed source milestones, the actual lifecycle-transcript snapshot refusal, retained-state/runner prerequisites, and the separate exact-tag, official-pack-publication and M4 approvals still required. Source merges and the deferred durable helper do not complete the parent release/native checkboxes.

Activity

  1. added
    cleanupRefactoring, simplification, dependency reduction, and cleanup
    on Oct 28, 2026
  2. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Execution started: Rust-size ceiling and first consolidation

    The maintainer has set an explicit goal of fewer than 1,000,000 Rust lines and asked that every umbrella acceptance item be addressed and verified. This is the full delivery goal, not permission to close the issue after one slice.

    Initial worktree baseline: 1,227,697 physical Rust lines in 2,808 .rs files, measured from rg --files -g "*.rs" (excluding build/state directories) and Python bytes.splitlines(). Includes comments and blanks; this is not executable SLOC. Path categories: 81,999 under third_party/ or crates/deps/, 98,362 in test/bench/example paths, and 1,047,336 elsewhere (including inline tests and potentially generated source). These categories are not a complete generated/test classification. No category is being silently excluded to meet the ceiling. A first-party/generated/vendor/test breakdown and a reproducible final count remain outstanding.

    Latest published release inspected: v0.22.0, published 2026-10-02, commit b6b77f83730bed54d52f5f8b9cdcd8d5136ca1de. This identifies a reference release; it does not resolve which release the original runbook meant by “next release.”

    In progress: #4542’s mvm-mcp consolidation into a private CLI module. Source and the issue audit establish a single production consumer and no independent published package boundary. Preserve protocol/drive/policy/error tests and the pinned tool contract; remove the package and redundant standalone example. Expect one fewer first-party dependency node, not hundreds fewer third-party dependencies. This alone will not meet the Rust-size goal.

    Preserving existing compiler/cache edits and the independently owned demo-policy work. The privileged Firecracker prototype is not being deleted while its relationship to #4414 remains unresolved. Graph lookup timed out, so this slice uses targeted source, manifest, and issue evidence. No new checkbox is marked complete yet.

  3. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Workspace update

    The cleanup thread now has attached worktrees for mvm, mvm-studio, mvm-images, and mvm-packs. This removes the Studio attachment blocker recorded above. Revalidate the library-parity findings against the attached Studio worktree, which is newer than the previously inspected sibling checkout, before implementing.

    Scope remains the full umbrella, including no legacy support, library-first Studio integration, and the Rust-size ceiling. Attachment is not a merge/publication authorization and does not resolve the separately reported Git index-lock blocker in the MVM worktree.

  4. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    First Studio library-parity cleanup implemented (validation blocked)

    On the attached Studio branch chore/library-validation-cleanup:

    • Replaced the duplicated machine-name grammar with mvm_client::validate_vm_name, preserving typed InvalidSpec errors and the library error reason. This closes concrete drift: Studio previously accepted 64-character names and leading/trailing hyphens that MVM refuses.
    • Added positive and negative boundary cases (1/63/64 characters, hyphen boundaries, invalid characters).
    • Removed the unused direct async-trait declaration/feature edge and obsolete comments describing the deleted subprocess backfill. No third-party closure reduction is claimed; other consumers still need the package.
    • Updated Studio sprint state under its repository rules. No legacy execution route was added, and no machine was started.

    Passed: direct rustfmt checks on both changed Rust files and git diff --check.

    Blocked: Cargo cannot load ../mvm/crates/mvm-client from the Studio Delta checkout because the attached repositories live under different parent directories. Studio also requires the ../mvmd dependency. just ci was attempted exactly as required but this checkout contains no Justfile. No Rust test, compilation, full CI, or live integration pass is claimed. These blockers must be resolved before checking the corresponding umbrella acceptance items.

    The MVM-side MCP consolidation remains uncommitted and not fully validated; its moved sources are local-only while the separately reported stale Git index lock prevents tracking them for Delta replication. No umbrella completion is claimed.

  5. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Maintainer clarification and dependency correction

    Maintainer authorized removing the stale MVM Git index lock, attached MVMD, and asked: “I thought mvm supplied the mvm-client... can we make sure that’s true?” Direction reaffirmed: “Simplify the heck out of this project.”

    Verified: mvm/crates/mvm-client/Cargo.toml declares the mvm-client package. Studio consumes that machine-operation library. The separate mvmd-client declaration in Studio is for its legacy fleet integration, not the MVM facade.

    The newly attached MVMD V1 tree has no crates/mvmd-client and no mvmd-gateway package. Its root README explicitly describes a replacement implementation; it exposes mvmd-types, mvmd-core, mvmd-api, the mvmd binary, and a detached mvmd-mvm adapter consuming MVM. Therefore the Studio build blocker is not merely checkout layout: its old fleet client/sidecar contract is obsolete. Do not resurrect an old checkout or invent a compatibility crate just to make it compile. Retirement/migration of the affected fleet/auth/observability surface needs an explicit current contract and acceptance decision; local MvmClient functionality remains required.

    The authorized stale-lock removal was performed only after checking for an owner and verifying that the lock did not change during inspection. The four moved MCP files are now Git-tracked and recognized by Delta. No commit, push, or merge occurred. MVM validation restarted with durable /tmp logs rather than turn-scoped scratch.

  6. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Maintainer request: “Post an issue in mvm-studio to give these details.” Created tinylabscom/mvm-studio#30 — Retire obsolete MVMD gateway integration and enforce library-only MVM access, labelled cleanup.

    The issue records the verified mvm-client vs mvmd-client ownership distinction; current MVMD V1’s missing legacy client/gateway; Studio’s already-completed CLI-backfill removal; the remaining gateway/sidecar and unused shell-plugin surfaces; required scope/ADR decisions; the existing uncommitted validation cleanup; and exact validation blockers. It links Studio #11/#17/#19/#18/#25/#12 and MVM #4414/#4415.

    Use Studio #30 for implementation ownership and evidence, with this umbrella retaining the cross-repository acceptance criteria. No acceptance item is marked complete by creating the issue.

  7. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Parallel cleanup results and validation status

    • Independent MCP consolidation review found no actionable regressions. It verified unchanged production dispatch/policy behavior, all 37 test attributes, fixture SHA256 9cc2502293c78f1e39746a9444ca2ad711aa08ce4afb8d9ca8c3004a77cb106d, and manifest metadata. This is source-review evidence, not a test-execution pass.
    • Integrated the capture worker’s bounded deletion: remove three private RPM/Pacman/APK providers whose ownership/version methods always returned None. Real dpkg→nix-index ordering remains; a new Linux-only regression test checks unsupported-manager observations remain unchanged. Net physical Rust reduction: 25 lines including the added test. No third-party dependency reduction is claimed.
    • Studio cleanup removed the unused shell plugin (Rust registration/manifests and npm dependency) and unused npm mvm-sdk; the required Rust mvm-client remains. The old gateway/sidecar retirement is still a separate design-dependent task in tinylabscom/mvm-studio#30.

    Validation exposed a harness/environment problem: background jobs inherited Delta’s per-terminal TMPDIR, which disappeared after the terminal call. pnpm failed before install; Clang failed to create a temporary file at MCP-test link time. Those are failures, not test passes. Retried with job-owned durable temporary directories and logs: MVM /tmp/mvm-cleanup-validated-5953tubt, Studio UI /tmp/studio-cleanup-validated-ib_bazb1. The MVM queue includes MCP/tool-gate tests, capture tests, Linux-target capture test compilation, workspace check, and Clippy. UI queue includes frozen install, tests, lint, typecheck, and build.

    Separately recovered previous workspace validation records: fmt passed; scoped tests, workspace check, Clippy, and workspace tests each timed out at 1200 seconds. No full-suite pass or ≤30-minute CI claim is made.

    The demo-readiness scout is still assigned the 12 current demo issues and active-owner/dependency reconciliation. Demo/security contracts remain unchanged; no publication, live VM/model execution, or issue closure is authorized by these reports.

  8. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Demo critical-path reconciliation — 12 tracked demo issues

    The original twelve issues below track full delivery and acceptance, not merely code presence. This comment is reconciled with the live umbrella ledger as of 2026-10-30; linked receipts distinguish completed source work from outstanding artifact/runtime witnesses.

    Completion rule for every box below: address the complete owning-issue scope; implement required changes; link reviewed PRs, passing validation and merged commits; and verify any required artifact/release/live acceptance. Existing landed work may supply evidence—do not create redundant PRs. A diagnosis, plan, open PR or partial source delivery is not completion. Separate signing, publication and live-execution approvals still apply.

    • mvm#4764 — Release owner: source foundations including fix(vmm): preserve peer EOF after socket timeout setup refusal #4879 are landed; complete qualified runtime, exact release candidate/tag and final release gates remain. No alternate release implementation.
    • mvm#4655 — Native custody/recovery remains incomplete. Builder-specific ownership and scoped test identity implementation are approved; original-session-only builder work is not general workload reconnect or completed native containment.
    • mvm#4511 — Existing signed-launch source is retained. A real pinned-descriptor-to-OCI fallback defect is reproduced and being fixed in the canonical classifier. Genuine signed installed-application launch remains unwitnessed.
    • mvm#4510 — All seven original source/hermetic criteria are checked after reviewed current-source validation; receipt. This full delivery item remains open on the genuine signed-application/platform dependency; no SIGKILL/power-loss proof is inferred.
    • mvm#4509 — Original criteria 1/2/3/4/6 checked with 109 passing cases; receipt. Genuine outer Sigstore application/full public CLI positive remains open. No injected verifier or inner archive signature substitutes.
    • mvm#4508 — Allocation parity remains established; final execution baseline requires the current signed runtime/artifact and approved execution boundary, not historical source smoke.
    • mvm#4507 — Demo umbrella still depends on qualified release/custody/policy, fresh archive and actual public-consumer witnesses. Historical runtime/archive inputs are not promotable.
    • mvm#4391 — Historical hard 300-ms ceiling result is not current percentile/cold-supervisor completion. Existing runtime owner retains measured-budget evidence; thresholds are not relaxed.
    • tinylabscom/mvm-packs#84 — Consumer source feat(demo): enforce bounded Claude consumer acceptance #4845/fix(policy): retain signed AI budgets through application folding #4859/fix(demo): prepare prompt pipe before consumer spawn #4870 is landed, including budget enforcement and prefilled stdin. Final released-input public search/pull/HVF one-request witness remains open; M4 already selected. No duplicate policy implementation.
    • tinylabscom/mvm-packs#77 — Supplementary correlated allow/deny rehearsal remains after final archive/application qualification, with its own applicable operator/model-call authority.
    • tinylabscom/mvm-packs#76 — Frozen FlakeImage source packet is ready; current closure gates. Fresh measured quartet, independent rebuild, runtime/base binding, official signatures/publication/readback remain. Old missing raw bytes are not fabricated; historical chore(mvm-guest): drop unnecessary as i64 casts in syscall_nr table #83 archive is not final.
    • tinylabscom/mvm-packs#31 — Broader runnable-environment acceptance includes SDK/PTY/vendor/publication beyond one demo request and remains open.

    mvm-images has zero currently open demo-labelled issues. This is not proof of image readiness; preserve its Linux-only ownership and do not add MVM runtime/source roles or publication shortcuts.

    Current critical path — 2026-10-30

    1. Finish reviewed builder original-owner/endpoint/durability/identity implementation; capture and volume safety remain independently tracked. Use existing published ABI-1 ARM inputs, no implicit Stage0 bootstrap.
    2. Execute the approved fresh isolated FlakeImage job only after those safety gates. The frozen source packet is not the executing CLI/finalizer identity or a complete root lock.
    3. Produce fresh measured final artifacts and independent reconstruction/provenance; verify current runtime/base/revocation binding and the actual one-request client contract.
    4. Obtain the separate official signing/publication authorization, publish through the existing publisher and verify readback/installed acquisition.
    5. Complete the final M4 public HVF witness and separately authorized paired allow/deny rehearsal; reconcile each original issue before checking its box.

    Budget/consumer source #4845/#4859/#4870 is landed; the older “wait for an authoritative contract” instruction is superseded. The exact client contract still requires pinned model claude-haiku-4-5-20251001, max_tokens <= 20000, no beta headers/service_tier/unsupported fields/server-side tools, and refusal on missing/widened budget, wrong model, second request or excess spend. A version probe, historical three-turn wrapper or budget flag is not the witness.

    All twelve boxes retain full owning-issue acceptance. Source merges do not grant official publication, paid execution, old-state cleanup or broader credential authority. Both umbrella bodies and every comment checklist remain in completion scope.

  9. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Full-goal audit requested and delegated

    Maintainer: “Look at the ADRs, the README.md, and the issues and PRs and make sure we’ve covered all of our goals. And then continue working with subagents.”

    Three non-overlapping read-only audits are now reconciling (1) MVM README/current ADRs/issues/PRs, (2) Studio + MVMD goals/contracts, and (3) images + packs ownership/trust/publication goals. Outputs must distinguish documented intent, landed source, and witnessed behavior, identify missing umbrella acceptance criteria, and respect current demo-owner reservations. A fourth agent is identifying substantial safe code-deletion candidates only; implementation selection follows the goals reconciliation.

    The audit explicitly preserves the latest core goals: all fire-and-forget tracing and correlation/redaction/flush semantics, signed audit, UX/DX, cold<300ms and warm<50ms, all supported backends plus future WHP, authenticated vsock, host-held secrets, mailbox design, and library-first parity. It also checks README/ADR obligations beyond that short list: UID/filesystem isolation, verity, sealed DevOnly bans, artifact signatures/provenance/revocation, CVE/SBOM evidence, relocatable installation, and real consumer/release validation. No goal-coverage completion claim yet.

    New executed evidence: MCP tests 37/37 passed; tool-gate tests 11/11 passed with durable TMPDIR. Studio frozen UI install, lint, typecheck and build passed; UI tests report 60 passed and 3 skipped across 9 files. Rust capture/workspace validation remains in progress. Studio Rust still has the obsolete MVMD integration blocker described in #30; UI success is not full application validation.

  10. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Studio architecture recommendation — not yet approved

    Maintainer asked: “Is that a good option?” about retiring Studio’s obsolete gateway/fleet/auth integration.

    Recommendation: local-first Studio now, not local-only forever. Retire the nonfunctional legacy mvmd-client / mvmd-gateway integration and its obsolete UI/configuration, preserve all current local machine/library functionality, tracing, telemetry, verified audit, and required authorization, and keep fleet orchestration in MVMD V1. Future remote Studio support should use a current typed client contract once its auth/tenancy/capability semantics are defined—not a compatibility bridge over the retired API.

    Alternatives: repairing the old integration preserves an obsolete architecture; immediately building full MVMD V1 integration adds new public/auth contracts and competes with the HVF-first demo. Local-first is the smallest current path consistent with Studio #19, ADR0005, and cleanup goals. It does not itself fix MVM’s HVF/runtime/release blockers or prove startup budgets.

    Important boundary: retiring legacy fleet authentication does not remove local authorization, signed admission/audit, secret custody, or required authentication on any future loopback server. Existing tracing on retained paths must remain. This is a recommendation for the decision tracked in tinylabscom/mvm-studio#30, not owner approval or permission to silently drop required functionality.

  11. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Owner-approved Studio retirement; implementation assigned

    The maintainer explicitly approved local-first Studio now, not local-only forever (“Yes, I approve”). Recorded the decision in tinylabscom/mvm-studio#30. An isolated worker now owns the end-to-end legacy gateway/fleet/auth retirement plus ADR/docs/tests, preserving local MvmClient operations, tracing/telemetry/output, verified audit, authorization, host-held secrets, existing user state, and the independent PR#29 telemetry work. No new remote compatibility stack; future MVMD V1 support requires a current typed contract. This does not authorize landing or publication. HVF remains the first required demo backend.

    Separately integrated the private CaptureRequestBuilder simplification: 102 fewer Rust lines across the two CLI deps-capture files, identical values at all seven constructors, no production operation/validator or audit/tracing changes. Parent compilation/outcome tests remain pending.

    Current validation: MCP37 and tool-gate11 tests passed; capture host11+4 tests passed. Linux-target capture compilation reached an environment blocker: missing aarch64-linux-gnu-gcc for tree-sitter-python. No Linux execution or cross-compilation pass is claimed, and workspace check/Clippy have not yet run in that chained attempt. Studio UI validation remains passing (60 tests passed,3 skipped; lint/typecheck/build passed).

  12. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    New bounded cleanup follow-up from #5 / PR #4838: #4840 — Make pair-image tests hermetic and bound macOS validation time. It tracks the real compiled-from-checkout coupling, stable-baseline reproduction, owned-child cancellation/diagnostics, and identical-configuration timing evidence. All acceptance items remain unchecked. PR #4838 has green reported CI (20,731 Linux workspace tests), but its failed/stopped native macOS run is explicitly not being marked green. The separate local-fixture curl removal in #4838 preserves integrity checks and removes repeated subprocess overhead; it does not claim to solve the pair-checkout coupling.

  13. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Disposition coordinated with the cleanup owner: PR #4838 retains #5’s specifically approved singular-entrypoint/string-env compatibility. The newer no-legacy mandate should remove those forms only in an explicit coherent follow-up with callers/tests/docs migrated together; it is not an unrelated edit or silent landing blocker for #4838. No legacy-removal checkbox is being marked complete. macOS fixture/performance follow-up #4840 is unowned and also links the broader #4657 performance and #4412 canonical-identity owners. This scope coordination does not substitute for independent review or landing approval.

  14. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Coordination with PR #4838 / launch-plan owner

    The #5 owner requested overlap coordination for PR #4838 at 8c709b7a817e8c59618d33277257d7917267758a. I independently checked its eight-file list; none matches our intended active cleanup edit scopes. We will not edit that PR branch or its files. This is not independent review or landing approval.

    The owner reports passing required CI (including 20,731 Linux workspace tests) and scoped local checks, but an interrupted >30-minute macOS workspace run with pair-default-image/cache failures and slow children. HEAD moved during that run; a clean-baseline regression is not established. Reported stack: derive_pair_key → open_mvm_checkout → probe_identity → Git attribute normalization of the real compiled-from checkout. The PR’s fixture curl→in-process-copy change reportedly reduced the same 39-test selection from 81.37s to 5.25s, with a feature-configuration caveat. These are owner-reported results, not rerun here.

    No current cleanup agent owns that macOS fixture/source-identity performance slice. Searches found the broad #4657 latency umbrella and #4412 identity-contract owner, but no dedicated bounded child; the #5 owner will create/link a focused issue with exact reproduction, stable-source baseline, hermetic in-process fixture requirements and timing evidence. It must not weaken canonical identity, share mutable Cargo targets, remove diagnostics or inflate timeouts.

    PR #4838 retains legacy launch-plan forms under #5’s separately approved compatibility scope. The newer no-legacy cleanup direction will be handled in a coherent explicitly tracked follow-up, not by silently rewriting another owner’s active PR. HVF-first demo remains the priority.

  15. auser commented on Oct 28, 2026

    @auser
    CollaboratorAuthor

    Continued execution

    Maintainer requested continued work on the umbrella checkboxes. The current MVM tree passes cargo fmt --all --check and cargo test --locked -p mvm-cli --lib commands::deps:: (32 tests, 0 failures). The scoped command took 299.72s including compilation; test execution was 0.11s. This is one run, not the controlled repeated latency evidence required by #4657/#4840.

    Workspace check, Clippy, the supported Zig-based Linux capture-test compilation, and workspace tests remain queued in the durable validation run /tmp/mvm-cleanup-final-checks-zrn50yxm. The earlier plain GNU cross-check failed for a missing cross-compiler and is not a pass.

    The approved Studio local-first retirement remains assigned to its separate worker under Studio#30. A different worker is investigating #4840 read-only before proposing fixture changes; no overlap with PR#4838 or canonical identity work is authorized. PR#4838 remains open at this check, not verified landed. No broad acceptance item has been checked merely because a scoped test passed.

  16. 380 remaining items

  17. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Final source-slice handoff for this conversation (not two-architecture release closure): mvm #5549 head caeb2a0d8a0ffc9cce56353d56f8e19430c89dd3 merged by another operator as 61348d65dc365131b61af93c9ac255dd20a50548 at 2026-11-15T07:49:43Z, with all reported PR checks green. Exact-head local cargo fmt --all --check, TMPDIR=/tmp cargo test --workspace including doctests, TMPDIR=/tmp cargo check --workspace, and TMPDIR=/tmp cargo clippy --workspace -- -D warnings passed. The first chained xtask check-all timed out in uvx pinned generator resolution after earlier gates; a separate exact-head UV_OFFLINE=1 UV_NO_PROGRESS=1 TMPDIR=/tmp cargo run -p xtask -- check-all completed 86 gates clean. This offline-cache environment is a distinct check from the timed-out default invocation; neither result is hidden. The new production policy DTO and tests were extracted from crates/mvm-contract/src/plan/bundle.rs (978→839 lines), preserve schema-8 LocalComposition, and still leave schema-9 reader cap at 8. Independent source review found no actionable issue; it did not independently run tests. No protected exporter, recipient, or signer authority was enabled. I did not perform the shared-branch merge.

    Two-architecture final-package evidence remains OPEN:

    Required release gate x86_64 aarch64
    Original signed runtime/base inputs and independently trusted fresh feed Not qualified Not qualified
    Final self-contained .mvmpkg SHA-256 None None
    Health boot THAT file None None
    Clean install of THAT SAME file None None
    Boot installed file and assert authored Python value None None
    Exact-file tamper/stale-feed/wrong-arch/unenrolled-key/no-NIC/no-SSH refusals + rehash None None
    Authorized official release/readback None None

    The native x86_64 and aarch64 AF_VSOCK base-probe evidence is real but is not a Python archive witness. Draft mvm-images #80 and mvm-packs #167 are still open, with no authorization in this conversation to merge them. The parallel Claude/skill session acknowledged the nonoverlap and separately signed Claude component decision, but does not assume ownership of this locally authored Python release. Next owners: #5417 schema/policy gate, #5420–#5426 exporter/recipient and signed-input chain, then exact x86_64 #5429 witness and separately authorized #5430 release; repeat the complete release gate for aarch64 under this issue. Protected custodian must provision a distinct official Python author public key/enrollment and retain the private half; owner must authorize exact source/signer/descriptor/rights and final digest before official signing/publication. Keep #4839 open and do not label either architecture shipped.

  18. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Unattended continuation request: proceed with independent schema-9 exporter, recipient, policy and candidate source/test work while maintainer is away; do not reinterpret this as exact-source/signer/descriptor/rights authorization for protected official Python signing, publication, main-branch merge, tag or images.lock advance. No official Python author key is available locally and none will be generated or promoted from a test signer. I am inspecting current main and active #5552 policy PR before editing overlapping authority paths. x86_64 remains first required final-file gate; aarch64 remains a separate required release gate. The evidence table in the prior comment remains open until exact signed archives and clean installed boots actually exist.

  19. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Independent #5425 prerequisite source is now in the attached mvm main worktree as a five-file uncommitted, unmerged diff: a private staged-archive readback verifies the same held file descriptor’s manifest signature, declared member hashes and digest under a caller-supplied public key before PreparedPortableBootAssets::stage can return; failure aborts private staging and does not publish a destination. It preserves existing selected Linux/runtime input re-verification and does not accept schema 9, change the reader cap, add publisher enrollment, use an official signer or create a Python package. Test-signer positive/wrong-key/tampered-member/abort cases were added. Focused tests and scoped Clippy/check are running in the isolated source thread; independent security review is also underway, so no pass or protected-export claim yet. This is reusable integrity readback, not a health boot, a fresh revocation feed, or recipient admission.

  20. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Evidence update (local feature branch only; not a Python release): feat/portable-stage-readback at local commit fad0f3eec6756a167943185f3345f086378fef16 adds verification of the exact privately staged .mvmpkg through its held file descriptor before publication, then rechecks the selected input closure. Wrong-key and changed-member failures abort staging without publishing. The archive readers now reject duplicate paths consistently; a signed, descriptor-pinned schema-9 production archive remains refused at the registry recipient boundary under reader cap 8.

    Validation: focused staged readback/refusal/duplicate tests passed; scoped Clippy (mvm-core, mvm-bundler, mvm-client, all targets), formatting, diff check, xtask check-all (86 gates), and TMPDIR=/tmp MVM_EMBED=0 cargo test --workspace -- --test-threads=1 passed. The unmodified parallel workspace command failed twice on different unrelated tests (CLI doctest import errors, then a temporary Git-config file read); the CLI doctest and Git-identity test each passed alone. The serial workspace run is a different check, not a claim that parallel tests are green.

    This does not close the production evidence boxes: no protected official Python signer, schema-9 producer/recipient admission, final x86_64/aarch64 Python archive SHA, selected-backend installed boot, or publication witness exists yet. No PR, push, merge, signing, tag, publication, or images.lock update was performed for this slice.

  21. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Coordination for the plan_admission.rs / workload_runner/runner.rs splits: #5538 has an uncommitted behavior-only draft on fix/5538-record-then-respond, based on main 7eb015747545051fb5e26ae2c6d5fa4c86e4de00. It is not a ready PR and must not be folded into a behavior-preserving split.

    Its current shared-file footprint is:

    • plan_admission.rs::populate_audit_substrate: project the actual admitted plan and production/development posture into AuditContext, plus an assertion in the existing projection test.
    • workload_runner/runner.rs: pass that context to the endpoint; compare it with the admitted plan; gate supported shutdown; register the target after boot/fork.
    • workload_runner/claim.rs: carry the one-shot audit-control registration handle.

    The post-boot target-acquisition/registration path has a known ownership blocker, recorded on #5538; it is not a safe original-owner API for other work to consume. No shared cold-HVF custody refactor or FC/warm original-owner expansion is being implemented here. #5522's explicit deferral remains in force. The overlapping mailbox work is also paused on these shared paths pending a single owner and agreed scope.

    No further edits are planned in the shared admission/runner/claim files while split coordination is pending. Remaining #5538 changes are bounded FlowMux UDP cleanup and documentation, followed by validation and a clearly blocked draft PR. Please share split source pins/new owning module paths before integration; do not merge stale dirty snapshots across the move. No landing or queue permission is conveyed.

  22. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    PS-21 status/coordination, no checklist mutation: current read-only call-graph and operation inventory distinguishes zero check-thin-cli allowlist entries on clean b45ab83 from functional parity, and names unresolved Firecracker shell/reaper and helper verify-to-exec paths under their existing owners. An isolated, uncommitted metadata-only secret.get hostlib/SDK slice is being validated against origin/main 7eb0157; no supervisor-regroup files are in its git diff (Delta's large deleted-file notice came from switching the isolated checkout to newer upstream history). Do not tick boxes 220/222/224/225/236/246/248 on this progress: required checks, source review, native #4414, Studio PR #29 current-pin build/tests and full #3730 child acceptance remain. Direct Delta cross-session messages could not be delivered because remote synchronization is disabled; this comment is the coordination handoff.

  23. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Follow-up to the staged-readback evidence update: local-only feat/portable-stage-readback commit a80ced98ec83822e5531ed1cfb5cd817464a535b makes pack completion compare the health-checked output to the verified staged manifest and report the archive SHA returned by that same held-file readback. It reads the existing host public key without minting an identity; missing/mismatched keys and changed payloads abort the owned stage before publication. An independent source review found and resolved a needless-borrow lint; no additional actionable security issue was identified in this narrow flow.

    Exact validation on the combined branch: cargo fmt --all --check, git diff --check, TMPDIR=/tmp MVM_EMBED=0 cargo test -p mvm-bundler --lib staged_readback, TMPDIR=/tmp MVM_EMBED=0 cargo test -p mvm-cli --lib (2,881 passed, 1 ignored), TMPDIR=/tmp MVM_EMBED=0 cargo clippy -p mvm-cli -p mvm-bundler --all-targets -- -D warnings, TMPDIR=/tmp MVM_EMBED=0 cargo test --workspace -- --test-threads=1, and UV_OFFLINE=1 UV_NO_PROGRESS=1 TMPDIR=/tmp cargo run -p xtask -- check-all (86 gates) all passed. No live pack health boot, official protected signing, schema-9 admission, final Python package bytes or installed two-architecture boot were run. Cache-hit application resolution already rechecks current revocations and archive bytes; existing tests cover these separately, but their injected feed is not a real signed-feed positive fixture. All production evidence boxes remain open. No PR, push, merge, tag, publication or images.lock update.

  24. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Handoff correction to the earlier local-only evidence note: the owner explicitly authorized a feature-branch push for review only. The clean two-commit source slice is now durably available at feat/portable-stage-readback, head a80ced98ec83822e5531ed1cfb5cd817464a535b. No PR was opened, no merge to main, official signing, publication, tag or image lock advance occurred. The production Python evidence boxes and limits in the prior comment remain unchanged.

  25. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Piece 3 of 3 (split of workload_runner/runner.rs by responsibility, pure move, identical test counts): #5565

  26. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Maintainer authorization recorded (2026-11-15): the cleanup session may queue a #4839 refactor pull request without asking again when it is a pure move (item bodies verbatim, visibility not widened, no compatibility shims), the cargo nextest list test names and counts are identical before and after, every required check is green, and it changes no security claim, release behavior or published artifact. Anything that changes behavior, a claim, a budget, a verification or an audit path, and anything outside #4839, still needs an explicit go-ahead. First use: #5565 (the workload runner split).

  27. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Piece 2 of 3 (split of plan_admission.rs) is up as #5566. It is a pure move: same item bodies, names and visibility, identical test list (2,344 before and after in mvm-hostd --lib). One note: #5564 edits admit_and_start_with_verified_release, which now lives in plan_admission/start.rs.

  28. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    Audit of boxes 348, 350 and 351 against main at 54eb7a0 (read-only; the cited witnesses were checked to exist, not re-run). No box is ticked. None of the three is "preserved" as worded, and ticking would overclaim.

    348 Tracing/stream completeness

    350 Protocol and readiness (ADR-019)

    • Preserved: readiness distinct from running and from disabled (ComponentState), bounded payload and control capacity (data_plane_limit_reserves_control_plane_capacity, a_saturated_data_plane_refuses_data_requests_and_still_admits_control), and a closed capability enum.
    • Contradicted by the shipped design: the box says to preserve explicit version/capability negotiation before dispatch. In production the authenticated session handshake is the prelude and ProtocolHello is optional; the guest accepts requests with no hello, handshake_as_guest echoes the version without a range check, and negotiate_protocol checks requested capabilities against the host's own list, not the guest's. A guest older than the host with fewer capabilities is not detected before dispatch. ADR-019 still says every session begins with ProtocolHello.
    • Partial: typed backpressure (only OutputConsumerSlow is ever emitted), cancellation (extension calls only), recovery (stream-level only; host reconnect belongs to open PS-21: Complete typed VMM lifecycle without shell or utility processes #4414 and PS-21: Validate and land complete client-boundary parity #4416, and machine exec: a nonzero guest exit (or a killed client) leaves the input journal unfinished and refuses every later exec #4809 stays open for the typed-task follow-up).
    • Needs a maintainer decision: amend ADR-019 to describe the authenticated handshake as the prelude with hello optional, or open an owner issue for real guest-advertised capability and version enforcement.

    351 Mailbox operational contract (ADR-057)

    Evidence is from a read-only audit; nothing was run. Refs #4839.

  29. auser commented on Nov 15, 2026

    @auser
    CollaboratorAuthor

    PS-21 footprint gate coordination (correction to prior progress note): isolated secret.get branch full workspace nextest 21,177/21,177 and required scoped/SDK checks passed, but its check-rust-footprint green result required increasing SLOC/physical ceilings to 991,493/1,259,820. The binding instruction says never loosen a check or budget to pass a gate, so do not treat that green result as accepted validation or publish the branch with this change. The worker measured base origin/main 7eb0157 at 991,237/1,259,528 before the slice, already above the current origin/main gate ceilings 991,000/1,259,000; the new operation adds approximately 256/292. This needs coordination with the footprint/supervisor-regroup owner for legitimate reduction or an explicit separate design/scope decision, not hidden compression, test deletion, or a cap bump. #3730/#4415/this umbrella remain open; no PR/merge/box change.

  30. auser commented on Nov 16, 2026

    @auser
    CollaboratorAuthor

    Read-only audit of boxes 339 and 340 against main (cited test functions were checked to exist; nothing was run). Neither box is ticked.

    339 Studio PR#29 telemetry adapter

    • PR state: tinylabscom/mvm-studio PR#29 is open and draft, with no reviews. Its body says ADR 0008 is Proposed and not to merge until it is accepted. CI on its head passed, which this box says is not a witness. It pins an old MVM commit, so nothing checks it against the current contract. Our 2026-11-15 comment asking who owns the pin update has no reply.
    • This repo's side, witnessed: bounded cursor paging (MAX_PAGE_RECORDS=1024, pages_walk_the_stream_oldest_first_and_the_last_cursor_polls_for_more, telemetry_records_pages_from_the_cursor_it_is_given), stale-cursor refusal (a_cursor_off_a_line_boundary_or_past_the_end_is_refused; "reset" is only the caller restarting from TelemetryCursor::START), unavailable/not-provisioned (NotProvisioned and the status fixtures), and fixtures on the producer side (studio_fixture_streams_match_the_committed_vectors, specs/contracts/studio-telemetry-contract.md).
    • Not witnessed here: selected-machine attribution (reads are per MachineId; the pane is Studio code) and cancellation (a synchronous page call; any cancel is Studio-side and has no MVM witness).
    • Live witness would need: ADR 0008 accepted, PR#29 landed with the pin updated, and Studio tests run against that exact pin, ideally on a real HVF machine. None exists.
    • Follow-up: confirm or reassign the PR#29 owner, gate on ADR 0008, record exact-source Studio tests, and note that cancellation is Studio-owned.

    340 MVMD V1 contract boundaries

    Refs #4839.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    cleanupRefactoring, simplification, dependency reduction, and cleanup

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions