/** * Live harness status. * * This is not `doctor` and not `status`. Those describe install health or * call tool handlers inside this process. `harness` reports what is already * running for this working tree: the host session, a live daemon pid, ruflo * MCP servers whose cwd is this tree, processes holding the memory databases * open, and teams that are still active. * * ruflo harness * ruflo harness --json * ruflo harness --hook # SessionStart payload for Codex (and Claude) * ruflo harness --print-codex-hook # opt-in .codex/hooks.json for this install * * `harness` is observe-only: bin/cli.js runs it through `runHarnessCli` * before the normal CLI starts, so no daemon autostart, update check, policy * migration or config adoption runs, and nothing is written to disk. The CLI * class also exempts it from those side effects (see OBSERVE_ONLY_COMMANDS). */ import type { Command } from '../types.js'; import { type LiveHarness } from '../services/live-harness.js'; export type { LiveHarness } from '../services/live-harness.js'; export { collectLiveHarness } from '../services/live-harness.js'; /** This install's bin/cli.js, from dist/src/commands/harness.js (or src/commands). */ export declare function installedCliPath(moduleUrl?: string): string; /** * A .codex/hooks.json that runs this install's harness on SessionStart. The * path is absolute, so the hook does not depend on the session's git root. * Autostart and the update check are off, and failures stay silent. */ export declare function codexHookConfig(cliPath?: string): string; /** * Entry used by bin/cli.js before the CLI class loads. Returns the exit code. * With --hook it never fails: on any error it prints nothing and returns 0, * so a SessionStart hook can't break a session. */ export declare function runHarnessCli(argv: string[], write?: (text: string) => void, collect?: () => LiveHarness): number; export declare const harnessCommand: Command; export default harnessCommand; //# sourceMappingURL=harness.d.ts.map