docs(releasing): what moving the tag does to the heavy gates

conformance.yml and integration-tests.yml run on a v* tag and nowhere else.
With the tag cut last they now gate the final coordinated tree rather than the
npm-only commit — a tree that never shipped. Worth stating, because it is the
part of the change that makes it clearly an improvement rather than a
rearrangement, and because someone checking whether the move re-triggers a
publish needs to know publish-npm.yml keys on npm-v*, not v*.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NynrRND6ZUwGvq3ZUTCfxG

Author: dmealing

docs/RELEASING.md

@@ -178,6 +178,13 @@ Publish in tier order so a dependent never lands before its dependency. **`forge
    out:** `<version>` *is* the npm version, so a mismatch there always means
    `bun run site:payload` was not re-run.
 
+   **A second effect, and it is an improvement rather than a cost.** `conformance.yml` and
+   `integration-tests.yml` are the heavy gates that run on a `v*` tag and nowhere else.
+   Cutting the tag last means they now run against the FINAL coordinated tree — all four
+   registries bumped, docs refreshed, payload true — instead of the npm-only commit, which
+   is a tree that never actually shipped. `publish-npm.yml` triggers on `npm-v*`, not `v*`,
+   so moving the tag does not re-trigger a publish.
+
 ## Versioning policy
 
 **The version number's only mechanical meaning today is npm's caret rule.** For