verify-after-apply.md check 0 uses $stamp in a fence that does not define it

[ringo380]

skills/notation-audit/references/verify-after-apply.md check 0 has a project-scope backup snippet that references $stamp, but $stamp is set in a separate fenced block earlier in the same check. The Bash tool does not persist shell state between calls, so the variable is unset at that point and the backup gets a mis-named filename.

The adjacent prose already says to record the stamp and substitute it literally, and commands/notate.md Step 6 item 3 does exactly that - so this snippet contradicts both its own prose and its sibling file.

Low blast radius: the result is a mis-named backup, not a lost file. But it is the same class as the cross-invocation defect fixed in #0.10.0, and it is the one instance the fix wave missed.

Fix: substitute the literal stamp in the snippet, matching commands/notate.md Step 6 item 3.

[ringo380]

Fixed on the scope-independence branch. The project-scope snippet in verify-after-apply.md check 0 now carries a literal stamp value rather than $stamp, matching commands/notate.md Step 6 item 3, with an explicit note that neither enc nor $stamp survives between Bash invocations.

A later review raised the severity: an empty stamp does not just mis-name the backup, it makes a second audit run in the same repo overwrite the first run's only restore point.