pi-fovea 0.29.0 → 0.29.2

package/README.md

@@ -258,7 +258,11 @@ is absorbed silently, so broad umbrella coverage does not become broad model
 context. Set `sync.scope` to `"repository"` to restore root-wide steering.
 
 A meaningful current, mixed, or unattributed change inside the attention scope
-can still ship post-turn with `deliverAs: "steer"` and `triggerTurn`. A relevant
+can still ship post-turn with `deliverAs: "steer"` and `triggerTurn`. If
+[pi-queue-steer](https://github.com/monotykamary/pi-queue-steer-factory) still
+holds rows (`globalThis.__tmustierPiQueueSteerState.pending > 0`), that same
+notice rides `nextTurn` instead so a queued user row stays first in Pi's native
+lane and Fovea cannot `triggerTurn` ahead of it. A relevant
 change attributed solely to another Fovea-enabled session is queued for the
 next user prompt instead; it never restarts an idle agent. The compact update
 names changed files, route deltas, and newly relevant files. Shell commands,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-fovea",
-  "version": "0.29.0",
+  "version": "0.29.2",
   "description": "Token-budgeted repo mapping for agent sessions: foveated heat diffusion over a cross-language code graph, with progressive disclosure.",
   "type": "module",
   "license": "MIT",
@@ -71,8 +71,8 @@
     "test:smoke": "vitest run tests/startup.test.ts tests/config.test.ts tests/settings.test.ts tests/substrate.test.ts tests/scan.test.ts tests/extract.test.ts tests/join.test.ts tests/heat.test.ts tests/nuclei.test.ts tests/render.test.ts"
   },
   "devDependencies": {
-    "@earendil-works/pi-coding-agent": "0.85.1",
-    "@earendil-works/pi-tui": "0.85.1",
+    "@earendil-works/pi-coding-agent": "0.86.0",
+    "@earendil-works/pi-tui": "0.86.0",
     "@types/node": "^22.0.0",
     "esbuild": "^0.28.1",
     "knip": "^6.32.0",

package/skills/pi-fovea/SKILL.md

@@ -49,7 +49,7 @@ See README's “Many projects, one conversation” and `docs/workspace.md`.
 
 ## Turn sync
 
-Before an agent starts, pi-fovea establishes its baseline or injects relevant out-of-band semantic drift into that run. After each assistant turn it compares again. The default `sync.scope: "session"` indexes the whole root but steers only for top-level directories/root files this conversation entered through path-bearing tools or focus. Sibling-directory drift advances the index and baseline silently. Current, mixed, and unattributed changes in scope may trigger a continuation; changes owned solely by another Fovea session wait for the next user prompt and cannot restart an idle agent. Comment- and formatting-only edits stay silent. Set `sync.scope: "repository"` only when root-wide steering is intentional.
+Before an agent starts, pi-fovea establishes its baseline or injects relevant out-of-band semantic drift into that run. After each assistant turn it compares again. The default `sync.scope: "session"` indexes the whole root but steers only for top-level directories/root files this conversation entered through path-bearing tools or focus. Sibling-directory drift advances the index and baseline silently. Current, mixed, and unattributed changes in scope may trigger a continuation; parked pi-queue-steer rows (`pending > 0` on its globalThis mirror) and changes owned solely by another Fovea session wait for the next user prompt and cannot restart an idle agent. Comment- and formatting-only edits stay silent. Set `sync.scope: "repository"` only when root-wide steering is intentional.
 
 Sync is **mutation-path agnostic**: pi's edit/write tools, a pi-fabric `fabric_exec` program's inner `pi.edit`, a bash heredoc, a subagent, or an editor save outside the session all register identically. Content hashes are the source of truth; tool events establish attention but are not the drift oracle. Successful edit/write events additionally record exact hash transitions so sync can label current-session, other-Fovea-session, and mixed provenance; uninstrumented mutation paths remain explicitly unattributed. In repos with no `.git` directory content drift is also the only change signal — do not fall back to `git status` assumptions.
 

package/src/index.ts

@@ -92,6 +92,21 @@ const text = (s: string) => ({ type: "text" as const, text: s });
 const syncRuns = (config: FoveaConfig): boolean => config.sync.mode !== "disabled";
 const syncDisplays = (config: FoveaConfig): boolean => config.sync.mode === "enabled";
 
+/** pi-queue-steer mirrors `{ pending, paused, blocked }` on globalThis so
+ *  peers can yield the native steer/follow-up lane without a package
+ *  dependency or listener-order race (same snapshot pi-ledger reads). */
+const queueSteerPending = (): number => {
+  const state = (globalThis as { __tmustierPiQueueSteerState?: { pending?: unknown } }).__tmustierPiQueueSteerState;
+  return typeof state?.pending === "number" && Number.isFinite(state.pending) ? Math.max(0, state.pending) : 0;
+};
+
+/** Parked queue-steer rows own the next native slot. Do not `triggerTurn` a
+ *  Fovea steer in front of them — ride `nextTurn` until that backlog drains. */
+const syncDelivery = (nextPrompt: boolean): { deliverAs: "nextTurn" } | { deliverAs: "steer"; triggerTurn: true } =>
+  nextPrompt || queueSteerPending() > 0
+    ? { deliverAs: "nextTurn" }
+    : { deliverAs: "steer", triggerTurn: true };
+
 const NODE_KINDS = new Set<NodeKind>([
   "function", "method", "class", "interface", "type", "field", "decl", "file", "anchor",
 ]);
@@ -461,8 +476,7 @@ export default function fovea(pi: ExtensionAPI) {
     turnFiles = [];
     for (const notice of await pollRoots(ctx, "cheap", files)) {
       pi.sendMessage({ customType: "pi-fovea-sync", content: notice.content,
-        display: notice.display, details: notice.details }, notice.nextPrompt
-        ? { deliverAs: "nextTurn" } : { deliverAs: "steer", triggerTurn: true });
+        display: notice.display, details: notice.details }, syncDelivery(notice.nextPrompt));
     }
   });