v0.2.0 feat: add evidence-backed configuration onboarding

[Tom-R-Main]

Summary

Release 0.2.0 adds an evidence-backed discover → inspect → plan → apply → verify workflow for mixed-catalog projects.

• Make detection configuration-aware, identify uncovered catalogs, and suggest runtime syntax with supporting evidence and uncertainty.
• Add read-only configuration diagnostics and deterministic, reviewable plans with explicit decisions, drift checks, preserved settings, and application receipts.
• Expose versioned JSON, command schemas, bounded findings, structured recovery, and offline translation previews.
• Distinguish generated work from persisted catalog and manifest updates; partial failure reflects retained work, including cache reuse and adoption.
• Explain ambiguous automatic syntax without weakening explicit ICU or placeholder/protected-code validation.
• Package the onboarding guide and release notes. No ExecuFunction files are changed.

Compatibility

This is a pre-1.0 minor release because validate --json changes from a top-level array to a versioned envelope. Consumers must read data.reports and inspect schema_version. See docs/cli-onboarding.md and CHANGELOG.md for migration and retry behavior.

Verification

• Full Go test suite with race detection: passed.
• go vet ./... and golangci-lint run: passed, zero lint issues.
• Aggregate coverage: 77.6%, above the 60% gate; onboarding package: 86.9%.
• Node wrapper tests: all four passed; npm version consistency and package dry-run passed.
• Release binary built with version 0.2.0.
• Independent pre-landing review: no actionable findings.
• GitHub review identified a persistence-status bug; regression tests reproduce discarded-batch and retained cache/adoption cases, and the fix reports actual write boundaries.
• Plan/documentation audit: all nine prioritized items verified.

The acceptance fixture covers an existing temporary marketing catalog, a nested i18next web catalog, literal shell braces, preserved provider/locale settings, plan application and replay, an offline dry-run, and genuine placeholder/protected-code failures.

Risk-path coverage:

discover → configured/uncovered catalogs + runtime uncertainty
inspect  → resolved config + bounded failures + secret-safe JSON
plan     → explicit choices + setting preservation + integrity
apply    → drift rejection + lock cleanup + exact-byte receipts
verify   → no-provider dry-run + strict structural validation

Known test limitations: deterministic filesystem fault injection and precisely scheduled external-writer interleavings are not covered. Locking is cooperative; replay attests matching config, not fresh source readiness. Discovery is bounded and advisory, not an exhaustive runtime proof.

Release

After merge and successful checks, tag the merge commit v0.2.0. The release workflow publishes the five platform packages before the main npm package. Verify registry versions and a clean installed CLI before declaring publication complete.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-04T20:08:02.655901Z	b0e36ae	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b0e36ae60a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Tom-R-Main]

Released as internationalizer@0.2.0. Tag v0.2.0 points to merge commit 6330cf9. Post-merge CI and release run 33915357015 succeeded. Verified latest=0.2.0 for the main package and all five platform packages. A clean npm install passed discovery, explicit decisions, plan/apply/replay, preserved overrides, offline config checks, and translation dry-run; genuine placeholder and protected-code mismatches still fail validation. JSON consumers must migrate validate output to data.reports.