Skip to main content

AgentXchain v2.155.56

v2.155.56 fixes BUG-102: passing verification may include deliberate negative-case commands with non-zero exits only when those exits are explicitly declared as expected. This recovers the tusq.dev full-auto QA turn that proved CLI rejection paths with exit-1 checks.

Bug Fixes​

  • BUG-102: expected non-zero verification evidence. verification.machine_evidence[].expected_exit_code can now declare the expected exit code for a negative-case command.
  • Evidence-summary compatibility. Existing staged results can also pass when evidence_summary explicitly names the command or recognized snippet and says it exits with the observed non-zero code.
  • Fail-closed accidental failures. Non-zero machine evidence without a matching expected declaration still blocks verification.status: "pass".
  • Prompt hardening. Dispatch instructions still prefer wrapping negative checks in zero-exit verifiers, while documenting the explicit raw non-zero evidence contract.

Evidence​

  • npm test -- --test-timeout=60000 -> 7303 tests / 1479 suites / 0 failures / 5 skipped

Tester Re-Run Contract​

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

For BUG-102: resume retained tusq.dev failed-acceptance turn turn_cbc4204c2b1db778 on the shipped package. The staged result must accept without manual staging JSON edits because evidence_summary explicitly declares --first-type STRING exits 1 and --first-type boolean exits 1; acceptance must continue through the normal full-auto path without operator-side accept-turn, unblock, gate mutation, or cross-repo workaround.

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.