open-multi-agent-kit 0.78.5 → 0.78.7

package/dist/util/terminal-layout.js

@@ -98,7 +98,11 @@ export function fitHeight(lines, height) {
 }
 /** Wrap lines in a themed box panel. */
 export function panel(title, lines, width) {
-    const processed = lines.map((line) => padEndVisible(truncateLine(line, width), width));
+    const processed = lines.map((line) => {
+        const truncated = truncateLine(line, width);
+        const vw = visibleTerminalWidth(truncated);
+        return vw < width ? truncated + " ".repeat(width - vw) : truncated;
+    });
     return box(processed, title || undefined);
 }
 /** Render a section header. */

package/dist/util/version.js

@@ -1,6 +1,7 @@
 import { readFileSync } from "fs";
 import { dirname, join } from "path";
 import { fileURLToPath } from "url";
+import { OMK_RUNTIME_VERSION } from "../version.js";
 export const OMK_REPO_URL = "https://github.com/dmae97/open-multi-agent-kit";
 let cachedVersion;
 let cachedRepoUrl;
@@ -47,5 +48,5 @@ export function getOmkRepoUrlSync() {
     return cachedRepoUrl;
 }
 export function formatOmkVersionFooter(version = getOmkVersionSync()) {
-    return `omk v${version} • GitHub: ${getOmkRepoUrlSync()}`;
+    return `omk package v${version} • runtime ${OMK_RUNTIME_VERSION} • GitHub: ${getOmkRepoUrlSync()}`;
 }

package/docs/2026-06-10/critical-issues.md

@@ -0,0 +1,20 @@
+# 2026-06-10 Critical Issues
+
+## Critical Init Status
+- No critical init artifacts were missing when this daily file was generated.
+### Missing critical artifacts
+- None detected.
+
+
+## Critical Artifacts Present
+- ✅ `AGENTS.md` — top-level operating contract
+- ✅ `.kimi/AGENTS.md` — Kimi-specific operating rules
+- ✅ `.omk/config.toml` — OMK project runtime settings
+- ✅ `.omk/agents/root.yaml` — root coordinator agent
+- ✅ `.kimi/mcp.json` — Kimi project MCP registry
+- ✅ `.omk/hooks/pre-shell-guard.sh` — destructive shell guard
+- ✅ `.omk/hooks/protect-secrets.sh` — secret write guard
+- ✅ `.omk/memory/graph-state.json` — local ontology graph database
+
+## Escalation Rule
+- Treat missing shell/secret guards, root agent config, MCP registry, or ontology graph as critical until restored.

package/docs/2026-06-10/improvements.md

@@ -0,0 +1,14 @@
+# 2026-06-10 Improvements
+
+## Current Improvement Backlog
+### Optional init/support artifacts to add or refresh
+- None detected.
+
+### Critical init artifacts currently blocking reliable chat startup
+- None detected.
+
+
+## Suggested Focus
+- Keep `omk chat` startup idempotent and non-destructive.
+- Prefer local graph memory for default ontology state.
+- Keep generated daily docs small, dated, and safe to edit by hand.

package/docs/2026-06-10/init-checklist.md

@@ -0,0 +1,25 @@
+# 2026-06-10 Required Init Checklist
+
+**Run ID:** chat-2026-06-09T17-45-36-041Z-4951
+**Ontology graph:** `.omk/memory/graph-state.json`
+
+## Required Artifacts
+- ✅ `AGENTS.md` — critical; top-level operating contract
+- ✅ `.kimi/AGENTS.md` — critical; Kimi-specific operating rules
+- ✅ `DESIGN.md` — support; design/brand source of truth
+- ✅ `.omk/config.toml` — critical; OMK project runtime settings
+- ✅ `.omk/agents/root.yaml` — critical; root coordinator agent
+- ✅ `.kimi/mcp.json` — critical; Kimi project MCP registry
+- ✅ `.omk/mcp.json` — support; legacy OMK MCP fallback
+- ✅ `.omk/lsp.json` — support; bundled TypeScript/Python LSP config
+- ✅ `.omk/hooks/pre-shell-guard.sh` — critical; destructive shell guard
+- ✅ `.omk/hooks/protect-secrets.sh` — critical; secret write guard
+- ✅ `.omk/memory/graph-state.json` — critical; local ontology graph database
+- ✅ `.kimi/skills` — support; Kimi skill directory
+- ✅ `.agents/skills` — support; portable skill directory
+
+## Recovery Command
+```bash
+omk init
+omk doctor
+```

