@a5c-ai/babysitter-sdk 0.0.183-staging.64fe647d → 0.0.183-staging.714cc8f6

package/dist/cli/commands/harnessPhase1.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"harnessPhase1.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/harnessPhase1.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAGH,OAAO,KAAK,QAAQ,MAAM,eAAe,CAAC;AAa1C,OAAO,EAIL,KAAK,2BAA2B,EAEhC,KAAK,iBAAiB,EAGtB,KAAK,oBAAoB,IAAI,0BAA0B,EAwBxD,MAAM,gBAAgB,CAAC;AAkBxB,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,CAE/D;AAyHD,wBAAgB,eAAe,CAC7B,OAAO,EAAE,MAAM,EACf,IAAI,EAAE,MAAM,EAAE,EACd,GAAG,CAAC,EAAE,MAAM,GACX,OAAO,CAAC;IAAE,MAAM,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,CAAC,CAyB/D;AAg5BD,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,MAAM,CAmDzE;AAED,wBAAgB,sCAAsC,CAAC,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,MAAM,EAAE,CAU/F;AAED,wBAAgB,yBAAyB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAgBrE;AAED,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,CAwBhG;AAwGD,wBAAgB,oCAAoC,CAAC,IAAI,EAAE;IACzD,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,MAAM,CAAC;IACnB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,aAAa,EAAE,0BAA0B,CAAC;IAC1C,mBAAmB,EAAE,2BAA2B,CAAC;CAClD,GAAG,MAAM,CA+ET;AAED,wBAAgB,qCAAqC,CAAC,IAAI,EAAE;IAC1D,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,EAAE,MAAM,CAAC;CAChB,GAAG,MAAM,CA4BT;AAkND,wBAAsB,yBAAyB,CAAC,IAAI,EAAE;IACpD,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,MAAM,CAAC;IACnB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,WAAW,EAAE,OAAO,CAAC;IACrB,EAAE,EAAE,QAAQ,CAAC,SAAS,GAAG,IAAI,CAAC;IAC9B,IAAI,EAAE,OAAO,CAAC;IACd,OAAO,EAAE,OAAO,CAAC;IACjB,iBAAiB,EAAE,iBAAiB,GAAG,IAAI,CAAC;IAC5C,aAAa,EAAE,0BAA0B,CAAC;IAC1C,mBAAmB,EAAE,MAAM,CAAC;CAC7B,GAAG,OAAO,CAAC,MAAM,CAAC,CAwgBlB"}
+{"version":3,"file":"harnessPhase1.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/harnessPhase1.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAGH,OAAO,KAAK,QAAQ,MAAM,eAAe,CAAC;AAa1C,OAAO,EAIL,KAAK,2BAA2B,EAEhC,KAAK,iBAAiB,EAGtB,KAAK,oBAAoB,IAAI,0BAA0B,EAwBxD,MAAM,gBAAgB,CAAC;AAkBxB,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,CAE/D;AAyHD,wBAAgB,eAAe,CAC7B,OAAO,EAAE,MAAM,EACf,IAAI,EAAE,MAAM,EAAE,EACd,GAAG,CAAC,EAAE,MAAM,GACX,OAAO,CAAC;IAAE,MAAM,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,CAAC,CAyB/D;AAg5BD,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,MAAM,CAmDzE;AAED,wBAAgB,sCAAsC,CAAC,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,MAAM,EAAE,CAU/F;AAED,wBAAgB,yBAAyB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAgBrE;AAED,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,CAwBhG;AAwGD,wBAAgB,oCAAoC,CAAC,IAAI,EAAE;IACzD,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,MAAM,CAAC;IACnB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,aAAa,EAAE,0BAA0B,CAAC;IAC1C,mBAAmB,EAAE,2BAA2B,CAAC;CAClD,GAAG,MAAM,CA+ET;AAED,wBAAgB,qCAAqC,CAAC,IAAI,EAAE;IAC1D,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,EAAE,MAAM,CAAC;CAChB,GAAG,MAAM,CA4BT;AAkND,wBAAsB,yBAAyB,CAAC,IAAI,EAAE;IACpD,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,MAAM,CAAC;IACnB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,WAAW,EAAE,OAAO,CAAC;IACrB,EAAE,EAAE,QAAQ,CAAC,SAAS,GAAG,IAAI,CAAC;IAC9B,IAAI,EAAE,OAAO,CAAC;IACd,OAAO,EAAE,OAAO,CAAC;IACjB,iBAAiB,EAAE,iBAAiB,GAAG,IAAI,CAAC;IAC5C,aAAa,EAAE,0BAA0B,CAAC;IAC1C,mBAAmB,EAAE,MAAM,CAAC;CAC7B,GAAG,OAAO,CAAC,MAAM,CAAC,CAygBlB"}

package/dist/cli/commands/harnessPhase1.js

@@ -1502,7 +1502,7 @@ async function runProcessDefinitionPhase(args) {
     })));
     const workspaceAssessment = await assessWorkspaceForExternalAuthoring(args.workspace);
     writeVerboseData("phase1 workspace assessment", workspaceAssessment);
