feat: Korean (ko) translation

Summary

First Korean (한국어) localization for Huly Platform, following the structural pattern of PR #10478 (Brazilian Portuguese).

• 66 new ko.json files with 4,084 translated strings
• 5 code changes to register Korean as a selectable language
• 12 existing ui/lang/*.json files updated with the Korean label
• All en.json key sets preserved 1:1; ICU plurals, variables, HTML, and brand names kept verbatim

Korean joins the existing 12 languages (en, ru, es, pt, pt-br, zh, fr, cs, it, de, ja, tr).

Hopefully this is the last project management open source tool I'll ever have to look for. I put in 4,084 strings. Please let this be the one. I can't keep searching for project management tools.

Also, if anyone from the Huly team is reading this: please don't deprecate the project. I just spent 4,084 strings on you.

Code changes

plugins/love/src/types.ts and plugins/love-resources/src/types.ts already include 'ko' — no changes needed.

1. Translation criteria (priority order)

Each translation decision traces back to one of three sources, in priority order:

1. huly-docs — for domain concepts (QMS lifecycle, Owner vs. Author, Action items, Star reactions, etc.). When en.json is ambiguous, huly-docs is the deciding source of truth.
2. en.json — preserved literally for terminology, structure, key order, and part-of-speech distinctions where Korean grammar allows.
3. Korean grammar (no plural inflection, postpositional particles, honorifics, SOV order, counter words, vowel/consonant-aware particles) — applied where (1) and (2) underdetermine the choice.

2. Consistency goals

The translation pursues consistency along five axes:

1. Same English term → same Korean term within a plugin (no within-file drift).
2. Same English term → same Korean term across plugins, except where the underlying domain concept differs (e.g., Review is "면접" in recruit but "검토" in controlled-documents — huly-docs defines them as distinct concepts).
3. English part-of-speech preserved when Korean grammar allows (e.g., past participle Added → passive ~됨; verb stem set → active ~함).
4. English singular/plural collapsed in Korean (Korean has no plural inflection): Document/Documents → 문서, Issue/Issues → 이슈.
5. No anti-patterns (literal-translation tells, Korean spelling errors, redundant subjects). See verification section below.

3. Korean grammar background (for non-Korean reviewers)

The choices below follow Korean grammar, not stylistic preference.

1. No plural inflection — Korean does not mark plurals morphologically. Document and Documents both translate to 문서. The same applies across this PR for Issue/Issues → 이슈, Member/Members → 멤버, Reviewer/Reviewers → 검토자, etc. ICU plural blocks adjust the noun position only: =1 {1 issue} / other {# issues} → 이슈 1개 / 이슈 #개.

2. Postpositional particles attach to the preceding word — Korean grammatical particles (subject 이/가, object 을/를, topic 은/는, locative 에/에서, honorific 님, counter 개, etc.) are written without space to the preceding word. For variable interpolation, {name} + honorific is written as {name}님이, not {name} 님이. A space here is a grammatical error.

3. Vowel/consonant-aware particles — Some particles have two forms based on whether the preceding word ends in a consonant or vowel (이 after consonant, 가 after vowel). For runtime variables we cannot predict this, so we use the standard paired form 을(를), 이(가), 은(는). For known brand names we apply the appropriate form: consonant-ending (Slack을, GitHub은) vs. vowel-ending (Huly를, Linear는).

4. Honorific levels (politeness) — Korean has multiple politeness registers. This translation uses 격식체 (formal-polite, ~합니다 ending) for system messages and notifications, and 명사형 (noun form, no verb ending) for buttons, menu items, tooltips, and placeholders, matching the formal register of huly-docs. Casual ~해요 form is not used.

5. Subject omission — Korean rarely uses explicit second-person pronouns. English "You cannot delete this" → 삭제할 수 없습니다 (no subject), not 당신은 삭제할 수 없습니다. Including 당신 sounds translated rather than native.

6. Active vs. passive form mapping — The translation maps English voice deliberately: past participle (Added, Removed, Created) → passive ~됨; bare verb in activity-log mid-sentence position (set, removed) → active ~함; intransitive verbs (Joined, Reacted) → bare stem (참여, 반응함) since Korean intransitives have no passive form.

7. SOV word order — Korean is subject-object-verb. Some English label structures need rearrangement for natural reading. Example: "Connected to issue X in repo Y" → Y의 이슈 X에 연결됨 (not the literal English order).

8. Counter words (분류사) — Korean numeric expressions require a measure word. 5 issues → 이슈 5개, 5 people → 5명, 5 minutes → 5분. ICU plural blocks are written noun-first (이슈 #개), not number-first (#개 이슈).

Style policies derived from the above

• UI form by context: buttons / menus / tooltips → noun form (저장, 취소, 검색); confirmations → ~하시겠습니까?; notifications → ~합니다/~되었습니다; errors → ~할 수 없습니다 / ~에 실패했습니다
• Variable + particle spacing: no space ({name}님, {count}개, {ws}에서)
• ICU plural counter: noun-first (이슈 #개)
• Singular/plural collapse: one Korean form per concept

4. Faithful representation — key terminology decisions

Each row traces back to either a huly-docs concept, an en.json distinction, or a Korean grammar/etymology rule.

5. Verification

5.1 en.json ↔ ko.json integrity

5.2 Within-file translation consistency

Each ko.json file was scanned for cases where a single plugin renders the same English value as different Korean strings.

• drive-assets CreateFolder / CreateFolderPermission (both EN: "Create Folder") → unified to "폴더 만들기".
• Remaining 6 cases (calendar On/OnUntil, text-editor Add before/Add after, workbench Archive/Archived, time Completed/MarkedAsDone, chunter Mentioned/MentionNotification) have identical English values but distinct semantic roles in source code; Korean intentionally splits to preserve clarity (e.g., 보관 vs. 보관됨 — action vs. state; 앞에 추가 vs. 위에 추가 — column vs. row direction).

5.3 Anti-pattern scan (regex, all 66 files)

6. Test plan

• All 66 ko.json files parse as valid JSON; key sets match en.json exactly
• Built and ran locally via sh ./scripts/fast-start.sh; selected Korean from the language picker
• Verified rendering across Login, Workspace, Tracker, Cards, Controlled Documents, Office (love), HR, and Inbox
• Reviewer verification across email templates (server/account/lang/ko.json)

7. Notes for reviewers

This is the first Korean translation for Huly. Each terminology decision in §4 traces back to either a huly-docs concept, an en.json distinction, or a Korean grammar/etymology rule — not to comparisons with other Korean apps. Please flag any term that reads unnaturally in your UI context; adjustments don't affect key structure.

A few translation choices — notably 교육훈련, 유지관리자, and Configure → 설정 — are reasonable but may benefit from real user feedback down the line.

If this PR gets rejected, I will need therapy. The 반려 key has been translated. I know what it means.