Skip to content

[P3] Doctor/Linux ARM64: prove physical-host gates and real distribution provisioning #300

Description

@wsdt

[P3] Doctor/Linux ARM64: prove physical-host gates and real distribution provisioning

Review baseline and scope

Reviewed source: c9d32008e98d0e1711f47cb739f61c42376b884e on main, 22 September 2026.
Classification: ARM64 HOST / PROVISIONING EVIDENCE.
Predecessors: #279.
This replaces their remaining work; closing a predecessor during backlog migration is not a claim that its original scope was completed.

Already delivered — do not rebuild

The ARM64 tracking driver and prior local evidence exist. ab3ec58 changes two historically excluded real-distribution fixtures into explicit absent-provisioning probes with exact missing-bundle/selector diagnostics. Correctly observing missing provisioning is not a successful real-distribution lifecycle run or hosted promotion.

Remaining implementation / execution

  • Select and provision the real ARM64 Linux host/runner and exact distribution bundles required by the owning gate; retain it as a separate architecture track.
  • Run both the expected-absence negative controls and the genuinely provisioned real-distribution lifecycles, repairing architecture-specific failures without weakening confinement.
  • Retain the complete physical/hosted result and obtain the explicit architecture-support decision if promotion is intended.

Acceptance evidence

  • Every required real-distribution case actually executes when provisioned; missing-bundle probes are labelled negative evidence, not success substitutes.
  • Host architecture, kernel/capabilities, bundle digests, exact SHA and nonzero test counts are recorded.
  • Linux x86_64 results are not borrowed as ARM64 proof, and ARM64 work does not block or redefine the x86_64 ticket.

Boundaries

No automatic hosted dispatch or claim of ARM64 support follows from updating the tracker. A task description is not an authorization for provider spend, signing, publication, remote deployment or a change to support policy. Preserve existing stable identities, explicit profile limits, source authority and non-vacuous acceptance gates.

Evidence and implementation entry points

Test results described above are retained repository evidence, not a fresh full test run performed by this backlog review. Re-run the owning gates for the implementation being accepted.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions