muonroi-cli 1.8.4 → 1.9.0

package/dist/src/council/index.d.ts

@@ -1,6 +1,6 @@
 import type { ModelMessage } from "ai";
 import type { StreamChunk } from "../types/index.js";
-import type { CouncilLLM, CouncilStats, PreflightResponder, QuestionResponder } from "./types.js";
+import type { CouncilLLM, CouncilStats, IsolatedTaskRunner, PreflightResponder, QuestionResponder } from "./types.js";
 /**
  * Wrap a CouncilLLM so every `generate` call inherits the council-wide abort
  * signal. The whole generate-based call path (clarifier, research-need eval,
@@ -35,6 +35,79 @@ export interface RunCouncilOptions {
      * Typically <flowDir>/runs/<runId>. When absent the lock file is skipped.
      */
     runDir?: string;
+    /**
+     * Fired with the post-debate action the user chose (e.g. "continue_session",
+     * "save_exit"). Lets the caller (runCouncilV2) auto-continue an agent turn on
+     * "continue_session" instead of ending at the composer. Called at most once.
+     */
+    onPostDebateAction?: (action: string) => void;
+    /**
+     * When true, the leader-auto-promote note and the `Leader: … · Panel: …`
+     * summary are NOT emitted as inline `content` chunks — the same data still
+     * rides the structured `council_meta` patch, which the TUI Context Rail
+     * renders as ambient sidebar rows. Set by the TUI when the rail is active
+     * (`isContextRailEnabled()`) so the roster is not duplicated (rail + inline)
+     * and does not read as a decision announced before any task assessment.
+     * Railless sinks (headless, telegram) leave it unset → inline is preserved.
+     */
+    suppressInlineMeta?: boolean;
+    /**
+     * When true, the preflight "approve discussion plan" card is auto-approved
+     * (no user gate). Set by the sprint-planning call site (`runSprint`): the
+     * overall product plan + spec were already approved at the `/ideal` preflight,
+     * so re-gating each sprint's internal plan is a redundant rubber-stamp that
+     * strands the loop BEFORE implementation is ever reached. The meaningful gate
+     * — the post-sprint customer verdict — still fires, so the user reviews each
+     * sprint's OUTPUT, not its plan.
+     */
+    autoApprovePreflight?: boolean;
+    /**
+     * When true, skip the (redundant) research phase inside the debate. Set by the
+     * sprint-planning call site: CB-1 already researched the product at the
+     * product level; the per-sprint plan reuses that grounding (the ProductSpec is
+     * embedded in the council topic) instead of paying for a second research pass.
+     */
+    skipResearch?: boolean;
+    /**
+     * When true, this council runs INSIDE an automated per-sprint planning pass
+     * (`runSprint`) — there is no interactive user turn and no real `sessions` row
+     * (the caller passes the product-RUN id as sessionId). Two consequences:
+     *
+     *  1. The post-debate continuation menu is SUPPRESSED. Presenting "Refine /
+     *     Save & Exit / Lock plan" here strands the sprint before implementation —
+     *     the observed blocker: picking "Save & Exit" ended the run with NO Sprint
+     *     Implementation, and "Refine" (the default) looped back into more debate.
+     *     Instead the synthesized plan is auto-locked (equivalent to "Lock plan and
+     *     execute Sprint 1") and control returns to the sprint runner.
+     *  2. Session-scoped persistence (appendSystemMessage / logInteraction /
+     *     SessionStore.setStatus) is SKIPPED. Those tables FK-reference
+     *     `sessions(id)`; the product-run id has no session row, so the FIRST write
+     *     throws `FOREIGN KEY constraint failed` — which previously aborted the
+     *     entire persist block (silently, under a bare catch), taking
+     *     `writeDecisionsLock` down with it. Skipping them lets the file-based
+     *     decisions.lock artifact actually get written for sprint-runner injection.
+     */
+    sprintPlanningMode?: boolean;
+    /**
+     * Convene-tool path (the `convene_council` builtin). When true, render
+     * clarify(optional)+debate+synthesis exactly as normal, then RETURN the
+     * synthesis string WITHOUT any post-debate decision surface: NO
+     * `pickPostDebateRecommendation`, NO option set, NO `council_question`
+     * post-debate card, NO `onPostDebateAction`, NO `postDebateContinuation`
+     * routing. The calling AGENT decides what happens next (continue silently,
+     * ask the user via `ask_user`, or hand off to `/ideal`) — the CLI hardcodes
+     * none of it (user directive: no CLI-hardcoded post-council branch). The
+     * persistence block (decisions.lock, judge, council record) still runs — it
+     * is an audit trail, not a decision.
+     */
+    convenePath?: boolean;
+    /**
+     * #2 — isolated sub-agent bridge (orchestrator.runTaskRequest). When wired,
+     * the debate's research phase runs in a budget-capped explore sub-agent
+     * instead of an in-process 15-step generateText. Forwarded onto CouncilConfig
+     * for runDebate. Optional — omitted by headless/direct callers/tests.
+     */
+    runIsolatedTask?: IsolatedTaskRunner;
 }
 export type PostDebateAction = "save_exit" | "generate_plan" | "refine" | "ask_followup" | "retry_synthesis";
 /**
@@ -49,6 +122,21 @@ export type PostDebateAction = "save_exit" | "generate_plan" | "refine" | "ask_f
  * generate_plan OPTION is still offered downstream; it's just no longer the
  * pre-selected default for non-build topics.
  */
