open-multi-agent-kit 0.78.0 → 0.78.2

package/docs/getting-started.md

@@ -1,17 +1,17 @@
 # Getting Started
 
-Source release target: `@omk/cli@0.78.0`.
+Source release target: `open-multi-agent-kit@0.78.1` (`pre-1.0`).
 
 ## Prerequisites
 
 - Node.js 20+
 - Git
-- At least one supported provider or local runtime adapter (Codex CLI, Gemini CLI, Claude Code, OpenRouter, DeepSeek, Kimi, etc.)
+- At least one configured provider or local runtime adapter. Kimi is the most mature authority path; other lanes depend on local CLI/API availability and the provider-maturity contract.
 
 ## Install
 
 ```bash
-npm install -g @omk/cli
+npm install -g open-multi-agent-kit
 ```
 
 ## Initialize a project
@@ -35,3 +35,31 @@ omk chat
 omk plan "refactor auth module"
 omk run feature-dev "add user dashboard"
 ```
+
+## Updates
+
+On startup OMK checks npm for a newer release and, when one exists, shows an
+interactive prompt (Update now / Skip this version / Remind me later). Choosing
+"Update now" runs `npm i -g open-multi-agent-kit`.
+
+- **Automatic (non-interactive) updates:** set `OMK_AUTO_UPDATE=1` (also accepts
+  `true|yes|on|always`). When OMK is outdated it self-updates on startup without
+  prompting. CI is always skipped, and `OMK_UPDATE_PROMPT=off` disables update
+  checks entirely.
+- Manual check: `omk update check` (add `--refresh` to bypass the cache).
+
+## Adaptive runtime algorithms
+
+OMK embeds three adaptive control behaviors (all additive, safe defaults, non-fatal fallback):
+
+- **Topology-routed first run** — on the first DAG composition OMK derives structural features (width, critical depth, coupling, parallel ratio) and selects an execution topology (parallel / pipeline / map-reduce / hierarchical / hybrid / dag) with layered waves. Toggle with `OMK_ADAPTORCH_ROUTING=off`.
+- **Context guard before 90%** — before the context window crosses a threshold (default `0.90`) OMK compacts via [headroom](https://github.com/chopratejas/headroom) when available, otherwise its built-in budget optimizer. Tune with `OMK_HEADROOM_THRESHOLD` (0.50–0.99), `OMK_CONTEXT_WINDOW`, or disable with `OMK_HEADROOM=off`.
+- **Spec-first via Ouroboros** — goal/spec/orchestration intents prefer the embedded Ouroboros flow by default; when Ouroboros is not installed OMK degrades to the native path with no error. Modes: `OMK_OUROBOROS=always` (default) `| auto | off`. See [Ouroboros integration](integrations/ouroboros.md).
+
+## Support the project (GitHub star)
+
+First-time users get a one-time prompt to star the repository. If the GitHub CLI
+(`gh`) is authenticated the star is applied directly; otherwise OMK prints the
+repo URL and, on a desktop session, opens it in your browser so you can star in
+one click. You can star anytime with `omk star`, check status with
+`omk star --status`, and disable the prompt with `OMK_STAR_PROMPT=off`.

package/docs/github-organic-promotion.md

@@ -0,0 +1,127 @@
+# GitHub organic promotion checklist
+
+OMK's strongest GitHub search position is:
+
+> Provider-neutral multi-agent control plane for coding agents: route runtimes, scope MCP tools, run DAG workers, verify evidence, and replay agent runs.
+
+## Repository About
+
+Recommended GitHub About description:
+
+```txt
+Provider-neutral multi-agent control plane for coding agents. Route runtimes, scope MCP tools, run DAG workers, verify evidence, and replay agent runs from the omk CLI.
+```
+
+Apply after maintainer confirmation:
+
+```bash
+gh repo edit dmae97/open-multi-agent-kit \
+  --description "Provider-neutral multi-agent control plane for coding agents. Route runtimes, scope MCP tools, run DAG workers, verify evidence, and replay agent runs from the omk CLI."
+```
+
+## GitHub Topics
+
+Use all 20 topics:
+
+```txt
+ai-agent
+ai-agents
+llm
+coding-agent
+ai-coding
+agentic-coding
+multi-agent
+multi-agent-orchestration
+agent-orchestration
+agent-runtime
+agent-control-plane
+developer-tools
+ai-devtools
+cli
+typescript
+nodejs
+mcp
+model-context-protocol
+workflow-automation
+provider-neutral
+```
+
+Apply after maintainer confirmation:
+
+```bash
+gh repo edit dmae97/open-multi-agent-kit \
+  --add-topic ai-agent \
+  --add-topic ai-agents \
+  --add-topic llm \
+  --add-topic coding-agent \
+  --add-topic ai-coding \
+  --add-topic agentic-coding \
+  --add-topic multi-agent \
+  --add-topic multi-agent-orchestration \
+  --add-topic agent-orchestration \
+  --add-topic agent-runtime \
+  --add-topic agent-control-plane \
+  --add-topic developer-tools \
+  --add-topic ai-devtools \
+  --add-topic cli \
+  --add-topic typescript \
+  --add-topic nodejs \
+  --add-topic mcp \
+  --add-topic model-context-protocol \
+  --add-topic workflow-automation \
+  --add-topic provider-neutral
+```
+
+## Social preview
+
+Upload this generated image in GitHub repository settings:
+
+```txt
+readmeasset/social-preview.png
+```
+
+It uses the message:
+
+```txt
+OMK
+Provider-Neutral Multi-Agent Control Plane
+Route. Verify. Replay.
+```
+
+## Awesome-list PR entries
+
+### bradAGI/awesome-cli-coding-agents
+
+Preferred section: `Harnesses & orchestration`.
+
+```md
+- **[OMK](https://github.com/dmae97/open-multi-agent-kit)** `⭐ <current>` — Provider-neutral CLI control plane for coding agents: routes runtimes, scopes MCP, runs DAG workers, and verifies evidence before completion. MIT.
+```
+
+### e2b-dev/awesome-ai-sdks
+
+```md
+## [OMK](https://github.com/dmae97/open-multi-agent-kit)
+
+OMK is a provider-neutral multi-agent control plane for coding workflows. It routes agent runtimes, scopes MCP tools, runs DAG-based workers, verifies evidence, and preserves replayable run artifacts.
+
+### Links
+
+- [GitHub](https://github.com/dmae97/open-multi-agent-kit)
+- [npm](https://www.npmjs.com/package/open-multi-agent-kit)
+```
+
+### punkpeye/awesome-mcp-devtools
+
+Preferred section: `Frameworks` or `Development Tools`.
+
+```md
+- [OMK](https://github.com/dmae97/open-multi-agent-kit) - TypeScript CLI control plane for coding agents with scoped MCP injection, provider routing, evidence gates, and replayable run telemetry.
+```
+
+## Measurement plan
+
+- Topics applied + 7 days: inspect GitHub topic/search traffic.
+- First awesome PR merged + 7 days: check `Referring sites` for that awesome repo.
+- 2 weeks: compare visitors, clones, npm downloads, and popular README content.
+- 4 weeks: review visitor-to-star conversion; 1-3% is acceptable for early OSS.

package/docs/integrations/ouroboros.md

@@ -0,0 +1,96 @@
+# Ouroboros integration (embedded in OMK)
+
+[Ouroboros](https://github.com/Q00/ouroboros) is a spec-first "Agent OS"
+(PyPI `ouroboros-ai`). OMK embeds it through the documented runtime-adapter
+surface that Ouroboros already supports for the `pi`-family CLI that OMK builds
+on:
+
+- an **MCP server** (`ouroboros mcp serve`, ~29 `ouroboros_*` tools) registered in OMK's MCP config,
+- the official **`ooo` bridge extension** installed into OMK's agent extensions dir, so `ooo ...` works inside interactive OMK sessions, and
+- the 20 Ouroboros **skills** (SKILL.md) installed namespaced as `ouroboros-*`.
+
+Ouroboros owns its own workflow engine; the OMK runtime CLI is selected as its
+`runtime_backend` (a `--mode json` subprocess). This follows the runtime guide
+in the Ouroboros repository.
+
+## Prerequisites
+
+- Python `>=3.12`, `uv` (or `pipx`), and the OMK runtime CLI on `PATH`.
+- OMK global agent dir at `~/.omk/agent` (extensions, skills, `mcp.json`).
+
+## Install (reproducible)
+
+```bash
+# 0. Back up the global MCP config (mode 600, contains secrets) before merging.
+ts=$(date +%Y%m%d-%H%M%S)
+cp -a ~/.omk/agent/mcp.json ~/.omk/agent/mcp.json.bak-$ts
+
+# 1. Install the package with MCP support.
+uv tool install 'ouroboros-ai[mcp,claude]'      # or: pipx install 'ouroboros-ai[mcp,claude]'
+
+# 2. Non-interactive runtime setup: writes ~/.ouroboros/config.yaml
+#    (runtime_backend) and generates the ooo bridge extension.
+ouroboros setup --runtime pi --non-interactive
+
+# 3. Mirror the generated ooo bridge into OMK's extension dir.
+#    (locate the file Ouroboros generated, regardless of upstream dir)
+BRIDGE_SRC=$(find "$HOME" -maxdepth 4 -name ouroboros-ooo-bridge.ts -not -path '*/.omk/*' 2>/dev/null | head -1)
+cp "$BRIDGE_SRC" ~/.omk/agent/extensions/ouroboros-ooo-bridge.ts
+
+# 4. Register the MCP server in OMK (additive jq merge; keep mode 600).
+OURO_BIN="$(command -v ouroboros)"
+jq --arg bin "$OURO_BIN" '.mcpServers.ouroboros = {command:$bin, args:["mcp","serve"], env:{}}' \
+  ~/.omk/agent/mcp.json > /tmp/omk-mcp.new \
+  && python3 -m json.tool < /tmp/omk-mcp.new >/dev/null \
+  && install -m600 /tmp/omk-mcp.new ~/.omk/agent/mcp.json && rm -f /tmp/omk-mcp.new
+
+# 5. Install the 20 Ouroboros skills (namespaced).
+git clone --depth 1 https://github.com/Q00/ouroboros.git /tmp/ouroboros-src
+for d in /tmp/ouroboros-src/skills/*/; do b=$(basename "$d");
+  mkdir -p ~/.omk/agent/skills/ouroboros-$b;
+  cp "$d/SKILL.md" ~/.omk/agent/skills/ouroboros-$b/SKILL.md; done
+```
+
+> The MCP entry uses the absolute `ouroboros` binary path because OMK sanitizes
+> the child environment; a bare `ouroboros`/`uvx` command may not resolve under
+> the sanitized `PATH`.
+
+## Verify
+
+```bash
+ouroboros --version
+ouroboros mcp serve --help                  # MCP entrypoint
+ouroboros dispatch --help                   # ooo bridge dispatch entrypoint
+test -f ~/.omk/agent/extensions/ouroboros-ooo-bridge.ts && echo "omk bridge OK"
+grep -q ouroboros ~/.omk/agent/mcp.json && echo "mcp registered"
+ls -d ~/.omk/agent/skills/ouroboros-* | wc -l   # expect 20
+grep runtime_backend ~/.ouroboros/config.yaml   # expect: pi
+```
+
+A successful MCP handshake reports `serverInfo: ouroboros-mcp` and ~29
+`ouroboros_*` tools. In an interactive OMK session, after restart or `/reload`:
+
+```text
+ooo status
+ooo auto build a small CLI
+```
+
+## Scope and safety notes
+
+- The `ouroboros` MCP server is registered in the **global** `~/.omk/agent/mcp.json`,
+  so it is available under all-scope MCP sessions. Default project-scope sessions
+  (`omk-project` only) are unaffected, so OMK startup is not slowed by Ouroboros.
+- `ouroboros setup` mutates `~/.ouroboros/config.yaml` and the upstream runtime's
+  global extensions dir; it does not touch the OMK repo.
+- First MCP cold start resolves the uv tool venv and can be slow; `omk mcp doctor
+  ouroboros` may need a longer timeout on first run.
+
+## Rollback
+
+```bash
+ts=<backup timestamp>
+rm -f ~/.omk/agent/extensions/ouroboros-ooo-bridge.ts
+[ -f ~/.omk/agent/mcp.json.bak-$ts ] && install -m600 ~/.omk/agent/mcp.json.bak-$ts ~/.omk/agent/mcp.json
+rm -rf ~/.omk/agent/skills/ouroboros-*
+uv tool uninstall ouroboros-ai                # or: pipx uninstall ouroboros-ai
+```

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

@@ -400,3 +400,304 @@ Recent OMK revisions harden worker execution by removing prompt payloads from pr
 - Provider stderr diagnostics still require continued redaction/debug-gating work; safety claims depend on the exact adapter path and tests.
 - Provider health probes are improving, but binary/API presence, auth state, model support, and quota state are not yet uniformly separated across every adapter; Algorithm 5 routes by available registry/capability/evidence metadata, not by universal quota-aware health.
 - ActionAtom, Novelty Guard, and provider-lane fanout language in prompt/harness surfaces remains contract-level unless backed by a concrete runtime implementation and tests.
+
+# Appendix: OMK Next-Step Runtime Hardening Algorithms
+
+This appendix defines the hardening gate algorithms used to advance the OMK native root runtime from internal → pre-release → stable. Each algorithm returns a score or verdict; the thresholds and weights below must be preserved exactly.
+
+## Algorithm 1: Next Implementation Stage Controller
+
+**Inputs**
+
+- Current stage $s \in \{\text{internal}, \text{pre-release}, \text{stable}\}$
+- Proof trust score $T_b$
+- Evidence item trust $T_e$
+- Public surface count $P$
+- Router v2 cutover status $C_r \in \{\text{shadow}, \text{cutover}\}$
+
+**Output**
+
+- Next stage $s'$
+
+**Pseudocode**
+
+```text
+function NextStage(s, T_b, T_e, P, C_r):
+    if P > 7:
+        return s
+    if s = internal:
+        if T_b ≥ 0.60 and T_e ≥ 0.75:
+            return pre-release
+    if s = pre-release:
+        if T_b ≥ 0.75 and T_e ≥ 0.75 and C_r = cutover:
+            return stable
+    return s
+```
+
+## Algorithm 2: Public Surface Freeze
+
+**Inputs**
+
+- Public surface set $S_{\text{pub}}$ (documented API, CLI commands, environment variables)
+- Freeze baseline $B_{\text{pub}}$
+
+**Output**
+
+- Freeze verdict $\in \{\text{pass}, \text{fail}\}$
+
+**Pseudocode**
+
+```text
+function PublicSurfaceFreeze(S_pub, B_pub):
+    P ← |S_pub|
+    Δ ← S_pub \ B_pub
+    if P > 7:
+        return fail
+    if |Δ| > 0:
+        return fail
+    return pass
+```
+
+**Invariant**
+
+- Surface public count $P \le 7$.
+- No new public members may be added after the freeze baseline.
+
+## Algorithm 3: Proof Trust MVP
+
+**Inputs**
+
+- Eight normalized proof dimensions $b_1 \dots b_8$:
+  1. Unit test pass rate
+  2. Lint / format gate
+  3. Type-check gate
+  4. Secret-scan gate
+  5. Smoke test gate
+  6. Code-review sign-off
+  7. Documentation sync
+  8. Build / provenance gate
+
+**Formula**
+
+$$
+T_b = 0.15 b_1 + 0.15 b_2 + 0.10 b_3 + 0.15 b_4 + 0.15 b_5 + 0.15 b_6 + 0.05 b_7 + 0.10 b_8
+$$
+
+**Thresholds**
+
+- Stable: $T_b \ge \tau_{\text{proof}} = 0.85$
+- Pre-release: $T_b \ge 0.75$
+- Internal: $T_b \ge 0.60$
+
+## Algorithm 4: Evidence Item Trust
+
+**Inputs**
+
+- Six normalized evidence dimensions $e_1 \dots e_6$:
+  1. Changed-file inventory
+  2. Commands-run log
+  3. Passed quality gates
+  4. Failure disclosure completeness
+  5. Risk note presence
+  6. Harness artifact presence
+
+**Formula**
+
+$$
+T_e = 0.25 e_1 + 0.20 e_2 + 0.15 e_3 + 0.20 e_4 + 0.10 e_5 + 0.10 e_6
+$$
+
+**Threshold**
+
+- $\tau_{\text{evidence}} = 0.75$
+
+## Algorithm 5: Provider Maturity MVP
+
+**Inputs**
+
+- Eight normalized provider dimensions $p_1 \dots p_8$:
+  1. Binary / package presence
+  2. Authentication health
+  3. Model list currency
+  4. Quota-separation probe
+  5. Recent error rate
+  6. Fallback success rate
+  7. Stderr redaction coverage
+  8. Sandbox hint enforcement
+
+**Formula**
+
+$$
+M_p = 0.10 p_1 + 0.10 p_2 + 0.15 p_3 + 0.10 p_4 + 0.15 p_5 + 0.15 p_6 + 0.15 p_7 + 0.10 p_8
+$$
+
+**Cutoffs**
+
+- $M_p \ge 0.75$ required for pre-release worker eligibility.
+- $M_p \ge 0.85$ recommended for stable default authority.
+
+## Algorithm 6: Router v2 Cutover
+
+**Inputs**
+
+- Six positive router quality dimensions $r_1 \dots r_6$:
+  1. Intent classification accuracy
+  2. Median routing latency
+  3. Fallback utilization
+  4. Evidence-pass rate
+  5. Decision-trace completeness
+  6. Health-separation coverage
+- Two penalty terms $r_7, r_8$
+
+**Formula**
+
+$$
+Q_r = 0.25 r_1 + 0.15 r_2 + 0.20 r_3 + 0.15 r_4 + 0.10 r_5 + 0.10 r_6 - 0.15 r_7 - 0.10 r_8
+$$
+
+**Shadow rule**
+
+- If $\texttt{OMK\_ROUTER\_V2} = \text{shadow}$:
+  - Execute Router v2 alongside Router v1.
+  - Record both decisions and discrepancies.
+  - Cutover is allowed only when $Q_r \ge 0.85$ and the discrepancy rate is zero across the minimal verified demo run.
+
+## Algorithm 7: Minimal Verified Demo Run
+
+**Inputs**
+
+- Runtime $\mathcal{R}$
+- Demo scenario set $D = \{d_{\text{read}}, d_{\text{write}}, d_{\text{shell}}, d_{\text{fallback}}\}$
+
+**Output**
+
+- Demo verdict and evidence bundle $\mathcal{E}_D$
+
+**Pseudocode**
+
+```text
+function MinimalVerifiedDemoRun(R, D):
+    E_D ← ∅
+    for d in D:
+        r ← R.Execute(d, abortSignal=NewAbortController())
+        if r.exitCode ≠ 0:
+            return (fail, E_D)
+        if SecretScan(r.stdout, r.stderr) ≠ clean:
+            return (fail, E_D)
+        E_D ← E_D ∪ {d, r.metadata, r.evidence}
+    T_e ← ComputeEvidenceTrust(E_D)
+    if T_e < 0.75:
+        return (fail, E_D)
+    return (pass, E_D)
+```
+
+## Algorithm 8: Release Promotion Gate
+
+**Inputs**
+
+- Nine positive release dimensions $v_1 \dots v_9$:
+  1. Proof trust $T_b$
+  2. Evidence trust $T_e$
+  3. Public surface freeze pass
+  4. Provider maturity $M_p$
+  5. Router v2 quality $Q_r$
+  6. Minimal demo run pass
+  7. Security review closure
+  8. Docs / changelog sync
+  9. Issue closure rate
+- One penalty term $v_{10}$ for unresolved high-severity risk
+
+**Formula**
+
+$$
+R_v = 0.15 v_1 + 0.10 v_2 + 0.10 v_3 + 0.10 v_4 + 0.10 v_5 + 0.15 v_6 + 0.15 v_7 + 0.10 v_8 + 0.10 v_9 - 0.15 v_{10}
+$$
+
+**Promotion logic**
+
+```text
+function ReleasePromotion(R_v, T_b, T_e, P, Δ):
+    if P > 7 or |Δ| > 0:
+        return internal
+    if R_v ≥ 0.85 and T_b ≥ 0.85 and T_e ≥ 0.75:
+        return stable
+    if R_v ≥ 0.75 and T_b ≥ 0.75 and T_e ≥ 0.75:
+        return pre-release
+    return internal
+```
+
+> **Final Rule 1:** No stage promotion may occur while the public surface count exceeds 7 or any new public surface has been added since the freeze baseline.
+
+> **Final Rule 2:** Router v2 cutover remains in `OMK_ROUTER_V2=shadow` mode until $Q_r$ exceeds the stable threshold and zero decision regressions are observed across the minimal verified demo run.
+
+> **Final Rule 3:** Release promotion to stable requires $\tau_{\text{proof}} \ge 0.85$, $\tau_{\text{evidence}} \ge 0.75$, and all eight algorithms to report pass with recorded harness artifacts.
+
+## Algorithm 9: Regression Proof Matrix
+
+Algorithm 9 is the release-defense proof that Algorithms 1--8 are not only documented or implemented, but repeatedly verifiable through tests, proof bundles, decision traces, and reachable CLI surfaces.
+
+**Inputs**
+
+- Algorithm set $A = \{a_1, \dots, a_8\}$
+- Test suite $T$
+- Proof bundles $B$
+- Release candidate $v$
+
+**Per-algorithm coverage**
+
+For each algorithm $a_i$:
+
+$$
+coverage_i =
+0.35\mathbf{1}[|t_i|>0]
++0.30\mathbf{1}[|b_i|>0]
++0.20\mathbf{1}[|d_i|>0]
++0.15\mathbf{1}[c_i=\texttt{reachable}]
+$$
+
+Where:
+
+- $t_i$ is the set of tests linked to algorithm $a_i$
+- $b_i$ is the set of proof bundles linked to algorithm $a_i$
+- $d_i$ is the set of decision traces linked to algorithm $a_i$
+- $c_i$ is whether the algorithm has a reachable CLI or runtime surface
+
+**Pseudocode**
+
+```text
+function RegressionProofMatrix(A, T, B, v):
+    for a_i in A:
+        t_i ← FindTestsForAlgorithm(a_i, T)
+        b_i ← FindProofBundlesForAlgorithm(a_i, B)
+        d_i ← FindDecisionTraceForAlgorithm(a_i, B)
+        c_i ← FindCliSurfaceForAlgorithm(a_i, v)
+
+        coverage_i ←
+            0.35 * 1[|t_i| > 0]
+          + 0.30 * 1[|b_i| > 0]
+          + 0.20 * 1[|d_i| > 0]
+          + 0.15 * 1[c_i = reachable]
+
+        if coverage_i < 0.75:
+            return fail
+
+    trust ← MedianProofTrust(B)
+    router ← RouterShadowSafetyPass(B)
+    maturity ← ProviderAuthorityInvariantPass(B)
+    demo ← MinimalVerifiedDemoPass(v)
+
+    if trust ≥ 0.75 and router = 1 and maturity = 1 and demo = 1:
+        return pass
+    return fail
+```
+
+**Implementation targets**
+
+- `src/evidence/regression-proof-matrix.ts`
+- `scripts/regression-proof-matrix.mjs`
+- `test/regression-proof-matrix.test.mjs`
+- `proof/verified-runs/011-regression-proof-matrix/`
+
+**Release rule**
+
+> Algorithms 1--8 are release-defensible only when Algorithm 9 returns `pass` and `scripts/proof-check.mjs --trust --json` validates the corresponding proof bundles.

package/docs/provider-maturity.md

@@ -4,7 +4,7 @@ This page documents provider status for the current source tree.
 
 ## Current source target
 
-- Package version: `0.78.0`
+- Package version: `0.78.1`
 - Runtime contract family: `v1.2`
 - Release channel: `pre-1.0`
 

package/docs/versioning.md

@@ -4,11 +4,11 @@ OMK uses two version fields in release artifacts:
 
 | Field | Current value | Source | Meaning |
 | --- | --- | --- | --- |
-| Package version | `0.78.0` | `package.json`, `package-lock.json` | npm/package source version. |
+| Package version | `0.78.1` | `package.json`, `package-lock.json` | npm/package source version. |
 | Runtime version | `v1.2` | `src/version.ts`, JSON schemas | Contract/runtime family used by OMK envelopes. |
 | Release channel | `pre-1.0` | `src/version.ts` | Pre-1.0 package channel. |
 
-`0.78.0` is the package version for the `v1.2` runtime contract family.
+`0.78.1` is the package source version for the `v1.2` runtime contract family.
 Use `v1.2` only for runtime contracts; do not substitute it for the package version.
 
 ## Contract versions
@@ -44,6 +44,6 @@ The `version --json` command emits one `omk.contract.v1` envelope whose data pay
 
 ## Documentation rules
 
-- Use `0.78.0` when referring to the current package source version.
+- Use `0.78.1` when referring to the current package source version.
 - Use `v1.2` only for the runtime contract family.
 - Keep historical changelog entries unchanged unless the text is not clearly historical.

package/package.json

@@ -1,10 +1,9 @@
 {
   "name": "open-multi-agent-kit",
-  "version": "0.78.0",
+  "version": "0.78.2",
   "description": "Provider-neutral multi-agent control plane for coding workflows: route agents, verify evidence, orchestrate MCP-aware DAGs, and control the loop from the omk CLI.",
   "type": "module",
   "bin": {
-    "omk": "dist/cli.js",
     "omk-project-mcp": "dist/mcp/omk-project-server.js",
     "omk-acp": "dist/mcp/acp-server.js",
     "omk-mcp-host": "dist/mcp/host.js"
@@ -33,7 +32,9 @@
     "version:check": "node scripts/check-version-consistency.mjs",
     "contract:check": "npm run build:clean && npm run schema:check && node scripts/check-json-stdout.mjs",
     "verify:contracts": "npm run contract:check",
-    "release:check": "npm run verify && npm run verify:no-kimi && npm run contract:check && npm run schema:check && npm run version:check && npm run proof:check && npm run smoke:execution && npm run native:build && npm run pack:dry && npm run audit:package && npm run smoke:pack",
+    "release:check": "node scripts/release-gate.mjs",
+    "release:full": "npm run verify && npm run verify:no-kimi && npm run contract:check && npm run schema:check && npm run version:check && npm run proof:check && npm run smoke:execution && npm run native:build && npm run pack:dry && npm run audit:package && npm run smoke:pack",
+    "regression:matrix": "node scripts/regression-proof-matrix.mjs",
     "release:rc": "npm run verify && npm run verify:no-kimi && npm run contract:check && npm run schema:check && npm run version:check && npm run proof:check && npm run smoke:execution && npm run native:build && npm run pack:dry && npm run audit:package && npm run smoke:pack",
     "smoke:no-kimi:chat": "OMK_MCP_PREFLIGHT=off OMK_PROJECT_ROOT=\"$PWD\" node dist/cli.js chat --provider auto --mode agent --execution ask --layout plain --mcp-scope none --smoke --json",
     "smoke:no-kimi:codex": "OMK_MCP_PREFLIGHT=off OMK_PROJECT_ROOT=\"$PWD\" node dist/cli.js chat --provider codex --mode agent --execution ask --layout plain --mcp-scope none --smoke --json",

package/readmeasset/ASSET_INDEX.md

@@ -6,6 +6,7 @@ Curated OMK//CONTROL assets in this directory. Assets are provenance-covered and
 | ------------------------------- | --------- | ---------------------------------------------- | ------------------------------------------ | ----------- | ------ | -----: |
 | `omk-control.webp`              | yes       | Canonical README hero                          | Codex/OpenAI Images reviewed source        | `1536x1024` | `WEBP` | 164502 |
 | `omk-social-preview.png`        | yes       | GitHub/NPM social preview                      | local crop from omk-control.webp           | `1200x630`  | `PNG`  | 737974 |
+| `social-preview.png`            | repo-only | GitHub social preview upload candidate         | local Pillow render from omk-control.webp  | `1280x640`  | `PNG`  | 441349 |
 | `omk-tui-0.78.0.webp`           | yes       | 0.78.0 TUI mockup                              | Codex OAuth gpt-image-2 + local correction | `1536x1024` | `WEBP` | 244008 |
 | `omk_tui.png`                   | yes       | GitHub README terminal dashboard screenshot    | existing OMK TUI capture                   | `1712x1129` | `PNG`  | 141653 |
 | `omk-runtime-flow-0.78.0.webp`  | yes       | 0.78.0 runtime flow diagram                    | Codex OAuth gpt-image-2 + local correction | `1536x1024` | `WEBP` | 235842 |