/** * * Three subcommands under the existing `peaks workflow` verb: * - `read --project --json` * - `refresh --project [--apply] --json` * - `detect-trigger --project --rid [--refresh] --json` * * CLI justification (per dev-preference rules): * - `read` (2) JSON-gated — slice workflow reads plan hash. * - `refresh` (3) destructive write needs explicit `--apply`. * - `detect-trigger` (2) JSON-gated — slice workflow needs the verdict. * * strict-remediation c1 split: the action handlers and session/project * resolution moved to `workflow-plan-commands-actions.ts` and * `workflow-plan-commands-session.ts`. This module keeps only the commander * registration and re-exports the action entry points, so the public surface — * `registerWorkflowPlanCommands` plus the underscore test hooks `_runPlanRead` / * `_runPlanRefresh` / `_runPlanDetectTrigger` — is byte-for-byte the same that * `_register.ts` and the integration suite already import. */ import type { Command } from 'commander'; import { type ProgramIO } from '../cli-helpers.js'; import { runPlanDetectTrigger, runPlanRead, runPlanRefresh } from './workflow-plan-commands-actions.js'; export declare function registerWorkflowPlanCommands(program: Command, io: ProgramIO): void; export { runPlanRead as _runPlanRead }; export { runPlanRefresh as _runPlanRefresh }; export { runPlanDetectTrigger as _runPlanDetectTrigger };