@dreb/coding-agent 2.50.0 → 2.52.0

package/docs/extensions.md

@@ -162,24 +162,33 @@ export default function (dreb: ExtensionAPI) {
     ctx.ui.setStatus("my-ext", "Processing...");  // Footer status
     ctx.ui.setWidget("my-ext", ["Line 1", "Line 2"]);  // Widget above editor (default)
 
-    // ctx.ui.ask — a rich clarifying question with options + free text,
-    // rendered natively in the TUI and Dashboard (and over RPC). Resolves to
-    // { selected: string[], customText?: string }. Dismissing or timing out an
-    // ask stops the current agent turn and resolves undefined. This is the same
-    // primitive that powers the built-in `ask_user` tool.
-    const answer = await ctx.ui.ask(
+    // ctx.ui.ask — one or more rich clarifying questions asked together as a
+    // single wizard, rendered natively in the TUI and Dashboard (and over RPC).
+    // Resolves to { answers: Array<{ selected: string[], customText?: string,
+    // skipped?: boolean }> } with one answer per question, in order. Dismissing
+    // or timing out an ask stops the current agent turn and resolves undefined.
+    // This is the same primitive that powers the built-in `ask_user` tool.
+    const result = await ctx.ui.ask(
       {
         title: "Choose a database",
-        question: "Which persistence strategy should I use?",
-        options: ["SQLite", "PostgreSQL", "Keep the JSON file"],
-        allowFreeText: true, // default; offers a "type your own answer" field
-        multiSelect: false,  // true → checkboxes, combined with any free text
-        multiline: false,    // true → multi-line free-text area
+        questions: [
+          {
+            question: "Which persistence strategy should I use?",
+            options: ["SQLite", "PostgreSQL", "Keep the JSON file"],
+            allowFreeText: true, // default; offers a "type your own answer" field
+            multiSelect: false,  // true → checkboxes, combined with any free text
+            multiline: false,    // true → multi-line free-text area
+          },
+          { question: "Any migration constraints I should know about?", multiline: true },
+        ],
       },
       { signal, timeout: 60000 }, // both optional; absent user never deadlocks
     );
-    if (!answer) {
+    if (!result) {
       // The ask was dismissed or timed out; the current agent turn is stopping.
+    } else {
+      const [dbAnswer] = result.answers; // one entry per question, in order
+      // dbAnswer.selected / dbAnswer.customText / dbAnswer.skipped
     }
   });
 
@@ -1804,14 +1813,21 @@ const ok = await ctx.ui.confirm("Delete?", "This cannot be undone");
 // Text input
 const name = await ctx.ui.input("Name:", "placeholder");
 
-// Rich question: question text supports Markdown and options can be combined
-// with free text. Dismissal stops the current agent turn and returns undefined.
-const answer = await ctx.ui.ask({
+// Rich question wizard: one or more questions asked together, question text
+// supports Markdown and options can be combined with free text. Resolves to
+// { answers: [...] } (one per question, in order); dismissal stops the current
+// agent turn and returns undefined.
+const result = await ctx.ui.ask({
   title: "Choose a database",
-  question: "Which persistence strategy should I use?",
-  options: ["SQLite", "PostgreSQL"],
-  allowFreeText: true,
+  questions: [
+    {
+      question: "Which persistence strategy should I use?",
+      options: ["SQLite", "PostgreSQL"],
+      allowFreeText: true,
+    },
+  ],
 });
+const answer = result?.answers[0];
 
 // Multi-line editor
 const text = await ctx.ui.editor("Edit:", "prefilled text");
@@ -2156,6 +2172,7 @@ All examples in [examples/extensions/](../examples/extensions/).
 | `overlay-qa-tests.ts` | Comprehensive overlay tests | `ui.custom`, all overlay options |
 | `notify.ts` | Simple notifications | `ui.notify` |
 | `timed-confirm.ts` | Dialogs with timeout | `ui.confirm` with timeout/signal |
+| `rpc-demo.ts` | Complete RPC extension-UI demo, including the batch question wizard | `ui.select`, `ui.confirm`, `ui.input`, `ui.editor`, `ui.ask`, status/widget/title methods |
 | `mac-system-theme.ts` | Auto-switch theme | `setTheme`, `exec` |
 | **Complex Extensions** |||
 | `plan-mode/` | Full plan mode implementation | All event types, `registerCommand`, `registerShortcut`, `registerFlag`, `setStatus`, `setWidget`, `sendMessage`, `setActiveTools` |

package/docs/rpc.md

@@ -2015,7 +2015,7 @@ Expected response: `extension_ui_response` with `value` (the edited text) or `ca
 
 #### ask
 
-Ask the user a rich clarifying question with Markdown-formatted question text, optional single- or multi-select options, and an optional free-text field. This powers the built-in `ask_user` tool. `options` (2-4 nonblank strings) is optional; `allowFreeText` (default `true`), `multiSelect`, and `multiline` are optional booleans.
+Ask the user one or more rich clarifying questions together as a single wizard. Each question has Markdown-formatted question text, optional single- or multi-select options, and an optional free-text field. This powers the built-in `ask_user` tool. The request carries a `questions` array (1-10 entries); per question, `options` (2-4 nonblank strings) is optional and `allowFreeText` (default `true`), `multiSelect`, and `multiline` are optional booleans. An overall `title` defaults to `"Question"`.
 
 ```json
 {
@@ -2023,11 +2023,20 @@ Ask the user a rich clarifying question with Markdown-formatted question text, o
   "id": "uuid-5",
   "method": "ask",
   "title": "Choose a database",
-  "question": "Which persistence strategy should I use?",
-  "options": ["SQLite", "PostgreSQL", "Keep the JSON file"],
-  "allowFreeText": true,
-  "multiSelect": false,
-  "multiline": false,
+  "questions": [
+    {
+      "question": "Which persistence strategy should I use?",
+      "title": "Storage",
+      "options": ["SQLite", "PostgreSQL", "Keep the JSON file"],
+      "allowFreeText": true,
+      "multiSelect": false,
+      "multiline": false
+    },
+    {
+      "question": "Any migration constraints I should know about?",
+      "multiline": true
+    }
+  ],
   "timeout": 60000,
   "expiresAt": 1785434460000
 }
@@ -2035,12 +2044,21 @@ Ask the user a rich clarifying question with Markdown-formatted question text, o
 
 `timeout` is the original duration in milliseconds. `expiresAt` is the corresponding absolute Unix timestamp in milliseconds; Dashboard clients should use it for the visible countdown so reload, resync, or drill-in recovery does not restart the full duration.
 
-Expected response: `extension_ui_response` with `selected` (an array of strings) and optional string `customText` (the typed answer). Sending `cancelled: true`, or an empty `selected` with no nonblank `customText`, stops the current agent turn rather than continuing without an answer. A timeout has the same stop semantics. Other malformed ask responses are rejected as protocol failures.
+Expected response: `extension_ui_response` with `answers` — an array with one entry per question, in the same order. Each answer has `selected` (an array of strings) and optional string `customText` (the typed answer); an answer with an empty `selected` and no nonblank `customText` is treated as skipped (an explicit `skipped: true` is also honored). Answering submits the batch even when some questions are skipped. Sending `cancelled: true` stops the current agent turn rather than continuing; a timeout has the same stop semantics. A missing/non-array `answers`, or a malformed `selected`/`customText`, is rejected as a protocol failure.
 
 ```json
-{ "type": "extension_ui_response", "id": "uuid-5", "selected": ["SQLite"], "customText": "with WAL enabled" }
+{
+  "type": "extension_ui_response",
+  "id": "uuid-5",
+  "answers": [
+    { "selected": ["SQLite"], "customText": "with WAL enabled" },
+    { "selected": [], "skipped": true }
+  ]
+}
 ```
 
+`ask` requests are single-flight per RPC runtime. If parallel tool execution starts several calls concurrently, RPC emits only the first request and queues the rest in FIFO order. The next request is emitted only after the active request settles; a queued call that is aborted before it starts settles without emitting. Hosts therefore need to render at most one pending `ask` wizard at a time.
+
 #### notify
 
 Display a notification. Fire-and-forget, no response expected.

package/examples/extensions/rpc-demo.ts

@@ -10,6 +10,7 @@
  * - confirm() - on session_before_switch
  * - input() - via /rpc-input command
  * - editor() - via /rpc-editor command
+ * - ask() - via /rpc-ask command
  * - notify() - after each dialog completes
  * - setStatus() - on turn_start/turn_end
  * - setWidget() - on session_start
@@ -112,6 +113,34 @@ export default function (dreb: ExtensionAPI) {
 		},
 	});
 
+	// -- batch ask wizard via command --
+
+	dreb.registerCommand("rpc-ask", {
+		description: "Open a batch question wizard (demonstrates ctx.ui.ask in RPC)",
+		handler: async (_args, ctx) => {
+			const result = await ctx.ui.ask({
+				title: "Configure the RPC demo",
+				questions: [
+					{
+						question: "Which **transport checks** should run?",
+						title: "Checks",
+						options: ["Protocol", "Reconnect", "Timeout"],
+						multiSelect: true,
+						allowFreeText: true,
+					},
+					{
+						question: "Anything else the RPC host should display?",
+						title: "Notes",
+						multiline: true,
+					},
+				],
+			});
+			if (!result) return;
+			const answered = result.answers.filter((answer) => !answer.skipped).length;
+			ctx.ui.notify(`Submitted ${answered} of ${result.answers.length} answers`, "info");
+		},
+	});
+
 	// -- setEditorText via command --
 
 	dreb.registerCommand("rpc-prefill", {

package/examples/rpc-extension-ui.ts

@@ -3,15 +3,16 @@
  *
  * A lightweight TUI chat client that spawns the agent in RPC mode.
  * Demonstrates how to build a custom UI on top of the RPC protocol,
- * including handling extension UI requests (select, confirm, input, editor).
+ * including handling extension UI requests (select, confirm, input, editor, ask).
  *
  * Usage: npx tsx examples/rpc-extension-ui.ts
  *
  * Slash commands:
- *   /select  - demo select dialog
- *   /confirm - demo confirm dialog
- *   /input   - demo input dialog
- *   /editor  - demo editor dialog
+ *   /select   - demo select dialog
+ *   /confirm  - demo confirm dialog
+ *   /input    - demo input dialog
+ *   /editor   - demo editor dialog
+ *   /rpc-ask  - demo batch ask wizard from the companion extension
  */
 
 import { spawn } from "node:child_process";
@@ -39,12 +40,28 @@ const RESET = "\x1b[0m";
 // Extension UI request type (subset of rpc-types.ts)
 // ============================================================================
 
+interface AskQuestion {
+	question: string;
+	title?: string;
+	options?: string[];
+	allowFreeText?: boolean;
+	multiSelect?: boolean;
+	multiline?: boolean;
+}
+
+interface AskAnswer {
+	selected: string[];
+	customText?: string;
+	skipped?: boolean;
+}
+
 interface ExtensionUIRequest {
 	type: "extension_ui_request";
 	id: string;
 	method: string;
 	title?: string;
 	options?: string[];
+	questions?: AskQuestion[];
 	message?: string;
 	placeholder?: string;
 	prefill?: string;
@@ -239,6 +256,98 @@ class InputDialog implements Component {
 	}
 }
 
+/**
+ * Compact batch-question wizard for the RPC example. Each page accepts option
+ * numbers and optional free text separated by commas, then sends one ordered
+ * answers[] response after the final question.
+ */
+class AskDialog implements Component {
+	private readonly input = new Input();
+	private readonly answers: AskAnswer[] = [];
+	private questionIndex = 0;
+	onSubmit?: (answers: AskAnswer[]) => void;
+	onCancel?: () => void;
+	onCtrlD?: () => void;
+
+	constructor(
+		private readonly title: string,
+		private readonly questions: AskQuestion[],
+	) {
+		this.input.onSubmit = (value) => this.acceptAnswer(value);
+		this.input.onEscape = () => this.onCancel?.();
+	}
+
+	private acceptAnswer(value: string): void {
+		const question = this.questions[this.questionIndex];
+		if (!question) return;
+		const raw = value.trim();
+		const options = question.options ?? [];
+		const selected: string[] = [];
+		const customParts: string[] = [];
+
+		if (options.length === 0) {
+			if (raw) customParts.push(raw);
+		} else if (raw) {
+			for (const token of raw
+				.split(",")
+				.map((part) => part.trim())
+				.filter(Boolean)) {
+				const numericIndex = /^\d+$/.test(token) ? Number(token) - 1 : -1;
+				const matched =
+					options[numericIndex] ?? options.find((option) => option.toLowerCase() === token.toLowerCase());
+				if (matched && (question.multiSelect || selected.length === 0)) {
+					if (!selected.includes(matched)) selected.push(matched);
+				} else if (!matched && question.allowFreeText !== false) {
+					customParts.push(token);
+				}
+			}
+		}
+
+		const customText = customParts.join(", ").trim() || undefined;
+		this.answers.push(selected.length > 0 || customText ? { selected, customText } : { selected: [], skipped: true });
+		this.questionIndex++;
+		if (this.questionIndex >= this.questions.length) {
+			this.onSubmit?.(this.answers);
+			return;
+		}
+		this.input.setValue("");
+	}
+
+	handleInput(data: string): void {
+		if (matchesKey(data, "ctrl+d")) {
+			this.onCtrlD?.();
+			return;
+		}
+		this.input.handleInput(data);
+	}
+
+	invalidate(): void {
+		this.input.invalidate();
+	}
+
+	render(width: number): string[] {
+		const question = this.questions[this.questionIndex];
+		if (!question) return [`${RED}Invalid empty ask request${RESET}`];
+		const options = question.options ?? [];
+		const optionLines = options.map((option, index) => `  ${index + 1}. ${option}`);
+		const answerHint =
+			options.length === 0
+				? "Type an answer"
+				: question.multiSelect
+					? "Type option numbers separated by commas"
+					: "Type one option number";
+		const customHint = options.length > 0 && question.allowFreeText !== false ? ", plus optional text" : "";
+		return [
+			`${MAGENTA}${BOLD}${this.title} — ${this.questionIndex + 1}/${this.questions.length}${RESET}`,
+			`${BOLD}${question.title ?? question.question}${RESET}`,
+			...(question.title ? [question.question] : []),
+			...optionLines,
+			...this.input.render(width),
+			`${DIM}${answerHint}${customHint}. Enter to continue, Esc to cancel.${RESET}`,
+		];
+	}
+}
+
 // ============================================================================
 // Main
 // ============================================================================
@@ -300,6 +409,7 @@ async function main() {
 	// These helpers swap between them.
 
 	let activeDialog: Component | null = null;
+	let activeDialogId: string | null = null;
 
 	function setBottomComponent(component: Component): void {
 		root.clear();
@@ -312,6 +422,7 @@ async function main() {
 
 	function showPrompt(): void {
 		activeDialog = null;
+		activeDialogId = null;
 		setBottomComponent(promptInput);
 		tui.setFocus(promptInput.input);
 	}
@@ -374,8 +485,27 @@ async function main() {
 		tui.setFocus(dialog.inputComponent);
 	}
 
+	function showAskDialog(
+		title: string,
+		questions: AskQuestion[],
+		onDone: (answers: AskAnswer[] | undefined) => void,
+	): void {
+		const dialog = new AskDialog(title, questions);
+		dialog.onSubmit = (answers) => {
+			showPrompt();
+			onDone(answers);
+		};
+		dialog.onCancel = () => {
+			showPrompt();
+			onDone(undefined);
+		};
+		dialog.onCtrlD = exit;
+		showDialog(dialog);
+	}
+
 	function handleExtensionUI(req: ExtensionUIRequest): void {
 		const { id, method } = req;
+		if (["select", "confirm", "input", "editor", "ask"].includes(method)) activeDialogId = id;
 
 		switch (method) {
 			// Dialog methods: replace prompt with interactive component
@@ -422,6 +552,23 @@ async function main() {
 				break;
 			}
 
+			case "ask": {
+				const questions = req.questions ?? [];
+				if (questions.length === 0) {
+					showPrompt();
+					send({ type: "extension_ui_response", id, cancelled: true });
+					break;
+				}
+				showAskDialog(req.title ?? "Question", questions, (answers) => {
+					if (answers) {
+						send({ type: "extension_ui_response", id, answers });
+					} else {
+						send({ type: "extension_ui_response", id, cancelled: true });
+					}
+				});
+				break;
+			}
+
 			// Fire-and-forget methods: display as notification
 			case "notify": {
 				const notifyType = (req.notifyType as string) ?? "info";
@@ -450,6 +597,10 @@ async function main() {
 				break;
 			}
 
+			case "setTitle":
+				terminal.setTitle(req.title ?? "");
+				break;
+
 			case "set_editor_text":
 				promptInput.input.setValue((req.text as string) ?? "");
 				tui.requestRender();
@@ -535,6 +686,11 @@ async function main() {
 			return;
 		}
 
+		if (data.type === "extension_ui_response_handled") {
+			if (data.id === activeDialogId) showPrompt();
+			return;
+		}
+
 		if (data.type === "message_update") {
 			const evt = data.assistantMessageEvent as Record<string, unknown> | undefined;
 			if (evt?.type === "text_delta") {
@@ -620,7 +776,7 @@ async function main() {
 
 	outputLog.append(`${BOLD}RPC Chat${RESET}`);
 	outputLog.append(`${DIM}Type a message and press Enter. Esc to abort or exit. Ctrl+D to quit.${RESET}`);
-	outputLog.append(`${DIM}Slash commands: /select /confirm /input /editor${RESET}`);
+	outputLog.append(`${DIM}Slash commands: /select /confirm /input /editor /rpc-ask${RESET}`);
 	outputLog.append("");
 
 	tui.start();

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@dreb/coding-agent",
-	"version": "2.50.0",
+	"version": "2.52.0",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"type": "module",
 	"drebConfig": {

package/skills/mach6-implement/SKILL.md

@@ -18,7 +18,7 @@ This skill has two modes:
 2. **No `#N` in comment bodies** — Use "finding 3", "item 3" etc. instead.
 3. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets.
 4. **Task tracking** — Use the `tasks_update` tool to show progress.
-5. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
+5. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
 
 ## Parent ownership and the formal-review checkpoint
 

package/skills/mach6-issue/SKILL.md

@@ -16,7 +16,7 @@ argument-hint: "[issue-number | description]"
 4. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets (.env, credentials, tokens, keys).
 5. **Task tracking** — Use the `tasks_update` tool to show progress through multi-step commands.
 6. **Project conventions** — Check for CLAUDE.md, AGENTS.md, .dreb/CONTEXT.md, and CONTRIBUTING.md before planning or implementing.
-7. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
+7. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
 
 ## Determine Mode
 
@@ -76,7 +76,7 @@ Present to the user:
 Post as an issue comment:
 
 ```bash
-GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"
+GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"
 cat > "$GH_BODY" << 'MACH6_EOF'
 <!-- mach6-assessment -->
 ## Issue Assessment
@@ -128,7 +128,7 @@ Present the draft to the user for approval.
 ### Step 3: Create the issue
 
 ```bash
-GH_BODY="$(mktemp /tmp/gh-body.XXXXXX.md)"
+GH_BODY="$(mktemp /tmp/gh-body.$$.XXXXXXXX)"
 cat > "$GH_BODY" << 'MACH6_EOF'
 <body>
 MACH6_EOF

package/skills/mach6-plan/SKILL.md

@@ -18,7 +18,7 @@ This command is strictly for **planning**. Do NOT implement any code changes —
 4. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets.
 5. **Task tracking** — Use the `tasks_update` tool to show progress through multi-step commands.
 6. **Project conventions** — Check for CLAUDE.md, AGENTS.md, .dreb/CONTEXT.md, and CONTRIBUTING.md before planning.
-7. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
+7. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
 
 ## Step 1: Set up task tracking
 
@@ -98,7 +98,7 @@ git commit --allow-empty -m "chore: open PR for issue <N>"
 git push -u origin feature/issue-<N>-<slug>
 
 # Open draft PR
-GH_BODY="$(mktemp /tmp/gh-body.XXXXXX.md)"
+GH_BODY="$(mktemp /tmp/gh-body.$$.XXXXXXXX)"
 cat > "$GH_BODY" << 'MACH6_EOF'
 Closes #<N>
 
@@ -114,7 +114,7 @@ Update task: branch → completed, post → in_progress.
 ## Step 7: Post plan to PR
 
 ```bash
-GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"
+GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"
 cat > "$GH_BODY" << 'MACH6_EOF'
 <!-- mach6-plan -->
 ## Implementation Plan

package/skills/mach6-publish/SKILL.md

@@ -14,7 +14,7 @@ argument-hint: "<pr-number>"
 2. **No `#N` in comment bodies** — Use "finding 3", "item 3" etc. instead.
 3. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets.
 4. **Task tracking** — Use the `tasks_update` tool to show progress.
-5. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
+5. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
 
 ## Step 1: Set up task tracking
 
@@ -180,7 +180,7 @@ git push --tags
 
 3. Present draft to user for approval, then create:
    ```bash
-   GH_NOTES="$(mktemp /tmp/gh-release-notes.XXXXXX.md)"
+   GH_NOTES="$(mktemp /tmp/gh-release-notes.$$.XXXXXXXX)"
    cat > "$GH_NOTES" << 'MACH6_EOF'
    <release-notes>
    MACH6_EOF

package/skills/mach6-push/SKILL.md

@@ -15,7 +15,7 @@ argument-hint: "[commit message]"
 3. **No `#N` in comment bodies** — Use "finding 3", "item 3", "stage 2" etc. instead.
 4. **Safe git** — Never use `git add -A` or `git add .`. Stage files by name. Never stage secrets (.env, credentials, tokens, keys).
 5. **Task tracking** — Use the `tasks_update` tool to show progress.
-6. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
+6. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
 7. **Stop after durable progress** — The commit, push, and GitHub progress comment are the accountability and recovery boundary. Do not invoke `mach6-review` or continue into a formal review cycle. Only the user may start formal review; offer it with `suggest_next` and stop.
 
 ## Step 1: Set up task tracking
@@ -82,7 +82,7 @@ If session context points to an issue but a PR also exists on the current branch
 
 Post a progress comment:
 ```bash
-GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"
+GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"
 cat > "$GH_BODY" << 'MACH6_EOF'
 <!-- mach6-progress -->
 ## Progress Update

package/skills/mach6-review/SKILL.md

@@ -14,7 +14,7 @@ argument-hint: "<pr-number> [code|errors|tests|completeness|simplify]"
 2. **HTML markers** — Use `<!-- mach6-review -->` and `<!-- mach6-assessment -->` as the first line of comment bodies.
 3. **No `#N` in comment bodies** — Use "finding 3", "item 3", "stage 2" etc. instead.
 4. **Task tracking** — Use the `tasks_update` tool to show progress.
-5. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
+5. **Non-interactive `gh`** — Set `GH_PAGER=cat` and `GH_EDITOR=cat` before all `gh` commands to prevent interactive prompts from hanging the agent. Use `--body-file` instead of inline `--body` for all `gh pr comment`, `gh pr create`, and `gh issue create` calls to avoid shell interpretation of backticks. Write each body to a **unique per-invocation temp file** via `mktemp` (e.g. `GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"`) — never a fixed path like `/tmp/gh-comment.md`, which concurrent mach6 sessions on the same machine would clobber, cross-posting one session's body to another's PR/issue.
 6. **User-controlled checkpoint** — This formal multi-agent review runs only from an explicit user request, either through its slash command or a direct instruction to an agent to invoke it. An agent may invoke it in response to that request; otherwise agents must only offer it with `suggest_next`, never invoke it autonomously or start a review-fix-review loop.
 7. **Review durable work only** — Do not launch formal review agents against uncommitted or unpushed work. The commit, push, and GitHub progress comment are the accountability and recovery boundary.
 
@@ -126,7 +126,7 @@ Update task: review → completed, post-review → in_progress.
 Compile all findings from all agents into a single structured comment:
 
 ```bash
-GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"
+GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"
 cat > "$GH_BODY" << 'MACH6_EOF'
 <!-- mach6-review -->
 ## Code Review
@@ -195,7 +195,7 @@ Update task: assess → completed, post-assess → in_progress.
 ## Step 7: Post assessment
 
 ```bash
-GH_BODY="$(mktemp /tmp/gh-comment.XXXXXX.md)"
+GH_BODY="$(mktemp /tmp/gh-comment.$$.XXXXXXXX)"
 cat > "$GH_BODY" << 'MACH6_EOF'
 <!-- mach6-assessment -->
 ## Review Assessment
@@ -229,7 +229,7 @@ Present to the user:
 
 If any findings were classified as **deferred**, ask the user if they want to create issues for them:
 ```bash
-GH_BODY="$(mktemp /tmp/gh-body.XXXXXX.md)"
+GH_BODY="$(mktemp /tmp/gh-body.$$.XXXXXXXX)"
 cat > "$GH_BODY" << 'MACH6_EOF'
 <body referencing PR and finding>
 MACH6_EOF

package/dist/modes/interactive/components/ask-user.d.ts

@@ -1,59 +0,0 @@
-/**
- * ask_user question component.
- *
- * Renders a clarifying question with optional single- or multi-select options
- * and an optional free-text field, matching the approved cross-surface design.
- *
- * Keyboard model (settled in issue 396 discussion):
- *   ↑/↓        move a single cursor through the options and, last, the free-text field
- *   Space      toggle the highlighted checkbox (multi-select only)
- *   Enter      single-select: pick the highlighted option and submit;
- *              free-text field: submit the typed answer;
- *              multi-select: submit all checked options plus any free text
- *   Shift+Enter insert a newline in the multiline free-text field
- *   Esc        stop the current agent turn
- */
-import { Container, type Focusable, type TUI } from "@dreb/tui";
-import type { AskRequest, AskResult } from "../../../core/extensions/types.js";
-export interface AskUserComponentOptions {
-    tui?: TUI;
-    timeout?: number;
-}
-export declare class AskUserComponent extends Container implements Focusable {
-    private options;
-    private allowFreeText;
-    private multiSelect;
-    private multiline;
-    /** Cursor over [options..., freeTextRow?]. */
-    private cursorIndex;
-    /** Checkbox state for multi-select, aligned to options. */
-    private checked;
-    private onSubmitCallback;
-    private onStopCallback;
-    private titleText;
-    private baseTitle;
-    private optionsContainer;
-    private fieldLabel;
-    private input;
-    private editor;
-    private countdown;
-    private submitted;
-    private _focused;
-    get focused(): boolean;
-    set focused(value: boolean);
-    private get freeTextRow();
-    private get lastRow();
-    private cursorOnField;
-    constructor(request: AskRequest, onSubmit: (result: AskResult) => void, onStop: () => void, opts?: AskUserComponentOptions);
-    private buildHint;
-    private renderRows;
-    private syncFieldFocus;
-    private moveCursor;
-    private fieldText;
-    private currentAnswer;
-    private submit;
-    private stop;
-    handleInput(keyData: string): void;
-    dispose(): void;
-}
-//# sourceMappingURL=ask-user.d.ts.map