package/docs/2026-06-10/plan.md

@@ -0,0 +1,20 @@
+# 2026-06-10 OMK Chat Plan
+
+**Run ID:** chat-2026-06-09T17-45-36-041Z-4951
+**Generated by:** omk chat bootstrap
+
+## Purpose
+- Start every chat with a dated workspace for planning, issue triage, and verification evidence.
+- Keep ontology-backed memory available before the root coordinator starts.
+- Make required init state visible without overwriting user-authored docs.
+
+## Today Plan
+1. Review `init-checklist.md` and resolve missing critical init artifacts first.
+2. Use `improvements.md` as the active improvement backlog.
+3. Use `critical-issues.md` for blocking defects, safety risks, and verification gaps.
+4. Record command evidence before claiming work is complete.
+
+## Stop Condition
+- Critical init artifacts are present.
+- Ontology graph exists at `.omk/memory/graph-state.json`.
+- Any new code/docs changes have explicit verification evidence.

package/docs/2026-06-11/critical-issues.md

@@ -0,0 +1,20 @@
+# 2026-06-11 Critical Issues
+
+## Critical Init Status
+- No critical init artifacts were missing when this daily file was generated.
+### Missing critical artifacts
+- None detected.
+
+
+## Critical Artifacts Present
+- ✅ `AGENTS.md` — top-level operating contract
+- ✅ `.kimi/AGENTS.md` — Kimi-specific operating rules
+- ✅ `.omk/config.toml` — OMK project runtime settings
+- ✅ `.omk/agents/root.yaml` — root coordinator agent
+- ✅ `.kimi/mcp.json` — Kimi project MCP registry
+- ✅ `.omk/hooks/pre-shell-guard.sh` — destructive shell guard
+- ✅ `.omk/hooks/protect-secrets.sh` — secret write guard
+- ✅ `.omk/memory/graph-state.json` — local ontology graph database
+
+## Escalation Rule
+- Treat missing shell/secret guards, root agent config, MCP registry, or ontology graph as critical until restored.

package/docs/2026-06-11/improvements.md

@@ -0,0 +1,14 @@
+# 2026-06-11 Improvements
+
+## Current Improvement Backlog
+### Optional init/support artifacts to add or refresh
+- None detected.
+
+### Critical init artifacts currently blocking reliable chat startup
+- None detected.
+
+
+## Suggested Focus
+- Keep `omk chat` startup idempotent and non-destructive.
+- Prefer local graph memory for default ontology state.
+- Keep generated daily docs small, dated, and safe to edit by hand.

package/docs/2026-06-11/init-checklist.md

@@ -0,0 +1,25 @@
+# 2026-06-11 Required Init Checklist
+
+**Run ID:** chat-2026-06-10T18-23-46-194Z-9124
+**Ontology graph:** `.omk/memory/graph-state.json`
+
+## Required Artifacts
+- ✅ `AGENTS.md` — critical; top-level operating contract
+- ✅ `.kimi/AGENTS.md` — critical; Kimi-specific operating rules
+- ✅ `DESIGN.md` — support; design/brand source of truth
+- ✅ `.omk/config.toml` — critical; OMK project runtime settings
+- ✅ `.omk/agents/root.yaml` — critical; root coordinator agent
+- ✅ `.kimi/mcp.json` — critical; Kimi project MCP registry
+- ✅ `.omk/mcp.json` — support; legacy OMK MCP fallback
+- ✅ `.omk/lsp.json` — support; bundled TypeScript/Python LSP config
+- ✅ `.omk/hooks/pre-shell-guard.sh` — critical; destructive shell guard
+- ✅ `.omk/hooks/protect-secrets.sh` — critical; secret write guard
+- ✅ `.omk/memory/graph-state.json` — critical; local ontology graph database
+- ✅ `.kimi/skills` — support; Kimi skill directory
+- ✅ `.agents/skills` — support; portable skill directory
+
+## Recovery Command
+```bash
+omk init
+omk doctor
+```

