P1: Publish a reproducible deployable controlled-alpha release

[wms2537]

Risk: MAR-P1-005

Problem

Exact-commit CI evidence exists, but the repository has no versioned OCI image, image smoke test, migration/rollback runbook, SBOM/digest record, or release tag.

Required outcome

Produce a reproducible, non-root runtime image and a controlled-alpha release procedure without weakening the existing gate.

Acceptance criteria

• multi-stage image build pins the Node major and installs from the committed lockfile
• runtime runs as a non-root user with API, worker, relay, admin, migration, and health contracts documented
• image build and local health/migration smoke test run in CI
• release records image digest and SBOM/provenance artifacts
• forward migration, rollback limitations, and application rollback are documented
• package/changelog/tag agree on v0.1.0-alpha.2
• PR and post-merge main gates pass before the tag is created
• published immutable GHCR digest is anonymously pullable from a credential-free client

Release candidate history

v0.1.0-alpha.1 is retained as an immutable failed publication candidate. v0.1.0-alpha.2 is the controlled-alpha release that corrected and strictly validates the BuildKit SLSA/SPDX attestations.

[wms2537]

Controlled-alpha packaging is merged via #33 at d422e042c4f8060960648c3768a0e4aea54c96e2.

Post-merge evidence:

• main push gate: https://github.com/Straits-AI/managed-agents-runtime/actions/runs/29688978575
• retained artifact: controlled-alpha-d422e042c4f8060960648c3768a0e4aea54c96e2
• artifact digest: sha256:18f111939a9840b0a06334c36cec91bd6c0a5cffccf44185ba2c9f290a63f09e
• gate: 293/293 tests, 30/30 critical assertions, zero production dependency findings
• source: exact clean main commit
• image: non-root node, linux/amd64, version 0.1.0-alpha.1
• image config digest: sha256:e20249d76ef2f2285cc9e1a1e589c19dd796c50d98aecdc32b17139984f32a33
• CycloneDX SBOM recorded and hash-verified

The tag remains intentionally uncreated. Live BytePlus provider conformance is still blocked because the local dev profile session has expired and requires bp login --profile dev --region ap-southeast-1. After reauthentication, the remaining sequence is live conformance -> annotated tag on exact verified main -> GHCR publication -> public-pull verification.

[wms2537]

Repository-side release hardening is merged through #41 at exact main commit 15928d445a422271331e8e49c935170df264aff1.

Evidence:

• PR gate: https://github.com/Straits-AI/managed-agents-runtime/actions/runs/29889411711 — passed
• exact post-merge main gate: https://github.com/Straits-AI/managed-agents-runtime/actions/runs/29889478460 — passed
• full local suite: 391/391
• clean controlled-alpha gate: 30/30 critical assertions, zero production dependency findings
• independent specification and standards reviews: PASS
• publication now propagates the immutable digest to smoke/evidence and requires an isolated anonymous GHCR pull before promotion or prerelease creation
• first-publication private-to-public bootstrap and its irreversible visibility boundary are documented

The annotated tag remains intentionally uncreated until #26's current live-provider matrix is reconciled, as required by the release sequence.

[wms2537]

Controlled-alpha publication is complete except for the package visibility switch.

Published release:

• prerelease: https://github.com/Straits-AI/managed-agents-runtime/releases/tag/v0.1.0-alpha.2
• source commit: 633e20e0737a736dfae02aeb423dc5c289c229cf
• immutable registry digest: sha256:07dcb446d811fa51fb30a7746f55ed72becbbb8b5ad41dfafc6ec8cff9af2440
• tag publication workflow: https://github.com/Straits-AI/managed-agents-runtime/actions/runs/29907892675 — passed
• seven retained release assets include SLSA provenance, SPDX and CycloneDX SBOMs, registry/container summaries, and kernel gate evidence

Publication hardening:

• release: recover controlled alpha as v0.1.0-alpha.2 #59 repaired strict structural BuildKit SLSA/SPDX validation; PR and post-merge gates passed
• fix: prove public registry visibility without daemon cache #60 replaced the daemon-cache-sensitive pull check with an authoritative anonymous token plus exact digest-addressed manifest check
• fix: prove public registry visibility without daemon cache #60 exact candidate gate: 475/475 tests, independent specification and standards reviews PASS
• fix: prove public registry visibility without daemon cache #60 PR gate: https://github.com/Straits-AI/managed-agents-runtime/actions/runs/29909022506 — passed
• fix: prove public registry visibility without daemon cache #60 post-merge main gate: https://github.com/Straits-AI/managed-agents-runtime/actions/runs/29909155006 — passed

Current authoritative public check correctly fails at the anonymous GHCR token exchange with HTTP 401. The GitHub package is private. GitHub documents visibility promotion as an irreversible package-settings UI action; once an organization package is public it cannot be made private again. The issue remains open until that switch is completed and the exact digest passes credential-free verification.

[wms2537]

Public-image verification completed on 2026-07-22.

• Release: https://github.com/Straits-AI/managed-agents-runtime/releases/tag/v0.1.0-alpha.2
• Source commit: 633e20e0737a736dfae02aeb423dc5c289c229cf
• Immutable image: ghcr.io/straits-ai/managed-agents-runtime@sha256:07dcb446d811fa51fb30a7746f55ed72becbbb8b5ad41dfafc6ec8cff9af2440
• Anonymous registry verifier: PASS (anonymous token exchange, digest-addressed manifest retrieval, and Docker-Content-Digest equality)
• Credential-free pull: PASS using a fresh empty Docker config and --platform linux/amd64; Docker reported the exact expected digest
• Runtime smoke from the exact release commit: PASS container release contract
• Standalone boundary verification: PASS standalone Kertas runtime conformance

The initial native arm64 pull was correctly rejected because this controlled-alpha release declares linux/amd64 only. Explicitly selecting the documented platform completed successfully.