pi-dev-flow 0.52.0 → 0.52.2

package/CHANGELOG.md

@@ -4,6 +4,18 @@ 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
+
+- **The npm listing describes the flow instead of the pipeline.** The pi.dev package gallery builds its cards from name + description + keywords — its search box matches exactly that text, and the page renders no images — so the manifest now carries a description that says what the flow *is* (gated checkpoints, self-improvement reflections, one worktree per feature, changelog + publish as part of the release) plus thirteen keywords in the shape the other pi packages use. It also ships a banner (`banner.svg`, rasterized to `banner.png`, declared as `pi.image`): the five stages with the four checkpoint words over the gates, and the release stage pointing at "registry · image · release page" — deliberately generic, because where a release ships is the project's playbook, not dev-flow's. The package now names its resource directories explicitly under `pi` rather than relying on conventional discovery (the packed tarball was loaded against the real pi binary).
+
 ## [0.52.0] - 2026-10-21
 
 ### Added

package/README.md

@@ -1,5 +1,7 @@
 # dev-flow
 
+![dev-flow stages: plan, implement, pre-release, release, done — with the four operator checkpoints and the tag that publishes to npm](banner.png)
+
 An enforced feature workflow for [Pi](https://pi.dev), shipped as a pi package. You say what you
 want; an agent builds it; **the harness — not the agent's good manners — decides whether a stage
 may advance.** One feature at a time, five stages, and four questions asked of you —
@@ -48,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/banner.svg

@@ -0,0 +1,52 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1280" height="640" viewBox="0 0 1280 640" font-family="ui-monospace, SFMono-Regular, Menlo, monospace">
+  <rect width="1280" height="640" rx="18" fill="#0f1216"/>
+  <text x="60" y="112" fill="#e6edf3" font-size="46" font-weight="700">dev-flow</text>
+  <text x="60" y="156" fill="#8b98a9" font-size="21">enforced feature workflow for pi — one flow, one branch, one worktree per feature</text>
+
+  <!-- gates (checkpoint words the operator answers in chat) -->
+  <g fill="none" stroke="#f0b429" stroke-width="2">
+    <path d="M 260 236 l 14 14 l -14 14 l -14 -14 z"/>
+    <path d="M 500 236 l 14 14 l -14 14 l -14 -14 z"/>
+    <path d="M 740 236 l 14 14 l -14 14 l -14 -14 z"/>
+    <path d="M 980 236 l 14 14 l -14 14 l -14 -14 z"/>
+  </g>
+  <g fill="#f0b429" font-size="17" text-anchor="middle">
+    <text x="260" y="212">Approve?</text>
+    <text x="500" y="212">Verified?</text>
+    <text x="740" y="212">Release?</text>
+    <text x="980" y="212">Finish?</text>
+  </g>
+
+  <!-- stages -->
+  <g font-size="19" text-anchor="middle">
+    <rect x="60" y="270" width="200" height="62" rx="10" fill="#161b22" stroke="#39424e"/>
+    <text x="160" y="308" fill="#e6edf3">plan</text>
+    <rect x="300" y="270" width="200" height="62" rx="10" fill="#161b22" stroke="#39424e"/>
+    <text x="400" y="308" fill="#e6edf3">implement</text>
+    <rect x="540" y="270" width="200" height="62" rx="10" fill="#161b22" stroke="#39424e"/>
+    <text x="640" y="308" fill="#e6edf3">pre-release</text>
+    <rect x="780" y="270" width="200" height="62" rx="10" fill="#12261f" stroke="#3fb950"/>
+    <text x="880" y="308" fill="#7ee2a3">release</text>
+    <rect x="1020" y="270" width="200" height="62" rx="10" fill="#161b22" stroke="#39424e"/>
+    <text x="1120" y="308" fill="#e6edf3">done</text>
+  </g>
+  <g stroke="#4b5563" stroke-width="2" fill="#4b5563">
+    <line x1="260" y1="301" x2="296" y2="301"/><path d="M 296 301 l -8 -5 v 10 z"/>
+    <line x1="500" y1="301" x2="536" y2="301"/><path d="M 536 301 l -8 -5 v 10 z"/>
+    <line x1="740" y1="301" x2="776" y2="301"/><path d="M 776 301 l -8 -5 v 10 z"/>
+    <line x1="980" y1="301" x2="1016" y2="301"/><path d="M 1016 301 l -8 -5 v 10 z"/>
+  </g>
+
+  <text x="60" y="404" fill="#8b98a9" font-size="18">each gate refuses until its exit criteria hold — plan, checks, deploy, changelog, manifest, tag</text>
+
+  <!-- publishing hangs off the release stage: where it goes is the project's playbook, not dev-flow's -->
+  <g font-size="17">
+    <line x1="880" y1="332" x2="880" y2="444" stroke="#3fb950" stroke-width="2"/>
+    <path d="M 880 444 l -5 -8 h 10 z" fill="#3fb950"/>
+    <rect x="620" y="452" width="600" height="82" rx="10" fill="#12261f" stroke="#3fb950"/>
+    <text x="920" y="484" fill="#7ee2a3" text-anchor="middle">the release ships: registry · image · release page</text>
+    <text x="920" y="512" fill="#8b98a9" text-anchor="middle" font-size="15">release-done refuses to close while the artifact is missing</text>
+  </g>
+
+  <text x="60" y="576" fill="#5b6672" font-size="16">.dev-flow/&lt;slug&gt;/ — plan, state, worktree · guards keep edits inside the feature</text>
+</svg>

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,10 +1,22 @@
 {
   "name": "pi-dev-flow",
-  "version": "0.52.0",
-  "description": "Enforced plan → implement → pre-release → release → done flow for Pi, as a pi package",
+  "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": [
-    "pi-package"
+    "pi-package",
+    "pi",
+    "pi-coding-agent",
+    "extension",
+    "workflow",
+    "dev-flow",
+    "spec",
+    "plan",
+    "release",
+    "semver",
+    "changelog",
+    "git-worktree",
+    "guardrails"
   ],
   "license": "MIT",
   "repository": "https://github.com/dmarchevsky/pi-dev-flow",
@@ -16,10 +28,21 @@
     "src/",
     "skills/",
     "docs/",
+    "banner.svg",
+    "banner.png",
     "README.md",
     "CHANGELOG.md",
     "LICENSE"
   ],
+  "pi": {
+    "extensions": [
+      "./extensions/dev-flow.ts"
+    ],
+    "skills": [
+      "./skills"
+    ],
+    "image": "./banner.png"
+  },
   "peerDependencies": {
     "@earendil-works/pi-ai": "*",
     "@earendil-works/pi-coding-agent": "*",