Skip to content

v0.14.0 — gate integrity: a green you can trust

Choose a tag to compare

View all tags
@stranxik stranxik released this 13 Jul 10:26
v0.14.0
a7ba2cf

A multi-agent functional audit of the toolchain (build, tests, init, the full check --strict chain, compliance, the example floor) confirmed the core runs green end to end with no blocker, but surfaced gate-integrity defects: paths by which a mission could look done when it wasn't, or an operator typo could read as a real failure. This release closes them, so a green check is trustworthy ground truth.

  • CLI misuse now exits 2, distinct from 1 "the gate has gaps" — an unknown command/option or missing/excess argument no longer reads in CI like a real gate failure (exitOverride on the root and every subcommand).
  • The "filled" heuristic no longer passes a one-byte edit — a divergence guard stops decision-matrix.md / execution-topology.md closing their gate on a trivial change. The reference stays green.
  • Non-vacuity holds at exactly zero — a stripped phase mapping still fails --strict (ADR-0002), instead of being silently skipped.
  • One shared isRealAdr helper — mission, status and conformance now agree; an ADR named ...-10000-ms.md is no longer dropped.
  • Frame/Architect workflows name every gate artifact — mission-contract.md and decision-matrix.md, so no uncloseable gate.
  • Minor hardening — --tools lists all 8 profiles; ADR-1 no longer matches ADR-10; an evidence-cell pipe is no longer truncated. Regressions added to test/smoke.js.

Full notes: CHANGELOG.md

Assets 2
Loading