@bakers-build/conductor 0.4.1-next.318 → 0.4.1-next.431

package/dist/src/config.d.ts

@@ -15,13 +15,18 @@ export { findBbDir, resolveConfigPath, } from '@bakers-build/core';
  * ticket content into a single typed pane line overran the PTY canonical line
  * cap and truncated the dispatch command. Instead the prompt is a bounded,
  * constant-size pointer and the agent reads the ticket + all comments at run
- * start via `bakers dropsh read … --include comments`.
+ * start.
+ *
+ * That read goes through the bakers tool `bakers_ticket_read`, the same path
+ * every skill step uses, so the run does not read its ticket twice in two
+ * formats. The prompt names both transports because the agent has not loaded
+ * a skill yet; why the fallback must run alone lives in bb-workflow's tools.md.
  *
  * herdr no longer types this into the pane: the launch command goes to a file
  * that a short `sh '<file>'` line runs (BB-635), so its length is not bound
  * by the tty canonical cap (macOS 1024 B, Linux 4096 B). The prompt is still
  * kept single-line (BB-128 test).
- * Placeholders: `{identifier}`, `{state}`, `{runUuid}` ({state} falls back to
+ * Placeholders: `{identifier}`, `{state}`, `{runUuid}`, `{ticketUuid}` ({state} falls back to
  * `qualification` for unclassified tickets).
  *
  * WHERE THE PROMPT SENDS THE AGENT, and why it no longer names a WORKFLOW.md

package/dist/src/config.js

@@ -23,13 +23,18 @@ export { findBbDir, resolveConfigPath, } from '@bakers-build/core';
  * ticket content into a single typed pane line overran the PTY canonical line
  * cap and truncated the dispatch command. Instead the prompt is a bounded,
  * constant-size pointer and the agent reads the ticket + all comments at run
- * start via `bakers dropsh read … --include comments`.
+ * start.
+ *
+ * That read goes through the bakers tool `bakers_ticket_read`, the same path
+ * every skill step uses, so the run does not read its ticket twice in two
+ * formats. The prompt names both transports because the agent has not loaded
+ * a skill yet; why the fallback must run alone lives in bb-workflow's tools.md.
  *
  * herdr no longer types this into the pane: the launch command goes to a file
  * that a short `sh '<file>'` line runs (BB-635), so its length is not bound
  * by the tty canonical cap (macOS 1024 B, Linux 4096 B). The prompt is still
  * kept single-line (BB-128 test).
- * Placeholders: `{identifier}`, `{state}`, `{runUuid}` ({state} falls back to
+ * Placeholders: `{identifier}`, `{state}`, `{runUuid}`, `{ticketUuid}` ({state} falls back to
  * `qualification` for unclassified tickets).
  *
  * WHERE THE PROMPT SENDS THE AGENT, and why it no longer names a WORKFLOW.md
@@ -49,7 +54,10 @@ export { findBbDir, resolveConfigPath, } from '@bakers-build/core';
  * only against the most literal readers.
  */
 export const DEFAULT_AGENT_PROMPT = `You are working ticket {identifier}, current state: {state}. Read the ticket and all comments ` +
-    `(bakers dropsh --format md read bb_ticket/bb_ticket/$BB_ID --include comments), ` +
+    `with the bakers tool bakers_ticket_read, arguments {"ticket":"{ticketUuid}"} ` +
+    `(MCP: tool_api__bakers_ticket_read, without a connector: ` +
+    `bakers dropsh tool tool_api__bakers_ticket_read --data '{"ticket":"{ticketUuid}"}', ` +
+    `run as a Bash call of its own), ` +
     `then read ./WORKFLOW.md, load the bakers.build skill its loader names for this ticket's work type ` +
     `and state, and execute only that skill's {state} section. ` +
     `Do not start or prepare a later state. ` +

package/dist/src/core/conductor.js

@@ -151,7 +151,8 @@ function renderPrompt(template, values) {
     return template
         .replaceAll('{identifier}', values.identifier)
         .replaceAll('{state}', values.state)
-        .replaceAll('{runUuid}', values.runUuid);
+        .replaceAll('{runUuid}', values.runUuid)
+        .replaceAll('{ticketUuid}', values.ticketUuid);
 }
 export class Conductor {
     config;
@@ -1155,6 +1156,7 @@ export class Conductor {
                 identifier: t.identifier,
                 state: t.state || 'qualification',
                 runUuid: run.runUuid,
+                ticketUuid: t.uuid,
             })
             : '';
         // BB-473 review round 2 (Critical 1): pinning the run's own UUID

package/dist/src/types.d.ts

@@ -34,7 +34,7 @@ export interface ConductorSettings {
      * Agent prompt template - the bakers.build run contract, NOT project workflow. Bounds
      * the agent to exactly one state and tells it to release + stop, keeping run
      * mechanics out of the repo's WORKFLOW.md. Placeholders: `{identifier}`,
-     * `{state}`, `{runUuid}`. Defaults to `DEFAULT_AGENT_PROMPT`.
+     * `{state}`, `{runUuid}`, `{ticketUuid}`. Defaults to `DEFAULT_AGENT_PROMPT`.
      */
     prompt: string;
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bakers-build/conductor",
-  "version": "0.4.1-next.318",
+  "version": "0.4.1-next.431",
   "description": "bakers.build conductor engine + CLI: registers, claims tickets via JSON:API, dispatches agents.",
   "type": "module",
   "license": "MIT",
@@ -32,8 +32,8 @@
   "dependencies": {
     "@dropsh/plugin-jsonapi-schema": "^0.8.2",
     "@dropsh/plugin-oauth2": "^0.8.2",
-    "@bakers-build/core": "^0.4.1-next.318",
-    "@bakers-build/message": "^0.4.1-next.318",
+    "@bakers-build/core": "^0.4.1-next.431",
+    "@bakers-build/message": "^0.4.1-next.431",
     "commander": "^12.1.0",
     "dropsh": "^0.8.2"
   }