apmx 0.4.2

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

Standalone apmx 0.4.2; candidate commit 00928304850d70d36213da2d0230ac31d7d56fb1.

Changes in v0.4.2

Make the Windows logger presentation tests assert dim styling on actual elapsed-time metadata instead of a platform-dependent trailing line position. Use path-safe labels for native, LF and CRLF output variants while preserving exact newline translation, byte-identical transcript and finalization coverage.

No GitHub release or native assets were published for v0.4.1. Its immutable public source tag remains unchanged and records the failed release-preparation candidate. These v0.4.2 archives are fresh builds and do not reuse, repack or relabel v0.4.1 assets. The earlier v0.4.0 tag and failed-candidate record also remain unchanged.

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.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. 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.