Phase — Exports (combined)

Status: Completed — public @zamdevio/i18nprune/core surface, CLI --json contract, and programmatic run* helpers are shipped. Hub: active-phase.md.

This folder holds planning and history for the exports / JSON / core surface. Normative user docs live under docs/json/README.md, docs/json/programmatic.md, and docs/exports/.

What shipped (single checklist)

• Command-orchestrator boundary (commands phase + ADR 006).
• Namespaced core facade + flat re-exports (packages/cli/src/exports/core.ts, exports/namespaces/*).
• Stable vs Advanced classification (exports/core.md).
• CLI JSON envelope { ok, kind, data, issues, meta } for all COMMANDS_WITH_JSON_OUTPUT (json/README.md).
• issues[] + issue-code registry (issue codes).
• Programmatic tryResolveContext, stringifyEnvelope, run* for envelope commands (programmatic.md).
• Types: envelope in packages/cli/src/types/core/json/envelope.ts; command payloads under types/command/*/json.ts where applicable.

Companion notes (same phase)

Residual ideas (not tracked here)

Optional later work (product decision): richer summary footer lines with issues[], or extra alignment between global --report-file and stdout envelopes. File an issue or a new phase when scope is concrete.

Execution order (historical)

1. Lock command-orchestrator boundary.
2. Namespaced public API in packages/cli/src/exports/*.
3. Stable vs advanced classification in docs/exports/core.md.
4. Align CLI JSON with typed data payloads + envelope.
5. Single JSON spec: docs/json/README.md; programmatic pointers in docs/json/programmatic.md.