fix(i18n): resync ko Storage catalog with the inventory model

[k33bz]

Problem / Motivation

catalogParity is red on main. The Korean catalog is desynced from en across the
whole Storage screen, so Frontend Tests fails for every open pull request that
touches website/:

FAIL src/i18n/catalogParity.test.ts > catalog parity > ko > has no key missing relative to en
  missing 29 key(s)
FAIL src/i18n/catalogParity.test.ts > catalog parity > ko > has no key absent from en
  36 stray key(s)

Reproduced on a pristine checkout of main: 2 failed | 75 passed (77).

Why it matters

Two layers, as #2298 sets out:

1. Product — a Korean user on the Storage screen gets English for all 29 new
   strings, including the destructive-action explanations (cannot_delete_running,
   cannot_delete_resumable). Those are the strings you least want falling back to a
   language the user did not choose.
2. CI — catalogParity runs inside Frontend Tests, so this reds an unrelated
   PR's Frontend Tests → Coverage Gate → PR Readiness chain. Every author is
   currently proving the failure is not theirs before they can call their own PR green.

What changed (motivation → approach → change)

Root cause. The two assertions are one event. ko.json was translated against the
bucket-based Storage screen, and the inventory-model redesign replaced that key set in
en.json without re-syncing Korean. The 36 strays are the retired bucket vocabulary
(bucket_7_30d, threshold_90d, batch_detail, …); the 29 missing are the inventory
vocabulary en gained. It is the rename half of a key migration applied to one locale.

Change. Delete the 36 retired keys from pages.sessionStorage in ko.json and add
the 29 inventory keys. One object in one file; no code, no English, no other locale.

The 36 removals are unreachable, not merely unused — grep -rn "sessionStorage.<key>" website/src returns zero call sites for all 36. The only surviving matches on the
move_to_trash stem are the two new keys at SessionStorageScreen.tsx:271 and :478.

Wording follows the terms already in ko.json rather than a dictionary, per
style/ko.md §2.2 "one concept, one word":

Concept	Rendering	Precedent in this catalog
Session storage	세션 스토리지	pages.performanceTab.session_storage — the screen that links here
Turns	턴	pages.sessionsTab.turns, pages.telemetryPanel.turns_col
Clear (selection)	선택 해제	issueRadar…prBulkBar.clear_selection
Oldest first	오래된순	pages.chatSidebar.sort_oldest
reclaim	회수	the retired headline_detail
Move to Trash	휴지통으로 이동	the retired fact_instant

trash_summary and trash_batch_reason recover their Korean from the retired
batch_detail, which the redesign split into two keys — so that copy is the
translator's own, not new.

Seven keys survived the redesign unchanged and are untouched, visible as context lines
in the diff.

Deliberately out of scope. #2298 also proposes running parity over every catalog on
disk rather than only SUPPORTED_LANGUAGES, so a key migration fails in its own PR
instead of surfacing later as someone else's red build. That is a good change and a
separate one — it alters a shared gate's behaviour and could red other locales. Happy
to open it separately.

Tests

No new tests. This change exists to make existing gates pass, and those gates already
encode the invariant precisely:

• catalogParity.test.ts — key-set parity, non-empty values, placeholder parity
• style/koStyle.test.ts — §1 punctuation, §1.1 Hangul-only, §2 의존명사 spacing +
  placeholder 조사 in both forms + fragment-initial 조사, §2.2 외래어 spellings, §4
  register / 이중 피동 / label full stop, §5 plural categories
• scripts/lib/qa-checks.mjs via check-source-strings.mjs — zero tolerance on
  changed values

Adding a test here would only restate catalogParity.

Manual verification

Check	Result
vitest run src/i18n/catalogParity.test.ts on main	2 failed | 75 passed — bug reproduced
vitest run src/i18n/ on this branch	38 files, 597 passed
node scripts/check-source-strings.mjs	0 new key(s) vs origin/main, 0 finding(s); 0 catalog QA finding(s) among values changed
node scripts/i18n-check.mjs	all sub-gates ok; 20 DNT terms intact across 11 catalogs
npm run check	typecheck clean, lint 0 errors, 840 files / 11240 tests passed
dead-key grep for all 36 removals	0 call sites

One unrelated failure in the full run: src/i18n/unitLiterals.test.ts timed out at
15 s under --coverage with 8 workers. It passes in isolation in 2.7 s, and it
explicitly skips locales/ (lines 187 and 193), so it cannot see this diff. Same
family as #2294 and #2301.

The diff was produced by a round-trip-verified rewrite: json.dumps(…, ensure_ascii=False, indent=2) + "\n" reproduces the original file byte-for-byte
before patching, so the diff contains only the 65 intended lines and no reformatting.

Screenshots / video

N/A — catalog-only diff. No component, layout, or theme changed; the rendered surface
is identical apart from the string values themselves.

Related Issues

Fixes #2298

Checklist

• Single commit with a Conventional Commits title
• Existing tests pass; no new tests (see Tests — the gates already encode this)
• Self-review completed; code follows project style guidelines
• Documentation updated (if applicable) — N/A, no documented behaviour changes
• No secrets, credentials, or internal references in the diff

Contribution License Agreement

[github-actions]

GPT 5.6 Review (fork) — ✅ no blocking findings

Reviewed 462e9f3fa4e301e706b4d96f636984bd0700888a via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 462e9f3

[github-actions]

Opus 5 Review (fork) — ✅ no blocking findings

Reviewed 462e9f3fa4e301e706b4d96f636984bd0700888a via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 462e9f3

[github-actions]

Design Review (Fable 5, fork) — ✅ PASS

Advisory design-level review of 462e9f3fa4e301e706b4d96f636984bd0700888a via the fork AI-review pipeline — updated in place on each push; does not block merge.

Design-Verdict: PASS

Minimal catalog-only resync that exactly restores en↔ko key parity (verified: 7 survivors + 29 additions = en's 36-key set, placeholders intact); right scope, right layer.

[DESIGN-REVIEWED] 462e9f3

[github-actions]

UX Review (Fable 5, fork) — ✅ PASS

Advisory UX-level review of 462e9f3fa4e301e706b4d96f636984bd0700888a via the fork AI-review pipeline — updated in place on each push; does not block merge.

All strings verified against en.json (36-key parity holds), consumption sites in SessionStorageScreen.tsx, and existing catalog precedent. One minor copy inconsistency found; otherwise the Korean strings read cleanly cold, destructive-path copy (cannot_delete_running, confirm_delete_forever) is accurate to the handlers, and terminology follows the catalog's established renderings.

UX-Verdict: PASS

Korean Storage strings are accurate, self-explanatory, and consistent with catalog precedent; the destructive-path copy now reaches Korean users in Korean.

Suggestions

• Sort dropdown mixes spacing for the same suffix: "sort_largest": "큰 순" (spaced) sits beside "sort_oldest": "오래된순" (unspaced, matching chatSidebar.sort_oldest/sort_newest) in one SimpleSelect — align sort_largest to the catalog's unspaced convention.

[UX-REVIEWED] 462e9f3