[iscekic]

bot: fix(mobile): correct Thai agent, session, code reviewer and auth copy

Change

Value-only corrections in apps/mobile/src/i18n/locales/th.json. No key is added or removed,
every placeholder, $t() reference and edge space is unchanged, and the catalogs stay at
parity with en.json.

Fixed classes:

• Agent terminology. common.agent and the whole profiles.agents.* editor family now use
  the catalog's established AI-agent loanword instead of the human-representative word; the
  slug labels say "identifier" instead of the animal word (proxy decisions 4-8).
• Token terminology. One transliteration across agentChat.contextUsage.tokens and
  codeReviewer.reviewDetail.tokens; the two keys share an English string, so the catalog
  one-wording rule requires them to match, and the family-majority spelling is used.
• Pull request terms. agentChat.prBadge.open/closed/merged, common.openPullRequest and
  agents.sessionRow.pullRequest use the correctly cased PR acronym, matching
  agentChat.prBadge.draft and the review surfaces that main moved to it in fix(mobile): correct Thai PR review terminology #7999.
• Live states. agents.sessionList.live and codeReviewer.reviewDetail.transcriptLive
  (one English-wording group) now name a live state instead of duplicating the running status;
  the running-state keys keep their own wording.
• Admin terminology. One organization-admin term across the GitHub install alerts, matching
  the existing not-admin message.
• Clearer copy. The profile empty state asks to create a profile; the repo profile label
  names a repository instead of the repurchase word; the remote-exit message drops the temporal
  qualifier for a permanent, non-retryable error; the too-large changes message reuses its
  family's term; the Bitbucket message attaches "unsupported" to the repository, not to Start
  agent; the sign-out message points at the signed-out device; the camera rationale reuses the
  take-photo verb.
• Consistency. Polite retry phrasing across the auth error family; one guidance term for
  custom instructions (instructions.title + overview.customInstructions, one wording group);
  a single ellipsis glyph; the no-decision label no longer implies a pending verdict.

The slash-command Agent field placeholder this item set out to fix is already an agent-name
example on main: #8205 added profiles.slashCommands.agentPlaceholder and pointed
kilo-command-form-sheet.tsx at it. This branch therefore carries no key addition and no
call-site edit, and keeps main's placeholder value.

Rules conformance

• apps/mobile/AGENTS.md restricts copy edits to en.json; this is a reviewed translation
  slice (work item labeled janitor:i18n), hand-editing th.json values with the catalog
  parity checks as the guard.
• No keys removed, no _one families touched, placeholders and $t() references unchanged.
• The tokens, live, custom-instructions and pull-request wording groups were checked as whole
  sets; no wording-exception entry was needed.

Verification (all on this VM, head commit 0f7e3f4)

main is merged at 3b73995. The only conflicting file was th.json, in four regions:
common.openPullRequest, profiles.agents.* and agentChat.prBadge (which main had also
edited), plus the profiles.slashCommands.agentPlaceholder row that both sides added. The
resolution keeps this item's copy fixes, keeps main's newly added profiles.agents.deleteFailed
key, and leaves main's placeholder value in place. The branch now differs from main in that
one file only.

• pnpm --filter kilo-app check:i18n → oxlint i18n config 0 warnings/0 errors, then
  check-catalogs: 87 languages, every catalog matches en.json
• node tools/i18n/check-plurals.mjs → every counted message and every locale declares its
  plural categories
• npx oxfmt --list-different src/i18n/locales/th.json → no output
• npx vitest run src/i18n → 16 files, 1611 tests passed
• Runtime smoke (throwaway script, deleted after the run) with the app's i18next options
  (compatibilityJSON: 'v4', fallbackLng: 'en'), lng: 'th', asserting the changed keys
  resolve to the new Thai values with placeholders bound and no English fallback:
  agentChat.prBadge.open | เปิด PR, closed | PR ที่ปิดแล้ว, merged | PR ที่รวมโค้ดแล้ว,
  draft | PR ฉบับร่าง, common.openPullRequest | เปิด PR,
  agents.sessionRow.pullRequest with number: 7 → PR 7,
  agentChat.contextUsage.tokens | โทเคน, codeReviewer.reviewDetail.tokens | โทเคน,
  codeReviewer.reviewDetail.transcriptLive | สด, agents.sessionList.live | สด,
  codeReviewer.instructions.title | คำแนะนำที่กำหนดเอง,
  codeReviewer.overview.customInstructions | คำแนะนำที่กำหนดเอง,
  codeReviewer.manualReview.starting ends with a single ellipsis glyph,
  codeReviewer.decision.noDecision | ไม่มีข้อสรุป,
  agents.githubInstall.pendingTitle | รอการอนุมัติจากผู้ดูแลองค์กร,
  agentChat.remoteSession.exitUnavailable, agentChat.newSession.noProfiles,
  agentChat.newSession.repoProfile, agentChat.sessionChanges.tooLarge,
  deviceSessions.signOutThisSessionMessage with device: 'Pixel 7',
  authErrors.invalidToken, authErrors.default,
  chat.attachmentPicker.cameraAccessMessage,
  appActions.start.repositoryUnsupported with repository: 'acme/repo',
  profiles.agents.slug, profiles.agents.slugRequired, profiles.agents.slugConflict
