open-multi-agent-kit 0.79.3 → 0.80.0

package/dist/schema/evidence-bundle.schema.d.ts

@@ -7,12 +7,12 @@ export declare const EvidenceBundleArtifactSchema: z.ZodObject<{
 }, "strip", z.ZodTypeAny, {
     sha256: string;
     path: string;
-    kind?: "review" | "file" | "diff" | "log" | "custom" | "metric" | undefined;
+    kind?: "diff" | "review" | "file" | "log" | "custom" | "metric" | undefined;
     required?: boolean | undefined;
 }, {
     sha256: string;
     path: string;
-    kind?: "review" | "file" | "diff" | "log" | "custom" | "metric" | undefined;
+    kind?: "diff" | "review" | "file" | "log" | "custom" | "metric" | undefined;
     required?: boolean | undefined;
 }>;
 export declare const EvidenceBundleSchema: z.ZodObject<{
@@ -43,12 +43,12 @@ export declare const EvidenceBundleSchema: z.ZodObject<{
     }, "strip", z.ZodTypeAny, {
         sha256: string;
         path: string;
-        kind?: "review" | "file" | "diff" | "log" | "custom" | "metric" | undefined;
+        kind?: "diff" | "review" | "file" | "log" | "custom" | "metric" | undefined;
         required?: boolean | undefined;
     }, {
         sha256: string;
         path: string;
-        kind?: "review" | "file" | "diff" | "log" | "custom" | "metric" | undefined;
+        kind?: "diff" | "review" | "file" | "log" | "custom" | "metric" | undefined;
         required?: boolean | undefined;
     }>, "many">;
     verifier: z.ZodObject<{
@@ -120,7 +120,7 @@ export declare const EvidenceBundleSchema: z.ZodObject<{
     artifacts: {
         sha256: string;
         path: string;
-        kind?: "review" | "file" | "diff" | "log" | "custom" | "metric" | undefined;
+        kind?: "diff" | "review" | "file" | "log" | "custom" | "metric" | undefined;
         required?: boolean | undefined;
     }[];
     verifier: {
@@ -129,12 +129,12 @@ export declare const EvidenceBundleSchema: z.ZodObject<{
         checkedAt?: string | undefined;
     };
     commit: string;
+    changedFiles: string[];
     redaction: {
         summary: string;
         applied: boolean;
         leakedSecretPatterns?: string[] | undefined;
     };
-    changedFiles: string[];
     runtimeVersion: string;
     model?: string | undefined;
     nodeId?: string | undefined;
@@ -162,7 +162,7 @@ export declare const EvidenceBundleSchema: z.ZodObject<{
     artifacts: {
         sha256: string;
         path: string;
-        kind?: "review" | "file" | "diff" | "log" | "custom" | "metric" | undefined;
+        kind?: "diff" | "review" | "file" | "log" | "custom" | "metric" | undefined;
         required?: boolean | undefined;
     }[];
     verifier: {
@@ -171,12 +171,12 @@ export declare const EvidenceBundleSchema: z.ZodObject<{
         checkedAt?: string | undefined;
     };
     commit: string;
+    changedFiles: string[];
     redaction: {
         summary: string;
         applied: boolean;
         leakedSecretPatterns?: string[] | undefined;
     };
-    changedFiles: string[];
     runtimeVersion: string;
     model?: string | undefined;
     nodeId?: string | undefined;

package/dist/schema/proof-bundle.schema.d.ts

@@ -96,6 +96,7 @@ export declare const ProofBundleSchema: z.ZodObject<{
 }, "strip", z.ZodTypeAny, {
     runId: string;
     schemaVersion: "omk.proof-bundle.v1";
+    providerPolicy: string;
     commit: string;
     title: string;
     files: {
@@ -112,7 +113,6 @@ export declare const ProofBundleSchema: z.ZodObject<{
         inspectJson?: string | undefined;
         diffPatch?: string | undefined;
     };
-    providerPolicy: string;
     omkVersion: string;
     verdict: "failed" | "partial" | "passed";
     runtimeVersion: "v1.2";
@@ -123,6 +123,7 @@ export declare const ProofBundleSchema: z.ZodObject<{
 }, {
     runId: string;
     schemaVersion: "omk.proof-bundle.v1";
+    providerPolicy: string;
     commit: string;
     title: string;
     files: {
@@ -139,7 +140,6 @@ export declare const ProofBundleSchema: z.ZodObject<{
         inspectJson?: string | undefined;
         diffPatch?: string | undefined;
     };
-    providerPolicy: string;
     omkVersion: string;
     verdict: "failed" | "partial" | "passed";
     runtimeVersion: "v1.2";

package/dist/util/hash.d.ts

@@ -0,0 +1,2 @@
+export declare function sha256Hex(value: string): string;
+export declare function sha256FileSync(path: string): string | undefined;

package/dist/util/hash.js

@@ -0,0 +1,13 @@
+import { createHash } from "node:crypto";
+import { readFileSync } from "node:fs";
+export function sha256Hex(value) {
+    return createHash("sha256").update(value, "utf-8").digest("hex");
+}
+export function sha256FileSync(path) {
+    try {
+        return createHash("sha256").update(readFileSync(path)).digest("hex");
+    }
+    catch {
+        return undefined;
+    }
+}

package/dist/util/session.js

@@ -1,6 +1,7 @@
-import { writeFile, readdir, readFile } from "fs/promises";
+import { writeFile, readdir, readFile, mkdir } from "fs/promises";
 import { join } from "path";
-import { getRunPath, getOmkPath, pathExists, ensureDir, validateRunId } from "./fs.js";
+import { getOmkPath, pathExists, validateRunId } from "./fs.js";
+import { getRunArtifactPath } from "./run-store.js";
 export function createOmkSessionId(prefix = "session") {
     const timestamp = new Date().toISOString().replace(/[:.]/g, "-");
     return `${prefix}-${timestamp}-${process.pid}`;
@@ -13,8 +14,8 @@ export function createOmkSessionEnv(projectRoot, sessionId) {
 }
 export async function ensureSessionDir(runId) {
     const sanitized = validateRunId(runId);
-    const dir = getRunPath(sanitized);
-    await ensureDir(dir);
+    const dir = getRunArtifactPath(sanitized, ".");
+    await mkdir(dir, { recursive: true });
     return dir;
 }
 export async function writeSessionMeta(runId, meta) {
@@ -30,7 +31,7 @@ export async function writeSessionMeta(runId, meta) {
 }
 export async function readSessionMeta(runId) {
     const sanitized = validateRunId(runId);
-    const metaPath = join(getRunPath(sanitized), "session.json");
+    const metaPath = getRunArtifactPath(sanitized, "session.json");
     if (!(await pathExists(metaPath)))
         return null;
     try {

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

@@ -0,0 +1,19 @@
+# 2026-06-16 Critical Issues
+
+## Critical Init Status
+
+### Missing critical artifacts
+- `.omk/hooks/pre-shell-guard.sh` — destructive shell guard
+- `.omk/hooks/protect-secrets.sh` — secret write guard
+
+
+## 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/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-16/improvements.md

@@ -0,0 +1,15 @@
+# 2026-06-16 Improvements
+
+## Current Improvement Backlog
+### Optional init/support artifacts to add or refresh
+- None detected.
+
+### Critical init artifacts currently blocking reliable chat startup
+- `.omk/hooks/pre-shell-guard.sh` — destructive shell guard
+- `.omk/hooks/protect-secrets.sh` — secret write guard
+
+
+## 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-16/init-checklist.md

@@ -0,0 +1,25 @@
+# 2026-06-16 Required Init Checklist
+
+**Run ID:** chat-2026-06-15T18-37-32-586Z-3029826
+**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-16/plan.md

@@ -0,0 +1,20 @@
+# 2026-06-16 OMK Chat Plan
+
+**Run ID:** chat-2026-06-15T18-37-32-586Z-3029826
+**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

@@ -2,7 +2,8 @@
 
 > 분석일: 2026-05-25
 > 도구: CodeGraph (SQLite 기반 코드 의존성 그래프)
-> 대상: /home/yu/open_multi-agent_kit (open-multi-agent-kit v1.1.18)
+> 대상: /home/yu/open_multi-agent_kit (open-multi-agent-kit@0.79.3, runtime contract family v1.2, pre-1.0)
+> 최신화: 2026-06-15 — release truth, authority/evidence gates, health-aware routing, and spec-kit docs refreshed.
 
 ---
 

package/docs/GSTACK_MIGRATION.md

@@ -1,7 +1,7 @@
 # External Multi-Agent Stack → OMK Migration Guide
 
 > Generic migration path from any external multi-agent orchestration stack (e.g., gstack, custom frameworks) to OMK.
-> OMK v1.1.18+ with externalized skill presets.
+> OMK `open-multi-agent-kit@0.79.3` (`v1.2` runtime contract family, `pre-1.0`) with externalized skill presets, scoped MCP/skills/hooks, evidence gates, and provider-neutral runtime routing.
 
 ## Why Migrate to OMK
 

package/docs/algorithm-hardening-playbook.md

@@ -0,0 +1,219 @@
+# OMK Algorithm Hardening Playbook
+
+> How to evolve OMK's runtime algorithms safely, contract-first, and with evidence.
+
+## 1. Principles
+
+### 1.1 Change contracts before code
+
+When hardening an algorithm, start with:
+
+1. Type/interface changes (e.g., `AgentTask.safety`, `RuntimeHealthVectorV2`).
+2. Unit tests that express the new contract in isolation.
+3. Adapter updates to satisfy the compiler.
+4. Integration tests.
+5. Documentation updates.
+
+This order catches contract violations at compile time rather than at runtime.
+
+### 1.2 Declare, observe, then verify
+
+For evidence gates:
+
+- **Declare**: node/task says what evidence kinds are required.
+- **Observe**: after execution, extract actual observations from stdout, metadata, artifacts.
+- **Verify**: compare observations against declarations.
+
+A declaration is never proof.
+
+### 1.3 Runtime-mode authority
+
+Authority is not provider identity. It is `(provider, runtimeMode)`:
+
+```text
+kimi:api   → read, review (advisory)
+kimi:cli   → read, write, patch, shell, merge, review (authority)
+deepseek:api → read, review (advisory)
+codex:cli  → read, plan, review (advisory unless explicit policy)
+```
+
+Any code path that selects a runtime must consult this matrix.
+
+### 1.4 Fail-closed defaults
+
+- Unknown health → route with penalty or block.
+- Missing evidence → exit 78.
+- Advisory runtime asked to write/shell/merge → exit 78.
+- Low-confidence risk → downgrade to `ask`.
+
+### 1.5 Preserve backward compatibility
+
+- Do not remove old fields until the full phase is released.
+- Use optional/new fields first, then deprecate.
+- Keep existing smoke tests passing.
+
+## 2. Step-by-step hardening loop
+
+### Step 0 — Isolate the concern
+
+Pick one algorithm concern per phase:
+
+- evidence semantics
+- health probes
+- authority matrix
+- prompt privacy
+- audit graph
+
+Do not mix two concerns in one diff.
+
+### Step 1 — Specify the contract
+
+Write the LaTeX/TypeScript contract first. Example:
+
+```ts
+// Before changing implementations, add the new contract.
+export interface AgentTaskSafety {
+  readonly risk: string;
+  readonly approvalPolicy: string;
+  readonly sandboxMode: string;
+  readonly evidenceRequired: boolean;
+  readonly authorityMode: string;
+}
+```
+
+### Step 2 — Add isolated tests
+
+Create a new test file that fails before implementation:
+
+```text
+test/evidence-v2-declared-vs-observed.test.mjs
+test/health-vector-tri-state.test.mjs
+test/authority-matrix-kimi-api-advisory.test.mjs
+```
+
+### Step 3 — Implement behind a flag when possible
+
+For large changes, use an environment flag:
+
+```ts
+const evidenceModelV2 = process.env.OMK_EVIDENCE_MODEL === "v2";
+```
+
+This lets you merge incrementally without breaking existing paths.
+
+### Step 4 — Update adapters incrementally
+
+For each runtime adapter:
+
+1. Make it compile with the new contract.
+2. Add a focused test for that adapter.
+3. Move to the next adapter.
+
+### Step 5 — Integrate and remove flag
+
+Once all adapters and tests pass:
+
+1. Default the flag to the new behavior.
+2. Add a revert path.
+3. Run full quality gates.
+
+### Step 6 — Document and release-gate
+
+- Update `docs/provider-maturity.md`, `docs/native-root-runtime-hardening.md`.
+- Add the new behavior to `release:check` or a dedicated smoke script.
+- Update `CHANGELOG.md`.
+
+## 3. Parallel subagent orchestration
+
+When spawning parallel workers (when the tool is available):
+
+### 3.1 Decompose by concern, not by file
+
+Each worker owns one concern end-to-end:
+
+- evidence worker: contract + tests + runtime-backed + DAG executor
+- health worker: vector v2 + adapters + scoring
+- authority worker: matrix + resolver + docs + smoke
+
+### 3.2 Grant least privilege
+
+| Worker | Authority | Allowed paths | Blocked paths |
+|--------|-----------|---------------|---------------|
+| evidence | write-scoped | `src/runtime/contracts/evidence.ts`, `src/runtime/runtime-backed-task-runner.ts`, `src/orchestration/executor.ts`, `test/evidence-*.mjs` | secrets, env files |
+| health | write-scoped | `src/runtime/contracts/shared.ts`, `src/runtime/runtime-router.ts`, `src/runtime/*-runtime.ts`, `test/health-*.mjs` | secrets, env files |
+| authority | write-scoped | `src/runtime/authority-matrix.ts`, `src/runtime/runtime-bootstrap.ts`, `src/runtime/runtime-router.ts`, `docs/provider-maturity.md`, `test/authority-*.mjs` | secrets, env files |
+
+### 3.3 Shared read-only reviewers
+
+Run reviewer/QA/security lanes in parallel after implementation lanes:
+
+- `omk-reviewer`: diff review, type safety
+- `omk-tester`: test matrix, release gate
+- `omk-security`: secret exposure, authority boundary
+
+### 3.4 Synthesis gate
+
+Do not merge until:
+
+1. Every lane produced evidence.
+2. `npm run check` passes.
+3. `npm run release:check` passes.
+4. New negative tests pass.
+5. Documentation is updated.
+
+## 4. Regression prevention
+
+### 4.1 Test hierarchy
+
+1. **Contract tests**: pure functions, no IO.
+2. **Adapter tests**: runtime mocks, no live provider calls.
+3. **Integration tests**: local CLI with `--dry-run`.
+4. **Smoke tests**: real provider only in CI with ephemeral keys.
+
+### 4.2 Required negative tests
+
+For every new gate, add a negative test:
+
+- Evidence declared but not observed → blocked.
+- Health fail → runtime excluded or penalized.
+- Advisory runtime asked for write → exit 78.
+- Private prompt leaked to public node → redaction/failure.
+
+### 4.3 Durable checkpoints
+
+Before each phase:
+
+```bash
+git branch phase-<N>-<concern>
+npm run check
+npm run test
+```
+
+After each phase:
+
+```bash
+npm run check
+npm run release:check
+git commit -m "feat(<concern>): <phase N> hardening"
+```
+
+## 5. When to stop
+
+Stop a phase and ask for guidance when:
+
+- A contract change would break public CLI behavior.
+- A runtime adapter cannot satisfy the new contract without a large refactor.
+- `npm run check` fails and the fix is not local.
+- A lane would need to write files outside its granted scope.
+
+## 6. Checklist
+
+- [ ] Contract specified in TypeScript/LaTeX
+- [ ] Isolated failing tests added
+- [ ] Implementation behind flag or in isolated file
+- [ ] All adapters updated incrementally
+- [ ] Negative tests added
+- [ ] Documentation updated
+- [ ] Quality gates pass
+- [ ] Evidence artifacts recorded
+- [ ] Result artifact written

package/docs/claims.md

@@ -66,7 +66,7 @@ Evidence:
 
 ## Claim: OMK is a stable 1.x release
 
-Status: not claimed. Current source version is `0.78.9` (`pre-1.0`); `v1.2` is a runtime contract family.
+Status: not claimed. Current source version is `0.80.0` (`pre-1.0`); `v1.2` is a runtime contract family.
 
 Evidence:
 - [versioning](versioning.md)

package/docs/getting-started.md

@@ -1,6 +1,6 @@
 # Getting Started
 
-Source release target: `open-multi-agent-kit@0.79.3`. Treat npm latest claims as valid only after registry verification and release gates pass.
+Source release target: `open-multi-agent-kit@0.80.0`. Treat npm latest claims as valid only after registry verification and release gates pass.
 
 ## Prerequisites
 

package/docs/native-root-runtime-hardening.md

@@ -1,29 +1,32 @@
 # Native Root Runtime Hardening
 
-Last updated: 2026-05-24
-Current `new-origin/main`: `6305e2b62185c11549f59e2340936769a3027cdd`
+Last updated: 2026-06-15
+Current package version: `open-multi-agent-kit@0.79.3`
+Runtime contract family: `v1.2`
+Release channel: `pre-1.0`
 
 ## Current State
 
-OMK is now on the right architectural path: OMK is the root orchestrator and Kimi is one provider adapter, with Codex, DeepSeek, OpenCode, CommandCode, and future adapters routed through OMK-owned runtime contracts.
+OMK is the root orchestrator. Kimi, Codex, DeepSeek, OpenCode, CommandCode, GLM, and future providers are runtime/provider lanes selected through OMK-owned contracts. API advisory runtimes remain read/review/advisory unless a runtime-mode contract grants write/shell/merge authority.
 
-This is still a hardening milestone, not a stable provider-neutral release claim. The current release stop condition is:
+This is still a hardening milestone, not a stable 1.x or OS-level sandbox claim. The current release stop condition is:
 
 - Local `npm run release:check` must pass on the exact release diff.
-- GitHub Actions Smoke Test must pass on the exact commit.
-- GitHub Actions CI must pass on the exact commit.
-- Release evidence must be kept under `.omk/release-evidence/<short-sha>/` or an equivalent run artifact path.
+- GitHub Actions Smoke Test must pass on the exact commit/tag.
+- GitHub Actions CI or Release workflow gates must pass on the exact commit/tag.
+- npm registry `latest` must be verified when a release claim references a published version.
+- Release evidence must be kept under `.omk/runs/<run-id>/`, `.omk/release-evidence/<short-sha>/`, or an equivalent run artifact path.
 
 Fresh verification at the time of this update:
 
-- `new-origin/main` points at `6305e2b62185c11549f59e2340936769a3027cdd`.
-- GitHub Actions Smoke Test for that commit completed successfully.
-- GitHub Actions CI for that commit failed on Windows test jobs, so v1.1.18 publish/tag remains blocked.
+- `open-multi-agent-kit@0.79.3` is published as npm `latest`.
+- Main CI, main Smoke, tag Release, and tag Smoke passed for `v0.79.3` after rerunning transient failures.
+- Local verification for the machine-checkable hardening slice passed: `npm run check`, `npm run build:clean`, `npm run lint`, `npm run secret:scan`, `npm run version:check`, targeted runtime tests, and `npm test`.
 
 For the LaTeX/paper-ready algorithm appendix and acceptance criteria, see
 [Native Root Runtime Algorithms](./native-root-runtime-algorithms.md). Treat
-that appendix as hardening criteria, not a stable-release proof, until the
-exact release diff passes CI, smoke, and local release gates.
+that appendix as hardening criteria; release claims still require exact-diff
+local gates, CI/smoke, and registry evidence.
 
 ## Runtime Safety Contract
 
@@ -43,7 +46,7 @@ Native chat turns must be default-safe. A turn should request only the minimum c
 |-----------|----------------|--------------|
 | `read` | explain, review, summarize, inspect docs | `read` only |
 | `write` | edit, fix, implement, refactor | `read`, `write`, `patch` |
-| `shell` | run tests, build, execute commands | `read`, `write`, `shell` with approval policy |
+| `shell` | run tests, build, execute commands | `read`, `write`, `shell` with approval policy and required command evidence |
 | `merge` | publish, release, push, merge, destructive changes | authority provider plus release/security gates |
 
 DeepSeek remains an advisory/read/review lane unless an explicit future contract grants safe write/shell execution. Write/shell tasks should route to Kimi, Codex, or a configured authority provider with the matching approval and sandbox policy.
@@ -75,9 +78,7 @@ Unknown or unresolved authority must fail with remediation instead of silently d
 
 ### Provider health probes
 
-Related: Algorithm 5. Current routing uses available registry, capability, and
-evidence metadata; uniform auth/model/quota health remains part of this
-hardening backlog.
+Related: Algorithm 5. Runtime routing now filters unavailable runtimes in async execution paths and includes health in normalized route scoring. The next hardening step is to expand every adapter to a uniform auth/model/quota/rate-limit/latency vector.
 
 Provider bootstrap must distinguish:
 
@@ -94,31 +95,40 @@ Related: Algorithm 4 and Algorithm 7.
 
 MCP, skills, and hooks must not disappear silently. Runtime manifests should include diagnostics for parse/read failures, unknown names, and scope drops. If a task requires runtime MCP, invalid MCP config is a hard failure.
 
+## Current status after 0.79.3 hardening
+
+Completed foundations:
+
+- Runtime authority is resolved by `(provider, runtimeMode)` through `src/runtime/authority-matrix.ts`; native routing also consults this matrix instead of maintaining a separate advisory-provider list.
+- `OMK_TOOL_AUTHORITY_MODE=enforce` coverage is release-gated through the shared `release:gate-core` script and includes a native-turn subprocess enforcement smoke.
+- Native prompt payloads are private artifacts; public synthetic node labels carry prompt hashes, not raw prompts.
+- `prompt:privacy:check` audits private prompt artifacts against public run artifacts, decision traces, and graph-memory snapshots, and is part of the release gate.
+- Per-turn route/result artifacts are written best-effort and replay-indexed with SHA-256 hashes.
+- Evidence declarations and produced observations are type-separated; command/test evidence requires high-confidence metadata or artifact observations, not stdout keywords alone, and DAG executor/verify/replay paths bridge through the same EvidenceGate v2 contract.
+- Provider route/evidence audit nodes are materialized into local graph memory on native turns, with Provider/Artifact nodes, `EvidenceRequirement -> SATISFIED_BY -> EvidenceObservation` semantics, and route/evidence/artifact edges.
+- Runtime health checks accept requested probe levels; API, local LLM, Codex CLI, and external CLI adapters perform static/cheap/live probes with latency and auth/model/quota/rate-limit dimensions where observable. Router health scoring is normalized and high-risk probes fail closed on unknown runtime/auth/model dimensions.
+- Runtime failure stderr is redacted before public exposure and can be retained as a private redacted full artifact in debug mode, including direct `toTaskResult` conversion paths outside `RuntimeRouter`.
+- Mixed-provider advisory reviewer + CLI coder/verifier routing has regression coverage.
+- Native risk classification is negation-aware, so excluded scopes such as `릴리즈 제외`, `no release`, or `npm 체크 제외` do not trigger false merge/shell routing.
+- Runtime routing now classifies failed attempts (`auth`, `quota`, `rate_limit`, `timeout`, `model`, `runtime`, `authority`, `transient`) and opens short-lived in-process circuit breakers so fallback runtimes are tried without repeatedly hitting known-bad adapters.
+- Runtime scoring reads audit-graph `ProviderRoute -> EVIDENCED_BY -> Evidence` pass/fail observations, so local graph memory can influence future route ordering without exposing raw logs.
+- The scheduler exposes critical-path runnable-plan metadata (`criticalPathDepth`, downstream fanout, score, evidence flags) for replay/debug panels.
+- Headroom compaction uses an explicit `omk.structured-compaction.v1` contract for required task/routing/evidence/safety/capability sections.
+
 ## P0 Backlog
 
-1. Infer native turn risk before building the DAG node; do not default every turn to write/shell.
-2. Keep explicit DeepSeek routes read-only/advisory or block write/shell with a clear fallback message.
-3. Propagate approval policy and sandbox mode into runtime adapters, especially Codex CLI.
-4. Resolve `authority` to a concrete provider during runtime bootstrap.
-5. Replace binary-only provider auth checks with structured provider health probes.
-6. Keep release evidence current; do not tag/publish while CI is red.
+1. Keep release evidence current; do not tag/publish while exact-diff CI/smoke or registry verification is missing.
 
 ## P1 Backlog
 
-1. Make `/model` either a real live state update or clearly restart-only.
-2. Use the provider registry as the source of truth for DeepSeek default models.
-3. Remove `cmd` as a CommandCode fallback binary.
-4. Emit tool-plane diagnostics for MCP config parse/read failures.
-5. Gate Kimi failure stderr previews behind `OMK_DEBUG=1` and redaction.
-6. Preserve routing metadata in external CLI adapter `execute(task)` paths.
+1. Extend exact-diff CI status ingestion once a remote check surface is available in the current runtime.
+2. Add provider-specific model-existence probes where vendors expose safe no-token model metadata or non-generating validation endpoints.
 
 ## P2 Backlog
 
 1. Add configurable non-zero exit behavior for native root-loop turn failures.
-2. Move prompt envelopes out of `DagNode.name` into structured payload fields.
-3. Validate capability names before prompt/runtime injection.
-4. Persist per-turn route artifacts under `.omk/runs/<run-id>/turns/<turn-id>.json`.
-5. Link provider routes and evidence gates into graph memory for replay/audit.
+2. Add experimental OS sandbox modes only behind explicit opt-in and without public stable claims.
+3. Add broader pty/TTY regression coverage for scroll-safe rendering and interactive selectors.
 
 ## Spec-Kit Acceptance Gates