@signalridge/pi-goal 1.4.4 → 1.4.6

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # @signalridge/pi-goal
 
+## 1.4.6
+### Patch Changes
+
+- c2fd867: Treat unknown continuation-shaped user comments as ordinary input while retaining owned stale-delivery rejection and provenance guards.
+- Updated dependencies [c2fd867]
+  - @signalridge/pi-ui@1.4.0
+
+## 1.4.5
+### Patch Changes
+
+- 3364cc0: Adopt Pi 1.0.4's host-provided dependency contract: declare imported Pi and TypeBox modules as `*` peers rather than installing duplicate runtime modules, and align Pi development pins with the repository's tested 1.0.4 baseline. The wildcard identifies host module ownership; it does not promise compatibility with every Pi version.
+- 3364cc0: Keep Goal terminal tools directly declared but unavailable to nested execution, where termination is not propagated. Verify direct termination and settlement-gated queue advancement against the installed Pi 1.0.4 host and codemode.
+  
+  Translate Pi exec results into the existing gate executor contract, failing killed commands even when their code is zero and enabling successful git fingerprint inspection. Exercise real-SDK exposure, nested approval, policy, and navigation regressions on Pi 1.0.4 instead of skipping them.
+- Updated dependencies [3364cc0]
+- Updated dependencies [3364cc0]
+- Updated dependencies [3364cc0]
+  - @signalridge/pi-ui@1.3.3
+
 ## 1.4.4
 ### Patch Changes
 

package/README.md

@@ -38,7 +38,7 @@ Goal mode uses Codex-like persistence instructions and sends guarded continuatio
 
 ## Install
 
