v0.5.30

v0.5.30 — release-notes pipeline validated end-to-end

v0.5.29 hit the new pre-publish gate exactly as designed
because actions/checkout@v4 fetch-tags: true fetches tag
REFS but NOT annotated tag OBJECTS — git for-each-ref refs/tags/v0.5.29 --format='%(contents)' fell through to
the COMMIT's auto-message. Gate aborted publish; v0.5.29
stays orphaned per [[only-forward-never-revert]].

v0.5.30 ships the fix: a new step "Refetch annotated tag
objects (actions/checkout #1467)" runs git fetch --tags --force origin between checkout and body-render. Full
annotated tag objects are now available to for-each-ref.

This text. If you see "v0.5.30 — release-notes pipeline
validated end-to-end" as the heading and this body text on
the release page once the chain settles, the full pipeline
works:

1. checkout (shallow tag refs)
2. NEW: refetch --tags --force (full annotated tag objects)
3. for-each-ref %(contents) extracts THIS annotation
4. pre-publish gate confirms '0.5.30' appears in body
5. softprops/action-gh-release publishes /tmp/release_body.md
6. release page shows this annotation

If the body on the release page is anything OTHER than this
text (e.g. a merge commit message, or "v0.5.1 — PGXN...",
or empty), something in step 1-3 still isn't right.

The four Rule 7 gates plus this new pre-publish gate all
have to pass for v0.5.30 to advertise on LATEST.md:

Gate 0: ci.yml regression on push (passed)
Gate 1: release.yml pre-build (Cargo + control + META match tag)
Gate 2: release.yml post-build (SQL filename + control match tag)
NEW: release.yml pre-publish (body mentions tag)
Gate 3: oci-publish.yml post-publish smoke verify

If any of these fails, LATEST.md stays at v0.5.28. That's
the orphan-tag-but-never-advertised behavior, working
end-to-end.

Cargo.toml, pgrdf.control, compose.yml SQL mount, 00-smoke,
META.json (both fields), docs example output. Upgrade bridge
renamed sql/pgrdf--0.5.1--0.5.29.sql ->
sql/pgrdf--0.5.1--0.5.30.sql.

Orphaned. Tag exists on GitHub (the git push succeeded). No
release page (gate aborted softprops/action-gh-release
before it ran). No OCI artifact (oci-publish.yml never
dispatched). LATEST.md still at v0.5.28. Walking past via
v0.5.30 per PROVENANCE.md Rule 4 (v0.5.28 IS in LATEST.md;
v0.5.30 is the next end-to-end-correct release).

33 / 92 unchanged. Hygiene release validating the fix from
v0.5.29's commit. Next batch resumes Track A spikes with
TA-11 (heap_multi_insert) targeting the 19% insert_ms phase
that TA-D2 + TA-D3 left untouched.

Refs: actions/checkout#1467 (the shallow-tag-fetch issue
worked around); v0.5.29 commit ff3bc47 (the release-notes
leak fix); v0.5.30 commit 6816cdb (the annotated-tag
workaround); PROVENANCE.md Rule 7 (the gate stack).

Full Changelog: v0.5.29...v0.5.30