package/docs/2026-06-11/plan.md

@@ -0,0 +1,20 @@
+# 2026-06-11 OMK Chat Plan
+
+**Run ID:** chat-2026-06-10T18-23-46-194Z-9124
+**Generated by:** omk chat bootstrap
+
+## Purpose
+- Start every chat with a dated workspace for planning, issue triage, and verification evidence.
+- Keep ontology-backed memory available before the root coordinator starts.
+- Make required init state visible without overwriting user-authored docs.
+
+## Today Plan
+1. Review `init-checklist.md` and resolve missing critical init artifacts first.
+2. Use `improvements.md` as the active improvement backlog.
+3. Use `critical-issues.md` for blocking defects, safety risks, and verification gaps.
+4. Record command evidence before claiming work is complete.
+
+## Stop Condition
+- Critical init artifacts are present.
+- Ontology graph exists at `.omk/memory/graph-state.json`.
+- Any new code/docs changes have explicit verification evidence.

package/docs/ARCHITECTURE_ANALYSIS_CODEGRAPH.md

@@ -0,0 +1,223 @@
+# OMK CLI 아키텍처 분석 보고서 (CodeGraph)
+
+> 분석일: 2026-05-25
+> 도구: CodeGraph (SQLite 기반 코드 의존성 그래프)
+> 대상: /home/yu/open_multi-agent_kit (open-multi-agent-kit v1.1.18)
+
+---
+
+## 1. 개요
+
+OMK CLI는 Commander.js 기반의 단일 진입점(entry point)을 가진 Node.js CLI 도구로, 4개의 핵심 축으로 구성됨.
+
+## 2. Entry Point & Command Routing 흐름
+
+Entry: src/cli.ts → main.ts → createOmkProgram() → registerCliCommands()
+Root Flow (no args): runRootHudFlow() → HUD + mode selector + spawn
+
+병목: Command Registry Coupling — register-*.ts가 commands/와 1:1 coupling
+
+## 3. Theme System
+
+src/brand/palette.ts (21색상) → src/util/theme.ts (God Module, 230 inbound)
+
+## 4. Render Pipeline
+
+src/hud/render.ts (42KB, 74 nodes, 115 outbound) → LiveHudRenderer
+
+## 5. Orchestration
+
+src/orchestration/executor.ts (39KB, DAG 실행 엔진)
+src/orchestration/routing.ts (825L, 73 nodes)
+src/orchestration/parallel-orchestrator.ts (650L, 59 nodes)
+
+## 6. 의존성 분석 (CodeGraph 기반)
+
+Hub Modules:
+- src/util/fs.ts — 496 total degree
+- src/util/theme.ts — 343 total degree
+- src/providers/provider-router.ts — 298 total degree
+
+최고 복잡도 파일:
+- providers/provider-task-runner.ts — 1,442L
+- mcp/omk-project-server.ts — 1,737L
+- commands/mcp.ts — ~1,800L
+- commands/design.ts — ~1,600L
+
+순환 의존성: File-level 명확한 순환은 미발견. 단 theme.ts와 render.ts 간 강한 coupling 존재.
+
+## 7. 병목 지점
+
+Critical:
+1. util/fs.ts (496 degree) → path/project/run으로 분리
+2. util/theme.ts (343 degree) → ansi/colors/panels로 분리
+3. providers/provider-task-runner.ts (1,442L) → runner/selection/state 분리
+
+Major:
+4. orchestration/routing.ts (825L)
+5. mcp/omk-project-server.ts (1,737L)
+6. hud/render.ts (1,300+L)
+
+## 8. 개선 권장사항
+
+P0: util/fs.ts, util/theme.ts, provider-task-runner.ts, routing.ts 구조적 분리
+P1: commands/ 서브디렉토리화, cli/register 동적 임포트
+P2: orchestration/ → execution/, routing/, ensemble/, evidence/ 분리
+P3: theme.ts와 render.ts 간 interface 기반 의존성 전환
+
+## 9. 결론
+
+OMK CLI는 기능적으로 성숙했으나 구조적 부채가 누적된 상태.
+핵심: util/fs.ts + util/theme.ts 허브화 → 1,000L+ 파일 5개 이상 → orchestration/ 책임 과다
+권장 우선순위: fs/theme 분리 → provider-task-runner 분리 → orchestration 관심사 분리 → commands 서브디렉토리화
+
+---
+
+## 10. HUD Render Pipeline Decoupling (2026-05-25)
+
+### 변경 개요
+`src/hud/render.ts` → `src/util/theme.ts` 간 강한 coupling 해소 작업 완료.
+
+### 생성/변경 파일
+- `src/hud/types.ts` (새로 생성)
+  - `HudStyle`, `HudStatus`, `SystemUsage`, `HudTheme` 인터페이스 정의
+  - render pipeline이 필요로 하는 theme 계약을 당소화
+- `src/util/theme.ts` (수정)
+  - `hudTheme: HudTheme` 객체 추가 → 인터페이스 구현체
+- `src/hud/render.ts` (성형 보전)
+  - `theme.ts`의 직접 import를 제거하고 `HudTheme` 타입의 `theme` 객체를 하나의 출입점에서 사용
+  - `fetchHudDashboardData()`: compact/medium/full/section 4개 모드의 중복되던 run state/git/session 폴링 로직 통합
+  - `buildHudHeader()`: matrix rain + 헤더 + summary 생성 함수 분리
+  - `buildHudFooter()`: 기존 `renderFooter` 을 이름 변경 후 독립 함수화
+  - dashboard renderer 4개 모드 모두 `fetchHudDashboardData` + `buildHudHeader` + `buildHudFooter` 조합으로 단순화
+
+### 결과
+- **순환 의존성 해소**: render.ts → theme.ts 직접 의존이 `HudTheme` 인터페이스로 대체되면서 구현체 교체 시 단 하나의 import만 바뀌면 됨
+- **코드 줄이기**: render.ts 1,300+줄 → 1,076줄 (약 18% 감소)
+- **경로 최소화**: HUD 렌더러의 공통 데이터 폐치가 한 곳에서 관리되면서 바뀌는 경우의 추적성 향상
+- **컴파일 성공**: `tsc --noEmit` 패스
+
+---
+
+## 11. OMK CLI V2 런타임 아키텍처 (2026-05-28)
+
+> 아키텍처 문서: `docs/OMK_CLI_V2_RUNTIME_ARCHITECTURE.md` (2058 lines)
+> 구현 진행률: ~85%
+
+### 11.1 핵심 문제 (해결됨)
+
+1. **Prompt bloat**: 2자 요청에 전체 오케스트레이션 계약 전송 → `context-broker.ts`에서 `promptMode === "dnc-nlp"` 체크 추가
+2. **available ≠ required MCP 분리**: `CapabilityPlan`로 분리 완료
+3. **Optional MCP 실패 = 치명적**: 경고로 변경 완료
+4. **Provider raw stdout 유출**: `ProviderEventNormalizer` → `OutputRouter` 경유 필수
+5. **Slash commands 미연결**: `CommandBus`에 핸들러 등록 완료
+6. **kimi-cli 의존성**: `kimi-api` (직접 Moonshot HTTP)로 대체 완료
+
+### 11.2 런타임 파이프라인 (현재)
+
+```
+User Input → Clipanion CLI → OmkCommand.executePipeline()
+  → CommandBus (slash commands registered)
+  → IntentClassifier (classifyIntent)
+  → CapabilitySelector (selectCapabilities)
+  → RuntimeSidecar (compileBloatToNlp)
+  → OutputRouter (ThemePalette resolve)
+  → ThemeRenderer / NlpRenderer / JsonRenderer / NlgRenderer
+```
+
+### 11.3 핵심 런타임 파일
+
+| 파일 | 라인 | 역할 |
+|------|------|------|
+| `src/runtime/contracts/command-envelope.ts` | ~130 | CommandKind, OutputFormat, StdoutMode, OutputProfile, OmkEvent, CapabilityPlan |
+| `src/runtime/contracts/reasoning-trace.ts` | 144 | RTE 스키마 (ReasoningTrace, TraceSummary, ConsentAwareNlgInput/Output) |
+| `src/runtime/debloat-nlp.ts` | ~531 | classifyIntent, classifyRisk, selectCapabilities, compileBloatToNlp, filterMcpConfigForTurn, selectProviderRuntime |
+| `src/runtime/command-bus.ts` | 88 | CommandBus 인터페이스, slash → handler 매핑 |
+| `src/runtime/slash-commands.ts` | 194 | SlashCommandParser + /model, /status, /theme, /help 핸들러 |
+| `src/runtime/provider-event-normalizer.ts` | 555 | KimiEventNormalizer + KimiPrintNormalizer, i18n bilingual |
+| `src/runtime/output-router.ts` | ~200 | OutputRouter 인터페이스, ThemePalette resolve, routeTrace, NLG renderer |
+| `src/runtime/renderers.ts` | 272 | ThemeRenderer (opencode-style), NlpRenderer (bilingual), JsonRenderer |
+| `src/runtime/ui-components.ts` | 301 | statusCard, providerCard, memoryCard, mcpHealthCard, errorBox, traceSummaryCard, consentNotice |
+| `src/runtime/nlg-renderer.ts` | 190 | NlgRenderer (renderTrace, renderSummary, renderConsentReport, renderTurnResult) |
+| `src/runtime/reasoning-trace.ts` | 354 | RTE 구현 (createReasoningTrace, redactTrace, summarizeTrace, generateConsentReport, createReasoningTraceStore) |
+| `src/runtime/context-broker.ts` | 375 | ContextCapsule 빌더, promptMode dnc-nlp 체크 |
+| `src/runtime/mimo-api-runtime.ts` | 35 | MiMo API 런타임 (KimiApiRuntime 확장) |
+| `src/runtime/kimi-api-runtime.ts` | 445 | Moonshot API 직접 HTTP 런타임 |
+| `src/runtime/runtime-router.ts` | 513 | 런타임 우선순위, provider → runtime 매핑 |
+
+### 11.4 CLI v2 파일
+
+| 파일 | 라인 | 역할 |
+|------|------|------|
+| `src/cli/v2/cli-v2-skeleton.ts` | ~340 | Clipanion 기반 7개 명령어 + 전체 파이프라인 |
+| `src/cli/v2/chat-repl.ts` | ~170 | 대화형 REPL + 파이프라인 통합 |
+| `src/cli/v2/interactive-prompt.ts` | 225 | Clack 프롬프트 |
+| `src/cli/v2/persistent-memory.ts` | 350 | Section 17 영구 메모리 (.omk/memory/) |
+| `src/cli/main.ts` | ~115 | OMK_CLI_V2=1일 때 모든 명령어 cli-v2로 라우팅 |
+
+### 11.5 오케스트레이션 파일
+
+| 파일 | 라인 | 역할 |
+|------|------|------|
+| `src/orchestration/interactive-orchestrator.ts` | 667 | InteractiveOrchestrator (goal-driven, SubAgentRole 10개) |
+| `src/commands/parallel/interactive.ts` | 246 | omk parallel:interactive CLI 명령어 |
+
+### 11.6 Provider 시스템
+
+| 파일 | 역할 |
+|------|------|
+| `src/providers/model-registry.ts` | KnownProviderId (9개: codex/commandcode/deepseek/kimi/local-llm/mimo/opencode/openrouter/qwen), DEFAULT_PROVIDER_CONFIGS |
+| `src/providers/provider-runtime.ts` | discoverKimiRuntime, discoverMimoRuntime (kimi-api/mimo-api 항상 등록) |
+| `src/providers/types.ts` | ProviderId, ProviderPolicy, RuntimeId, DEFAULT_RUNTIME_FALLBACK_CHAIN |
+| `src/runtime/runtime-bootstrap.ts` | resolveAutoProvider (mimo 자동 감지) |
+
+### 11.7 i18n 시스템
+
+- `src/util/i18n.ts` (~1070 lines): KO/EN 사전, `t()` 함수
+- 키 카테고리: nlp.*, normalizer.*, ui.*, nlg.*
+- `getLanguage()`, `setLanguage()`, `initI18n()`
+
+### 11.8 테스트
+
+- `test/v2-regression.test.mjs` (217 lines, 10/10 PASS)
+- `test/cli-v2-gating.test.mjs` (2/2 PASS)
+
+### 11.9 설정
+
+- `~/.kimi/config.toml` (154 lines): default_model = "mimo/mimo-v2.5-pro", providers: mimo, kimi, deepseek, codex, opencode, openrouter, qwen
+- `.omk/kimi.config.toml` (53 lines): hooks만 포함 (중복 키 해결)
+- `~/.kimi/mcp.json`: 8개 MCP 서버 (context7, gh_grep, filesystem, playwright, memory, sequential-thinking, clearthought, obsidian)
+
+### 11.10 아키텍처 문서 이행률
+
+| 섹션 | 상태 | 비고 |
+|------|------|------|
+| 0-2 (Executive Summary, Problem, Target) | ✅ | 전체 파이프라인 구현 |
+| 5-13 (Data Models ~ ProviderEventNormalizer) | ✅ | 타입 정렬 완료 |
+| 14 (Theme Architecture) | ✅ | ThemePalette + UiComponents |
+| 15 (NlpRenderer) | ✅ | bilingual i18n |
+| 16 (Slash Command) | ✅ | CommandBus 핸들러 등록 |
+| 17 (Persistent Memory) | ✅ | .omk/memory/ |
+| 20 (Regression Tests) | ✅ | 6개 테스트 |
+| 22 P1 (RuntimeSidecar, ThemeRenderer) | ✅ | |
+| 22 P2 (Clipanion, Clack) | ✅ | cli-v2-skeleton + interactive-prompt |
+| 4 (Directory Structure) | ❌ | flat 구조 유지 |
+| 19 (Migration Plan Phase 4-5) | ❌ | |
+| 21 (CLI v2 full migration) | ⚠️ | skeleton exists, wiring partial |
+
+### 11.11 핵심 불변식 (I-001 ~ I-012)
+
+- I-001: availableMcp ≠ prompt MUST activate
+- I-004: optional failure = warning
+- I-005: raw TurnBegin/StatusUpdate not in stdout
+- I-006: status requiredMcp=[]
+- I-008: slash command through CommandBus
+- I-011: kimi-print debug-only
+
+### 11.12 남은 작업
+
+1. Section 21 CLI v2 전체 마이그레이션 (Commander → Clipanion)
+2. Section 4 디렉토리 구조 재편
+3. Section 19 Migration Phase 4-5
+4. omk chat 실제 모델 연결 테스트
+5. UI/UX opencode-style 최종 적용 확인

