Best possible solution:

Land the native refresh workflow only after the test-routing guard is repaired and maintainers explicitly accept the guarded contents-write artifact refresh model.

Do we have a high-confidence way to reproduce the issue?

Not applicable for the requested feature: this is new maintainer native i18n automation rather than a reported current-main bug. The patch defect is reproducible from CI: checks-node-compact-small-whole-2 fails the top-level temp-dir helper routing guard after the new test import.

Is this the best way to solve the issue?

No, not merge-ready as-is. Reusing the Control UI translation path is a reasonable owner-boundary shape, but the PR needs the test-routing repair plus maintainer acceptance of the contents-write workflow before it is the best merge path.

Full review comments:

• [P2] Update the helper routing guard — test/scripts/native-app-i18n.test.ts:11
  This import makes test/scripts/native-app-i18n.test.ts an affected importer of test/helpers/temp-dir.ts, but the expected route list in src/scripts/test-projects.test.ts was not updated. The current CI run fails routes top-level test helpers to importing repo tests; either include this test in the expected tooling route or avoid the shared helper import here.
  Confidence: 0.9

Overall correctness: patch is incorrect
Overall confidence: 0.88

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 5e4d71686a6a.

Label changes:

• add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: The external-contributor real behavior proof gate does not apply because this is a MEMBER-authored PR; the PR body and comments provide command-level validation summaries.
• remove status: 👀 ready for maintainer look: Current PR status label is status: ⏳ waiting on author.

Label justifications:

• P2: This is normal-priority native i18n workflow/tooling work with a CI blocker and limited user-facing blast radius.
• merge-risk: 🚨 automation: The diff adds a GitHub Actions workflow that uses provider secrets and pushes generated locale artifacts back to the default branch.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: The external-contributor real behavior proof gate does not apply because this is a MEMBER-authored PR; the PR body and comments provide command-level validation summaries.

PR surface:

Source +42, Tests +168, Config +121, Other +209. Total +540 across 6 files.

Acceptance criteria:

• [P1] node scripts/run-vitest.mjs src/scripts/test-projects.test.ts test/scripts/native-app-i18n.test.ts test/scripts/ci-workflow-guards.test.ts.
• [P1] node --import tsx scripts/native-app-i18n.ts check.
• [P1] git diff --check.

What I checked:

• Repository policy applied: Root AGENTS.md and scoped scripts, test, test/helpers, and UI guides were read; the applicable guidance affected the review through protected maintainer handling, generated i18n artifact alignment, and automation-risk surfacing for workflow changes. (AGENTS.md:1, 5e4d71686a6a)
• Live PR state: Live GitHub reports the PR as open, MERGEABLE but UNSTABLE at head 9e1cf3b, with one failing CI check: checks-node-compact-small-whole-2. (9e1cf3b46e5f)
• Blocking CI failure: The failing CI job reports src/scripts/test-projects.test.ts > routes top-level test helpers to importing repo tests, which matches the PR's new import of test/helpers/temp-dir from test/scripts/native-app-i18n.test.ts without updating the expected routing plan. (src/scripts/test-projects.test.ts:856, 5e4d71686a6a)
• Changed test-helper dependency: The PR changes test/scripts/native-app-i18n.test.ts to import the shared temp-dir helper, making the top-level helper routing expectation need an update or a different local cleanup strategy. (test/scripts/native-app-i18n.test.ts:11, 9e1cf3b46e5f)
• Write-capable workflow: The added workflow runs on main, grants contents: write, checks provider secrets, translates 21 locales, and commits/pushes apps/.i18n/native artifacts back to the default branch with fetch/rebase retry logic. (.github/workflows/native-app-locale-refresh.yml:20, 9e1cf3b46e5f)
• Native refresh implementation: The PR head adds syncNativeLocale, per-locale JSON artifact rendering, placeholder/line-break validation, and command parsing for sync --write --locale. (scripts/native-app-i18n.ts:918, 9e1cf3b46e5f)

Likely related people:

• vincentkoc: Recent main history shows vincentkoc authored the native i18n inventory, Android/Apple localization stack, native i18n CI routing, and the current PR head. (role: recent native i18n feature owner; confidence: high; commits: 6497c3ca1b7b, 9eae0b4d3883, a53b6823c631; files: scripts/native-app-i18n.ts, .github/workflows/native-app-locale-refresh.yml, test/scripts/native-app-i18n.test.ts)
• xialonglee: The recent shared temp-dir helper migration updated src/scripts/test-projects.test.ts routing expectations, which is the guard now failing after this PR imports the helper from native-app-i18n.test.ts. (role: recent test-helper routing contributor; confidence: medium; commits: b9ae0a76fa0c; files: src/scripts/test-projects.test.ts, test/helpers/temp-dir.ts)
• steipete: History shows steipete touched the Control UI i18n docs/script area that this PR reuses as the native translation client and workflow model. (role: adjacent Control UI i18n owner; confidence: medium; commits: b311fd607f6c, b8d08f0cfd0c; files: scripts/control-ui-i18n.ts, ui/AGENTS.md, test/helpers/temp-dir.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.