Skip to main content

AgentXchain v2.16.0

2.16.0 closes three real product gaps that were still weakening the “governed software factory” story:

  • coordinator reports described too little
  • workflow-kit gates claimed more planning truth than they enforced
  • external adapter adoption was importable, but not yet executable from the installed package boundary

Upgrade:

npm install -g [email protected]

What changed since 2.15.0​

Coordinator governance reports are now operational​

The coordinator report surface now answers the operator questions that matter without forcing raw-artifact spelunking:

  • What happened? Coordinator Timeline
  • When did it happen? coordinator timing
  • Which barriers changed and why? Barrier Summary plus Barrier Transitions
  • What decisions did the coordinator make? Coordinator Decisions
  • What should I do next? deterministic Next Actions

This is backed by real coordinator-authored decision-ledger entries, not fixture-only report sugar.

Workflow-kit gates now enforce the repo-native planning contract​

The planning/docs layer is now treated as a real governed contract, not decorative repo furniture.

2.16.0 enforces:

  • baseline planning system spec presence
  • template-specific SYSTEM_SPEC.md overlays
  • implementation-exit proof through IMPLEMENTATION_NOTES.md
  • QA acceptance-matrix semantics
  • release-notes presence at ship verdict time

If those artifacts drift, the gate fails closed.

External consumers can dispatch a real adapter-backed turn​

The published package now includes a second executable starter under examples/external-runner-starter/:

  • run-one-turn.mjs proves manual runner-interface usage
  • run-adapter-turn.mjs proves real agentxchain/adapter-interface dispatch through local_cli

The new starter is guarded by a clean consumer pack-and-install test, so the external adoption path is executable, not just documented.

Why this release matters​

2.15.0 proved intake-to-coordinator continuity. 2.16.0 hardens the next layer up:

  • the coordinator can now explain itself truthfully
  • the workflow kit is now a real gate input
  • third-party adopters can exercise the package boundary the way the docs already implied

That is a better fit for the project north star: governed, evidence-backed, long-horizon multi-agent software delivery.

Where to go next​

Evidence​

  • 2186 node tests / 483 suites, 0 failures.
  • Tier 1: 46 / 46 conformance fixtures passing.
  • Docusaurus production build passes.
  • npm publish verified: [email protected] live on registry.