@alexeiled/pi-fusion 0.5.2 → 0.6.1

package/src/types.ts

@@ -8,15 +8,34 @@ export const THINKING_LEVELS = [
 ] as const;
 
 export type ThinkingLevel = (typeof THINKING_LEVELS)[number];
+export const PANEL_AGENT = "pi-fusion.fusion-panelist";
+export const PANEL_AGENT_WEB = "pi-fusion.fusion-panelist-web";
+export const PANEL_AGENT_FULL = "pi-fusion.fusion-panelist-full";
+export const JUDGE_AGENT = "pi-fusion.fusion-judge";
+export const COMPOSER_AGENT = "pi-fusion.fusion-composer";
+
 export type FusionContextMode = "fresh" | "fork";
 
+/**
+ * How panel answers become one report.
+ * `select` — panelists answered the same question; the judge picks or reconciles.
+ * `merge`  — panelists answered different facets; the composer unions them.
+ */
+export type FusionSynthesisMode = "select" | "merge";
+
 export interface PanelMemberConfig {
   id: string;
-  label: string;
+  /** Report label. Defaults to `id` — set it only when they should differ. */
+  label?: string;
   agent: string;
   model?: string;
   thinking?: ThinkingLevel;
   role?: string;
+  /**
+   * Facet prompt sent instead of the raw task. `{task}` is substituted with the
+   * original prompt. Turns a redundant panel into one that divides the work.
+   */
+  question?: string;
 }
 
 export interface JudgeConfig {
@@ -32,6 +51,65 @@ export interface FusionProfile {
   timeoutMs?: number;
   context?: FusionContextMode;
   stopWhenPanelAgrees?: boolean;
+  /**
+   * Present panel answers to the judge as "Candidate A/B/C" instead of the
+   * configured labels. Role names read as authority cues before a word of
+   * content is compared. The report always restores the real labels.
+   */
+  blindPanelLabels?: boolean;
+  /**
+   * Caps the tool calls the judge may spend verifying contested claims.
+   * `soft` nudges, `hard` blocks further tool use so the judge still finalises.
+   */
+  judgeToolBudget?: ToolBudget;
+  /**
+   * Usually omit this. It is inferred: a panel where any member has a
+   * `question` is answering facets, so it merges; otherwise it selects.
+   * Set it only to override that — most often `"select"` on a faceted panel
+   * when you deliberately want the judge to pick rather than union.
+   *
+   * Under `merge` the synthesis spawn uses the composer agent and contract
+   * instead of the judge's. It reuses the judge run slot, so no new
+   * `FusionPhase` is introduced and `fusion:rpc:v1` stays compatible.
+   */
+  synthesis?: FusionSynthesisMode;
+}
+
+/**
+ * Facets are the thing that actually decides how answers combine, so the mode
+ * follows them by default. Requiring `synthesis` and `question` to agree made
+ * two ways to get a silently wrong report: facets judged for consensus they
+ * cannot have, or a composer told to merge facets that do not exist.
+ */
+/**
+ * Report label for a panel item. `label` is optional; it falls back to `id`, and
+ * then to the position. One definition so report and prompt never disagree.
+ */
+export function panelItemLabel(
+  item: Pick<PanelOutput, "index" | "id" | "label">,
+): string {
+  return item.label?.trim() || item.id?.trim() || `Panelist ${item.index + 1}`;
+}
+
+/** Report label for a member; `label` is optional and falls back to `id`. */
+export function memberLabel(
+  member: Pick<PanelMemberConfig, "id" | "label">,
+): string {
+  return member.label?.trim() || member.id;
+}
+
+export function resolveSynthesisMode(
+  profile: Pick<FusionProfile, "panel" | "synthesis">,
+): FusionSynthesisMode {
+  if (profile.synthesis) return profile.synthesis;
+  return profile.panel.some((member) => member.question?.trim())
+    ? "merge"
+    : "select";
+}
+
+export interface ToolBudget {
+  soft?: number;
+  hard?: number;
 }
 
 export type PanelConfidence = "low" | "medium" | "high";
@@ -79,6 +157,8 @@ export interface ParsedFusionArgs {
   prompt: string;
   profile?: string;
   operationId?: string;
+  /** Inline panel entries from `--panel`: `<model>` or `<agent>:<model>`. */
+  panel?: string[];
 }
 
 export interface PanelOutput {
@@ -121,6 +201,14 @@ export interface FusionRun {
   id: string;
   prompt: string;
   profileName: string;
+  /**
+   * Inline `--panel` entries, when the run used them. `profileName` then carries
+   * a display name that no config defines, so restore rebuilds the profile from
+   * `baseProfileName` plus these entries instead of looking the display name up.
+   */
+  inlinePanel?: string[];
+  /** Name of the config profile the inline panel was layered onto. */
+  baseProfileName?: string;
   operationId?: string;
   phase: FusionPhase;
   createdAt: number;