@jwilger/pi-development-system 0.12.0 → 0.13.0

package/agents/implementer.md

@@ -32,7 +32,7 @@ You are an implementer. You receive exactly one task record and nothing else: do
 - Touch only the files the task lists. If the task needs another file, a new dependency, or a design choice, call agent_pause naming what you need. Do not invent policy to make something pass.
 - Never weaken, skip or delete a test to get green, and never add a lint suppression without a stated reason.
 - Do not commit, push or run git history commands; the coordinator delivers.
-- Follow the repo's skills and `principles/NON-NEGOTIABLES.md`; they are loaded in your context.
+- You start with no skills or repository rules loaded and no devsys guards running in your session: the rules in this list are the whole contract. If the task conflicts with one, stop and ask.
 
 ## Finish
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jwilger/pi-development-system",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "description": "A pi extension package representing a seasoned approach to software development using a full AI SDLC.",
   "keywords": [
     "pi-package"

package/skills/delegation/SKILL.md

@@ -28,7 +28,7 @@ implementer and reviewer work. It returns a slot, a thinking level and, when one
 resolves on this machine, a model. Pass them through:
 
 ```text
-agent_spawn({path: "/root/add-flag", type: "implementer", task: "...",
+agent_spawn({path: "/impl-add-flag", type: "implementer", task: "...",
              model: "<from route>", thinkingLevel: "<from route>"})
 ```
 
@@ -48,8 +48,10 @@ you deliver after review.
 
 ## The reviewer is always fresh
 
-A reviewer that watched the work being written shares its blind spots. Spawn it
-with `/root/<name>` paths that do not inherit your reasoning, give it the diff
+A reviewer that watched the work being written shares its blind spots. A path
+under `/root/...` inherits your whole conversation, so spawn reviewers and
+implementers at a top-level independent path (one segment, for example
+`/review-1` or `/impl-add-flag`): independent roots start with no history. Give it the diff
 range and the packet format (`agents/reviewer.md`), and never tell it what you
 concluded. Fix every blocking and should-fix finding, then ask for a new round.
 

package/src/subagents/orch/manager.ts

@@ -730,6 +730,8 @@ export class ThreadManager {
       ...record.view,
       sessionFile: record.driver ? record.driver.sessionFile : record.view.sessionFile,
     });
+    // devsys: show per-spawn pins so agent_status reports what the thread was told to run on.
+    if (record.definition?.spawnOverrides) view.pinned = { ...record.definition.spawnOverrides };
     if (record.liveInputTokens) view.inputTokens = (view.inputTokens ?? 0) + record.liveInputTokens;
     if (record.liveOutputTokens)
       view.outputTokens = (view.outputTokens ?? 0) + record.liveOutputTokens;

package/src/subagents/orch/runtime.ts

@@ -200,7 +200,9 @@ export function createDriverFactory(
       ? resolved.get(`${ctx.sessionManager.getSessionId()}:${parentPath}`)
       : undefined;
     const mode = getModelSelection();
-    const preferences = mode === "use-current" ? undefined : getModelPreferences(type);
+    // devsys: an explicit per-spawn model pin bypasses preference/scope policy (also on resume).
+    const pinned = type.spawnOverrides?.model !== undefined;
+    const preferences = mode === "use-current" || pinned ? undefined : getModelPreferences(type);
     let provider = parent?.provider ?? ctx.model?.provider;
     let id = parent?.id ?? ctx.model?.id;
     if (mode === "use-current") {

package/src/subagents/types.ts

@@ -68,6 +68,8 @@ export interface ThreadView {
   inputTokens?: number;
   /** Cumulative output tokens. Live views include the in-progress message. */
   outputTokens?: number;
+  /** devsys: per-spawn model/thinkingLevel pin requested through agent_spawn, when any. */
+  pinned?: SpawnOverrides;
 }
 export type DriverEvent =
   | { kind: "activity" | "error"; text: string }