apmx 0.7.0

EXPERIMENTAL prerelease. Native notices and exact downloaded bytes are gated; this is not production certification.

Standalone apmx 0.7.0; candidate commit 315491bff45f653e728c91c7ad1fc07465b97535.

Changes in v0.7.0: One receipt bundle, code-only PRs, central factories

Receipts are one standard in-toto bundle; PRs carry only code; run factories centrally across repos.

• Breaking: every COMPLETE run writes one receipt.intoto.jsonl (SLSA Provenance v1, in-toto Test Results and the CycloneDX 1.5 inventory, one DSSE envelope per line) plus content-addressed evidence/sha256/<hex>. It replaces the v1 receipt/ folder, which is no longer read.
• PRs carry code only. run.yml signs a SLSA Verification Summary over the delivered files and attests the receipt bundle beside it; apmx audit looks the PR's changed files up by SHA-256 in the signer's attestation store and refuses a PR built on a stale base.
• Run factories centrally: run.yml takes target-repository, target-ref, a GitHub App (target-app-client-id, target-app-private-key) or target-token, and deliver: pull-request|branch|bundle. The agent's job never receives a target credential (examples/factory-platform).
• Pin a signer to immutable code with factories.signers[].workflow_sha; the signing certificate's commit or annotated tag object both match.
• apmx audit --explain and --export abom; stages record harness, harness version and models (recorded, not yet enforced).
• Reference the actions and run.yml at @v0.7.0 or its commit SHA.

See the v0.7.0 changelog.

What's new since v0.2.0

• Run a factory directory without writing orchestration: APMX derives execution order from the contracts' declared file dependencies.
• Deliver multiple output files together. Handoffs require every declared file, complete passing checks and an intact recorded inventory; the aggregate artifact view retains admitted outputs and the original required inputs/checks.
• Export real patches from private source edits with the bounded artifact tools, without changing the original checkout.
• Discover selected imported skills through native Copilot skill discovery, with clearer package-preparation progress and bounded terminal evidence.
• Try the software-factory example with optional Gherkin/Behave acceptance checks and separate regression checks. Its standalone checker now supports deeply nested Windows file paths with child-only Git configuration.

Compatibility and migration

BREAKING: imported skill metadata. Previously accepted imported skills can now fail admission without a nonempty name and description in SKILL.md. Names must be 1-64 lowercase letters/digits separated by single hyphens, with no leading or trailing hyphen. Selected context names must not collide case-insensitively; unsupported activation metadata is rejected.

Update the authored source package (for example, name: handoff-style with description: Write concise handoffs.), then select its updated revision through the normal dependency workflow, keeping apm.yml and its lock coherent. Do not patch generated apm_modules copies or edit lock digests by hand. Migration guide.

Leaf records use apm-contract-run/0.3 and factory records use apmx-contract-chain/0.2, separating execution from native assurance. Historical records are not rewritten and cannot authorize new handoffs.

Factory execution asks for consent interactively. Automation must pass --allow-host-access --allow-unproven-inputs; these flags do not admit failed or incomplete handoffs. Native execution is not a sandbox. Complete validated and finalized execution yields COMPLETE (0), not isolation or certification. Incomplete work remains UNPROVEN (21); rejection 20; halt 22.

Installation and assurance limits

Five native onedir archives include the runtime, LICENSE, NOTICE, release metadata, and the pinned official APM 0.33.0 backend with its complete runtime under libexec/apm. Extract the complete archive; do not move the executable out of its runtime directory.

Git, Copilot CLI, and contract-declared checker tools are external prerequisites. The CI actor is an explicitly hermetic Copilot JSONL protocol fixture, NOT live inference. Complete validated and finalized execution yields COMPLETE (0), not isolation or certification. Incomplete work remains UNPROVEN (21); rejection 20; halt 22.

No trusted publisher signature or Apple notarization is provided. macOS may carry PyInstaller's local ad-hoc signature; it is not publisher identity. Checksums prove byte integrity, not publisher authentication. Do not disable platform security to run these binaries.