feat(i18n-ko): desktop slice 1 — settings-preferences, onboarding, shell, permissions

[heeoneie]

Summary

Refs #3977

The Korean catalogs for the four desktop surfaces #3977 scopes, plus the
language selector rows that make them reachable.

This sits on the shared core base from #5100 and does not typecheck on
its own. The other slices' catalogs still have no ko entry, so the
workspace typecheck stays red until the stack is assembled. That is the
stack boundary, not a defect in this branch. Within this branch, each
translation commit removes exactly the missing-ko errors its file was
producing and adds none (see Verification).

Catalog	Strings	Translated
settings-preferences-copy.ts	325	321
onboarding-copy.ts	31	29
shell-copy.ts	524	499
shell-remaining-copy.ts	56	55
permission-center-copy.ts	114	102
Total	1,050	1,006

Counted on the en copy at the base. The remaining 44 strings are:

• 16 enum keys
• one empty string
• 27 others: 14 shortcut glyphs, 10 search-keyword entries, one separator,
  and the second branch of two ternaries

shell-copy.ts also needed two new module-level constants,
KO_STATIC_COMMANDS (70) and KO_SETTINGS_SECTIONS (16). zh-CN and
zh-TW share one ZH_* pair; Korean has no variant to share with, so it
gets its own. Pointing ko at the EN_* constants would have
typechecked and shown 86 English strings in the Korean UI.

The language selector

#3977 requires Korean to be selectable. localeOptions is a plain array
that the UiCatalog<T> type does not constrain, so adding a ko block
alone leaves the selector without Korean and nothing fails. This PR
therefore also adds a ko row to the zh-CN, zh-TW and en catalogs,
following the existing convention: endonyms everywhere (한국어), and a
translated name only in en (Korean).

That is the only reason files outside the ko blocks are touched. The
en catalog grows by two strings, the 'ko' code and 'Korean'.

Three English-only branches removed

Korean has no case distinction and no plural agreement, so three
expressions in the templates do nothing once the locale is Korean:

• permission-center-copy.ts: ${label.toLowerCase()} → ${label}
• settings-preferences-copy.ts: a singular/plural ternary → one template
• shell-copy.ts: a singular/plural ternary → one template

zh-CN and zh-TW already do the same in these places. Otherwise, every
placeholder keeps the name and count it has in the English. Because of
the last change, the Korean shell-copy.ts has 523 strings against 524.

One string needs a maintainer's call

app.useSkillPrompt (Use the ${skillName} skill:) is inserted into the
composer at app-shell.tsx:973 and reaches the model, so it is prompt
text as much as UI copy. I translated it like the rest, but I could not
verify how the model handles the Korean prefix. If you would rather keep
this one in English so skill invocation stays on the path it was tuned
for, say so and I will revert just this string.

How the copy was decided

• Core anchors. The copy is anchored on the Korean strings already in
  the core layer (redaction.ts, relative-time.ts,
  tool-quiet-preview.ts): 14 fixed values this slice must not
  contradict. They apply to status labels, not to the same English word
  used as a verb, so could not be written is not forced into the
  written label.

• Cross-domain terms first. Terms that cross domain boundaries were
  fixed before translating. Their frequencies were measured by a script
  over the base commit rather than estimated, so the table is
  reproducible rather than remembered. Where one English word covers two
  concepts, the Korean keeps them apart:

  • Remove (non-destructive) / Delete / Clear are three different
    words.
  • Diagnostics is 진단 정보 for the data and 진단 for a command
    group.

• OS surface names. These follow what macOS actually shows in
  Korean, because the copy sends users to find them there:
  시스템 설정, 손쉬운 사용, 화면 및 시스템 오디오 녹음,
  개인정보 보호 및 보안. The names were read from the macOS 26.6
  system .loctable resources. Screen Recording in the English copy
  is the pre-macOS 15 name; see below.

• Instruction endings. The Korean distinguishes guidance from a
  request.

  • A sentence that follows a product failure and asks the user to act
    again ends in …해 주세요.
  • Guidance, and requests to correct the user's own input, end in
    …하세요.
  • A message that covers both kinds of cause uses …해 주세요.
  • The rule was written down after the shell catalog was translated;
    all five catalogs were then re-checked against it. That is the last
    commit (one string in onboarding).

• Consonant-dependent particles. Korean particles such as 을/를
  change form with the preceding word's final consonant, which a
  placeholder's value makes unknowable. Sentences are reordered so no
  such particle follows a placeholder, for example
  `“${name}” 삭제할까요?`.