-    const processDefinitionSystemPrompt = (0, harnessPrompts_1.buildProcessDefinitionSystemPrompt)(args.outputPath, args.promptContext);
+    const processDefinitionSystemPrompt = await (0, harnessPrompts_1.buildProcessDefinitionSystemPrompt)(args.outputPath, args.promptContext, args.interactive);
     const initialMetaPrompt = (0, harnessPrompts_1.buildProcessDefinitionUserPrompt)(args.prompt, args.outputPath, {
         interactive: args.interactive,
         workspaceAssessment: workspaceAssessment.kind,

package/dist/cli/commands/harnessPhase2.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"harnessPhase2.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/harnessPhase2.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAGH,OAAO,KAAK,QAAQ,MAAM,eAAe,CAAC;AAkB1C,OAAO,EAOL,KAAK,mBAAmB,EACxB,KAAK,iBAAiB,EACtB,KAAK,sBAAsB,EAI3B,KAAK,oBAAoB,IAAI,0BAA0B,EACvD,KAAK,YAAY,EA8BjB,eAAe,EAIhB,MAAM,gBAAgB,CAAC;AAaxB,wBAAsB,aAAa,CACjC,MAAM,EAAE,YAAY,EACpB,WAAW,EAAE,MAAM,EACnB,OAAO,EAAE;IACP,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,iBAAiB,CAAC,EAAE,iBAAiB,GAAG,IAAI,CAAC;CAC9C,EACD,SAAS,CAAC,EAAE,eAAe,GAAG,IAAI,EAClC,UAAU,CAAC,EAAE,sBAAsB,EAAE,EACrC,EAAE,CAAC,EAAE,QAAQ,CAAC,SAAS,GAAG,IAAI,EAC9B,IAAI,CAAC,EAAE,OAAO,EACd,sBAAsB,CAAC,EAAE,CAAC,CAAC,MAAM,EAAE,OAAO,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC,GAAG,IAAI,GACtE,OAAO,CAAC,mBAAmB,CAAC,CAwO9B;AA2ND,wBAAsB,qBAAqB,CAAC,IAAI,EAAE;IAChD,WAAW,EAAE,MAAM,CAAC;IACpB,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,OAAO,EAAE,MAAM,CAAC;IAChB,aAAa,EAAE,MAAM,CAAC;IACtB,IAAI,EAAE,OAAO,CAAC;IACd,OAAO,EAAE,OAAO,CAAC;IACjB,WAAW,EAAE,OAAO,CAAC;IACrB,EAAE,EAAE,QAAQ,CAAC,SAAS,GAAG,IAAI,CAAC;IAC9B,mBAAmB,EAAE,MAAM,CAAC;IAC5B,UAAU,EAAE,sBAAsB,EAAE,CAAC;IACrC,iBAAiB,EAAE,iBAAiB,GAAG,IAAI,CAAC;IAC5C,aAAa,EAAE,0BAA0B,CAAC;IAC1C,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB,GAAG,OAAO,CAAC,MAAM,CAAC,CAw1ClB"}
+{"version":3,"file":"harnessPhase2.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/harnessPhase2.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAGH,OAAO,KAAK,QAAQ,MAAM,eAAe,CAAC;AAkB1C,OAAO,EAOL,KAAK,mBAAmB,EACxB,KAAK,iBAAiB,EACtB,KAAK,sBAAsB,EAI3B,KAAK,oBAAoB,IAAI,0BAA0B,EACvD,KAAK,YAAY,EA8BjB,eAAe,EAIhB,MAAM,gBAAgB,CAAC;AAaxB,wBAAsB,aAAa,CACjC,MAAM,EAAE,YAAY,EACpB,WAAW,EAAE,MAAM,EACnB,OAAO,EAAE;IACP,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,iBAAiB,CAAC,EAAE,iBAAiB,GAAG,IAAI,CAAC;CAC9C,EACD,SAAS,CAAC,EAAE,eAAe,GAAG,IAAI,EAClC,UAAU,CAAC,EAAE,sBAAsB,EAAE,EACrC,EAAE,CAAC,EAAE,QAAQ,CAAC,SAAS,GAAG,IAAI,EAC9B,IAAI,CAAC,EAAE,OAAO,EACd,sBAAsB,CAAC,EAAE,CAAC,CAAC,MAAM,EAAE,OAAO,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC,GAAG,IAAI,GACtE,OAAO,CAAC,mBAAmB,CAAC,CAwO9B;AA2ND,wBAAsB,qBAAqB,CAAC,IAAI,EAAE;IAChD,WAAW,EAAE,MAAM,CAAC;IACpB,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,OAAO,EAAE,MAAM,CAAC;IAChB,aAAa,EAAE,MAAM,CAAC;IACtB,IAAI,EAAE,OAAO,CAAC;IACd,OAAO,EAAE,OAAO,CAAC;IACjB,WAAW,EAAE,OAAO,CAAC;IACrB,EAAE,EAAE,QAAQ,CAAC,SAAS,GAAG,IAAI,CAAC;IAC9B,mBAAmB,EAAE,MAAM,CAAC;IAC5B,UAAU,EAAE,sBAAsB,EAAE,CAAC;IACrC,iBAAiB,EAAE,iBAAiB,GAAG,IAAI,CAAC;IAC5C,aAAa,EAAE,0BAA0B,CAAC;IAC1C,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB,GAAG,OAAO,CAAC,MAAM,CAAC,CA01ClB"}

package/dist/cli/commands/harnessPhase2.js

@@ -430,6 +430,7 @@ async function runOrchestrationPhase(args) {
                 },
                 prompt: args.prompt,
                 inputs: args.prompt ? { prompt: args.prompt } : undefined,
+                ...(args.interactive === false ? { metadata: { nonInteractive: true } } : {}),
             });
             state.runId = created.runId;
             state.runDir = created.runDir;
@@ -673,6 +674,7 @@ async function runOrchestrationPhase(args) {
                     inputs: effectivePrompt
                         ? { prompt: effectivePrompt }
                         : undefined,
+                    ...(args.interactive === false ? { metadata: { nonInteractive: true } } : {}),
                 });
                 state.runId = result.runId;
                 state.runDir = result.runDir;
@@ -1275,7 +1277,7 @@ async function runOrchestrationPhase(args) {
         uiContext: args.interactive && args.rl
             ? (0, harnessUtils_1.createReadlineAskUserQuestionUiContext)(args.rl)
             : undefined,
-        appendSystemPrompt: [(0, harnessPrompts_1.buildOrchestrationSystemPrompt)(args.selectedHarnessName, args.promptContext)],
+        appendSystemPrompt: [(0, harnessPrompts_1.buildOrchestrationSystemPrompt)(args.selectedHarnessName, args.promptContext, args.interactive)],
         ephemeral: true,
     });
     writeVerbose(`[phase2 setup] harness=${args.selectedHarnessName} workspace=${path.resolve(args.workspace ?? process.cwd())} model=${args.model ?? "(default)"} processPath=${path.resolve(args.processPath)}`);
