Public: anyone can read this; nobody can change it.
seed: cut + publish from the Forgejo UI, SEED_URL germination #125
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
Re-cut the seed from the Actions tab — pick a branch, click Run — instead of a laptop script run. .forgejo/workflows/seed.yml (workflowdispatch): Runs bin/seed on the isolated pool; the public git host is derived from the repo's htmlurl, so the same workflow re-seeds daughters too.
shipped merged
Scope pivot — consolidated into the existing reseed/coldstart flow. The original commit here added a parallel seed.yml; that duplicated what reseed.yml + scripts/reseed-run.sh already do better (build → verify → no-op guard → PR → coldstart germination gate). The branch now carries three focused changes instead:
reseed.yml: auto-triggers.pushtomain(withpaths-ignore: genesis/**so a merged reseed never re-triggers itself) plus a nightly cron at 03:17. The cron is the piece that actually catches the drift class we hit: pushes to sibling system repos (_app-template,mcp, …) never touch this repo, which is how a daughter germinated 2026-08-14 from a seed frozen ~2026-07-23. Thereseed-run.shno-op guard (refs compare) keeps both triggers churn-free.seed-publish.yml(new). Fires on amainpush touchinggenesis/seed.tar.gz— i.e. exactly when a gate-validated reseed PR merges — and mirrors the committed seed into the package registry asplat/seed@<date>-<sha>+latest. The package list becomes the versioned seed history, and the URL feedsSEED_URLgerminations.deploy/lib/mitosis-node.sh: optionalSEED_URLto germinate from a package URL instead of the committed blob. Default behavior unchanged.
seed.yml is deleted from the branch. Validation of the flow itself: dispatch r246 already produced #126 with a verified seed; once these triggers merge, that loop runs itself.
🤖 Generated with Claude Code
Re-cut the seed from the Actions tab — pick a branch, click Run — instead of a laptop script run.
.forgejo/workflows/seed.yml(workflow_dispatch):bin/seedon the isolated pool; the public git host is derived from the repo'shtml_url, so the same workflow re-seeds daughters too.plat/seed@<date>-<sha>plus a movinglatest— the package list becomes the seed history / drift audit trail, browsable in the UI and fetchable by URL.genesis/seed.tar.gzback to the selected branch, so the existing deploy path (deploy/lib/mitosis-node.sh→/opt/mitosis/genesis/seed.tar.gz) keeps working byte-for-byte unchanged.deploy/lib/mitosis-node.sh: optionalSEED_URLfetches a fresher seed (e.g. the parent's…/api/packages/plat/generic/seed/latest/seed-lean.tar.gz) over the committed one at germinate time. Default unset — behavior identical.One-time setup (admin): repo Settings → Actions → Secrets →
PLAT_PAT= aplatPAT with read on allplat/*repos and write onplat/mitosis+ packages. The per-jobgithub.tokencan't read the private system repos, which is why the secret exists.Motivation: benjivers.com germinated 2026-08-14 from a seed frozen ~2026-07-23 —
_app-template28 commits andmcp26 commits stale, invisibly. This makes seed freshness a visible, one-click property.🤖 Generated with Claude Code