• Four mechanical checks ran over all five finished catalogs:

  1. Glossary terms appear in their fixed Korean form. Whole-string labels
     are compared exactly; inside sentences, the fixed stem must be present.
  2. Placeholder names and counts match the English.
  3. Sentence-final punctuation mirrors the English.
  4. No consonant-dependent particle sits directly after a placeholder.

  Results on the five catalogs as committed:

  • Checks 2–4: nothing flagged in any catalog.
  • Check 1: 12 hits.
    • 8 are documented exceptions recorded during review: 6 in
      shell-copy.ts and 2 in settings-preferences-copy.ts. Examples are
      key cap names left as printed on the keys, the adjective in
      clear sky, and the noun copy.
    • The other 4 are in the three smaller catalogs. 3 are false positives
      on inflected forms: 지원이 종료 for 지원 종료, 켤 for 켜,
      지울 for 지우. 1 is an approved wording, 생성할 수 없음 for
      Daily Review generation is unavailable.

  Check 1 has a known limitation. It matches the fixed Korean stem as a
  literal substring, so a correctly inflected form whose stem changes
  shape is reported as a mismatch and needs a human look. On
  shell-copy.ts, each checker was also verified by seeding a deliberate
  error and confirming that it was caught.

Verification

Renderer typecheck. tsc -p tsconfig.renderer.json --noEmit in
apps/desktop, run at the base and after each commit:

Commit	Errors	Removed	Added
base a193ad8d1	611
onboarding	610	TS2741 (typed catalog, so no TS7053)	none
permission center	608	TS2741, TS7053	none
shell remaining	606	TS2741, TS7053	none
settings preferences + selector	604	TS2741, TS7053	none
shell	602	TS2741, TS7053	none
onboarding request form	602	none	none

• The remaining 602 are not from this PR:
  • 98 Property 'ko' is missing errors in other slices' catalogs, plus
    their indexing errors.
  • 231 unresolved @maka/ui imports, because workspace packages were not
    built in my checkout.
• Three of them sit in files this PR touches, and each is present
  identically at the base: one unresolved @maka/ui import in
  permission-center-copy.ts, and two missing exports from the built
  @maka/core in shell-copy.ts.

No English fallbacks. The Korean copy never points at the English
copy. Lines added on this branch contain no EN_* or enCopy reference.
In shell-copy.ts, the only identifiers in value position inside the
Korean copy are:

• KO_STATIC_COMMANDS
• KO_SETTINGS_SECTIONS
• the shared STATIC_COMMAND_KEYWORDS

Structure. With string literals masked:

• KO_STATIC_COMMANDS and KO_SETTINGS_SECTIONS match their EN_*
  counterparts token for token.
• Each ko block matches its en block, except for the removed
  ternaries.

String counts. Every Korean catalog has the same keys and the same
number of strings as its English one, except shell-copy.ts (523 against
524, see above). The English strings that existed at the base are
unchanged.

Lint and format. biome check is clean on the five files.

Not run:

• The test suites, because workspace packages were not built locally.
• Repo-wide lint, format, build and typecheck. The typecheck is expected
  to stay red; see Summary.
• Screenshots.

ci.yml, which provides the required test check, triggers only on pull
requests targeting main, so that check will not run here until the stack is
assembled. The Verification section above is the evidence until then.

Observations about the English copy

These are not change requests, and this PR does not touch them. They are
just things that surfaced while translating:

• Screen Recording is the name macOS used before 15. The current pane is
  "Screen & System Audio Recording", and the Korean follows the current
  name so users can find it.
• The en search-keyword arrays in shell-copy.ts carry a few Simplified
  Chinese entries, which look like a copy from the zh-CN row.
• Plan mode and Plan Mode both appear. The Korean uses the proper-noun
  spelling consistently.

Remaining before this is ready

• ko unit tests for the five catalogs
• Screenshots at 1280 and 430
• Repo-wide build and typecheck green — blocked on the rest of the
  stack, not on this branch

#3977's acceptance criteria include all three, which is why this is a draft
and why it says Refs rather than Fixes.

Not in scope

• workHubHelp disagrees across en, zh-CN and zh-TW (workHubHelp copy disagrees across en, zh-CN, and zh-TW #5289).
  The Korean follows en pending that issue.
• Shared Simplified constants. zh-CN and zh-TW share Simplified
  constants in the command palette and settings sections (zh-TW shows Simplified Chinese in the command palette and settings section names #5377).
• Unread keys. Six keys in shell-remaining-copy.ts are read by no
  code. The type requires them, so they are translated.
• Settings sidebar labels. They come from settings-navigation-copy.ts,
  which belongs to a later slice. The command palette's section names
  here use the same English. When that catalog is translated, its labels
  should use the same Korean as KO_SETTINGS_SECTIONS.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: Claude Code — drafted the Korean copy for the five
catalogs, the verification scripts, and this description. The terminology
and every judgment call were reviewed and decided by me, and I verified
and submitted the result. Each of the six commits ends with a
Generated-by: Claude Code trailer. This repository merges by squash
only, and GitHub's default squash message lists the commit messages, so
the trailer is carried into the squash commit and remains its final
trailer. If the squash message is edited at merge time, please keep that
line as the last paragraph.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

No tests were added (ko unit tests are a remaining #3977 criterion).
biome passes on the changed files, and the per-file typecheck result is
under Verification. Repo-wide typecheck is expected to stay red on this
branch alone.

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No