audit: Stackbilt-dev portfolio .charter/config.json coverage before v0.12

[stackbilt-admin]

Context

Rollout prerequisite for #113 (repo-brief / cold-boot tax reduction).

The brief's quality depends on .charter/config.json having stack / preset set — that's how per-project-type seed strategy for blast is derived. If a significant share of Stackbilt-dev repos lack that config at #113 merge time, Day 1 briefs run in "unknown stack" degraded mode and operators perceive the win as underwhelming.

Proposal

Before v0.12 tagging, audit .charter/config.json presence and completeness across Stackbilt-dev repos. Quantify:

• Repos with .charter/config.json present and stack/preset populated
• Repos with .charter/config.json present but incomplete
• Repos with no .charter/config.json

If adoption is <70%, block v0.12 release on a remediation pass:

• Stand up charter config fill (or equivalent) to bootstrap missing config from repo introspection
• Run across the portfolio before cutting the release

If adoption is ≥70%, release proceeds; lagging repos get remediated opportunistically.

Acceptance

• Portfolio audit completed — counts + list of non-compliant repos
• Remediation decision made based on the 70% threshold
• If remediation: charter config fill scoped and shipped, portfolio swept
• Audit results referenced in v0.12 release notes

Related

• feat(adf): auto-populate context modules from blast/surface/classify — reduce LM-agent cold-boot token cost #113 — the consuming RFC
• refactor(surface,cli): Zod-Core-Out vertical slice for surface #114 — surface Core-Out (prerequisite for feat(adf): auto-populate context modules from blast/surface/classify — reduce LM-agent cold-boot token cost #113 implementation)