Skip to main content

AgentXchain v2.155.57

v2.155.57 fixes BUG-103: roadmap-replenishment PM turns that emit decision text as decisions[].title now normalize that text into the required statement field before schema validation. This recovers the tusq.dev full-auto PM turn that derived the next roadmap milestone from remaining VISION scope.

Bug Fixes​

  • BUG-103: decision title statement normalization. Missing or blank decisions[].statement now copies from non-empty title after existing decision, description, and summary sources.
  • Fail-closed missing content. Decisions with no statement source material still fail schema validation; AgentXchain does not synthesize decision text from rationale alone.
  • Prompt hardening. Dispatch instructions now explicitly forbid title as the decision statement field name.

Evidence​

  • npm test -- --test-timeout=60000 -> 7305 tests / 1480 suites / 0 failures / 5 skipped

Tester Re-Run Contract​

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

For BUG-103: resume retained tusq.dev failed-acceptance turn turn_644dcda246f21bc1 on the shipped package. The staged result must accept without manual staging JSON edits because each decision has a non-empty title plus rationale; acceptance must continue through the normal full-auto path without operator-side accept-turn, unblock, gate mutation, or cross-repo workaround.

For BUG-102 carry-forward: deliberate negative-case verification commands with explicitly expected non-zero exits must still accept, while undeclared non-zero machine evidence under verification.status: "pass" remains fail-closed.

For BUG-101 carry-forward: decision objects that include summary plus rationale must still normalize summary into missing statement fields while decisions with no statement source fail closed.

For BUG-100 carry-forward: productive retries-exhausted local_cli timeout blockers must still auto-retry once with a 60-minute deadline, while silent/no-output failures remain fail-closed.

For BUG-99 carry-forward: pre-acceptance gate_semantic_coverage must still evaluate workflow-kit ownership with accepted turn history.

For BUG-98 carry-forward: retained QA skip-forward requests from implementation to launch must still normalize to immediate next phase qa, with stale proposed_next_role aligned only when routing-safe.

For BUG-97 carry-forward: retained active-turn run_id drift must still auto-normalize only when the staged turn_id proves active-turn ownership.

For BUG-96 carry-forward: decision entries that include existing decision text but omit rationale must still auto-normalize before schema validation.

For BUG-95 carry-forward: staged results that use files_modified instead of files_changed and omit runtime_id, summary, artifact, and proposed_next_role must still auto-normalize before schema validation.

For review-only carry-forward: a review_only role with missing or empty objections must still fail protocol challenge enforcement.

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.