Skip to content

Releases

DSH Korean Locale 0.0.1-rc.4 — regenerated against DSH 0.2.2-rc.3

Choose a tag to compare

@Nolitor Nolitor released this 15 Nov 03:27

0.0.1-rc.4 — regenerated against DSH 0.2.2-rc.3; rc ladder corrected — 2026-11-14

The pack had stayed at 0.0.1-rc.1 while two later sessions changed its files without
incrementing the history marker, and one of those sessions left a corrupted README.md
(v0.0.1-rc.1 misprinted as a doubled scheme, source and archives mangled the same way — a
naive global replacement of the rc token). This entry fixes the ladder and the corruption, and
regenerates the dictionary
snapshot against the running rc.3 runtime.

Measured before → after (extracted from the installed 0.2.2-rc.3 client bundles with
scripts/extract-dictionaries.mjs; the extractor executes each bundle in a node:vm sandbox,
so ...spread bases and interpolated values resolve instead of being dropped):

Surface Before (rc.1 pack) After (rc.3)
Namespaces 74 77
Keys 3,843 4,253
New rc.3 namespaces — cuaPermissions 66, deepseekChatImport 31, account.notifications 1
New strings translated — 461 (362 in surviving namespaces + 98 in the new ones + contextMenu.back)
Retired namespaces removed — none — see the extraction blind spot below
Retired keys in surviving namespaces — 0
Placeholder repairs pluginManager.updateStepInstalling, settings.webSearch.baseUrlHint {source} / {path} restored
Version 0.0.1-rc.1 0.0.1-rc.4
npm run verify 74 / 3,843 77 / 4,253, 0 missing, 0 extra, 0 placeholder mismatches, en/zh parity 0

Version ladder (owner instruction: the rc.<n> suffix is the agent's history marker, the numeric
part 0.0.1 is owner-gated): rc.1 = 2026-11-05 reset; the 2026-11-06 metadata session changed
release.manifest.json and README.md without bumping (should have been rc.2); the 2026-11-13
session rewrote both READMEs, corrupted README.md, and did not bump (should have been rc.3);
this is the fourth session → rc.4. The corrupted README is restored from HEAD and then
updated for rc.3 rather than patched in place.

Extraction blind spot found after the first regeneration

The first regeneration dropped five namespaces (schedule.manager 215 keys,
permission.access 17, directory-browser 13, inspectorPanel 5, contextMenu 1) because
rc.3 registers them with a variable payload (locale.register(NS, dictionaries)), the
three-argument form (locale.register(NS, locale, dict)), or from lib/client.page.js
instead of lib/client.js. A parser that only accepts an inline object literal cannot bind the
en/zh dictionaries for those calls, so they looked retired while remaining live in the GUI.
That is a silent regression: verify.mjs stays green because it only checks internal
consistency. The extractor now resolves all five shapes (and positional const redefinitions),
and the committed pack carries them again — 237 of the 252 strings are the existing rc.1 Korean
restored verbatim; only contextMenu.back is new.

Tooling and review:

  • scripts/extract-dictionaries.mjs added (contributed by the OpenCode/MiniMax subagent):
    executes the installed client bundles in a sandbox and emits en.json, zh.json, and a
    parity report.
  • The workspace's scripts/measure-locale-delta.mjs was updated for the minified rc.3 bundle
    shape (backtick literals, ctx.effect(() => ctx.locale.register(...)), ...spread bases).
    Before the fix it reported 0 namespaces against rc.3.
  • Korean wording: drafted by the OpenCode/MiniMax pipeline and independently translated/reviewed
    by Gemini 4 Hydrogen (466/466 keys, plus a 20-term glossary), then merged per key with
    placeholder and terminology checks. EXAONE k-exaone_v2.5 did not complete: the provider
    declares no subagent surface (the generic subagent route fails), and the direct
    OpenAI-compatible endpoint answered /v1/chat/completions with
    429 rate_limit_exceeded plus multi-minute stalls, so a full or sampled comparison could not be
    produced. The EXAONE half of the requested two-model comparison remains open.
  • verify.mjs now asserts 77 namespaces / 4,253 keys and the @deepseek-ai/dsh 0.2.2-rc.3
    source commit.

Not changed, and why:

  • engines.dsh stays >=0.2.2-alpha.2 <0.3.0; 0.2.2-rc.3 is inside that declared window.
  • NOTICE:11 still records Base version: DSH 0.2.2-alpha.2; the NOTICE is an attribution
    document owned by the Master, not release metadata.
  • $schema in release.manifest.json remains unresolvable, matching the sibling published
    repository (workspace-wide convention decision, not a per-track defect).

DSH Korean Locale v0.0.1-rc.1 — and why the version number went down

Choose a tag to compare

@Nolitor Nolitor released this 06 Nov 15:27

Read this first: the version number went down, on purpose

This release is 0.0.1-rc.1. The previous release on this repository was v0.2.4.
No work was undone. The @nolit version ladder was reset by owner decision on 2026-11-05.

Every @nolit package moved to one scheme, 0.0.1-rc.N, in which only the rc# moves.
0.2.5 is not a milestone under that scheme — the scheme replaced it. The numbers are not
comparable across the boundary.