-The declared Pi peer range covers `0.84.x`–`0.87.x` and `0.99.1+` within the 0.99 minor; the current development host is `0.99.1`. See the [compatibility review](https://github.com/signalridge/pi-extensions/blob/main/docs/pi-0.99-compatibility.md) for verification details. The `agent_settled` lifecycle event this extension depends on landed in `0.80.6`.
+The current tested host is Pi `1.0.4`. Host-provided dependencies use `"*"` peers to identify module ownership, not to guarantee compatibility with every Pi version. See the [compatibility review](https://github.com/signalridge/pi-extensions/blob/main/docs/pi-1.0-compatibility.md) for verification details. The `agent_settled` lifecycle event this extension depends on landed in `0.80.6`.
 
 ```bash
 pi install npm:@signalridge/pi-goal
@@ -211,6 +211,8 @@ Elapsed time is accumulated only while status is `active`. Pause, blocked, usage
 
 ## How completion works
 
+All three terminal tools use `model-only` exposure: they remain direct model declarations with codemode `on` or `only`, but scripts and nested `ctx.executeTool()` calls cannot invoke them. Nested execution does not propagate `terminate`, so allowing it could change Goal state without ending the enclosing run. Call terminal tools directly and alone.
+
 While a goal is active, `pi-goal` injects persistence rules, a `<goal_id>` stale-turn guard, and exposes `goal_complete`. Kickoff, resume, edited-objective, system, and automatic-continuation prompts all place a trust boundary before the escaped objective, identifying it as user-provided task data; they preserve its full scope across turns and require the agent to derive concrete requirements from the objective and referenced artifacts. They treat the current worktree, command output, tests, runtime behavior, PR state, rendered artifacts, and external state as authoritative; previous conversation and plans are context rather than proof.
 
 Before completion, the shared audit tells the agent to treat completion as unproven, inspect requirement-by-requirement evidence for every named artifact, command, test, gate, invariant, and deliverable, and match each check's scope to the requirement it supports. Weak, indirect, missing, or merely consistent evidence means work must continue. This prompt wording is a behavioral guardrail, not proof by itself: `pi-goal` can enforce the current goal id and reject empty or plainly contradictory summaries, but it cannot independently prove that external work is complete.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@signalridge/pi-goal",
-  "version": "1.4.4",
+  "version": "1.4.6",
   "description": "Pi extension for autonomous /goal completion with opt-in experimental ordered queues.",
   "type": "module",
   "license": "MIT",
@@ -36,22 +36,22 @@
     "lint": "biome check ."
   },
   "peerDependencies": {
-    "@earendil-works/pi-ai": "^0.84.0 || ^0.85.0 || ^0.86.0 || ^0.87.0 || ^0.99.1",
-    "@earendil-works/pi-coding-agent": "^0.84.0 || ^0.85.0 || ^0.86.0 || ^0.87.0 || ^0.99.1",
-    "@earendil-works/pi-tui": "^0.84.0 || ^0.85.0 || ^0.86.0 || ^0.87.0 || ^0.99.1",
-    "typebox": "^1.3.11"
+    "@earendil-works/pi-ai": "*",
+    "@earendil-works/pi-coding-agent": "*",
+    "@earendil-works/pi-tui": "*",
+    "typebox": "*"
   },
   "devDependencies": {
     "@biomejs/biome": "2.5.7",
-    "@earendil-works/pi-ai": "0.99.1",
-    "@earendil-works/pi-coding-agent": "0.99.1",
-    "@earendil-works/pi-tui": "0.99.1",
-    "typebox": "1.3.11",
+    "@earendil-works/pi-ai": "1.0.4",
+    "@earendil-works/pi-coding-agent": "1.0.4",
+    "@earendil-works/pi-tui": "1.0.4",
+    "typebox": "1.3.27",
     "typescript": "7.0.2"
   },
   "dependencies": {
     "@narumitw/pi-tui-kit": "^0.54.0",
-    "@signalridge/pi-ui": "^1.3.2"
+    "@signalridge/pi-ui": "^1.4.0"
   },
   "repository": {
     "type": "git",

package/src/runtime.ts

@@ -1088,7 +1088,14 @@ export class GoalRuntime {
 
   markContinuationStarted(prompt: string) {
     const marker = extractContinuationMarker(prompt);
-    if (!marker) {
+    const owned = Boolean(
+      marker &&
+        (this.continuationDelivery?.marker === marker ||
+          this.claimedContinuationMarkers.has(marker) ||
+          this.cancelledContinuationMarkers.has(marker)),
+    );
+    if (!owned) {
+      // Marker-shaped user text is ordinary input, not proof of ownership.
       // A paused wait is not continuation work. An unrelated prompt can fail
       // before agent_settled, so its deadline must remain armed.
       if (this.activeGoal?.status === "paused" && this.activeGoal.wait) return undefined;
@@ -1098,6 +1105,7 @@ export class GoalRuntime {
       this.cancelContinuationWork();
       return undefined;
     }
+    if (!marker) return undefined;
     if (this.continuationDelivery?.marker === marker) {
       this.continuationDelivery = undefined;
       this.rememberClaimedContinuationMarker(marker);

package/src/tools.ts

@@ -59,6 +59,8 @@ const MAX_BLOCKER_EVIDENCE_LENGTH = 4_000;
 export function registerGoalTools(pi: ExtensionAPI, runtime: GoalRuntime) {
   const goalCompleteTool = defineTool({
     name: GOAL_COMPLETE_TOOL,
+    // Nested execution strips terminate; terminal transitions must be direct model calls.
+    exposure: "model-only",
     label: "Goal Complete",
     description:
       "Mark the active /goal as complete after all required work is done and verified, using the current goal_id stale-turn guard. Do not use for partial progress, blockers, failing, or unverified work.",
@@ -215,6 +217,7 @@ export function registerGoalTools(pi: ExtensionAPI, runtime: GoalRuntime) {
 
   const goalBlockedTool = defineTool({
     name: GOAL_BLOCKED_TOOL,
+    exposure: "model-only",
     label: "Goal Blocked",
     description:
       "Stop the active /goal only at a true impasse after the same blocker recurs for at least three consecutive goal turns, with the current goal_id and concrete evidence that user or external action is required. Do not use for ordinary clarification, uncertainty, or recoverable failures.",
@@ -304,6 +307,7 @@ export function registerGoalTools(pi: ExtensionAPI, runtime: GoalRuntime) {
 
   const goalWaitTool = defineTool({
     name: GOAL_WAIT_TOOL,
+    exposure: "model-only",
     label: "Goal Wait",
     description: `Keep the active /goal alive but quiet while something outside this session is expected — CI finishing, a review landing, a reply arriving. The goal pauses, stays resumable, and records why. Call it alone, after arranging whatever will wake it, or pass resume_after_ms as a safety deadline. Requests below ${MIN_GOAL_WAIT_DELAY_MS}ms are clamped to ${MIN_GOAL_WAIT_DELAY_MS}ms. Do not use it for ordinary unfinished work: if there is anything left you can do yourself, do it instead.`,
     promptSnippet: "Pause the active /goal while waiting on something outside this session",