open-multi-agent-kit 0.78.5 → 0.78.7

package/dist/util/native-safety.d.ts

@@ -1,28 +0,0 @@
-export type NativeSafetySource = "env" | "bundled" | "target-release" | "target-debug" | "missing";
-export type NativeSafetyStatus = "ok" | "warn" | "info";
-export interface NativeSafetyResolution {
-    ok: boolean;
-    source: NativeSafetySource;
-    path: string | null;
-    platformArch: string;
-    builtFromSource: boolean;
-    message: string;
-}
-export interface NativeSafetySelfTest extends NativeSafetyResolution {
-    status: NativeSafetyStatus;
-    checks: number | null;
-}
-export interface NativeSafetyOptions {
-    root?: string;
-    packageRoot?: string;
-    env?: NodeJS.ProcessEnv;
-    platform?: NodeJS.Platform | string;
-    arch?: string;
-    timeoutMs?: number;
-}
-export declare function getNativePlatformArchKey(platform?: NodeJS.Platform | string, arch?: string): string;
-export declare function getOmkSafetyBinaryName(platform?: NodeJS.Platform | string): string;
-export declare function getOmkPackageRoot(): string;
-export declare function getBundledOmkSafetyBinaryPath(packageRoot?: string, platform?: NodeJS.Platform | string, arch?: string): string;
-export declare function resolveOmkSafetyNative(options?: NativeSafetyOptions): Promise<NativeSafetyResolution>;
-export declare function runOmkSafetySelfTest(options?: NativeSafetyOptions): Promise<NativeSafetySelfTest>;

package/dist/util/native-safety.js

@@ -1,118 +0,0 @@
-import { constants } from "node:fs";
-import { access } from "node:fs/promises";
-import { dirname, isAbsolute, join } from "node:path";
-import { fileURLToPath } from "node:url";
-import { runShell } from "./shell.js";
-const SUPPORTED_PLATFORMS = new Set(["linux", "darwin", "win32"]);
-const SUPPORTED_ARCHES = new Set(["x64", "arm64"]);
-export function getNativePlatformArchKey(platform = process.platform, arch = process.arch) {
-    return `${platform}-${arch}`;
-}
-export function getOmkSafetyBinaryName(platform = process.platform) {
-    return platform === "win32" ? "omk-safety.exe" : "omk-safety";
-}
-export function getOmkPackageRoot() {
-    return join(dirname(fileURLToPath(import.meta.url)), "..", "..");
-}
-export function getBundledOmkSafetyBinaryPath(packageRoot = getOmkPackageRoot(), platform = process.platform, arch = process.arch) {
-    return join(packageRoot, "dist", "native", getNativePlatformArchKey(platform, arch), getOmkSafetyBinaryName(platform));
-}
-function isSupportedPlatformArch(platform, arch) {
-    return SUPPORTED_PLATFORMS.has(platform) && SUPPORTED_ARCHES.has(arch);
-}
-function normalizeEnvPath(rawPath) {
-    return isAbsolute(rawPath) ? rawPath : join(process.cwd(), rawPath);
-}
-function getNativeSafetyCandidates(options = {}) {
-    const env = options.env ?? process.env;
-    const packageRoot = options.packageRoot ?? getOmkPackageRoot();
-    const root = options.root ?? packageRoot;
-    const platform = options.platform ?? process.platform;
-    const arch = options.arch ?? process.arch;
-    const binaryName = getOmkSafetyBinaryName(platform);
-    const candidates = [];
-    if (env.OMK_SAFETY_BIN) {
-        candidates.push({ source: "env", path: normalizeEnvPath(env.OMK_SAFETY_BIN), builtFromSource: false });
-    }
-    if (isSupportedPlatformArch(platform, arch)) {
-        candidates.push({ source: "bundled", path: getBundledOmkSafetyBinaryPath(packageRoot, platform, arch), builtFromSource: false });
-    }
-    candidates.push({ source: "target-release", path: join(root, "target", "release", binaryName), builtFromSource: true });
-    candidates.push({ source: "target-debug", path: join(root, "target", "debug", binaryName), builtFromSource: true });
-    return candidates;
-}
-async function fileExists(path) {
-    try {
-        await access(path, constants.F_OK);
-        return true;
-    }
-    catch {
-        return false;
-    }
-}
-export async function resolveOmkSafetyNative(options = {}) {
-    const platform = options.platform ?? process.platform;
-    const arch = options.arch ?? process.arch;
-    const platformArch = getNativePlatformArchKey(platform, arch);
-    for (const candidate of getNativeSafetyCandidates(options)) {
-        if (await fileExists(candidate.path)) {
-            return {
-                ok: true,
-                source: candidate.source,
-                path: candidate.path,
-                platformArch,
-                builtFromSource: candidate.builtFromSource,
-                message: `native omk-safety resolved via ${candidate.source}: ${candidate.path}`,
-            };
-        }
-    }
-    return {
-        ok: false,
-        source: "missing",
-        path: null,
-        platformArch,
-        builtFromSource: false,
-        message: `native omk-safety binary not bundled for ${platformArch} — run npm run native:build or use TS fallback`,
-    };
-}
-export async function runOmkSafetySelfTest(options = {}) {
-    const resolution = await resolveOmkSafetyNative(options);
-    if (!resolution.path) {
-        return { ...resolution, status: "info", checks: null };
-    }
-    const result = await runShell(resolution.path, ["self-test"], {
-        cwd: options.root ?? options.packageRoot ?? getOmkPackageRoot(),
-        timeout: options.timeoutMs ?? 5000,
-    });
-    if (result.failed) {
-        return {
-            ...resolution,
-            ok: false,
-            status: "warn",
-            checks: null,
-            message: `self-test failed for ${resolution.path}`,
-        };
-    }
-    try {
-        const parsed = JSON.parse(result.stdout);
-        if (parsed.ok === true && typeof parsed.checks === "number") {
-            const prefix = resolution.builtFromSource ? "self-test passed from source build" : "self-test passed";
-            return {
-                ...resolution,
-                status: "ok",
-                checks: parsed.checks,
-                message: `${prefix} (${parsed.checks} checks): ${resolution.path}`,
-            };
-        }
-    }
-    catch {
-        // fall through to warning below
-    }
-    return {
-        ...resolution,
-        ok: false,
-        status: "warn",
-        checks: null,
-        message: `self-test returned unexpected output for ${resolution.path}`,
-    };
-}