package/docs/adr/0001-no-native-rust-lane.md

@@ -0,0 +1,52 @@
+# ADR-0001: No native Rust lane for omk-safety
+
+Status: Accepted
+Date: 2026-06-10
+
+## Context
+
+`crates/omk-safety` was scaffolded as a future native lane for safety hot paths
+(redact_stream / sanitize_env / check_path_policy). Remediation item A4 required either
+building it into a measured, shippable lane or killing it with evidence.
+
+## Decision
+
+Remove the Rust surface. Keep TypeScript as the only implementation.
+
+## Evidence (measured, not estimated)
+
+| candidate | p (wall fraction, representative run) | Amdahl ceiling 1/(1−p) | gate (≥1.15) | capability gate |
+|---|---|---|---|---|
+| redact_stream | 0.297% | 1.0030 | FAIL (unreachable even at s=∞) | FAIL — TS hot lane already 65–428 MB/s; 0.26–0.70 ms per 64 KiB ≤ 2 ms budget |
+| sanitize_env | 0.018% | 1.0002 | FAIL | FAIL — cold path, once per spawn |
+| check_path_policy | <0.06% (below sampler resolution) | ≈1.0000 | FAIL | FAIL — realpath syscall-bound |
+
+s (local Rust speedup) was not measured: with all ceilings < 1.004, no finite or infinite
+s can satisfy the gate; building napi bindings to measure it cannot change the outcome.
+
+Profiles, throughput benches, and analysis: `proof/rust-lane-2026-06-10/`.
+
+## Removal scope (larger than "delete crates/" — wired surfaces)
+
+- `crates/`, root `Cargo.toml`, `Cargo.lock` (no rust-toolchain.toml exists)
+- package.json: `rust:build`, `native:build`, and `native:build` steps inside
+  `release:check`, `release:full`, `release:rc`; `native:no-kimi:turn` reference check
+- `scripts/build-native.mjs`, `scripts/rust-safety-check.mjs`,
+  `scripts/normalize-native-artifacts.mjs`, native branch of `scripts/package-audit.mjs`
+- `src/util/native-safety.ts` + doctor lane report (`src/commands/doctor/checks.ts:253,358`)
+- CI: rust/cargo steps in `.github/workflows/{ci,release,smoke-test}.yml`
+- README/CHANGELOG native-lane claims; SECURITY.md stays unchanged (it never claimed
+  native sandboxing — verify on execution)
+
+## What we keep instead (TS follow-ups carrying the real value)
+
+1. Fix O(matches × n) `SecretScanner.getLineColumn` (secret-scanner.ts:729) — measured
+   3 404 ms/call at 1 MiB match-heavy input vs 11.7 ms clean.
+2. Enforce `writableRoots` (src/runtime/sandbox-profile.ts:13) in tool dispatch — currently
+   declared but never consulted against any path.
+3. Deduplicate child-env sanitizer clones (kimi runner ↔ adapter).
+
+## Consequences
+
+- No supply-chain surface from prebuilds; `--ignore-scripts` installs remain trivially safe.
+- A future native lane proposal must re-run this gate with new measured p.

