@oisin-ee/pi-dogsled 0.13.0 → 0.13.1

package/README.md

@@ -188,7 +188,7 @@ A reader claims records with `inbox claim`, which is a lease. A claimed record i
 Readers:
 
 - **Pi:** the extension watches its inbox file, injects each batch as one `dogsled` message (`steer` while the agent runs, a new turn when it is idle), and acknowledges it when Pi has written the message to the session.
-- **Claude Code and Codex:** `dogsled hook inbox --harness claude|codex --event Stop|UserPromptSubmit`, registered by the plugin. The first hook run registers the reader. At `Stop`, records continue the turn as `{"decision":"block","reason":…}`; at `UserPromptSubmit`, they go beside the user's text as `additionalContext`. Records printed are acknowledged. An empty inbox prints nothing, so a stop ends as usual.
+- **Claude Code and Codex:** `dogsled hook inbox --harness claude|codex --event Stop|UserPromptSubmit`, registered by the plugin. The first hook run registers the reader. At `Stop`, records continue the turn as `{"decision":"block","reason":…}`; at `UserPromptSubmit`, they go beside the user's text as `additionalContext`. Records printed are acknowledged. At `Stop`, the same response also includes a new reminder about finished children with work to land. It prints nothing when neither is pending.
 
 A hook runs only when its harness acts, so an idle Claude Code or Codex agent sees a record at its next prompt or stop. Pi has no such delay.
 
@@ -446,12 +446,26 @@ The removed lead ledger and event log are not read or migrated.
 
 ## Prompt context and integrations
 
-`dogsled hook context --harness claude|codex|pi` formats the same text as `status --brief`.
+`dogsled hook context --harness claude|codex|pi` leads with your own children and jobs, then shows the fleet totals from `status --brief`.
+The owner summary separates work to land, attention, idle, done, running, and queued work.
+The `To land:` line names finished children with unmerged commits or uncommitted changes.
 Claude Code and Codex register `SessionStart` and `UserPromptSubmit` context hooks, and `UserPromptSubmit` and `Stop` inbox hooks (see [Inbox](#inbox)), in `plugins/dogsled`.
 Each registration supplies `--event`. The default context event is `UserPromptSubmit`.
 The CLI never reads stdin. Claude Code and Codex receive `hookSpecificOutput` JSON with `hookEventName` and `additionalContext`.
 Pi receives plain text through its `before_agent_start` extension. All three use the same snapshot reader and formatter.
 
+Before an orchestrator stops, the stop gate checks its own TO LAND children.
+Pi calls `dogsled hook gate` from `agent_before_settle` and adds a visible message that continues the run.
+Claude Code and Codex include the reminder in their existing `Stop` inbox response.
+The reminder requests a review, a commit from dirty children, integration, or an explicit blocker or deferral.
+It never commits, merges, closes, or discards work itself. Clean readers and working children do not trigger it.
+
+The gate records each set of child item IDs, commit counts, and dirty states in `gate.json`.
+It continues once per distinct set, across process restarts. Row order and idle/done transitions do not cause another reminder.
+New states can trigger another reminder. Closing all owner items clears the history.
+Pi skips the gate on errors, aborts, and boundaries that already request continuation.
+This is a bounded reminder, not a permanent prohibition on stopping.
+
 Without `HERDR_ENV`, service snapshots, or a usable binary, the hooks add nothing.
 A hook has a five-second command budget. Hook failures exit successfully without output.
 Plugin commands end with `|| true`. Pi also leaves the prompt unchanged if the binary fails.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oisin-ee/pi-dogsled",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "description": "Pi extension for dogsled: the board, the /dogsled panel, the inbox reader, and the dogsled tools. Needs the dogsled binary of the same version.",
   "type": "module",
   "license": "MIT",

package/pi/index.ts

@@ -240,12 +240,23 @@ export default function dogsled(pi: ExtensionAPI) {
 	// A delivered message is in the transcript once Pi ends it: only then is it acknowledged.
 	pi.on("message_end", async event => { await inbox.ended(event.message); });
 	pi.on("agent_settled", () => { inbox.settled(); });
+	pi.on("agent_before_settle", async event => {
+		if (!owner || event.outcome !== "completed" || !event.context.canContinue || event.continue) return;
+		// The Rust gate owns selection and durable deduplication across all harnesses.
+		const result = await pi.exec(binary, ["hook", "gate"], { timeout: 6_000 });
+		if (result.code !== 0) throw new Error(`dogsled stop gate failed: ${result.stderr.trim() || `exit ${result.code}`}`);
+		if (!result.stdout.trim()) return;
+		return {
+			entries: [...event.entries, { type: "custom_message" as const, customType: MESSAGE_TYPE, content: result.stdout.trim(), display: true }],
+			continue: true,
+		};
+	});
 	pi.on("before_agent_start", async (event) => {
 		// Context is optional, including when the binary is absent or fails.
 		try {
 			const result = await pi.exec(binary, ["hook", "context", "--harness", "pi"], { timeout: 6_000 });
 			if (result.code !== 0 || !result.stdout.trim()) return;
-			return { systemPrompt: `${event.systemPrompt}\n\n## Host status\n${result.stdout.trim()}\n` };
+			return { systemPrompt: `${event.systemPrompt}\n\n## Your work and fleet status\n${result.stdout.trim()}\n` };
 		} catch {
 			return;
 		}

package/plugins/dogsled/skills/dogsled/SKILL.md

@@ -18,7 +18,10 @@ dogsled read NAME_OR_PANE [--host H]
 ```
 
 The board groups what you started by what you must do: TO LAND (a finished child with commits), ATTENTION (blocked, stalled, failed), RUNNING, and WAITING (queued for a host). Each agent row shows its harness and model; each job row its command.
-Your prompt context carries host status and a `To land:` line. In Pi, the board widget above the editor shows host meters, the current task, and grouped agents and jobs. Alt+W or `/work` expands it in place. Work inspection stays inline, not in a popup. Todos follow the Pi branch; agents and jobs follow the owner pane. `/dogsled` retains host, profile, and inbox administration.
+Your prompt context leads with your own children and jobs, then a `To land:` line, then fleet status.
+Before you stop, a gate reminds you once per distinct set of finished children with unmerged commits or uncommitted changes.
+Read each result. Ask dirty children to finish and commit. Integrate approved work, or report its blocker or deferral.
+Never discard dirty work to satisfy the reminder. The gate does not close or merge anything. In Pi, the board widget above the editor shows host meters, the current task, and grouped agents and jobs. Alt+W or `/work` expands it in place. Work inspection stays inline, not in a popup. Todos follow the Pi branch; agents and jobs follow the owner pane. `/dogsled` retains host, profile, and inbox administration.
 
 ## Delegate