bug: gc init still emits the legacy city scaffold

[donbox]

Problem

gc init still emits the legacy city-first scaffold instead of the Pack/City v2 transitional shape we are actively documenting and trying to dogfood for 0.13.6.

Today it still writes old-style city.toml content and legacy prompt/formula scaffolding via DefaultCity, WizardCity, and GastownCity.

Why this is release-blocking

gc init is the first real entry point after install for most users.

Right now we have the worst possible combination:

• gc init teaches/emits the old shape
• gc register rejects a real schema = 2 city

That means new users are pushed onto the wrong path, while the intended path is blocked.

Desired outcome for 0.13.6

gc init should emit an honest transitional v2 city shape, even if runtime still enters through city.toml today.

At minimum that means:

• root pack.toml
• root city.toml
• convention-based directories such as agents/, commands/, doctor/, formulas/, orders/, template-fragments/, overlays/, assets/
• .template.md prompt naming where prompt templates are created
• no teaching of the fully old city-root scaffold as the main path

Notes

This does not need to solve the entire future-perfect Pack/City model in one shot. A truthful transitional scaffold is enough for 0.13.6.

[donbox]

Fresh audit on integration/merge-wave-20260410-release after the transitional v2 init patch:

What is fixed:

• gc init now emits pack.toml with schema = 2
• it now creates v2 convention directories like agents/, assets/, commands/, doctor/, formulas/, orders/, overlays/, and template-fragments/
• it no longer creates root prompts/ or root packs/

Remaining seams observed from a fresh init:

• it still creates root hooks/claude.json
• it still writes a legacy [[agent]] entry into city.toml for the default mayor agent
• stdout still says Writing default prompts, which is stale wording now that prompts are scaffolded under agents/

So gc init is much closer, but it is still transitional rather than fully schema-truthful.