daughters: rename plat/_app-template → plat/app-template once mcp ≥0.45.0 propagates; then drop the legacy name #202

New issue

Closed

opened 2026-08-24 21:53:33 +00:00 by plat · 1 comment

plat commented

2026-08-24 21:53:33 +00:00

Owner

Follow-up to the template rename (mcp#42/#43, agents#83, app-template#18, mitosis#200).

Prod is renamed and the template deploys itself. Daughters (plat.local, nest, product-garden, yardwaze, …) still carry plat/_app-template, which keeps working because mcp ≥0.45.0 resolves the new name first and falls back to the legacy name on 404 (mcp/src/template-repo.ts), and agents ≥0.36.3 probe hasFile(plat/app-template/Dockerfile).

Per daughter, AFTER its mcp pin is ≥0.45.0 (propagation lane):

PATCH /api/v1/repos/plat/_app-template {"name":"app-template","website":""} as the daughter's admin (Forgejo keeps a 301 for git/web; API POSTs to the old name break — that is why mcp must be new first).
Confirm template: true survived and REGISTRY_TOKEN is set on the repo.
Optional: create_app plat/app-template {migrate:true,database:true} + release_app if the daughter should host its template like the mother does.

When every daughter has renamed: delete LEGACY_TEMPLATE_REPO + the fallback in mcp (template-repo.ts, design.ts candidates, tests) and templateRepo() in agents' dispatcher.

Also: the committed genesis/seed.tar.gz still bundles plat___app-template until the next reseed PR (auto-opened on the #200 merge) is merged — its coldstart validates the new seed.

🤖 Generated with Claude Code

Follow-up to the template rename (mcp#42/#43, agents#83, app-template#18, mitosis#200). Prod is renamed and the template deploys itself. Daughters (plat.local, nest, product-garden, yardwaze, …) still carry `plat/_app-template`, which keeps working because mcp ≥0.45.0 resolves the new name first and falls back to the legacy name on 404 (`mcp/src/template-repo.ts`), and agents ≥0.36.3 probe `hasFile(plat/app-template/Dockerfile)`. Per daughter, AFTER its mcp pin is ≥0.45.0 (propagation lane): 1. `PATCH /api/v1/repos/plat/_app-template {"name":"app-template","website":""}` as the daughter's admin (Forgejo keeps a 301 for git/web; API POSTs to the old name break — that is why mcp must be new first). 2. Confirm `template: true` survived and `REGISTRY_TOKEN` is set on the repo. 3. Optional: `create_app plat/app-template {migrate:true,database:true}` + `release_app` if the daughter should host its template like the mother does. When every daughter has renamed: delete `LEGACY_TEMPLATE_REPO` + the fallback in mcp (`template-repo.ts`, `design.ts` candidates, tests) and `templateRepo()` in agents' dispatcher. Also: the committed `genesis/seed.tar.gz` still bundles `plat___app-template` until the next `reseed` PR (auto-opened on the #200 merge) is merged — its coldstart validates the new seed. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

plat referenced this issue

2026-08-24 21:54:54 +00:00

program-log: the template deploys itself (2026-08-24) #204

trevato commented

2026-08-31 21:01:39 +00:00

Owner

Closing: done on every axis. Parent renamed (plat/app-template, template=true, public; the legacy name is a Forgejo 301 redirect — kept on purpose so old references resolve). Seed r779 ships the new name. Old-seed daughters are covered twice over: mcp's dual-name resolver + 0.50.0's template-flag self-heal, and germinate is name-aware with a FATAL verify since #242.

trevato closed this issue

2026-08-31 21:01:40 +00:00