@aliou/pi-dev-kit 0.7.0 → 0.7.2

package/README.md

@@ -1,4 +1,4 @@
-![banner](https://assets.aliou.me/pi-extensions/banners/pi-dev-kit.png)
+![banner](https://assets.aliou.me/github/aliou/pi-dev-kit/banner.png)
 
 # Pi Dev Kit
 
@@ -11,7 +11,7 @@ Tools and commands for building, maintaining, and updating Pi extensions.
 https://github.com/user-attachments/assets/44a96009-0653-4803-8590-d5a8a5131f4c
 
 <small>
-  <a href="https://assets.aliou.me/pi-extensions/2026-02-02-pi-extension-dev-demo.mp4">Non sped-up version</a>
+  <a href="https://assets.aliou.me/github/aliou/pi-dev-kit/demo.mp4">Non sped-up version</a>
 </small>
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aliou/pi-dev-kit",
-  "version": "0.7.0",
+  "version": "0.7.2",
   "license": "MIT",
   "type": "module",
   "private": false,
@@ -26,7 +26,7 @@
     "prompts": [
       "./src/prompts"
     ],
-    "video": "https://assets.aliou.me/pi-extensions/2026-02-02-pi-extension-dev-demo.mp4"
+    "video": "https://assets.aliou.me/github/aliou/pi-dev-kit/demo.mp4"
   },
   "publishConfig": {
     "access": "public"
@@ -44,14 +44,15 @@
     "typebox": "*"
   },
   "devDependencies": {
-    "@biomejs/biome": "^2.3.13",
+    "@biomejs/biome": "^2.4.15",
     "@changesets/cli": "^2.27.11",
     "@earendil-works/pi-coding-agent": "0.74.0",
     "@earendil-works/pi-tui": "0.74.0",
     "typebox": "1.1.24",
     "@types/node": "^25.0.10",
     "husky": "^9.1.7",
-    "typescript": "^5.9.3"
+    "typescript": "^5.9.3",
+    "@aliou/biome-plugins": "^0.8.1"
   },
   "peerDependenciesMeta": {
     "@earendil-works/pi-coding-agent": {

package/src/commands/update.ts

@@ -1,23 +1,18 @@
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
 import { VERSION } from "@earendil-works/pi-coding-agent";
 
-const NPM_REGISTRY_URLS = [
-  "https://registry.npmjs.org/@earendil-works/pi-coding-agent/latest",
-  "https://registry.npmjs.org/@mariozechner/pi-coding-agent/latest",
-] as const;
+const NPM_REGISTRY_URL =
+  "https://registry.npmjs.org/@earendil-works/pi-coding-agent/latest";
 
 async function fetchLatestVersion(): Promise<string | null> {
-  for (const url of NPM_REGISTRY_URLS) {
-    try {
-      const res = await fetch(url);
-      if (!res.ok) continue;
-      const data = (await res.json()) as { version?: string };
-      if (data.version) return data.version;
-    } catch {
-      // Try the next registry URL.
-    }
+  try {
+    const res = await fetch(NPM_REGISTRY_URL);
+    if (!res.ok) return null;
+    const data = (await res.json()) as { version?: string };
+    return data.version ?? null;
+  } catch {
+    return null;
   }
-  return null;
 }
 
 const UPDATE_PROMPT = `# Update Pi Extensions
@@ -47,10 +42,11 @@ Current Pi core packages are:
 - \`@earendil-works/pi-tui\`
 - \`typebox\`
 
-Legacy packages under \`@mariozechner/*\` may still be present. Treat them as Pi core packages. Prefer \`@earendil-works/*\` when the target version exists on npm; if the new namespace is not published for the target version yet, keep the legacy namespace and report that decision.
 
 For distributed Pi packages:
-- Put imported Pi core packages in \`peerDependencies\` with \`"*"\` and mark each one \`optional: true\` in \`peerDependenciesMeta\`.
+- Put imported Pi core packages in \`peerDependencies\` and mark each one \`optional: true\` in \`peerDependenciesMeta\`.
+- Use \`"*"\` for Pi core peer ranges by default, per Pi package docs.
+- Only use a minimum range such as \`">=0.75.0"\` when source code uses an API that the changelog/docs show was introduced after Pi 0.74.0. In that case, set the minimum to the exact version that introduced the required API.
 - Keep the same Pi core packages in \`devDependencies\` at the exact target version for local type checking.
 - Keep \`typebox\` 1.x. Do not use \`@sinclair/typebox\` in new code.
 
@@ -81,7 +77,7 @@ For tools, verify:
 - Every \`promptGuidelines\` bullet names the exact tool, because Pi injects bullets flat into the global Guidelines section. Do not write "this tool".
 - Execute signature is \`(toolCallId, params, signal, onUpdate, ctx)\`; signal comes before \`onUpdate\`.
 - Use \`onUpdate?.(...)\` and forward \`signal\` to \`fetch\`, \`pi.exec\`, SDK clients, and long work.
-- Use \`StringEnum\` from \`@earendil-works/pi-ai\`/legacy \`@mariozechner/pi-ai\` for string enums; avoid \`Type.Union([Type.Literal(...)])\` for model-facing enums.
+- Use \`StringEnum\` from \`@earendil-works/pi-ai\` for string enums; avoid \`Type.Union([Type.Literal(...)])\` for model-facing enums.
 - Use \`prepareArguments(args)\` only for backward-compatible schema shims before validation.
 - Use \`executionMode: "sequential"\` for tools whose sibling calls mutate shared in-memory state or otherwise must not run concurrently.
 - File-mutating tools normalize leading \`@\` in paths and wrap the full read-modify-write window in \`withFileMutationQueue()\`.
@@ -116,7 +112,7 @@ For project structure and package docs, verify:
 ## 5. Create Update Plan
 
 Present a detailed plan with:
-- Package namespace/version changes and whether \`@earendil-works/*\` is available for the target.
+- Package namespace/version changes.
 - Files to change and why.
 - API migrations required by changelogs/docs.
 - Best-practice cleanups found in source, README, skills, prompts, and examples.

package/src/skills/pi-extension/SKILL.md

@@ -117,7 +117,7 @@ If using the legacy namespace, replace `@earendil-works/*` with the matching `@m
 22. Provider dynamic model discovery belongs in an async extension factory, not `session_start`.
 23. Use SDK helpers for Pi paths instead of `homedir()` when helpers exist.
 24. No `.js` extensions in TypeScript imports.
-25. Pi core packages you import belong in optional `peerDependencies` with `"*"`, and exact target versions in `devDependencies`.
+25. Pi core packages you import belong in optional `peerDependencies`; use `"*"` by default, or `">=x.y.z"` only when code needs an API introduced after Pi 0.74.0. Keep exact target versions in `devDependencies`.
 
 ## Completion Checklist
 

package/src/skills/pi-extension/references/publish.md

@@ -32,7 +32,7 @@ A publishable package needs Pi metadata and discoverability fields.
 
 Use the legacy `@mariozechner/*` namespace only while the target Pi packages are not published under `@earendil-works/*`.
 
-Pi core packages imported at runtime belong in optional `peerDependencies` with `"*"`. Keep exact target versions in `devDependencies` for local type checking. Third-party runtime packages belong in `dependencies`.
+Pi core packages imported at runtime belong in optional `peerDependencies`. Use `"*"` by default. Only use a minimum range such as `">=0.75.0"` when code requires an API introduced after Pi 0.74.0, and set the minimum to the introducing version. Keep exact target versions in `devDependencies` for local type checking. Third-party runtime packages belong in `dependencies`.
 
 ## Installation Specs
 
@@ -140,7 +140,7 @@ Run the repo's public-dependency check when available, for example `pnpm run che
 - [ ] `files` lists only shipped files users need.
 - [ ] `pi.extensions`, `pi.skills`, `pi.prompts`, and `pi.themes` paths are correct.
 - [ ] Demo `pi.video` or `pi.image` metadata is present when available.
-- [ ] Imported Pi core packages are optional peers with `"*"`.
+- [ ] Imported Pi core packages are optional peers with `"*"`, unless a post-0.74.0 API requires a documented minimum range.
 - [ ] Imported Pi core packages are exact dev dependencies for type checking.
 - [ ] Third-party runtime packages are in `dependencies`.
 - [ ] No private workspace dependencies in public packages.

package/src/skills/pi-extension/references/structure.md

@@ -146,7 +146,8 @@ Pi provides these runtime packages to extensions:
 
 For any of these that you import:
 
-- Put them in `peerDependencies` with `"*"`.
+- Put them in `peerDependencies` with `"*"` by default.
+- Use a minimum range such as `">=0.75.0"` only when code requires an API introduced after Pi 0.74.0, using the introducing version as the minimum.
 - Mark them `optional: true` in `peerDependenciesMeta`.
 - Put exact target versions in `devDependencies` for type checking.
 - Do not bundle them.
@@ -428,7 +429,7 @@ Do not publish packages that depend on private workspace packages.
 
 - [ ] One entry point per feature directory.
 - [ ] No root fan-out registrar in new code.
-- [ ] Pi core imports are optional peers with `"*"` and exact dev deps.
+- [ ] Pi core imports are optional peers with `"*"` unless a post-0.74.0 API requires a documented minimum range, and exact dev deps.
 - [ ] Third-party runtime packages are in `dependencies`.
 - [ ] Config uses raw/resolved TypeScript interfaces.
 - [ ] Settings use `registerSettingsCommand` when configurable.