doctor cold-start info for thin pointer files is unfixable and should be suppressed

[stackbilt-admin]

Description

After charter adf migrate, doctor reports [info] adf cold start for CLAUDE.md, .cursorrules, agents.md, and AGENTS.md — saying they are thin pointers with "no stack keywords" and suggesting charter adf populate.

However:

1. These files being thin pointers with no stack keywords is the desired post-migration state
2. charter adf populate targets .ai/*.adf modules, not vendor pointer files — so the suggested fix doesn't resolve the info message
3. Doctor already recognizes these as valid thin pointers ([ok] adf agent config: 4 agent config file(s) are thin pointers to .ai/)

This creates a confusing UX where doctor simultaneously says the files are OK (thin pointers) and not OK (cold start / no stack keywords).

Expected Behavior

Either:

• Suppress cold-start info for files already identified as thin pointers (the [ok] adf agent config check already validates them)
• Or have populate enrich pointer files with a brief stack summary if that's the intended resolution

Environment

• Charter v0.9.2

[stackbilt-admin]

Already fixed in 6f921bf — cold-start suppressed when populated .ai/ modules exist (line 293: && !hasPopulatedModules).