Artifact publish stuck in a loop refusing content as "identical to a previously refused version"

Repeatedly hit a publish-refusal loop on Artifact (action: publish) that the documented remedy path never resolved, on a private artifact I own.

Sequence:

1. publish → refused: "You hadn't viewed the live version of this artifact."
2. read on the URL, then Read the full saved file (matched my local content byte-for-byte, modulo the wrapper) → publish again → refused: "this is the identical content already refused against the newer version ..., resent unchanged."
3. Repeated fresh read + full Read + publish two more times, per the error's own instructions → same refusal each time, unchanged.
4. Made a real content change (bumped a timestamp string) → publish → refusal reverted to error 1 ("hadn't viewed").
5. read + full Read again → publish → back to error 2 ("identical... resent unchanged"), despite content now differing from every prior attempt.
6. Only force: true (with the user's explicit confirmation) got it through. Comparing the live content against my pre-edit baseline confirmed no real drift existed — the live content matched my pre-edit baseline exactly, so nothing was actually being discarded.

Expected: the "viewed" gate should clear once the full file is Read, and a publish with genuinely different content should not be flagged as "resent unchanged." Instead the check appears to compare against a stale cached fingerprint of an earlier refused attempt rather than the current live version, requiring force:true to escape even with no real conflict.

🤖 Filed via Claude Code