feat(parser-react): i18n adapter — locale-file resolution for t()/Trans keys

[officialCodeWork]

Summary

TRACKER Step 1.4 — failure mode A2, one of the two make-or-break matching gaps for real codebases. Source says t("team.title"); the Jira screenshot says "Team Members" — or "Membres de l'équipe" when the reporter runs the app in French. Text matching was blind to all of it.

What's in it

• Structured renderedText — entries are now { text, source: "jsx" | "attribute" | "i18n", key?, locale?, branch? }. Provenance flows into match evidence: "membres de l'équipe" matched (i18n key team.title, locale fr) — the agent sees why it matched. (branch is reserved for step 1.5.)
• Locale table — ScanOptions.i18n { localeGlobs, defaultLocale } loads JSON/YAML locale files (nested keys flattened, locale inferred from filename or parent dir, dependency-free mini-glob).
• Key expansion — t("key"), i18n.t("key"), and <Trans i18nKey="key"> expand to one entry per locale, so a screenshot in any language finds the same component. i18next namespace: prefixes fall back to the bare key.
• Per-fixture scan options — golden.json gains a scan field the runner passes through to scanReact (also how future fixtures will declare apiWrappers/baseUrls).

Eval movement

• New fixture a2-i18n-keys (en + fr, t() + <Trans>): all 5 locale queries green, including both French ones.
• Scorecard: 67 pass / 0 fail / 2 xfail / 0 unexpected-pass · precision 1.000 · recall 0.889 · match accuracy 1.000.

Test plan

• 49 unit tests green (5 new: per-locale expansion, Trans resolution, cross-locale matching, evidence provenance, unconfigured no-op)
• pnpm eval gate OK; schema regenerated (structured RenderedText), drift gate green

Documentation

• TRACKER.md — 1.4 done, Status → 1.5

🤖 Generated with Claude Code