• Copy-only catalog change: no screenshots; the affected strings are accessibility labels,
  alerts and placeholders behind authenticated screens.

Proxy answers

The owner's proxy gave these answers in the owner's place.

1. Question: Thai "live" badge (agents.sessionList.live + codeReviewer.reviewDetail.transcriptLive, currently กำลังทำงาน "working") must move to a liveness term. Which wording?
   Answer: สด (Recommended)
   Confidence: 0.70 · Precedent: UX: 'remove redundant copy'; keep badges terse and consistent (session a247f3c19b1e)
2. Question: New key agentChat.modeOptions.agentPlaceholder (placeholder of the slash-command Agent field, was reusing the Code mode label). English value and Thai rendering?
   Answer: en "e.g. Code", th "เช่น code" (Recommended)
   Confidence: 0.65 · Precedent: UX: 'Keep similar elements consistent across surfaces' (session a247f3c19b1e, thought row matching tool call row)
3. Question: GitHub-install alerts (pendingTitle/pendingMessage) currently say ผู้ดูแลระบบ; the brief wants one term, ผู้ดูแลองค์กร (organization admin), matching notAdminMessage. PendingTitle is a short badge-like title — "รอการอนุมัติจากผู้ดูแลองค์กร" is longer than the old title. OK?
   Answer: Yes, use ผู้ดูแลองค์กร in both (Recommended)
   Confidence: 0.80 · Precedent: UX: 'Keep similar elements consistent across surfaces' (session a247f3c19b1e)
4. Question: common.agent (ตัวแทน → เอเจนต์) feeds the slash-command form label, home widget and iOS glanceable. The finding also mentions aligning other Thai agent-naming entries (glanceable.newAgent/openAgents, mode options). The brief restricts changes to common.agent only. Limit to common.agent?
   Answer: Also sweep other ตัวแทน entries
   Confidence: 0.50 · Precedent: Autonomy: 'fix the class of the issue ... on every affected surface' (session 75f8833fe8c1) and 'if you saw a gap, fix it' (session 89824a222897)
5. Question: prBadge closed/merged: brief says use พูลรีเควสต์ like open/draft. Proposed: พูลรีเควสต์ที่ปิดแล้ว / พูลรีเควสต์ที่รวมโค้ดแล้ว. Confirm (these are accessibility labels, not visual badges)?
   Answer: Confirm (Recommended)
   Confidence: 0.80 · Precedent: UX: 'Keep similar elements consistent across surfaces' (session a247f3c19b1e)
6. Question: Sweep scope: Round 1 chose sweeping the other ตัวแทน entries. th.json has ~25 more occurrences, mostly in profiles.agents.* (the custom-agent editor: ตัวแทนโปรไฟล์ "agent profiles", เพิ่มตัวแทน "add agent", ชื่อตัวแทน "agent name", ตัวแทนทาก "agent slug" — that one is already mistranslating "slug" as ทาก "slug the animal") plus common.agents and glanceable. The work-item brief limits the change to common.agent. Sweep all of them to เอเจนต์?
   Answer: All th.json occurrences (Recommended)
   Confidence: 0.85 · Precedent: Fix the root cause and the class of the issue: session 00eb2a1d3e4b, "if anything repeats the same mistake over and over again, fix the class"
7. Question: Agent slug: If sweeping: profiles.agents.slug ตัวแทนทาก ("agent slug" mistranslated as "agent slug-animal") and slugRequired ใส่ตัวแทนทาก / slugConflict ทากนั้นถูกสงวนไว้โดยตัวแทนในตัว contain the animal word ทาก. Fix these too while in the family, and with which word?
   Answer: ใช้ "ตัวระบุ" (Recommended)
   Confidence: 0.55 · Precedent: none
