Extraction architecture

This section explains how i18nprune finds translation usage from source text and where the limits are.

Keep command behavior in command docs (validate, locales dynamic, missing), and keep extraction internals here.

Pages

• Dynamic key handling
• Regex and static-analysis limits

Primary command links

• validate
• locales dynamic
• cleanup

Adoption barriers moved here

Historical "barriers" docs are consolidated into extraction architecture:

• dynamic/non-literal key limits and mitigation -> dynamic
• regex/static analysis limits -> regex
• CI-safe non-interactive behavior -> command pages and CLI JSON behavior