package/templates/skills/agents/omk-adaptorch-orchestration-review/SKILL.md

@@ -1,52 +0,0 @@
----
-name: omk-adaptorch-orchestration-review
-description: Review AdaptOrch, OMK, and similar DAG multi-agent orchestration frameworks. Use when assessing DAG node responsibility, dependency edges, worker write authority, fallback/retry/timeout/evidence gates, review/merge boundaries, or reproducible decision traces.
----
-
-## Orchestration Review
-
-Use this for read-only architecture review of DAG runtimes, multi-agent pipelines, worktree teams, schedulers, and evidence-gated repair loops.
-
-## Checklist
-
-### DAG node contract
-
-- Verify each node has one responsibility, one owner role, and one observable outcome.
-- Verify inputs, outputs, side effects, and acceptance evidence are explicit.
-- Flag nodes that mix planning, implementation, review, and merge authority without a gate.
-
-### Dependency edges
-
-- Confirm each edge represents a real data dependency, verification dependency, or authority handoff.
-- Flag ordering-only edges that do not protect correctness or safety.
-- Check that failed evidence blocks dependent nodes or routes them to repair.
-
-### Worker authority
-
-- Confirm each worker has bounded write scope and cannot overwrite unrelated lanes.
-- Check shared-file ownership, merge points, and escalation paths.
-- Require reviewer/merger separation for risky or cross-cutting changes.
-
-### Resilience and gates
-
-- Look for explicit retry limits, timeout presets, fallback routes, stop conditions, and evidence gates.
-- Confirm fallback does not silently weaken acceptance criteria.
-- Check that blocked, skipped, failed, and complete states are distinct.
-
-### Decision trace
-
-- Confirm routing, scheduler decisions, tool calls, evidence, retries, and final verdict are replayable.
-- Flag missing timestamps, inputs, outputs, or rationale needed to reproduce a run.
-
-## Output
-
-```txt
-Verdict:
-DAG node issues:
-Dependency edge issues:
-Worker authority risks:
-Missing gates:
-Decision trace gaps:
-Recommended fixes:
-Files/artifacts reviewed:
-```

package/templates/skills/kimi/mcp-install/SKILL.md

