pi-dev-flow 0.52.1 → 0.52.2

package/CHANGELOG.md

@@ -4,6 +4,12 @@ Format: newest first. `Unreleased` collects what's merged but not yet tagged.
 
 ## [Unreleased]
 
+## [0.52.2] - 2026-10-21
+
+### Fixed
+
+- **The `[dev-flow]` stage line printed twice per prompt.** One package reaches one runtime twice as fast as you install it — a project `git:` pin beside the global `npm:` package, or a dogfood checkout whose `.pi/extensions` pointer sits next to the installed copy — and pi dedupes extensions by **file path**, not by package, so both copies register and both answers were appended: two `[dev-flow]` lines in every prompt, in the logs and to the model. The stage-context handler now claims the run: pi builds **one ctx object per `before_agent_start`** and hands it to every registered handler, so the first pass stamps it and a rival copy answers nothing. The claim is per run rather than per process on purpose — pi-web hosts many sessions inside one Node process (dev-flow's own session map is keyed by session id for that reason), and a process-wide "only the first copy registers" rule would leave every later session without guards, without the `flow` tool and without stage context. Each copy still registers its guards, tool and command: their verdicts are identical, and pi exposes no runtime identity during load to dedupe them against.
+
 ## [0.52.1] - 2026-10-21
 
 ### Changed

package/README.md

@@ -50,7 +50,9 @@ pi install ./pi-dev-flow                          # or a local checkout
 ```
 
 Later releases arrive with `pi update --extensions` (an npm install reconciles to the newest version);
-then `/reload` — a running session keeps the code it loaded at startup.
+then `/reload` — a running session keeps the code it loaded at startup. Two sources at once (a project
+`git:` pin beside the global `npm:` package) load two copies — pi dedupes extensions by path, not by
+package — so keep the one you actually update from.
 
 Then, once per project repo, `/flow init`. It reads the repo (default branch and forge from git,
 package manager, test/build/run conventions, version manifest) and writes **`.dev-flow/project.md`

package/extensions/dev-flow.ts

@@ -194,6 +194,9 @@ const compacting = new Set<string>();
 /** Seam for the takeover's summarize call (pi's own compact()); tests replace `.run` — mutable object stands in for ESM mocking. */
 export const compactionTakeover: { run: typeof compact } = { run: compact };
 
+/** Marks the before_agent_start pass that already wrote this run's [dev-flow] line — see the claim in that handler. */
+const CONTEXT_EMITTED = Symbol.for("pi-dev-flow.context-emitted");
+
 function unfinishedStates(root: string): FlowState[] {
 	if (!existsSync(dfDir(root))) return [];
 	return readdirSync(dfDir(root), { withFileTypes: true })
@@ -1464,6 +1467,14 @@ export default function devFlow(pi: ExtensionAPI) {
 	});
 
 	pi.on("before_agent_start", async (_event, ctx) => {
+		// One [dev-flow] line per run, whatever number of copies of this package are installed.
+		// The same package reaches one runtime twice all the time (a project pin beside the npm install,
+		// or this checkout's .pi/extensions pointer beside it) and pi dedupes extensions by file path
+		// only, so both copies answer and the line lands twice in the prompt. pi hands every handler of
+		// a run the same ctx object, so the first pass claims the run and the rival stays silent.
+		const run = ctx as unknown as Record<symbol, boolean | undefined>;
+		if (run[CONTEXT_EMITTED]) return undefined;
+		run[CONTEXT_EMITTED] = true;
 		if (!existsSync(dfDir(ctx.cwd))) return undefined;
 		const cfg = loadProject(dfDir(ctx.cwd)).cfg;
 		const state = boundFeature(ctx.cwd, sessionKey(ctx));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-dev-flow",
-  "version": "0.52.1",
+  "version": "0.52.2",
   "description": "Enforced feature workflow for Pi: plan → implement → pre-release → release, gated checkpoints, self-improvement reflections, one git worktree per feature, changelog + publish as part of the release",
   "type": "module",
   "keywords": [