release: ship GraphForge v0.5.1 with fast-fail recovery

[DecisionNerd]

Objective

Ship one version-consistent GraphForge v0.5.1 release across the approved public surfaces.

How this release is run

• ci: keep v0.5.1 publication automation small and resumable #288 owns the small amount of release-automation work that is still needed. CI runs candidate checks, ordering, and routine verification; those checks are evidence, not separate release projects.
• release: create v0.5.1 tag and GitHub Release #194 through release: publish v0.5.1 Node binding, CLI, and skills #198 each represent one human-authorized external release action. They record the resulting public URL/state once; they do not recreate CI test plans.
• Run only an eligible dependency branch. Do not repeat an unchanged candidate check, rebuild already recorded artifacts, or serially replay independent work.
• Stop the affected branch on an absent prerequisite, conflict, or indeterminate registry result. Fix it at its owner.

Close evidence

One short release record identifies the candidate/tag and the final GitHub Release, PyPI, npm, crates.io, and documentation states. It may point to the authoritative CI runs and public URLs; it must not require a second certification cascade.

Non-goals

• Replaying the v0.5.0 incident or altering immutable historical records.
• Creating a ticket for each CI check, retry, or workflow job.
• Running release workflows, publishing packages, or making authorization decisions as part of tracker maintenance.

[DecisionNerd]

§6 tracker status (agent execution)

No production publication performed (no v0.5.0 tag; registries still at prior lines).

Shipped prep (PR): https://github.com/CurateLabs/graphforge-legecy/pull/2820

• Written publication order + rollback (#2801)
• publish.yaml agent-skills job + crates.io plan artifact
• Registry metadata URL corrections (#2808 prep)
• crates.io name-conflict evidence (#2804 blocker)

Child	State	Notes
CurateLabs/graphforge-legecy#2983 tag	OPEN	Human: annotate on verified RC after §5 freeze
#194 GitHub Release	OPEN	Human: after tag; needs CHANGELOG cut + checksums
#196 crates.io	OPEN	Blocked: foreign gf-core/gf-cli names; path+version deps; token
#195 PyPI	OPEN	Workflow exists (OIDC); needs freeze + Release trigger
#198 npm Node+skills	OPEN	Node existed; skills job in PR; needs NPM_TOKEN + freeze + Release
#197 versioned docs	OPEN	docs.yml deploys main; confirm release-SHA set
#199 metadata	OPEN	Source metadata fixed in PR; live verify after publish

Upstream §5 (#2793) still open (version still 0.5.0-dev*, dry-runs, etc.). Do not close #192/#742 until real §6 outcomes exist.

[DecisionNerd]

Execution tracker — stay open until real publish

This tracker and children CurateLabs/graphforge-legecy#2802–#2808 are execution, not prep. They stay open until annotated tag / GitHub Release / crates.io / PyPI / npm / docs deploy / live registry metadata are actually done.

Do not close this tracker when §5 prep (#2793) finishes. Prep PRs that only add publication-order docs or registry-metadata tooling must use Refs (not Closes/Fixes) for #192.

CurateLabs/graphforge-legecy#2845 stays open; do not check off CurateLabs/graphforge-legecy#2845 §6 boxes from prep merges.

[DecisionNerd]

§5 prep closed — execution handoff from CurateLabs/graphforge-legecy#2975

CurateLabs/graphforge-legecy#2975 (publication prep) is closed. Prep tooling/docs landed on legecy main via CurateLabs/graphforge-legecy#2820–#2825.

Still owned here (#166 / CurateLabs/graphforge-legecy#2845 §6), not fake-closed as prep:

1. Apply version freeze to 0.5.0 (make release-version-check / scripts/set_release_version.py 0.5.0) on the RC commit
2. Produce all publishable artifacts from that same commit; fill record_release_artifacts.py JSON
3. Post-freeze dry-runs: docs preview, TestPyPI/wheel clean-install, full cargo publish --dry-run (after gf-core / path-version= disposition)
4. Annotated v0.5.0 tag, registry publishes, GitHub Release

Do not treat CurateLabs/graphforge-legecy#2845 as closed by this handoff.

[DecisionNerd]

Execution tracker — stay open

§5 prep (#2975) is closed. This tracker and tag/publish children stay open until real §6 execution completes. Prep merges must not auto-close this issue.