Surface Before After
Version scheme per-track (0.2.0 → 0.2.1 → … → 0.2.5) 0.0.1-rc.N
Version 0.2.5 0.0.1-rc.1

What changed since v0.2.4

Regenerated against DSH 0.2.2-rc.1 — not renamed from the alpha snapshot

The pack was regenerated from the rc.1 dictionaries, not carried over from alpha.3.

Surface Before (alpha.3) After (rc.1)
Namespaces 69 74
Keys 3,088 3,843
New rc.1 namespaces translated — stats 177, liveshare 225, forgePanel 253, creationRecommendations 55, pluginRecommendations 25, actionCards 14, contextMenu 1
Existing keys added — 76 (schedule catalog/manager host copy)
Retired keys removed — 66
Retired namespaces removed — claude-code-mods, deepseek-model-label-1017 (no rc.1 registrations)

Verified against the installed runtime: 74 namespaces / 3,843 keys, 0 missing, 0 extra,
0 placeholder mismatches
. Every Korean value carries exactly the {placeholders} of its
rc.1 English source.

Terminology: 작업 공간

The workspace term was unified to 작업 공간 across the pack, matching the alpha.3 dictionary
coverage.

Engine floors raised to the rc.1 minimum

engines.node >=24 → >=24.9. Registration is unchanged: addLanguage({id, label, fallback}) plus per-locale register, with ko selectable under fallback: "en".

Release metadata corrected

release.manifest.json still described the alpha.2 snapshot (68 dictionaries / 3,019 strings)
and carried the v0.2.4 release notes. Both now describe this release.


Install

dsh plugin --profile web add @nolit/dsh-korean-locale

DSH 0.2.2-rc.1 ships no built-in ko (de/en/es/fr/ja/pt/ru/zh). Select Korean in
Settings → Language after installing.

npm: @nolit/dsh-korean-locale@0.0.1-rc.1 · dist-tags rc and latest
Verify: npm run verify → 74 namespaces, 3,843 keys, metadata + apply contract +
typography + stand-down guard pass

Assets

No binary asset. The package is distributed through npm.


한국어

먼저 읽어주세요: 버전 숫자가 내려간 이유

이 릴리스는 0.0.1-rc.1입니다. 직전 릴리스는 v0.2.4였습니다.
작업이 되돌려진 것이 아닙니다. 2026-11-05 소유자 결정으로 @nolit 버전 사다리가
재설정됐습니다.

모든 @nolit 패키지가 0.0.1-rc.N 한 체계로 통일됐고, rc#만 올라갑니다.
0.2.5는 새 체계에서 마일스톤이 아니며, 새 체계가 이를 대체했습니다. 경계를 넘어 숫자를
비교할 수는 없습니다.

표면 이전 이후
버전 체계 트랙마다 제각각 (0.2.0 → 0.2.1 → … → 0.2.5) 0.0.1-rc.N
버전 0.2.5 0.0.1-rc.1

v0.2.4 이후 달라진 것

DSH 0.2.2-rc.1 기준 재생성 — alpha 스냅샷 이름만 바꾼 것이 아닙니다

표면 이전 (alpha.3) 이후 (rc.1)
네임스페이스 69 74
키 3,088 3,843
신규 rc.1 네임스페이스 번역 — stats 177, liveshare 225, forgePanel 253, creationRecommendations 55, pluginRecommendations 25, actionCards 14, contextMenu 1
기존 키 추가 — 76 (스케줄 카탈로그/매니저 호스트 문구)
폐기 키 제거 — 66
폐기 네임스페이스 제거 — claude-code-mods, deepseek-model-label-1017 (rc.1 등록 없음)

설치된 런타임 기준 검증: 74개 네임스페이스 / 3,843개 키, 누락 0, 초과 0, 플레이스홀더
불일치 0
. 모든 한국어 값이 rc.1 영어 원문과 정확히 같은 {placeholder}를 갖습니다.

용어 통일: 작업 공간

작업 공간을 가리키는 용어를 작업 공간으로 통일했습니다(alpha.3 사전 범위 기준).

엔진 하한을 rc.1 최소값으로 상향

engines.node >=24 → >=24.9. 등록 방식은 그대로입니다:
addLanguage({id, label, fallback}) + 로케일별 register, ko는 fallback: "en"으로 선택.

릴리스 메타데이터 정정

release.manifest.json이 아직 alpha.2 스냅샷(68개 사전 / 3,019개 문자열)과 v0.2.4 릴리스
노트를 담고 있었습니다. 둘 다 이번 릴리스 내용으로 고쳤습니다.

설치

dsh plugin --profile web add @nolit/dsh-korean-locale

DSH 0.2.2-rc.1에는 ko가 내장되어 있지 않습니다(de/en/es/fr/ja/pt/ru/zh). 설치 후
설정 → 언어에서 한국어를 선택하십시오.

npm: @nolit/dsh-korean-locale@0.0.1-rc.1 · dist-tag rc, latest
검증: npm run verify → 74 네임스페이스 / 3,843 키, 메타데이터·적용 계약·타이포그래피·
스탠드다운 가드 통과