package/docs/codex-oauth-setup.md

@@ -39,6 +39,14 @@ Codex/ChatGPT OAuth proves the Codex CLI login state only. It is not an OpenAI P
 OPENAI_API_KEY=<platform-project-key> omk image generate "OMK control-plane hero" --model gpt-image-2
 ```
 
+You can also run the guided key setup instead of exporting the variable manually:
+
+```bash
+omk openai setup
+```
+
+Do not store the API key in project files; prefer environment variables or a user-local secret store.
+
 See [`openai-platform-image-keys.md`](openai-platform-image-keys.md) for the one-shot key flow.
 
 ## Troubleshooting
@@ -46,3 +54,9 @@ See [`openai-platform-image-keys.md`](openai-platform-image-keys.md) for the one
 - If `codex` is not found, install the official Codex CLI/app or add it to `PATH`.
 - If login status is unclear, run `codex login`, then `omk provider doctor codex --soft`.
 - If MCP import finds nothing, check whether your Codex config has importable MCP servers.
+
+## Security principles
+
+- Never print token/session files.
+- OMK never reuses Codex OAuth values as OpenAI API bearer keys.
+- In shared environments, keep per-provider authentication and project configuration separate.

package/docs/decisions/2026-06-10-git-history-bloat.md

@@ -0,0 +1,61 @@
+# Decision: Git history bloat — defer rewrite, apply linguist-vendored interim
+
+- Date: 2026-06-10
+- Status: Accepted (interim mitigation only; rewrite deferred pending owner approval)
+
+## Problem
+
+The repository pack is far larger than the working tree:
+
+- `git count-objects -vH` → `size-pack: 80.19 MiB`
+- Tracked worktree content ≈ 27 MiB
+
+The gap is caused by large binary blobs (GIF/MP4/PNG/PPTX) committed and later
+replaced/removed, which remain in history forever.
+
+## Evidence: top-10 largest blobs
+
+Command:
+
+```bash
+git rev-list --objects --all \
+  | git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \
+  | sort -k3 -rn | head -10
+```
+
+Output (2026-06-10):
+
+```text
+blob f2aa8c50905967a71bab34b5045406ed668b3a1c 29252458 readmeasset/kimicat.gif
+blob fee8957c9ff26f7243d375f919c6cba5fa53ca3d 18261906 readmeasset/oneprompt.mp4
+blob 8ff0eb7cc1fa08c49fe51ade9dc016fb81f31cd7 10528089 readmeasset/kimicat.gif
+blob c4fea42c159c57e82f64e274335b9829ea1e8dbe 7016890 readmeasset/oneprompt.gif
+blob e1aa1c049e1444d250da52202944d6f8ef1aed9f 3643625 EGG_PEAK_IR_Malgun_Gothic_FIXED_TRUE_ANIM.pptx
+blob f6097940de448e09de07e9b949f6caab13fec433 3041622 readmeasset/kimicat.mp4
+blob 5f671d8ac6c8a6011891164a0bdfa84ea7733749 2802989 readmeasset/kimicat.mp4
+blob 75169d7c30c48b552c621c2f23779d6354974e9f 1849634 kimichan.png
+blob 8edbf5a56bf456284bbd8fb5aa580245684d72e0 1708509 readmeasset/kimicat.png
+blob 13a70fc8e0a35e20c1967b0306b29540bfb75b88 1522325 readmeasset/kimicat.png
+```
+
+The top 4 blobs alone account for ~65 MB of the 80.19 MiB pack.
+
+## Decision
+
+1. **No history rewrite now.** A `git filter-repo` rewrite of the blobs above
+   would shrink the pack to roughly worktree scale, but it rewrites every
+   commit hash, **invalidates all existing clones, forks, and open PRs**, and
+   requires a coordinated force-push. Execute it ONLY with explicit owner
+   approval and a scheduled migration window.
+2. **Interim mitigation:** mark the intentionally hand-written template JS
+   under `templates/web-bridge/chrome-extension/**` as `linguist-vendored` in
+   `.gitattributes` so language stats and code-scanning surfaces stay clean.
+   `dist/` and `coverage/` remain git-ignored (already present in `.gitignore`).
+
+## Follow-up (requires owner approval)
+
+- `git filter-repo --strip-blobs-bigger-than 1M` (or an explicit path list for
+  `readmeasset/` historical media + the stray `.pptx`/`.png`), then force-push
+  and re-clone guidance for all contributors.
+- Move future README media to GitHub release assets or an external CDN instead
+  of committing binaries.

package/docs/decisions/ADR-theme-dark-only-assets.md

@@ -0,0 +1,43 @@
+# ADR: Dark-only README SVG assets derived from the night-city theme
+
+- Status: accepted
+- Date: 2026-06-10
+- Owners: OMK theme contract lane (T4)
+- Related: `themes/night-city.theme.json`, `scripts/assets-build.mjs`, `scripts/theme-check.mjs`, `proof/theme-2026-06-10/t1-t2-summary.md`
+
+## Context
+
+OMK ships a single `omk.theme.v1` theme — `night-city` (`mode: dark`) — as the source of
+truth for all branded surfaces. Every foreground/background pair in that theme is
+contrast-gated by `npm run theme:check` (text ≥ 4.5, indicator ≥ 3.0; 48 pairs, 0 failed),
+and the gate blocks merge in CI. The 5 README SVG assets
+(`readmeasset/omk-{badges,core-loop,evidence-ledger,logo-mark,provider-lanes}.svg`) are now
+derived from that theme's primitives by `npm run assets:build`, which embeds a
+`derived-from: omk.theme.v1/night-city@<hash>` provenance comment per SVG.
+
+A light variant of the assets was considered for GitHub light-mode READMEs. There is no
+light theme file, no light contrast matrix, and no reviewed light palette — generating one
+by naive color inversion would ship pairs that were never gated.
+
+## Decision
+
+Do **not** build a light variant. Assets are dark-only and derive exclusively from the
+single contrast-gated dark theme.
+
+`scripts/assets-build.mjs` enforces this: it refuses any theme with `mode` other than
+`dark` unless every foreground/background token pair actually used by the SVGs passes the
+same 4.5/3.0 WCAG gates inline (the same model `theme:check` applies). The inline gate
+also runs for dark themes, so a drifted primitive cannot silently ship an unreadable
+asset.
+
+## Consequences
+
+- README assets render correctly on dark backgrounds only; light-mode viewers see the
+  dark cards as framed panels (each SVG paints its own `dark` background rect, so nothing
+  becomes unreadable on a light page).
+- Introducing a light variant requires: a new `omk.theme.v1` theme file with
+  `mode: light`, a full `npm run theme:check` pass for that file, and only then will
+  `npm run assets:build --theme <file>` accept it (its inline used-pair gate must pass).
+- Theme color changes propagate to assets only via `npm run assets:build`; the
+  `@<hash>` provenance suffix makes a stale asset detectable against the current theme
+  file hash.

package/docs/getting-started.md

@@ -1,6 +1,6 @@
 # Getting Started
 
-Source release target: `open-multi-agent-kit@0.78.5` (`pre-1.0`).
+Source release target: `open-multi-agent-kit@0.78.7` (`pre-1.0`).
 
 ## Prerequisites