You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3e1e26e
Browse filesBrowse the repository at this point in the historyBrowse files
fix(tests): a repro artifact can be regenerated after its input bytes move
The documented two-pass regeneration (reference `--write`, port
`OWN_SHADOW_WRITE=1`, reference `--write`) could not start once the input of a
committed artifact changed. The reference carried the port's committed capture
through verbatim; that capture attests the OLD bytes, so the artifact failed
to verify and the writer refused (exit 1). The port's writer in turn refuses
until the artifact's bytes equal the file on disk (exit 101). Each side waited
for the other, and the only way out was to delete the artifact by hand.
The writer no longer carries a foreign capture of other bytes into a rewritten
artifact: it is dropped with its reason, exactly like a pre-v3 entry, and the
port re-runs and authors its own. Verify mode drops nothing, so a moved input
still reads as a stale artifact.
The control `carry-moved-input` drives a state no committed fixture can reach
(an artifact and its input are always regenerated together). Without the fix
it fails three ways: the stale capture is carried, nothing says why, and the
rewritten artifact does not verify.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
0 commit comments