2 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	1a7c9fdac3	gitea runs on the host network at genesis ... So it reaches the substrate store's loopback-published postgres and answers where mesh-bootstrap and the builder look for it. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx	2026-09-16 10:33:07 +02:00
jschoubben	79863068fc	Genesis raises the package registry before it builds the base ... The base (mesh-tools) resolves the SDK by version from the mesh's package registry rather than cloning it from a git URL (hq ADR 0076, issue 053), so the registry has to answer and the SDK has to be in it before the base build runs. New steps, before base: seed gitea's database in the substrate store, raise gitea's server on it, create the admin/org/team and the builder's account, seal the builder its registry credential, and publish the SDK on a public base. gitea is adopted as an ordinary module after the base, so its provisioner image can be built. A minimal Go gitea admin client stands in until that module exists. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx	2026-09-16 10:27:11 +02:00