Smoke replay exposed a named snapshot mismatch

A smoke replay did not collapse terminal drift into a generic suite failure: it named the exact snapshot path and printed a unified diff directly in the terminal.

Last checked 2026-03-26Sinji, Musha

Smoke replay exposed a named snapshot mismatch

Summary

One smoke replay diverged from its saved snapshot, and the mismatch stayed visible as a named path plus unified diff instead of collapsing into a generic replay failure.

Trigger

During termwright replay, the live terminal state diverged from the saved snapshot for repl_smoke/snapshots/03_after_assistant_turn.yaml.

System response

The replay harness ended with suite failed, then explicitly printed snapshot mismatch, named the snapshot path, and showed the unified diff hunk below. The diagnostic surface stayed concrete all the way through terminal output.

Outcome

The mismatch survived as one reproducible debugging surface rather than a mute pass/fail bit. This page records the exact path and diff that were surfaced in that episode.

Why it mattered

Replay failures only help when a reviewer can reopen one concrete incident. Here the drift remained inspectable as a named snapshot mismatch tied to one replay family.

Current note

Historical drift episode. The replay family still exists, but this page records one preserved mismatch rather than the current smoke state.