Skip to main content

AgentXchain v2.155.20

v2.155.20 is a patch over v2.155.19 fixing the active retained-turn recovery half of BUG-73 in the DOGFOOD-EXTENDED charter materialization lane. v2.155.19 fixed blocked retained replay, but dogfood recovery proved an interrupted replay could leave the run active with a running stale dev turn. step --resume now corrects that role to PM before stale-turn recovery runs.

Bug Fixes

  • BUG-73 active retained-turn charter materialization recovery: step --resume now reissues an active stale dev turn as PM before stale-turn recovery runs when planning charter materialization is pending. This covers interrupted recovery states where a previous bad replay had already reactivated the run before being stopped.
  • Watchdog ordering hardening: materialization role correction now executes before stale-turn watchdog recovery for the single active-turn resume path, so the operator is not blocked with generic stale dev guidance when the protocol already knows PM owns the next turn.

Evidence

  • node --test --test-timeout=60000 cli/test/bug-70-charter-materialization.test.js cli/test/role-resolution.test.js cli/test/beta-tester-scenarios/bug-47-stale-turn-watchdog.test.js cli/test/step-command.test.js -> 59 tests / 18 suites / 0 failures / 0 skipped

Tester Re-Run Contract

Run the shipped package:

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

For dogfood verification, use shipped agentxchain@latest on the tusq.dev dogfood branch and quote direct diff evidence:

git diff --stat origin/main..HEAD -- src/ tests/ bin/ tusq.manifest.json

Closure requires the existing persisted materialization state or a fresh full-auto idle-expansion PM turn to dispatch PM for materialization, then reach implementation with a concrete charter and land real product code in src/, tests/, bin/, or tusq.manifest.json.

For downstream closure proof, quote any startup_latency_ms, elapsed_since_spawn_ms, and runtimes.<id>.startup_watchdog_ms evidence relevant to adapter-path reliability while confirming the downstream flow still uses the real runtime path. If a standing phase gate advances before dispatch, quote phase_entered with reconciled_before_dispatch; if continuous mode chains into another run, quote the session_continuation event.

For BUG-55 regression proof, continue using accept-turn followed by checkpoint-turn and quote verification.produced_files, undeclared_verification_outputs, and git status --short.

Clean tree means BUG-55 is fixed for your reproduction.