Fix two stale CLAUDE.md claims the Stage 5 exit audit's own sweep missed

[AdamClemens]

Criterion 10 had eight stale claims, not the six #48 recorded. Both
misses are the exact class that audit was about, and both are recorded in
the files themselves rather than quietly corrected (root CLAUDE.md's
Integrity section).

planning/CLAUDE.md

Called docs/planning/releases.md "a sustained argument that PyFlow
should not have a release process yet", and data/releases.yaml an empty
file "correct rather than incomplete". Both stopped being true in #48,
when reaching the MVP fired that document's own trigger.

Why the sweep missed it: the audit grepped for no release process;
this paragraph says "should not have a release process yet" — the
same claim in words the pattern did not match. An instance of the stated
limits of docs/practices.md's "A stage's documentation sweep is a grep,
not a diff review", now recorded as one.

The paragraph is rewritten to make releases.yaml the worked example of
a trigger firing, which is more useful than the example of one holding
that it used to be.

docs/architecture/CLAUDE.md

Still anchored sequences.md's checkpointing placeholder to "the
specific roadmap task that will build it (TASK-034)".

Why the sweep missed it: #48 re-anchored sequences.md itself and
did not re-read its companion CLAUDE.md in the same change — a
one-file-deep sweep, immediately after writing a rule against exactly
that. TASK-034 landed without building checkpointing, which Stage 5
Criterion 4 explicitly allows, so the placeholder stayed accurate while
its anchor pointed at a closed task.

Scope

Prose only, two CLAUDE.md files, no code. Every other CLAUDE.md was
swept for the same class — nothing further found;
examples/golden-demos/CLAUDE.md's "seven demos" count checks out
against the tree.

🤖 Generated with Claude Code