Skip to main content

AgentXchain v2.155.18

v2.155.18 is a patch over v2.155.17 fixing the dispatch-time half of BUG-73 in the DOGFOOD-EXTENDED charter materialization lane. v2.155.17 fixed future idle-expansion acceptance by setting next_recommended_role back to PM, but dogfood recovery proved older persisted states could still contain both charter_materialization_pending and stale next_recommended_role: "dev". That stale state re-dispatched dev while the run was still in planning.

Bug Fixes​

  • BUG-73 dispatch-time charter materialization routing: role resolution now forces pending charter materialization back to PM even when persisted state still has stale next_recommended_role: "dev". This covers dogfood recovery states created before 2.155.17, not only future acceptance paths.
  • Coordinator routing parity: multi-repo coordinator dispatch applies the same pending-materialization PM routing rule before honoring recommended roles, so stale implementation recommendations cannot leak through coordinator assignment.

Evidence​

  • node --test --test-timeout=60000 cli/test/role-resolution.test.js cli/test/bug-70-charter-materialization.test.js -> 14 tests / 2 suites / 0 failures / 0 skipped
  • node --test --test-timeout=60000 cli/test/dispatch-bundle.test.js cli/test/continuous-run.test.js cli/test/beta-tester-scenarios/bug-60-perpetual-idle-expansion.test.js cli/test/gate-evaluator.test.js cli/test/phase-transition-events.test.js -> 220 tests / 39 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.