adf tidy incorrectly scans charter-managed module index blocks for trigger keywords

[stackbilt-admin]

Description

charter adf tidy detects "vendor bloat" by scanning agent config files for trigger keywords. However, it also scans the <!-- charter:module-index:start --> block in CLAUDE.md, which is a charter-generated rendering of the manifest. This block naturally contains trigger keywords (e.g., "billing", "commit", "security") because it lists the on-demand module triggers.

Tidy then moves those table rows into core.adf as if they were user-authored rules — but they're charter's own output.

Steps to Reproduce

1. Run charter adf migrate (which generates a module index table in CLAUDE.md)
2. Run charter adf tidy
3. Observe that the module index table rows are moved into core.adf

Expected Behavior

Tidy should exclude <!-- charter:module-index:start --> ... <!-- charter:module-index:end --> blocks from keyword scanning, since these are charter-managed content.

Environment

• Charter v0.9.2

[stackbilt-admin]

Fixed in fdde1a9 — see commit message for per-issue details.