Exports API Surface

Goals

Expose predictable, discoverable symbols from packages/cli/src/exports/core.ts (and /config if needed).
Export stable/safe capabilities without leaking unstable internals.
Keep CLI-only concerns out of @zamdevio/i18nprune/core.

Over-exposing unstable internals as semver-stable APIs.

Mitigate with:

Stable/Advanced/Internal tiers
Decision records under docs/architecture/decisions/ when a choice spans code + docs
Conservative defaults (export less first)

Tier	Meaning
Stable	Intended integrations; breaking changes are major
Advanced	Documented sharp edges
Internal	Not exported

Public API uses grouped namespaces (json.*, extractor.*, dynamic.*, validate.*, reference.*, context.*, ask.*) plus flat re-exports.

Prefix	Meaning
`scan*`	read-only discovery
`compute*`	pure deterministic derivation
`resolve*`	config/context/path resolution
`run*`	side effects / workflows that return the same `CliJsonEnvelope` as CLI `--json`

Keep extractor and dynamic as separate namespaces with different trust levels.

Audit current exports vs internal capabilities (exports/core.ts + namespace modules).
Classify Stable/Advanced/Internal (table in docs/exports/core.md).
Implement grouped/namespaced public surface (export * as domains on @zamdevio/i18nprune/core).
Add flow-level run* exports for every command in COMMANDS_WITH_JSON_OUTPUT (including generate, report).
Document CLI JSON contract in docs/json/README.md (canonical spec).
package.json exports: primary core / config entrypoints maintained.