@@ -1,66 +0,0 @@
----
-name: mcp-install
-description: Install, validate, and manage MCP servers for OMK using the curated catalog and parallel processing.
----
-
-# MCP Server Installation Skill
-
-Guide for adding MCP servers to an OMK project using the built-in catalog and parallel orchestration.
-
-## Commands
-
-```bash
-# List configured MCP servers
-omk mcp list
-
-# Diagnose all MCP servers
-omk mcp doctor
-
-# Diagnose a specific server
-omk mcp doctor <server-name>
-
-# Install a single MCP server
-omk mcp install <name> <command> [args...]
-
-# Remove a server from project-local config
-omk mcp remove <name>
-
-# Sync global MCP servers into project
-omk mcp sync-global
-```
-
-## Curated Catalog
-
-OMK ships with a verified catalog in `src/mcp/server-catalog.ts` (or accessible via the runtime).
-Recommended categories:
-
-- **reasoning**: `sequential-thinking` — structured problem solving
-- **memory**: `memory` — persistent knowledge graph
-- **docs**: `pdf` — PDF text extraction
-- **web**: `puppeteer` — browser automation
-- **devtools**: `filesystem`, `sqlite` — file and database access
-- **ops**: `railway` — remote Railway MCP; `supabase` — database management and edge functions
-
-## Parallel Installation
-
-When installing multiple servers (e.g., during `omk init`), OMK uses `Promise.all` for parallel setup.
-Agents and hooks can also trigger bulk installs:
-
-1. **Agent lane**: explorer validates which servers are needed
-2. **Coder lane**: writes the MCP JSON entries
-3. **QA lane**: runs `omk mcp doctor` to verify each server
-4. **Hook**: `post-init-mcp.sh` runs non-blocking validation after init
-
-## Rules
-
-1. Prefer `npx -y <package>` so no global install is required.
-2. Use `${PROJECT_ROOT}` and `${DB_PATH}` placeholders in catalog entries; they are resolved at install time.
-3. Do not commit secrets in `mcp.json` env values.
-4. Run `omk mcp doctor` after adding servers to confirm they start.
-5. If a server fails to start, check `startup_timeout_sec` and network access.
-
-## When to Use
-
-- During `omk init` when selecting additional MCP servers.
-- When a task requires a new capability (browser, PDF, database).
-- Before reporting an MCP issue, run `omk mcp doctor --json` for structured evidence.

package/templates/skills/kimi/omk-adaptorch-orchestration-review/SKILL.md

@@ -1,52 +0,0 @@
----
-name: omk-adaptorch-orchestration-review
-description: Review AdaptOrch, OMK, and similar DAG multi-agent orchestration frameworks. Use when assessing DAG node responsibility, dependency edges, worker write authority, fallback/retry/timeout/evidence gates, review/merge boundaries, or reproducible decision traces.
----
-
-## Orchestration Review
-
-Use this for read-only architecture review of DAG runtimes, multi-agent pipelines, worktree teams, schedulers, and evidence-gated repair loops.
-
-## Checklist
-
-### DAG node contract
-
-- Verify each node has one responsibility, one owner role, and one observable outcome.
-- Verify inputs, outputs, side effects, and acceptance evidence are explicit.
-- Flag nodes that mix planning, implementation, review, and merge authority without a gate.
-
-### Dependency edges
-
-- Confirm each edge represents a real data dependency, verification dependency, or authority handoff.
-- Flag ordering-only edges that do not protect correctness or safety.
-- Check that failed evidence blocks dependent nodes or routes them to repair.
-
-### Worker authority
-
-- Confirm each worker has bounded write scope and cannot overwrite unrelated lanes.
-- Check shared-file ownership, merge points, and escalation paths.
-- Require reviewer/merger separation for risky or cross-cutting changes.
-
-### Resilience and gates
-
-- Look for explicit retry limits, timeout presets, fallback routes, stop conditions, and evidence gates.
-- Confirm fallback does not silently weaken acceptance criteria.
-- Check that blocked, skipped, failed, and complete states are distinct.
-
-### Decision trace
-
-- Confirm routing, scheduler decisions, tool calls, evidence, retries, and final verdict are replayable.
-- Flag missing timestamps, inputs, outputs, or rationale needed to reproduce a run.
-
-## Output
-
-```txt
-Verdict:
-DAG node issues:
-Dependency edge issues:
-Worker authority risks:
-Missing gates:
-Decision trace gaps:
-Recommended fixes:
-Files/artifacts reviewed:
-```