apmx 0.3.2

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

Standalone apmx 0.3.2; candidate commit 046520f2b57017684b9bc5b15913c72916366a63.

Changes in v0.3.2

Use the declared target's path-component ordering for native inventories, rather than the verifier host's ordering. Keep exact whole-inventory equality, record multiplicity, case-sensitive path identity and every hash/format/symlink field. Stored manifests are never reordered or rewritten.

All five v0.3.1 native builds and smoke matrices passed, but Linux draft staging stopped before release creation on a Windows inventory-order false alarm. This is separate from the v0.3.0 factory smoke fixture path comparison corrected in v0.3.1. The v0.3.0 and v0.3.1 tags and archive evidence remain unchanged. These v0.3.2 archives are fresh builds, not repacked or relabeled earlier artifacts.

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.

Scalar contracts and single-contract invocations remain supported. Scalar run records retain apm-contract-run/0.1; multiple-output inventories use apm-contract-run/0.2. Existing saved runs are not rewritten.

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, and complete passing checks still yield UNPROVEN (21), not VERIFIED.

Installation and assurance limits

Follow the native installation guide for checksum verification and platform-specific setup.

Five native onedir archives include the runtime, LICENSE, NOTICE, release metadata, and the pinned official APM 0.30.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. Passing native checks yield UNPROVEN (21), rejection 20, operational 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.