Skip to main content

AgentXchain v2.155.59

v2.155.59 fixes BUG-105: strict intent coverage now searches normalized verification evidence summaries and remaining command-shaped machine evidence after staged-result normalization. This preserves the acceptance-contract proof from the retained tusq.dev roadmap-replenishment PM turn after BUG-104 correctly moves typed observations out of verification.machine_evidence[].

Bug Fixes​

  • BUG-105: structured evidence remains visible to intent coverage. Intent coverage now evaluates verification.evidence_summary, textual decision proof, objections, file/artifact names, intent-response details, and still-valid command-shaped machine evidence.
  • Punctuation-normalized acceptance matching. Acceptance items are tokenized as word characters instead of raw whitespace, so text like bounded, testable, and non-duplicate is recognized as coverage for bounded, testable, and duplicate.
  • Fail-closed missing proof. The negative regression keeps failing when the bounded/testable/non-duplicate acceptance proof is absent, so the fix does not turn strict intent coverage into a blanket pass.
  • Dogfood regression coverage. The command-chain regression models the exact tusq.dev retained PM blocker after BUG-103 decision-title normalization and BUG-104 evidence-summary normalization.

Evidence​

  • npm test -- --test-timeout=60000 -> 7310 tests / 1482 suites / 0 failures / 5 skipped

Tester Re-Run Contract​

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

For BUG-105: resume retained tusq.dev failed-acceptance turn turn_644dcda246f21bc1 on the shipped package. The staged result must accept strict intent coverage without manual staging JSON edits because typed acceptance_contract_check evidence moved to evidence_summary remains visible to intent coverage and punctuation-normalized matching recognizes bounded/testable/non-duplicate evidence.

For BUG-104 carry-forward: the same retained PM turn must continue to move typed verification observations out of machine_evidence[] while preserving them in evidence_summary.

For BUG-103 carry-forward: the same retained PM turn must continue to normalize decisions[].title into required statement fields before validation.

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.