docs(release): document the manual check-versions discipline until catalog's pre-flight gate ships

Catalog confirmed --write --commit does not close the ERROR window (execFileSync
gate runs before the --commit conditional regardless of the flag) and is
evaluating a pre-flight gate as a future direction, not yet implemented. Per
their explicit request, document the interim discipline instead of a gate that
doesn't exist yet: run check-versions.mjs manually and confirm 0 ERROR before
--write, even for an unrelated plugin's error.

CLAUDE.md

@@ -340,6 +340,18 @@ unrelated plugin in ERROR aborts it with the catalog edit written but
 uncommitted. When that happens, commit the catalog's `marketplace.json` +
 `README.md` by hand and leave every other dirty file in that repo alone.
 
+**`--write --commit` does NOT close this window (confirmed by catalog,
+2026-08-10).** The gate (`check-versions.mjs`) runs via `execFileSync` before
+the `--commit` conditional, so it throws on any plugin's ERROR — including one
+we did not touch — after the catalog files are written and before commit,
+regardless of whether `--commit` was passed. Catalog is evaluating a
+pre-flight gate (run the check before writing, abort there) but it is **not
+implemented yet** — do not assume it exists. Until it ships: before running
+`--write`, run `node scripts/check-versions.mjs` in the catalog manually and
+confirm 0 ERROR first, even when the only ERROR belongs to an unrelated
+plugin. If it still fires mid-release, fall back to the manual-commit
+recovery above.
+
 ## Hardening roadmap
 
 Empty — the post-v0.1.0 queue (atomic delivery, `.`/`..` rejection,