자산

바이너리 자산 없음. 패키지는 npm으로 배포됩니다.

DSH Korean Locale v0.2.4

Choose a tag to compare

@Nolitor Nolitor released this 29 Oct 14:34

v0.2.4 translates the first-run onboarding screen that shipped with DSH 0.2.2-alpha.2: all 39 settings.account.onboarding* strings (welcome, purpose, detail level, credits, and skip prompts) now render in Korean instead of falling back to English. Six loading messages also use the ellipsis character (…) instead of three dots.

Verified against the installed DSH 0.2.2-alpha.2 runtime: 68 dictionaries / 3,019 keys, 0 missing, 0 extra, 0 placeholder mismatches. Repository, package, and documentation URLs now point at Nolitor/dsh-korean-locale.

Install: dsh plugin --profile web add @nolit/dsh-korean-locale
Verify: node scripts/verify.mjs → metadata, apply contract, typography, and stand-down guard pass.

Assets

  • dsh-korean-locale-0.2.4.zip — SHA-256 40adf1eb68246e9e10af4e2efb9608bcb01b273be47deb612be41132e9fcdaf7

한국어

v0.2.4는 DSH 0.2.2-alpha.2의 첫 실행 온보딩 화면을 번역했습니다. settings.account.onboarding* 39개 문자열(환영, 용도, 상세 수준, 크레딧, 건너뛰기 안내)이 영어로 폴백하지 않고 한국어로 표시됩니다. 로딩 문구 6개도 마침표 세 개 대신 줄임표 문자(…)를 사용합니다.

설치된 DSH 0.2.2-alpha.2 런타임과 대조해 검증했습니다: 68개 사전 / 3,019개 키, 누락 0, 초과 0, 플레이스홀더 불일치 0. 저장소·패키지·문서 URL도 Nolitor/dsh-korean-locale로 정규화했습니다.

설치: dsh plugin --profile web add @nolit/dsh-korean-locale
검증: node scripts/verify.mjs → 메타데이터·apply 계약·타이포그래피·양보 가드 통과.

산출물

  • dsh-korean-locale-0.2.4.zip — SHA-256 40adf1eb68246e9e10af4e2efb9608bcb01b273be47deb612be41132e9fcdaf7

DSH Korean Locale v0.2.3

Choose a tag to compare

@Nolitor Nolitor released this 29 Oct 14:21

v0.2.3 refreshes the Korean dictionary snapshot for DSH 0.2.2-alpha.2 — 68 namespaces / 3,019 strings (117 keys added, 8 retired keys removed), drops a duplicate % from the context tooltip, and keeps the scoped Pretendard typography. engines.dsh is verified as >=0.2.2-alpha.2 <0.3.0.

English README.md is the default document; README.ko.md is its reciprocal Korean translation. CHANGELOG.md and CHANGELOG.ko.md record the version history.

Install: dsh plugin --profile web add @nolit/dsh-korean-locale
Verify: node scripts/verify.mjs → 68 namespaces / 3,019 keys; metadata, apply contract, typography, and stand-down guard pass.

Assets

  • dsh-korean-locale-0.2.3.zip — SHA-256 6485b3b000e8f50a9362d2c40ea20fc4ffdc6a2c57e15b49787cd0d1ad3c1c2d

한국어

v0.2.3은 DSH 0.2.2-alpha.2 기준으로 한국어 사전 스냅샷을 갱신했습니다 — 68개 네임스페이스 / 3,019개 문자열(117개 키 추가, 8개 폐기 키 제거), 컨텍스트 툴팁의 중복 % 제거, 스코프 Pretendard 타이포그래피 유지. engines.dsh는 >=0.2.2-alpha.2 <0.3.0으로 검증했습니다.

영어 README.md가 기본 문서이고, README.ko.md는 이에 대응하는 한국어 번역입니다. CHANGELOG.md와 CHANGELOG.ko.md가 버전 기록을 담습니다.

설치: dsh plugin --profile web add @nolit/dsh-korean-locale
검증: node scripts/verify.mjs → 68개 네임스페이스 / 3,019개 키, 메타데이터·apply 계약·타이포그래피·양보 가드 통과.

산출물

  • dsh-korean-locale-0.2.3.zip — SHA-256 6485b3b000e8f50a9362d2c40ea20fc4ffdc6a2c57e15b49787cd0d1ad3c1c2d

DSH Korean Locale v0.2.2

Choose a tag to compare

@Nolitor Nolitor released this 23 Oct 11:54

v0.2.2 fixes Korean font-stack persistence across reloads. The scoped stylesheet now binds both --dsh-font-family-text and --dsw-font-family at :root:lang(ko) and on body, applies the text seat directly to body text, and keeps code/terminal monospace seats and explicit Settings fonts authoritative. Docs follow the global standard: English README.md plus a reciprocal Korean README.ko.md.

DSH Korean Locale v0.2.1

Choose a tag to compare

@Nolitor Nolitor released this 22 Oct 23:22

Korean language pack for DeepSeek Harness.