Round 3 of extensive_testing found ae319cb's _noticeIsStaleRenders flag
had the exact footgun it was built to avoid: exportSelected() and
saveSelectedToMediaBin() also write state.notice (through the generic
set() helper, spelled `notice:` in an object literal -- invisible to a
`state.notice =` grep) and never cleared the flag, so a pending
stale-render flag could survive into an unrelated export/save
confirmation and have _recordSegment wrongly clear THAT instead.
Every future writer of state.notice would have needed to remember to
maintain a parallel boolean by hand -- two already didn't. Replaced the
flag with a regex test against the stale-render sweep's own known
message template: _recordSegment now clears state.notice only when its
current text actually IS that message, derived from data instead of
tracked by convention. No writer needs to know about any other writer.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