8. Question: Excluded: The slug keys are unrelated to the agent-term finding and the brief did not ask for them. Include or skip?
   Answer: Fix ทาก too
   Confidence: 0.80 · Precedent: If you see a gap or an error, fix it: session 89824a222897, "if you saw a gap, fix it"; session a247f3c19b1e, "fix the error even though it's unrelated"
9. Question: prBadge term: fix(mobile): correct Thai PR review terminology #7999 (merged to main today 11:40Z, after your answer 5) changed Thai agentChat.prBadge.draft to "PR ฉบับร่าง" and prReview.merge.blocked.draftTitle to "PR ฉบับร่าง", leaving prBadge.closed/merged as the buggy "pR ..." that this item fixes. check-catalogs case-folds English, so "draft pull request" now has two Thai renderings ("PR ฉบับร่าง" vs this branch's "พูลรีเควสต์ฉบับร่าง") and fails the catalog check. Which terminology should the prBadge row use?
   Answer: PR across the badge
   Confidence: 0.60 · Precedent: UX: 'Keep similar elements consistent across surfaces' (session a247f3c19b1e, thought row must match tool call row); Product scope: 'Trust the code over documents' (session 269375d6e466, 'only trust code'). Main's merged fix(mobile): correct Thai PR review terminology #7999 now uses PR, so the badge follows it instead of reverting a fresh merge.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

The current PR diff against main is a single file, apps/mobile/src/i18n/locales/th.json (38 value-only lines), and the only increment since the previous review (c6548ee5) is f0 → 0f7e3f4d, which changes codeReviewer.reviewDetail.tokens from โทเค็น to โทเคน so it matches agentChat.contextUsage.tokens; no defect found.

Assumptions: [INFERENCE] The reported pnpm --filter kilo-app check:i18n run was not re-executed (review is read-only), so conformance was checked by reading tools/i18n/check-catalogs.mjs and comparing the affected values by hand. Also [INFERENCE] the en.json/87-catalog portion of this branch's work is already on main, since git diff 6e05b61d8..HEAD now shows only th.json.

Files Reviewed (1 file; en.json read as context)

• apps/mobile/src/i18n/locales/th.json - 0 issues; both tokens keys now read โทเคน (lines 1429 and 2690) and fold to one variant, so the English tokens/Tokens wording group has a single Thai rendering. Placeholders ({{number}}, {{device}}, {{repository}}, {{window}}), $t() refs and edge spacing are unchanged; no pR, ตัวแทน or conflict-marker leftovers remain in the catalog.
• apps/mobile/src/i18n/locales/en.json - 0 issues (context only; no longer in the PR diff); every wording group touched by the Thai changes has exactly two members and both now fold to the same Thai value (Live/LIVE → สด, Tokens/tokens → โทเคน, Custom instructions/Custom Instructions → คำแนะนำที่กำหนดเอง, Open pull request → เปิด PR), so no tools/i18n/wording-exceptions.json entry is needed.

Checks performed

• Confirmed 0f7e3f4d5 touches exactly one line in th.json and that HEAD is still 0f7e3f4d with base 6e05b61d8.
• Re-read the current PR diff (git diff 6e05b61d8..HEAD -- th.json) instead of the patch series, and verified the changed lines against the working tree.
• Checked every English wording group affected by the changed Thai values for the catalog one-wording rule, plus placeholder and key-parity invariants.
• Re-read remote inline comments: both existing en.json threads are line: null (outdated) and that file is not in the current changed-file list, so no finding is carried forward and no duplicate comment was created.

Previous Review Summaries (4 snapshots, latest commit c6548ee)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit c6548ee)

Status: No Issues Found | Recommendation: Merge

Executive Summary

The increment since f16d52bc is one PR-authored commit (c6548ee5f) that switches the Thai agentChat.prBadge row and common.openPullRequest to the PR acronym, and it keeps the catalog's one-wording rule satisfied; no defect found.

Assumptions: [INFERENCE] The reported pnpm --filter kilo-app check:i18n run was not re-executed (review is read-only), so conformance was checked by reading tools/i18n/check-catalogs.mjs rules and comparing the affected strings by hand.

Files Reviewed (88 files in the full PR; 1 file in the incremental commit)

