bootstrap --force replaces a hand-edited manifest.adf with the template (custom triggers, RULES, METRICS lost) #354

Found in review of #353 (#318 PR3). Exists on main; #353 carries only the VENDORS record across it.

charter bootstrap --force re-scaffolds .ai/manifest.adf (and core.adf / state.adf) from the preset template. The previous file is backed up to .ai/.backup/, but the live manifest loses:

• custom ON_DEMAND triggers (modules registered by adf migrate since feat(adf): register modules adf migrate creates in manifest.adf #348 come back only via orphan detection as (Triggers on: <stem>))
• custom manifest RULES
• the entire METRICS section, including LOC ceilings, so evidence gates silently disappear

Repro: bootstrap a repo, hand-edit manifest.adf (change a trigger list, add a METRICS ceiling, add a RULES line), then run charter bootstrap --force --yes and diff against .ai/.backup/manifest.adf.

--force is documented as "Overwrite existing files (hooks, ADF modules, config)", but users run it to repair hooks or pointers, not to reset governance state. Options: merge the template into the existing manifest through the shared append-only writer (#348) instead of replacing it, or scope --force per artifact. At minimum, print what was replaced and where the backup is.