fix(bootstrap): on-demand ADF modules missing after bootstrap completes

[SmartBrandStrategies]

Summary

Running charter bootstrap --yes on a fullstack repo creates a manifest.adf that references frontend.adf and backend.adf as on-demand modules, but the bootstrap process does not create those files. This causes charter doctor to immediately warn after a fresh bootstrap.

Steps to Reproduce

charter bootstrap --yes
charter doctor

Actual Result

[warn] adf on-demand modules: Missing or unparseable: frontend.adf (missing), backend.adf (missing)

Expected Result

charter doctor should pass cleanly immediately after charter bootstrap. If the manifest declares on-demand modules, bootstrap should scaffold them (even as stubs).

Workaround

charter adf init --module frontend --yes
charter adf init --module backend --yes

Environment

• charter v0.4.2
• Detected preset: fullstack
• Node 22

Suggested Fix

In the bootstrap step that creates the ADF context ([3/5]), iterate over ON_DEMAND entries in the generated manifest and scaffold any modules that don't already exist on disk.

[SmartBrandStrategies]

Update: v0.5.0 branch (docs/adx-005-cli-ux-feedback) does not address this. Bootstrap still only scaffolds manifest.adf, core.adf, state.adf — the on-demand modules referenced by the manifest (frontend.adf, backend.adf) are not created.

adf init does scaffold them (via FRONTEND_SCAFFOLD / BACKEND_SCAFFOLD constants), but bootstrap's runAdfInitPhase() doesn't use that path. The fix should be straightforward: add the two fs.writeFileSync calls for the on-demand modules in bootstrap's greenfield and force-overwrite branches.

Tagging for inclusion in v0.5.0 before release.