• apps/mobile/src/i18n/locales/th.json - 0 issues; c6548ee5f changed 5 values: common.openPullRequest เปิดพูลรีเควสต์ → เปิด PR, agentChat.prBadge.open → เปิด PR, .closed → PR ที่ปิดแล้ว, .merged → PR ที่รวมโค้ดแล้ว, .draft → PR ฉบับร่าง. Key order, placeholders ({{label}}, {{number}}) and edge spacing are unchanged, and no pR acronym remains in the catalog.
• apps/mobile/src/i18n/locales/en.json - 0 issues (unchanged in this increment); the one-wording group for the raw English open pull request holds only common.openPullRequest and agentChat.prBadge.open, and both now fold to the same Thai value, so the group has a single variant. Other pull request strings differ by wording or placeholders (Open pull request{{number}}, pull request {{number}}) and are separate groups.
• apps/mobile/src/i18n/locales/*.json (87 catalogs) - 0 issues (unchanged in this increment); key parity with en.json is unaffected, and th needs no new entry in tools/i18n/wording-exceptions.json for these lines.
• apps/mobile/src/components/profiles/kilo-command-form-sheet.tsx - 0 issues (unchanged in this increment); the sole consumer of profiles.slashCommands.agentPlaceholder still resolves that key with autoCapitalize="none".
• apps/mobile/src/components/agents/session-pr-badge-model.ts and apps/mobile/src/components/code-reviewer/review-detail-screen.tsx - 0 issues (unchanged in this increment); prBadge.* values are spoken accessibility labels and common.openPullRequest is the CTA, and both resolve the changed keys.

Checks performed

• Confirmed c6548ee5f touches only th.json (5 insertions, 5 deletions) and that git diff 43c8d1be4 HEAD still contains exactly the 88 PR files, so the merge of main at 775883a63 dropped none of main's Thai copy.
• Verified the changed lines against the current th.json at HEAD, not the patch text, and confirmed no pR leftovers and no test asserting the previous values.
• Checked the catalog rules that these values feed: the one-wording group for folded open pull request and draft pull request (the latter now matches prReview.merge.blocked.draftTitle PR ฉบับร่าง), the English-duplicate rule (raw-case values differ, so no key collision), and the English-identical allowlist (Thai differs from English).
• Found no new inline issues; the two existing en.json threads are outdated (line: null) and already answered, so no duplicate comment was created.

Previous review (commit f16d52b)

Status: No Issues Found | Recommendation: Merge

Executive Summary

The only PR-authored change since the last review is a one-line Thai value edit in th.json (agentPlaceholder now renders the example agent id lower-case, matching the lowercase agent ids the field accepts), and it introduces no defect and no new inconsistency that the repo's catalog checks enforce.

Files Reviewed (1 file in the incremental commit; 88 files in the full PR)

• apps/mobile/src/i18n/locales/th.json - 0 issues; line 3681 changed เช่น Code to เช่น code. The key keeps its position beside namePlaceholder/templatePlaceholder, carries no {{placeholder}} or $t() reference, and edge spacing is unchanged.
• apps/mobile/src/components/profiles/kilo-command-form-sheet.tsx - 0 issues (unchanged in this increment); the consumer at line 162 still resolves profiles.slashCommands.agentPlaceholder and the field sets autoCapitalize="none", so a lower-case example matches real agent ids such as code.
• apps/mobile/src/i18n/locales/en.json - 0 issues (unchanged in this increment); the key remains under profiles.slashCommands at line 3745.
• apps/mobile/src/i18n/locales/*.json (86 other catalogs) - 0 issues (unchanged in this increment); key parity with en.json is unaffected by a value-only edit.

Checks performed

• Verified the incremental commit f16d52bc touches only th.json (1 insertion, 1 deletion); the other changes in fdd5519ba6..f16d52bc come from merging origin/main and are not this PR's authored content.
• Verified agentPlaceholder is defined exactly once in each catalog and the only non-catalog reference is kilo-command-form-sheet.tsx:162, so the value is used solely as that placeholder.
• Verified no test or snapshot asserts the previous เช่น Code value.
• Reviewed tools/i18n/check-catalogs.mjs constraints (key parity, placeholders, $t() refs, edge spacing, double spaces, direction marks, one-wording groups); a case-only change to a literal example violates none of them, and e.g. Code belongs to no shared wording group.
• Verified HEAD (f16d52bc) and the existing inline comments immediately before publishing; the earlier agentPlaceholder suggestion thread is outdated (line: null) and already answered, so no duplicate comment was created.
• Not run: node tools/i18n/check-catalogs.mjs, pnpm check:i18n, and vitest i18n suites (review is read-only; the author reports them passing).

Previous review (commit fdd5519)

Status: No Issues Found | Recommendation: Merge

Executive Summary

The incremental commit fdd5519ba6 moves agentPlaceholder from agentChat.modeOptions to profiles.slashCommands, updates the single call site, and preserves every translated value, so the earlier key-context finding is resolved and no new issues were found in the changed lines.

Files Reviewed (88 files)

• apps/mobile/src/components/profiles/kilo-command-form-sheet.tsx - 0 issues; placeholder now resolves profiles.slashCommands.agentPlaceholder (line 162)
• apps/mobile/src/i18n/locales/en.json - 0 issues; key removed from modeOptions and added beside namePlaceholder/templatePlaceholder (line 3678)
• apps/mobile/src/i18n/locales/th.json - 0 issues; key relocated with its Thai value unchanged (เช่น Code)
• apps/mobile/src/i18n/locales/*.json (85 other catalogs) - 0 issues; key relocated in place, one occurrence per catalog, values byte-identical to the pre-move commit

Checks performed

• Verified all 87 catalogs contain exactly one agentPlaceholder key, so parity with en.json holds.
• Verified the moved values are identical in each catalog (- and + lines match for all 87).
• Verified no reference to agentChat.modeOptions.agentPlaceholder remains anywhere in the repo, and the only consumer is kilo-command-form-sheet.tsx:162.
• Verified modeOptions is consumed through the explicit MODE_OPTIONS list, not by iterating translation keys, so the removal cannot affect the mode picker.
• Verified HEAD (fdd5519ba6) and the existing summary comment before publishing; no duplicate inline comments created.
• Not run: pnpm check:i18n / node tools/i18n/check-catalogs.mjs (review is read-only; the author reports these pass on this commit).

Previous review (commit 88f2a62)

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

The PR is a value-only Thai catalog fix plus one new placeholder key added to all 87 catalogs; the only finding is that the new key is filed under the agent-chat mode-options group even though its sole call site is the profiles slash-command Agent field, which has already produced inconsistent translations.

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
apps/mobile/src/i18n/locales/en.json	2326	New agentChat.modeOptions.agentPlaceholder key is grouped with the mode labels although its only consumer is the profiles slash-command Agent field; translators reading it beside code/plan/debug localized Code as the mode word in several catalogs (sl.json npr. Programiraj, af.json bv. Kode, pt.json ex.: Código) while others kept it literal (de.json z.B. Code). Consider profiles.slashCommands.agentPlaceholder or common.agentPlaceholder.

Files Reviewed (88 files)

• apps/mobile/src/components/profiles/kilo-command-form-sheet.tsx - 0 issues; placeholder now resolves the new key (line 162)
• apps/mobile/src/i18n/locales/en.json - 1 issue
• apps/mobile/src/i18n/locales/th.json - 0 issues; 38 value-only Thai fixes, placeholders ({{number}}, {{device}}, {{repository}}) and $t() refs preserved
• apps/mobile/src/i18n/locales/*.json (86 other catalogs) - 0 issues; one agentChat.modeOptions.agentPlaceholder key added to each, so catalog parity is preserved

Checks performed

• Verified every one of the 87 catalogs gained exactly one agentPlaceholder key (parity with en.json).
• Verified no existing index comment was duplicated and HEAD (88f2a62bad) was unchanged before publishing.
• Confirmed modeOptions is consumed through the explicit MODE_OPTIONS list, not by iterating translation keys, so the added key cannot leak into the mode picker.
• Not run: pnpm check:i18n / node tools/i18n/check-catalogs.mjs (review is read-only; the author reports these pass).

Fix these issues in Kilo Cloud

---

_{Reviewed by deepseek-flash-latest · Input: 81.7K · Output: 18.4K · Cached: 1M}

_{Review guidance: REVIEW.md from base branch main}

[iscekic]

bot: Follow-up note: the reply above is now also posted in the review thread itself. No code change beyond fdd5519; the catalog check passes for 87 languages on that commit.

[iscekic]

bot: In-thread reply posted for the kilobot suggestion (see the resolved thread on apps/mobile/src/i18n/locales/en.json). Code state unchanged: fdd5519 moved the key to profiles.slashCommands.agentPlaceholder and the catalog check passes for 87 languages.