Skip to main content

AgentXchain v2.158.0

v2.158.0 adds two operator-facing shippability surfaces — agentxchain ship-status and agentxchain attention — and hardens the governed turn lifecycle so legitimate artifact-finalization turns are accepted and one-shot dispatched turns can't silently ghost. Every item in this release was produced by dogfooding agentXchain on itself with a VISION-driven lights-out run.

What's New​

  • Shippability visibility — agentxchain ship-status. A single command answers "is this ready to ship?" by composing five independent evidence dimensions — run completion/phase status, QA ship verdict, gate clearance across all phases, release-alignment validation, and test-verification evidence — into a structured ShipStatusReport with per-dimension pass/fail/pending and surfaced blocking reasons. Supports --json and --verbose, multi-repo coordinator aggregation via evaluateCoordinatorShipStatus(), and a ship-status summary section in the governance report.
  • Human-attention surface — agentxchain attention. A govern-by-exception view that composes six attention categories into one answer to "what needs me?", so operators act on exceptions instead of scanning everything. Supports --json and --all, exits cleanly in both the all-clear and attention-needed states, and integrates into the governance report.

Hardening​

  • The implementation gate no longer dead-ends artifact finalization. A completed implementation turn that changes only planning artifacts is now accepted when a prior completed implementation turn in the same run already committed product code (for example, QA finalizing the gate-required IMPLEMENTATION_NOTES ## Changes/## Verification sections after the implementation itself was committed). A run that has produced no product code at all is still held to the strict "code, not just docs" requirement.
  • Single-shot execution guard for dispatched turns. Every role's dispatch prompt now states plainly that the turn is a one-shot, non-interactive subprocess: do all work synchronously, never background a job and wait for an async notification, and write the turn result as the final action. This prevents "ghost" turns where an agent defers its conclusion to a wake-up that never fires and exits without a result.

Evidence​

  • npm test -- --test-timeout=60000 -> 7706 tests / 1561 suites / 0 failures / 5 skipped

Tester Re-Run Contract​

Verify: npx --yes -p [email protected] -c "agentxchain --version"

Carry-forward tester checks for shipped-package closure proof:

  • BUG-54 startup watchdog evidence should quote startup_latency_ms, elapsed_since_spawn_ms, and runtimes.<id>.startup_watchdog_ms.
  • BUG-55/87 verification-output evidence should quote undeclared_verification_outputs, verification.produced_files, and git status --short after accept-turn followed by checkpoint-turn. Clean tree means BUG-55 is fixed for your reproduction.
  • BUG-52/53 continuous recovery evidence should quote phase_entered, reconciled_before_dispatch, and session_continuation.