chore: the home registry is The Source, never 'the forge' — sweep the misnomer out of the release rail, workflows, and release notes (Forge is a different product; the stored CI secret keeps its historical name)
All checks were successful
CI / Node 22 (push) Successful in 12m10s
CI / Node 24 (push) Successful in 12m4s
CI / Bun (latest) (push) Successful in 12m16s

This commit is contained in:
David Snelling 2026-08-04 10:56:21 -07:00
parent c6c6ea6b57
commit 09352c2b37
4 changed files with 55 additions and 51 deletions

View file

@ -70,8 +70,8 @@ to the caller today.
pre-existing meaning). **Migration-grade exports set `includeHidden: true`** — a
complete-canon export must carry every visibility tier; consumer-facing exports
leave it off.
- **Ops note (consumer-invisible): the release pipeline's forge-registry publish now runs
on CI**, triggered by the release tag, instead of PUTting the tarball from the laptop
- **Ops note (consumer-invisible): the release pipeline's home-registry publish (The
Source, source.soulcraft.com) now runs on CI**, triggered by the release tag, instead of PUTting the tarball from the laptop
over WAN — no change to what gets published or how a consumer installs it.
## v9.0.0 — 2026-08-04 (the field-addressing law: your names and system.*, nothing in between)