+/**
+ * F1 — summarize how the debate did against its PINNED success criteria, so the
+ * post-debate card can distinguish "the criteria were actually met" from "the
+ * synthesis reads confidently" (evidence density). `metFlags` is index-aligned
+ * to `pinned` (from DebateState.finalCriteriaMet); a missing/short array treats
+ * the unmapped criteria as not-met. `inconclusive` is true when the spec had
+ * pinned criteria and at least one is still open — the caller ANDs this with
+ * `!synthesisFailed` before reframing the card.
+ */
+export declare function summarizeCriteriaOutcome(pinned: string[], metFlags: boolean[] | undefined): {
+    total: number;
+    metCount: number;
+    unmetLabels: string[];
+    inconclusive: boolean;
+};
 export declare function pickPostDebateRecommendation(input: {
     synthesisFailed: boolean;
     hasEmptySections: boolean;
@@ -56,10 +144,29 @@ export declare function pickPostDebateRecommendation(input: {
     confidenceLevel: "high" | "medium" | "low";
     hasPlan: boolean;
     outputKind: string;
+    /**
+     * F1 — count of pinned success criteria still unmet at debate end. When > 0 on
+     * a successful synthesis, the criteria bar the user actually set was NOT met, so
+     * we must not recommend committing (implement/plan/save) as if it were done —
+     * pressing the council to close the gap dominates the evidence-density and
+     * output-kind heuristics below.
+     */
+    criteriaUnmet?: number;
 }): {
     value: PostDebateAction;
     reason: string;
 };
+export declare function postDebateContinuation(action: string | undefined, synthesis: string, outputKind?: string): string | null;
+/**
+ * Neutral post-council continuation. Used by the auto-council path (tool-engine)
+ * and the `/council` slash path (runCouncilV2) once they run with
+ * `convenePath: true` — the hardcoded post-debate option card is suppressed, so
+ * there is no `chosenAction` to branch on. Instead of the CLI deciding the next
+ * step, we hand the synthesis back to a normal agent turn with a NON-BINDING
+ * nudge and let the agent's own intent drive the follow-up (respond / ask_user /
+ * implement). Returns "" for an empty synthesis so the caller skips re-entry.
+ */
+export declare function buildNeutralPostCouncilContinuation(synthesis: string): string;
 export declare function runCouncil(topic: string, sessionModelId: string, messages: Array<{
     role: string;
     content: string | unknown;