@@ -1283,7 +1285,7 @@ async function runOrchestrationPhase(args) {
         name: tool.name,
         label: tool.label,
     })));
-    writeVerboseData("phase2 system prompt", (0, harnessPrompts_1.buildOrchestrationSystemPrompt)(args.selectedHarnessName, args.promptContext));
+    writeVerboseData("phase2 system prompt", (0, harnessPrompts_1.buildOrchestrationSystemPrompt)(args.selectedHarnessName, args.promptContext, args.interactive));
     (0, harnessUtils_1.emitProgress)({ phase: "2", status: "started", harness: args.selectedHarnessName }, args.json, args.verbose);
     let unsubscribe = null;
     try {

package/dist/cli/commands/harnessPrompts.d.ts

@@ -23,9 +23,9 @@ export interface ProcessDefinitionUserPromptOptions {
     workspaceAssessment?: "empty" | "non-empty";
     workspaceEntries?: string[];
 }
-export declare function buildProcessDefinitionSystemPrompt(outputPath: string, context: HarnessPromptContext): string;
+export declare function buildProcessDefinitionSystemPrompt(outputPath: string, context: HarnessPromptContext, interactive?: boolean | undefined): Promise<string>;
 export declare function buildProcessDefinitionUserPrompt(userPrompt: string, outputPath: string, options?: ProcessDefinitionUserPromptOptions): string;
-export declare function buildOrchestrationSystemPrompt(selectedHarnessName: string, context: HarnessPromptContext): string;
+export declare function buildOrchestrationSystemPrompt(selectedHarnessName: string, context: HarnessPromptContext, interactive?: boolean | undefined): string;
 export declare function buildOrchestrationBootstrapPrompt(processPath: string, userPrompt: string | undefined, maxIterations: number): string;
 export declare function buildOrchestrationTurnPrompt(args: {
     processPath: string;

package/dist/cli/commands/harnessPrompts.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"harnessPrompts.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/harnessPrompts.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,sBAAsB,EAAE,MAAM,qBAAqB,CAAC;AAElE,MAAM,WAAW,oBAAoB;IACnC,QAAQ,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,GAAG,EAAE,MAAM,CAAC;IACZ,SAAS,EAAE,MAAM,CAAC;IAClB,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,mBAAmB,EAAE,sBAAsB,EAAE,CAAC;IAC9C,kBAAkB,EAAE,OAAO,CAAC;IAC5B,kBAAkB,EAAE,MAAM,CAAC;IAC3B,oBAAoB,EAAE,OAAO,GAAG,MAAM,GAAG,QAAQ,CAAC;IAClD,kBAAkB,EAAE,OAAO,CAAC;IAC5B,QAAQ,EAAE,KAAK,CAAC;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;CAClD;AAED,mDAAmD;AACnD,MAAM,MAAM,0BAA0B,GAAG,oBAAoB,CAAC;AAE9D,MAAM,WAAW,kCAAkC;IACjD,WAAW,EAAE,OAAO,CAAC;IACrB,mBAAmB,CAAC,EAAE,OAAO,GAAG,WAAW,CAAC;IAC5C,gBAAgB,CAAC,EAAE,MAAM,EAAE,CAAC;CAC7B;AAgFD,wBAAgB,kCAAkC,CAChD,UAAU,EAAE,MAAM,EAClB,OAAO,EAAE,oBAAoB,GAC5B,MAAM,CAiER;AAED,wBAAgB,gCAAgC,CAC9C,UAAU,EAAE,MAAM,EAClB,UAAU,EAAE,MAAM,EAClB,OAAO,CAAC,EAAE,kCAAkC,GAC3C,MAAM,CAyDR;AAED,wBAAgB,8BAA8B,CAC5C,mBAAmB,EAAE,MAAM,EAC3B,OAAO,EAAE,oBAAoB,GAC5B,MAAM,CA4BR;AAED,wBAAgB,iCAAiC,CAC/C,WAAW,EAAE,MAAM,EACnB,UAAU,EAAE,MAAM,GAAG,SAAS,EAC9B,aAAa,EAAE,MAAM,GACpB,MAAM,CAWR;AAED,wBAAgB,4BAA4B,CAAC,IAAI,EAAE;IACjD,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,aAAa,EAAE,MAAM,CAAC;IACtB,gBAAgB,EAAE,MAAM,CAAC;IACzB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,cAAc,CAAC,EAAE,KAAK,CAAC;QACrB,QAAQ,EAAE,MAAM,CAAC;QACjB,IAAI,EAAE,MAAM,CAAC;QACb,KAAK,CAAC,EAAE,MAAM,CAAC;QACf,OAAO,CAAC,EAAE,MAAM,CAAC;KAClB,CAAC,CAAC;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB,GAAG,MAAM,CA+CT"}
+{"version":3,"file":"harnessPrompts.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/harnessPrompts.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,sBAAsB,EAAE,MAAM,qBAAqB,CAAC;AAQlE,MAAM,WAAW,oBAAoB;IACnC,QAAQ,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,GAAG,EAAE,MAAM,CAAC;IACZ,SAAS,EAAE,MAAM,CAAC;IAClB,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,mBAAmB,EAAE,sBAAsB,EAAE,CAAC;IAC9C,kBAAkB,EAAE,OAAO,CAAC;IAC5B,kBAAkB,EAAE,MAAM,CAAC;IAC3B,oBAAoB,EAAE,OAAO,GAAG,MAAM,GAAG,QAAQ,CAAC;IAClD,kBAAkB,EAAE,OAAO,CAAC;IAC5B,QAAQ,EAAE,KAAK,CAAC;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;CAClD;AAED,mDAAmD;AACnD,MAAM,MAAM,0BAA0B,GAAG,oBAAoB,CAAC;AAE9D,MAAM,WAAW,kCAAkC;IACjD,WAAW,EAAE,OAAO,CAAC;IACrB,mBAAmB,CAAC,EAAE,OAAO,GAAG,WAAW,CAAC;IAC5C,gBAAgB,CAAC,EAAE,MAAM,EAAE,CAAC;CAC7B;AAiFD,wBAAsB,kCAAkC,CACtD,UAAU,EAAE,MAAM,EAClB,OAAO,EAAE,oBAAoB,EAC7B,WAAW,CAAC,EAAE,OAAO,GAAG,SAAS,GAChC,OAAO,CAAC,MAAM,CAAC,CA4DjB;AAED,wBAAgB,gCAAgC,CAC9C,UAAU,EAAE,MAAM,EAClB,UAAU,EAAE,MAAM,EAClB,OAAO,CAAC,EAAE,kCAAkC,GAC3C,MAAM,CAyDR;AAED,wBAAgB,8BAA8B,CAC5C,mBAAmB,EAAE,MAAM,EAC3B,OAAO,EAAE,oBAAoB,EAC7B,WAAW,CAAC,EAAE,OAAO,GAAG,SAAS,GAChC,MAAM,CA6BR;AAED,wBAAgB,iCAAiC,CAC/C,WAAW,EAAE,MAAM,EACnB,UAAU,EAAE,MAAM,GAAG,SAAS,EAC9B,aAAa,EAAE,MAAM,GACpB,MAAM,CAWR;AAED,wBAAgB,4BAA4B,CAAC,IAAI,EAAE;IACjD,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,aAAa,EAAE,MAAM,CAAC;IACtB,gBAAgB,EAAE,MAAM,CAAC;IACzB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,cAAc,CAAC,EAAE,KAAK,CAAC;QACrB,QAAQ,EAAE,MAAM,CAAC;QACjB,IAAI,EAAE,MAAM,CAAC;QACb,KAAK,CAAC,EAAE,MAAM,CAAC;QACf,OAAO,CAAC,EAAE,MAAM,CAAC;KAClB,CAAC,CAAC;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB,GAAG,MAAM,CA+CT"}

package/dist/cli/commands/harnessPrompts.js

@@ -5,6 +5,9 @@ exports.buildProcessDefinitionUserPrompt = buildProcessDefinitionUserPrompt;
 exports.buildOrchestrationSystemPrompt = buildOrchestrationSystemPrompt;
 exports.buildOrchestrationBootstrapPrompt = buildOrchestrationBootstrapPrompt;
 exports.buildOrchestrationTurnPrompt = buildOrchestrationTurnPrompt;
+const context_1 = require("../../prompts/context");
+const compose_1 = require("../../prompts/compose");
+const active_1 = require("../../processLibrary/active");
 function formatHarnessCatalog(context) {
     const lines = ["Discovered harnesses:"];
     for (const harness of context.discoveredHarnesses) {
@@ -55,12 +58,13 @@ function formatHarnessAssignmentGuidance(context) {
     return [
         "Harness assignment guidance:",
         `- Only assign installed harness names. Installed harnesses: ${installedList}.`,
-        "- Default `agent`, `node`, and `orchestrator_task` work to the internal PI worker. Set `task.metadata.harness` only when a task must explicitly override that default to a specific installed harness.",
+        "- Default `agent`, `node`, and `orchestrator_task` work to the internal PI worker. Prefer `task.execution.harness` to route a task to a specific installed harness. The legacy `task.metadata.harness` field is still supported but `execution.harness` takes precedence when both are present.",
         "- Treat `pi` / `oh-my-pi` as the internal harness. Its default worker mode is native/local PI execution with isolation disabled unless the task opts into stronger guardrails.",
         "- Shell effects run through the internal PI worker even when orchestration is bound to an external CLI harness. Keep shell work on that worker by default.",
         "- Do not set `task.metadata.bashSandbox`, `task.metadata.isolated`, or `task.metadata.enableCompaction` for ordinary internal PI work. Leave them unset unless the task truly requires stronger guardrails or long-running compaction.",
         "- For risky shell or system-changing subtasks that truly need stronger guardrails, encode them explicitly in task metadata: `bashSandbox: \"secure\"` to opt into AgentSH, `isolated: true` to disable repo/global extensions and skills, and `enableCompaction: true` when a long-running internal worker needs compaction.",
         "- Treat `claude-code`, `codex`, `gemini-cli`, and other external CLIs as text-agent harnesses. Use them only when their behavior is materially better for that task.",
+        "- Tasks may include an `execution` field with `model`, `harness`, and `permissions`. `execution.model` is universal (plugins and internal harness). `execution.harness` and `execution.permissions` are only used by the internal harness (`harness:create-run`) and ignored by plugins.",
         "- External CLI harnesses do not inherit AgentSH protection for their own internal shell or tool execution. Route security-sensitive shell work through the internal PI worker instead of assuming the external harness is guarded.",
         context.selectedHarnessName
             ? `- The selected orchestration binding harness for this run is ${context.selectedHarnessName}.`
@@ -77,7 +81,26 @@ function formatSharedContext(context) {
         ...formatHarnessAssignmentGuidance(context),
     ];
 }
-function buildProcessDefinitionSystemPrompt(outputPath, context) {
+async function buildProcessDefinitionSystemPrompt(outputPath, context, interactive) {
+    // Resolve the active process-library root for the PI context
+    let processLibraryRoot;
+    let processLibraryReferenceRoot;
+    try {
+        const resolved = await (0, active_1.resolveActiveProcessLibrary)();
+        if (resolved.binding?.dir) {
+            processLibraryRoot = resolved.binding.dir;
+            processLibraryReferenceRoot = (0, active_1.getDefaultProcessLibrarySpec)().referenceRoot;
+        }
+    }
+    catch {
+        // No binding — templates will fall back to manual instructions
+    }
+    const piCtx = (0, context_1.createPiContext)({
+        interactive,
+        processLibraryRoot,
+        processLibraryReferenceRoot,
+    });
+    const composedInstructions = (0, compose_1.composeProcessCreatePrompt)(piCtx);
     return [
         "You are the babysitter harness:create-run phase 1 agent.",
         "Your job is to turn the user's intent into a concrete babysitter process definition before any run is created or bound.",
@@ -88,33 +111,21 @@ function buildProcessDefinitionSystemPrompt(outputPath, context) {
         "- Use the AskUserQuestion tool when clarification is useful. Ask focused, high-signal questions in batches when possible.",
         "- Before authoring the process in any mode, resolve the active shared process-library and conduct a real search against it. In this built-in PI path, use `babysitter_resolve_process_library`, `babysitter_search_process_library`, and `babysitter_read_process_library_file`; those tools are the internal `harness:create-run` harness surface for process-library work. Outside this built-in path, use `babysitter process-library:active --json`, then search the returned `binding.dir`. Do not skip this process-library search step.",
         "- Treat `binding.dir` as the active process-library root that must be searched first. If you need the cloned repo root itself for adjacent material, use `defaultSpec.cloneDir`. Treat `reference/` under the active root or `defaultSpec.referenceRoot` as the canonical reference area.",
-        "- In interactive mode, follow a real interview phase: inspect the repo/workspace state first, inspect the most relevant process-library references through the active binding, then ask only the next highest-signal AskUserQuestion when material ambiguity remains. Do not plan more than one interview step ahead.",
-        "- In non-interactive mode, skip user questions but still parse the request, inspect the repo/workspace structure, resolve the active process-library root, and search that active library for the most relevant specialization or methodology before authoring the process.",
         "- Research the workspace before finalizing the process. Use your available read/search/bash/write tools as needed.",
         "- Treat the provided workspace as the only relevant filesystem root unless the user explicitly points you somewhere else.",
         "- You may inspect local babysitter process references when they materially improve the process design. Prefer project `.a5c/processes/`, the active process-library root returned in `binding.dir`, the cloned repo root returned in `defaultSpec.cloneDir` when you need adjacent reference material, local plugin paths such as `plugins/babysitter/skills/babysit/process/`, repository `library/` materials, and local babysitter discover/profile CLI commands when available.",
-        "- If you use user profile context, read it through the babysitter CLI only, for example `babysitter profile:read --user --json`. Never import or call SDK profile helpers directly from generated processes or task instructions.",
         "- Use babysitter_write_process_definition to write the final JavaScript process file to the exact output path provided below.",
         "- The module must export a named `async function process(inputs, ctx)`.",
         "- The process must orchestrate the work through babysitter tasks instead of doing the main implementation directly in `process(inputs, ctx)`.",
         "- Define at least one task with `defineTask(...)`, and invoke tasks from `process(inputs, ctx)` via `await ctx.task(...)`.",
-        "- Default every task to the internal PI worker. Omit `task.metadata.harness` unless a task must explicitly override that default.",
-        "- If you define tasks with `defineTask(...)`, every returned TaskDef must include a top-level `kind` field.",
-        "- Agent tasks must use `kind: \"agent\"` with `agent: { name, prompt, outputSchema }`; shell tasks must use `kind: \"shell\"` with `shell: { command: \"...\" }`; node tasks must use `kind: \"node\"` with `node: { entry, args? }`.",
-        "- Call defined tasks with `await ctx.task(definedTask, args)`; do not invent alternate task runners.",
-        "- At least one defined task must be an `agent` task for the main work. Shell tasks are for concrete runnable commands only.",
         "- Any task passed to `ctx.task(...)` must be a DefinedTask created via `defineTask(...)`; never pass plain object task definitions or ad-hoc task objects.",
         "- Inside that named `process(inputs, ctx)` export, do not reference Node's global process object as `process.*`; use `globalThis.process` or an imported alias like `nodeProcess` instead.",
         "- If the process needs the workspace root, do not assume `ctx.workspaceDir` or `ctx.cwd` exists in runtime context. Resolve it from the module location using `import.meta.url`, for example with `path.dirname(fileURLToPath(import.meta.url))`.",
         "- Keep the generated module syntactically valid ESM. If you embed HTML/CSS/JS asset contents inside the process source, do not use raw nested template literals; prefer arrays joined with \"\\n\", String.raw, or escaped inner backticks and \\${...} sequences.",
         "- The generated process must directly execute the user's requested work. Do not generate a meta-process that writes another babysitter process unless the user explicitly asked for process authoring.",
-        "- Prefer modular, reusable process composition when possible. Reference relevant methodologies, skills, agents, or prior processes before inventing a process structure from scratch.",
-        "- Prefer processes with explicit milestones, quality gates, verification loops, and convergence on the actual user request.",
         "- After the file is written through babysitter_write_process_definition, call babysitter_report_process_definition exactly once with the final path and a concise summary.",
         "- Do not claim completion in plain text without calling babysitter_report_process_definition.",
         "- If different tasks should run on different harnesses, encode that in the process definition rather than leaving it implicit.",
-        "- Do not set `task.metadata.bashSandbox`, `task.metadata.isolated`, or `task.metadata.enableCompaction` for ordinary internal PI tasks. Leave them unset unless the task truly requires stronger guardrails or long-running compaction.",
-        "- If a task truly needs stronger internal guardrails, encode them explicitly in task metadata instead of assuming every internal task is secure or isolated by default.",
         "",
         "Process Library Activation:",
         "- You MUST call `babysitter_resolve_process_library` to bootstrap and resolve the active process-library root before authoring the process. This is non-optional.",
@@ -122,22 +133,9 @@ function buildProcessDefinitionSystemPrompt(outputPath, context) {
         "- If the cloned repo root is needed for adjacent reference material, use `defaultSpec.cloneDir`.",
         "- Use `babysitter_search_process_library` and `babysitter_read_process_library_file` to search the library. Do not skip the search step.",
         "",
-        "Interview Phase Enhancement (interactive mode):",
-        "- In interactive mode, follow a structured multi-step interview: first inspect the repo/workspace state, then search the process library for relevant specializations, methodologies, skills, and agents. Use babysitter discover commands at various stages.",
-        "- After each interview step, decide what the next highest-signal step is. Do not plan more than one step ahead. The same step type can repeat.",
-        "- Interview steps can include: research the repo, search the process library, ask the user a question via AskUserQuestion, research online, inspect local processes.",
+        "--- Shared Process Creation Instructions ---",
         "",
-        "Process Creation Guidelines:",
-        "- Before writing the process, scan methodologies and processes in the active process library to find relevant patterns to use as reference. Also scan `.a5c/processes/` for project-level reusable processes.",
-        "- Search for process files (.js), skills (SKILL.md), and agents (AGENT.md) during the process building phase. Search paths: `.a5c/processes/` (project level), `specializations/` under active root, `methodologies/` under active root.",
-        "- When creating the process file, include `@skill` and `@agent` JSDoc markers in the file header listing skills and agents relevant to this process. The SDK reads these markers to provide targeted discovery results instead of scanning all available skills.",
-        "- JSDoc marker format: `@skill <name> <path-relative-to-binding.dir>`, `@agent <name> <path-relative-to-binding.dir>`.",
-        "- Prefer modular, reusable process composition. If a generic reusable part is identified, build it modularly in `.a5c/processes/` for future composition.",
-        "- Processes should include: explicit milestones, quality gates with executable verification, iterative convergence loops, integration phases with integration tests.",
-        "- Test-driven approach where quality gate agents can use executable tools, scripts, and tests to verify accuracy and completeness.",
-        "",
-        "Non-interactive Mode Enhancement:",
-        "- In non-interactive mode, still parse the request, inspect the workspace, resolve the active process-library root, and search for the most relevant specialization or methodology before authoring. Do not skip the search step just because it is non-interactive.",
+        composedInstructions,
         "",
         `Required output path: ${outputPath}`,
         ...formatSharedContext(context),
@@ -174,7 +172,9 @@ function buildProcessDefinitionUserPrompt(userPrompt, outputPath, options) {
     lines.push("Before writing the process, you MUST resolve and search the active process-library. Use babysitter_resolve_process_library, then babysitter_search_process_library to find relevant patterns.", "The generated process must directly execute the user's requested work rather than write another babysitter process.", "Use babysitter_write_process_definition to write the file now, then call babysitter_report_process_definition exactly once.");
     return lines.join("\n");
 }
-function buildOrchestrationSystemPrompt(selectedHarnessName, context) {
+function buildOrchestrationSystemPrompt(selectedHarnessName, context, interactive) {
+    const piCtx = (0, context_1.createPiContext)({ interactive });
+    const composedInstructions = (0, compose_1.composeOrchestrationPrompt)(piCtx);
     return [
         "You are the babysitter harness:create-run phase 2 orchestration agent.",
         "Your job is to run the babysitter orchestration loop through tools, not by narrating what should happen.",
@@ -187,18 +187,16 @@ function buildOrchestrationSystemPrompt(selectedHarnessName, context) {
         "- Call babysitter_run_create to create the run if it does not already exist.",
         "- Immediately call babysitter_bind_session after run creation and before the first orchestration iteration.",
         "- Work in bounded turns. In each turn, call babysitter_run_iterate at most once unless the prompt explicitly tells you otherwise.",
-        "- When babysitter_run_iterate reports pending effects, resolve each effect through tools.",
-        "- For breakpoint effects, use AskUserQuestion in interactive mode with explicit approval options, then call babysitter_task_post_result. Never auto-approve or fabricate an approval response. In non-interactive mode, select the best option according to the user intent and current context, then call babysitter_task_post_result.",
-        "- For `shell` effects, prefer `babysitter_run_shell_effect` so the command executes on an internal PI worker that respects task metadata. Use raw bash/coding tools only when the effect payload clearly requires manual inspection or direct intervention before posting the explicit outcome with babysitter_task_post_result.",
-        "- For `agent`, `node`, and `orchestrator_task` effects, prefer babysitter_dispatch_effect_harness so the pending effect is fulfilled through the intended harness wrapper. These babysitter effect tools are the built-in internal `harness:create-run` harness surface for phase 2. If you fulfill an effect directly with your own coding tools, you must still call babysitter_task_post_result with the explicit outcome.",
         "- Do not rely on a hidden host-side effect executor. Perform or dispatch each effect intentionally based on the effect payload you received from babysitter_run_iterate.",
         "- Shell effects are first-class pending effects. Do not skip them, narrate them, or assume the host will run them for you.",
         "- When choosing how to execute pending work, respect task-level harness metadata and the installed harness catalog provided below.",
-        "- Shell effects execute on internal PI worker sessions. Respect `task.metadata.bashSandbox`, `task.metadata.isolated`, and `task.metadata.enableCompaction` when the process encoded stronger guardrails for that worker.",
-        "- Internal secure execution is available through opt-in PI worker sessions; prefer that path for shell or security-sensitive work instead of assuming an external CLI harness is guarded.",
         "- Stay in the orchestration loop until the run completes, fails, or reaches a hard limit reported by the tools.",
         "- When the run reaches a terminal state, call babysitter_finish_orchestration exactly once.",
         "",
+        "--- Shared Orchestration Instructions ---",
+        "",
+        composedInstructions,
+        "",
         "This phase is the bound orchestration phase. Preserve the hook-style loop semantics by always continuing through the babysitter tools.",
         ...formatSharedContext(context),
     ].join("\n");

package/dist/cli/commands/hookRun.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"hookRun.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/hookRun.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAUH,MAAM,WAAW,kBAAkB;IACjC,QAAQ,EAAE,MAAM,CAAC;IACjB,wGAAwG;IACxG,OAAO,EAAE,MAAM,CAAC;IAChB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,OAAO,CAAC;IACd,OAAO,CAAC,EAAE,OAAO,CAAC;CACnB;AAgID,wBAAsB,aAAa,CAAC,IAAI,EAAE,kBAAkB,GAAG,OAAO,CAAC,MAAM,CAAC,CA2E7E"}
+{"version":3,"file":"hookRun.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/hookRun.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAWH,MAAM,WAAW,kBAAkB;IACjC,QAAQ,EAAE,MAAM,CAAC;IACjB,wGAAwG;IACxG,OAAO,EAAE,MAAM,CAAC;IAChB,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,OAAO,CAAC;IACd,OAAO,CAAC,EAAE,OAAO,CAAC;CACnB;AAmJD,wBAAsB,aAAa,CAAC,IAAI,EAAE,kBAAkB,GAAG,OAAO,CAAC,MAAM,CAAC,CA0F7E"}

package/dist/cli/commands/hookRun.js

@@ -16,6 +16,7 @@ exports.handleHookRun = handleHookRun;
 const harness_1 = require("../../harness");
 const config_loader_1 = require("../../compression/config-loader");
 const density_filter_1 = require("../../compression/density-filter");
+const runLogger_1 = require("../../logging/runLogger");
 // ---------------------------------------------------------------------------
 // Stdin reader
 // ---------------------------------------------------------------------------
@@ -130,6 +131,20 @@ async function handlePreToolUse() {
 // ---------------------------------------------------------------------------
 // Main dispatcher
 // ---------------------------------------------------------------------------
+/** Fire-and-forget log to the structured run log facility. */
+function logHookEvent(hookType, message, context) {
+    void (0, runLogger_1.appendRunLog)({
+        timestamp: new Date().toISOString(),
+        level: "info",
+        type: "hook",
+        label: `hook:${hookType}`,
+        message,
+        source: "hook:run",
+        context,
+    }).catch(() => {
+        // Never let logging break hook execution.
+    });
+}
 async function handleHookRun(args) {
     const { hookType, harness, json } = args;
     if (!hookType) {
@@ -145,12 +160,17 @@ async function handleHookRun(args) {
         }
         return 1;
     }
+    logHookEvent(hookType, "Hook invoked", { harness });
     // harness-agnostic hook types — handle before adapter lookup
     if (hookType === "user-prompt-submit") {
-        return await handleUserPromptSubmit();
+        const code = await handleUserPromptSubmit();
+        logHookEvent(hookType, `Hook completed with code=${code}`);
+        return code;
     }
     if (hookType === "pre-tool-use") {
-        return await handlePreToolUse();
+        const code = await handlePreToolUse();
+        logHookEvent(hookType, `Hook completed with code=${code}`);
+        return code;
     }
     const adapter = (0, harness_1.getAdapterByName)(harness);
     if (!adapter) {
@@ -159,6 +179,7 @@ async function handleHookRun(args) {
             error: "UNSUPPORTED_HARNESS",
             message: `Unsupported harness: "${harness}". Supported: ${supported.join(", ")}`,
         };
+        logHookEvent(hookType, `Unsupported harness: ${harness}`, { error: error.error });
         if (json) {
             process.stderr.write(JSON.stringify(error, null, 2) + "\n");
         }
@@ -175,6 +196,7 @@ async function handleHookRun(args) {
             error: "UNSUPPORTED_HOOK_TYPE",
             message,
         };
+        logHookEvent(hookType, message, { error: error.error });
         if (json) {
             process.stderr.write(JSON.stringify(error, null, 2) + "\n");
         }
@@ -183,16 +205,20 @@ async function handleHookRun(args) {
         }
         return 1;
     }
+    let exitCode;
     switch (hookType) {
         case "stop":
-            return await adapter.handleStopHook(args);
+            exitCode = await adapter.handleStopHook(args);
+            break;
         case "session-start":
-            return await adapter.handleSessionStartHook(args);
+            exitCode = await adapter.handleSessionStartHook(args);
+            break;
         default: {
             const error = {
                 error: "UNKNOWN_HOOK_TYPE",
                 message: `Unknown hook type: ${hookType}. Supported: stop, session-start, user-prompt-submit`,
             };
+            logHookEvent(hookType, error.message, { error: error.error });
             if (json) {
                 process.stderr.write(JSON.stringify(error, null, 2) + "\n");
             }
@@ -202,4 +228,6 @@ async function handleHookRun(args) {
             return 1;
         }
     }
+    logHookEvent(hookType, `Hook completed with code=${exitCode}`, { harness });
+    return exitCode;
 }

package/dist/cli/commands/instructions.d.ts

@@ -0,0 +1,19 @@
+/**
+ * CLI handlers for `instructions:*` commands.
+ *
+ * Each subcommand resolves a PromptContext for the given harness,
+ * calls the appropriate composer, and outputs the result.
+ *
+ * @module cli/commands/instructions
+ */
+export interface InstructionsCommandArgs {
+    subcommand: "babysit-skill" | "process-create" | "orchestrate" | "breakpoint-handling";
+    harness: string;
+    interactive: boolean | undefined;
+    json: boolean;
+}
+/**
+ * Route and handle an `instructions:*` subcommand.
+ */
+export declare function handleInstructionsCommand(args: InstructionsCommandArgs): Promise<number>;
+//# sourceMappingURL=instructions.d.ts.map

package/dist/cli/commands/instructions.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"instructions.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/instructions.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAkBH,MAAM,WAAW,uBAAuB;IACtC,UAAU,EAAE,eAAe,GAAG,gBAAgB,GAAG,aAAa,GAAG,qBAAqB,CAAC;IACvF,OAAO,EAAE,MAAM,CAAC;IAChB,WAAW,EAAE,OAAO,GAAG,SAAS,CAAC;IACjC,IAAI,EAAE,OAAO,CAAC;CACf;AA4GD;;GAEG;AACH,wBAAsB,yBAAyB,CAC7C,IAAI,EAAE,uBAAuB,GAC5B,OAAO,CAAC,MAAM,CAAC,CAiEjB"}

package/dist/cli/commands/instructions.js

@@ -0,0 +1,158 @@
+"use strict";
+/**
+ * CLI handlers for `instructions:*` commands.
+ *
+ * Each subcommand resolves a PromptContext for the given harness,
+ * calls the appropriate composer, and outputs the result.
+ *
+ * @module cli/commands/instructions
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.handleInstructionsCommand = handleInstructionsCommand;
+const prompts_1 = require("../../prompts");
+const active_1 = require("../../processLibrary/active");
+const registry_1 = require("../../harness/registry");
+/**
+ * Legacy fallback map — used only when an adapter does not implement
+ * `getPromptContext()`.  New harnesses should add the method to their
+ * adapter instead of extending this map.
+ */
+const KNOWN_HARNESSES = {
+    "claude-code": prompts_1.createClaudeCodeContext,
+    "codex": prompts_1.createCodexContext,
+    "pi": prompts_1.createPiContext,
+};
+const COMPOSERS = {
+    "babysit-skill": {
+        fn: prompts_1.composeBabysitSkillPrompt,
+        promptType: "babysit-skill",
+        partsIncluded: [
+            "non-negotiables", "dependencies", "interview", "user-profile",
+            "process-creation", "intent-fidelity-checks", "run-creation",
+            "iteration", "effects", "breakpoint-handling", "results-posting",
+            "loop-control", "completion-proof", "task-kinds", "task-examples",
+            "quick-reference", "recovery", "process-guidelines", "critical-rules",
+            "see-also",
+        ],
+    },
+    "process-create": {
+        fn: prompts_1.composeProcessCreatePrompt,
+        promptType: "process-create",
+        partsIncluded: [
+            "interview", "user-profile", "process-creation",
+            "intent-fidelity-checks", "process-guidelines",
+            "task-kinds", "task-examples",
+        ],
+    },
+    "orchestrate": {
+        fn: prompts_1.composeOrchestrationPrompt,
+        promptType: "orchestrate",
+        partsIncluded: [
+            "run-creation", "iteration", "effects", "breakpoint-handling",
+            "results-posting", "loop-control", "completion-proof",
+            "quick-reference", "recovery", "critical-rules",
+        ],
+    },
+    "breakpoint-handling": {
+        fn: prompts_1.composeBreakpointPrompt,
+        promptType: "breakpoint-handling",
+        partsIncluded: ["breakpoint-handling", "results-posting"],
+    },
+};
+/**
+ * Resolve a PromptContext factory by harness name.
+ *
+ * Prefers the adapter's own `getPromptContext()` method when available,
+ * falling back to the legacy KNOWN_HARNESSES map for adapters that have
+ * not yet been updated.  Returns undefined for completely unknown names.
+ */
+function resolveContextFactory(harness) {
+    // Try adapter-based resolution first
+    const adapter = (0, registry_1.getAdapterByName)(harness);
+    if (adapter?.getPromptContext) {
+        return (overrides) => {
+            const base = adapter.getPromptContext({ interactive: overrides?.interactive });
+            // Merge any additional overrides beyond interactive
+            if (overrides) {
+                return { ...base, ...overrides };
+            }
+            return base;
+        };
+    }
+    // Fallback to legacy map
+    return KNOWN_HARNESSES[harness];
+}
+/**
+ * Try to resolve the active process-library root from the SDK directly.
+ * Returns the library root and reference root if a binding exists,
+ * or undefined values if resolution fails (no binding, network error, etc.).
+ */
+async function tryResolveProcessLibraryRoot() {
+    try {
+        const resolved = await (0, active_1.resolveActiveProcessLibrary)();
+        if (resolved.binding?.dir) {
+            const defaultSpec = (0, active_1.getDefaultProcessLibrarySpec)();
+            return {
+                processLibraryRoot: resolved.binding.dir,
+                processLibraryReferenceRoot: defaultSpec.referenceRoot,
+            };
+        }
+    }
+    catch {
+        // No binding exists or resolution failed — fall back to manual instructions
+    }
+    return {};
+}
+/**
+ * Route and handle an `instructions:*` subcommand.
+ */
+async function handleInstructionsCommand(args) {
+    const factory = resolveContextFactory(args.harness);
+    if (!factory) {
+        const known = Object.keys(KNOWN_HARNESSES).join(", ");
+        if (args.json) {
+            console.log(JSON.stringify({
+                error: "unknown_harness",
+                message: `Unknown harness "${args.harness}". Known harnesses: ${known}`,
+            }));
+        }
+        else {
+            console.error(`[instructions] Unknown harness "${args.harness}". Known harnesses: ${known}`);
+        }
+        return 1;
+    }
+    const composer = COMPOSERS[args.subcommand];
+    if (!composer) {
+        const known = Object.keys(COMPOSERS).join(", ");
+        if (args.json) {
+            console.log(JSON.stringify({
+                error: "unknown_subcommand",
+                message: `Unknown subcommand "${args.subcommand}". Known subcommands: ${known}`,
+            }));
+        }
+        else {
+            console.error(`[instructions] Unknown subcommand "${args.subcommand}". Known subcommands: ${known}`);
+        }
+        return 1;
+    }
+    // Resolve the active process-library root before composing the prompt
+    const libraryInfo = await tryResolveProcessLibraryRoot();
+    const ctx = factory({
+        interactive: args.interactive,
+        ...libraryInfo,
+    });
+    const content = composer.fn(ctx);
+    if (args.json) {
+        console.log(JSON.stringify({
+            harness: args.harness,
+            interactive: args.interactive,
+            promptType: composer.promptType,
+            content,
+            partsIncluded: composer.partsIncluded,
+        }, null, 2));
+    }
+    else {
+        console.log(content);
+    }
+    return 0;
+}

package/dist/cli/commands/log.d.ts

@@ -0,0 +1,22 @@
+/**
+ * log CLI command.
+ *
+ * Writes a structured log entry to the appropriate contextual log file.
+ * Intended to be called from shell hooks and scripts as a canonical way
+ * to emit structured logs without embedding JSONL formatting inline.
+ *
+ * Usage:
+ *   babysitter log --type <process|hook|cli> --message <msg> [--run-id <id>] [--label <label>] [--level <level>] [--source <src>] [--json]
+ */
+export interface LogCommandArgs {
+    logType: string;
+    message: string;
+    runId?: string;
+    processId?: string;
+    label?: string;
+    level?: string;
+    source?: string;
+    json: boolean;
+}
+export declare function handleLog(args: LogCommandArgs): Promise<number>;
+//# sourceMappingURL=log.d.ts.map

package/dist/cli/commands/log.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"log.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/log.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AASH,MAAM,WAAW,cAAc;IAC7B,OAAO,EAAE,MAAM,CAAC;IAChB,OAAO,EAAE,MAAM,CAAC;IAChB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,IAAI,EAAE,OAAO,CAAC;CACf;AAaD,wBAAsB,SAAS,CAAC,IAAI,EAAE,cAAc,GAAG,OAAO,CAAC,MAAM,CAAC,CA4ErE"}