From f5b0a6416dbe214448bc8c33fd09932d7dedca2b Mon Sep 17 00:00:00 2001 From: Henry Lach Date: Wed, 17 Jun 2026 18:47:38 -0400 Subject: [PATCH] docs: follow-up sweep on stale @mariozechner/* refs (Pi scope rename TP-191 follow-up) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Background: Pi was renamed from `@mariozechner/pi-coding-agent` to `@earendil-works/ pi-coding-agent` at Pi v0.74.0 (issue #560). TP-191's tsconfig modernization was supposed to refresh the related stale references in spec docs and tsconfigs, but several were overlooked. This is a focused follow-up sweep to fix the truly stale references while preserving the ones that accurately describe back-compat behavior. What's updated (clearly stale or out of date): extensions/tsconfig.json (// NOTE comment) Previous text referenced only `@mariozechner/*` packages. The code-quality-gates spec explicitly flagged this as 'stale' and said 'TP-191 will refresh the comment' — but TP-191 left it alone. Updated to mention both scopes (`@earendil-works/*` as canonical, legacy `@mariozechner/*` as back-compat) and to point readers at tsconfig.ci.json for the CI-shim path mappings. docs/specifications/cli/CLI-SPEC.md Two locations had `@mariozechner/*` in package.json examples / peer- dependency tables. Current taskplane/package.json uses `@earendil-works/*` peerDependencies, so the spec was actively misleading. Both updated to match current state. docs/specifications/framework/33-parallel-task-orchestrator.md Three `npm install -g @mariozechner/pi-coding-agent` instructions in the cross-platform install guidance (Arch, macOS, Windows WSL). Per AGENTS.md and current Pi docs, the canonical install command is now `npm install -g @earendil-works/pi-coding-agent`. Updated in place. docs/specifications/taskplane/code-quality-gates.md Two changes to keep the spec's tsconfig quote in sync with the new tsconfig.json content: - The quoted `// NOTE` text updated to match the new comment. - The 'TP-191 will refresh the comment' forward-looking note retained with a strikethrough plus a follow-up 'Addressed 2026-06-17' callout explaining the cleanup pass. This preserves the spec's audit trail. What's deliberately left alone (accurate description of current state): docs/maintainers/development-setup.md (lines 111-112) docs/maintainers/testing.md (lines 105-106) Both describe the test loader's `@mariozechner/*` aliases. The loader (extensions/tests/loader-hooks.mjs) does still redirect these specifiers to local mocks — accurate documentation of current behavior. Source code (extensions/taskplane/*.ts) still imports from `@mariozechner/*` because Pi maintains both scope aliases at runtime for back-compat, and there is no pressure to migrate yet. When source imports migrate to `@earendil-works/*`, these docs (along with the loader and tsconfig.test.json) will need a coordinated update. docs/specifications/taskplane/migrate-to-node-test-runner.md Historical migration spec describing the pre-migration Vitest config. Quotes are accurate descriptions of what was migrated, not current state. Leaving as a historical document. docs/specifications/taskplane/code-quality-gates.md lines 106-107, 114 Quoting and commentary on `tsconfig.test.json`, which also still only references `@mariozechner/*` paths. This is internally consistent with current source-code imports — fixing the spec would require coordinated updates to tsconfig.test.json, loader-hooks.mjs, and possibly source imports. Out of scope for a docs-only sweep. CHANGELOG.md, taskplane-tasks/** Historical artifacts. Never edited. Validation npm run typecheck pass npm run lint 286 warnings / 671 infos (identical to main) npm run format:check pass Full test suite 3714/3715 pass, 1 skipped, zero new failures Confirmed grep: zero clearly-stale `@mariozechner` references remain in user-facing docs and current-state spec docs. Remaining refs are either accurate descriptions of back-compat behavior or historical artifacts. --- docs/specifications/cli/CLI-SPEC.md | 12 ++++++------ .../framework/33-parallel-task-orchestrator.md | 6 +++--- docs/specifications/taskplane/code-quality-gates.md | 4 ++-- extensions/tsconfig.json | 2 +- 4 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/specifications/cli/CLI-SPEC.md b/docs/specifications/cli/CLI-SPEC.md index d58bad00..28969993 100644 --- a/docs/specifications/cli/CLI-SPEC.md +++ b/docs/specifications/cli/CLI-SPEC.md @@ -152,9 +152,9 @@ taskplane/ ← npm package root (= repo root) "templates/" ], "peerDependencies": { - "@mariozechner/pi-coding-agent": "*", - "@mariozechner/pi-tui": "*", - "@mariozechner/pi-ai": "*", + "@earendil-works/pi-coding-agent": "*", + "@earendil-works/pi-tui": "*", + "@earendil-works/pi-ai": "*", "@sinclair/typebox": "*" }, "dependencies": { @@ -949,9 +949,9 @@ Clear ownership prevents upgrade conflicts: | Dependency | Range | Purpose | |---|---|---| -| `@mariozechner/pi-coding-agent` | `*` | Pi extension runtime | -| `@mariozechner/pi-tui` | `*` | TUI components for widgets | -| `@mariozechner/pi-ai` | `*` | AI utilities (StringEnum) | +| `@earendil-works/pi-coding-agent` | `*` | Pi extension runtime | +| `@earendil-works/pi-tui` | `*` | TUI components for widgets | +| `@earendil-works/pi-ai` | `*` | AI utilities (StringEnum) | | `@sinclair/typebox` | `*` | Schema definitions for tool parameters | ### Dev diff --git a/docs/specifications/framework/33-parallel-task-orchestrator.md b/docs/specifications/framework/33-parallel-task-orchestrator.md index 10d54cc3..c02bdd69 100644 --- a/docs/specifications/framework/33-parallel-task-orchestrator.md +++ b/docs/specifications/framework/33-parallel-task-orchestrator.md @@ -1606,7 +1606,7 @@ sudo dnf install git tmux sudo pacman -S git tmux # Pi (via npm) -npm install -g @mariozechner/pi-coding-agent +npm install -g @earendil-works/pi-coding-agent ``` TMUX and Git are standard packages on all major Linux distributions. @@ -1619,7 +1619,7 @@ No special configuration needed. brew install git tmux # Pi -npm install -g @mariozechner/pi-coding-agent +npm install -g @earendil-works/pi-coding-agent ``` macOS ships with Git, but the Homebrew version is typically newer. @@ -1668,7 +1668,7 @@ Key facts about Git Bash TMUX: ```bash # Inside WSL: sudo apt install tmux git -npm install -g @mariozechner/pi-coding-agent +npm install -g @earendil-works/pi-coding-agent ``` WSL works but introduces filesystem boundary considerations: diff --git a/docs/specifications/taskplane/code-quality-gates.md b/docs/specifications/taskplane/code-quality-gates.md index 45f71508..70532ff0 100644 --- a/docs/specifications/taskplane/code-quality-gates.md +++ b/docs/specifications/taskplane/code-quality-gates.md @@ -73,7 +73,7 @@ It slipped through: ```json { - "// NOTE": "Pi extensions are runtime-transpiled by pi's bundler. This tsconfig is for editor/CI type-checking only. Full tsc --noEmit will report module resolution errors for @mariozechner/* packages (globally installed, not in node_modules).", + "// NOTE": "Pi extensions are runtime-transpiled by pi's bundler. This tsconfig is for editor/CI type-checking only. Full tsc --noEmit will report module resolution errors for @earendil-works/* packages — and legacy @mariozechner/* aliases retained for back-compat — because pi packages are globally installed (not in node_modules). See extensions/tsconfig.ci.json for the CI variant that adds pi-shims path mappings.", "compilerOptions": { "target": "ES2022", "module": "ESNext", @@ -93,7 +93,7 @@ It slipped through: 1. The pi packages (`@earendil-works/pi-coding-agent`, `@earendil-works/pi-ai`, `@earendil-works/pi-tui` — and legacy `@mariozechner/*`) are NOT in `node_modules`. They live at `npm root -g//` and are aliased at runtime by Pi's extension loader. `tsc --noEmit` cannot resolve them. 2. `include: ["task-orchestrator.ts"]` only covers ONE entry point. The reviewer extension and the rest of `extensions/taskplane/` are excluded from typecheck scope today. -3. The `// NOTE` comment in this file is **stale** — it still references `@mariozechner/*` only, even though the canonical scope is now `@earendil-works/*` (per issue #560 and Pi v0.74.0). This is a historical reference, not the current canonical scope. **TP-191 will refresh the comment** as part of the tsconfig modernization. +3. ~~The `// NOTE` comment in this file is **stale** — it still references `@mariozechner/*` only, even though the canonical scope is now `@earendil-works/*` (per issue #560 and Pi v0.74.0). This is a historical reference, not the current canonical scope. **TP-191 will refresh the comment** as part of the tsconfig modernization.~~ **(Addressed 2026-06-17:** the comment now mentions both scopes — `@earendil-works/*` as canonical, `@mariozechner/*` as legacy back-compat — and points readers at `tsconfig.ci.json` for the CI-shim path mappings. This was overlooked during the TP-191 implementation and folded into a follow-up cleanup pass.**)** ### 4.2 `extensions/tsconfig.test.json` diff --git a/extensions/tsconfig.json b/extensions/tsconfig.json index 981f08e2..31dde3bd 100644 --- a/extensions/tsconfig.json +++ b/extensions/tsconfig.json @@ -1,5 +1,5 @@ { - "// NOTE": "Pi extensions are runtime-transpiled by pi's bundler. This tsconfig is for editor/CI type-checking only. Full tsc --noEmit will report module resolution errors for @mariozechner/* packages (globally installed, not in node_modules).", + "// NOTE": "Pi extensions are runtime-transpiled by pi's bundler. This tsconfig is for editor/CI type-checking only. Full tsc --noEmit will report module resolution errors for @earendil-works/* packages — and legacy @mariozechner/* aliases retained for back-compat — because pi packages are globally installed (not in node_modules). See extensions/tsconfig.ci.json for the CI variant that adds pi-shims path mappings.", "compilerOptions": { "target": "ES2022", "module": "ESNext",