Public: anyone can read this; nobody can change it.
seed-release: tag + Forgejo Release per merged seed; auto-link the package #129
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
new above
offline
The human half of seed history (packages are the machine half). On a
mainpush touchinggenesis/seed.tar.gz— i.e. exactly when a gate-validated reseed merges:seed-r<N>(run number parsed from the reseed merge message,seedVersionfallback) and create a Forgejo Release withseed.tar.gz+manifest.yamlattached and the manifest's repo refs in the body — the Releases tab becomes the browsable catalog of every seed that ever became genesis, pinned to the exact git state.seedgeneric package to this repo (idempotent,PLAT_PAT) so it appears on the repo's Packages tab instead of only under the plat user's package space — fixes the "I don't see the seed in packages" discoverability gap.Attachments and linking are best-effort with loud warnings (
[attachment] MAX_SIZEetc.); the package registry remains the always-works fetch path forresolve_seed. Only merged, coldstart-gated seeds get a release — build-time candidate packages never do.Companion to #125 (auto-triggers) and #127 (publish + resolution). Uses the existing
PLAT_PATsecret; no other setup. First run fires when ther278reseed PR merges.🤖 Generated with Claude Code