Skip to content

docs: follow-up sweep on stale @mariozechner/* refs (TP-191 follow-up) - #605

Merged
HenryLach merged 1 commit into
mainfrom
docs/mariozechner-stale-refs-cleanup
Jun 17, 2026
Merged

docs: follow-up sweep on stale @mariozechner/* refs (TP-191 follow-up)#605
HenryLach merged 1 commit into
mainfrom
docs/mariozechner-stale-refs-cleanup

Conversation

@HenryLach

Copy link
Copy Markdown
Owner

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.

What's updated (clearly stale)

File What changed Why
extensions/tsconfig.json (// NOTE comment) Updated to mention both scopes (@earendil-works/* canonical, legacy @mariozechner/* for back-compat) and point readers at tsconfig.ci.json Explicitly flagged stale in code-quality-gates.md; TP-191 was supposed to fix it but didn't
docs/specifications/cli/CLI-SPEC.md Two locations: peerDependencies JSON example + the 'Peer (Extensions)' dependency table Spec was misleading: current package.json uses @earendil-works/* peerDeps, not @mariozechner/*
docs/specifications/framework/33-parallel-task-orchestrator.md npm install -g @mariozechner/pi-coding-agent@earendil-works (Arch, macOS, Windows WSL install sections) Per AGENTS.md and current Pi docs, canonical install command is the new scope
docs/specifications/taskplane/code-quality-gates.md Updated the quoted tsconfig.json NOTE to match new file content + added 'Addressed 2026-06-17' callout next to the original 'TP-191 will refresh' forward-looking statement Keeps the spec's audit trail intact

What's deliberately left alone (accurate descriptions, not stale)

File Why preserved
docs/maintainers/development-setup.md lines 111-112 Accurately describes the test loader aliasing @mariozechner/* — which it does, because source code still imports from @mariozechner/* (Pi maintains both scope aliases at runtime for back-compat)
docs/maintainers/testing.md lines 105-106 Same context
docs/specifications/taskplane/migrate-to-node-test-runner.md Historical migration spec; quotes are accurate descriptions of pre-migration Vitest config
docs/specifications/taskplane/code-quality-gates.md lines 106-107, 114 Accurately describes the current tsconfig.test.json state. Fixing would require coordinated updates to tsconfig.test.json, loader-hooks.mjs, and source imports — out of scope for a docs-only sweep
CHANGELOG.md, taskplane-tasks/** Historical artifacts

Future cleanup (when convenient)

If source code ever migrates from @mariozechner/* imports to @earendil-works/* (which would match the current peerDependencies), a coordinated change to the loader and tsconfigs would be needed. The remaining accurate-as-of-today references in the maintainer docs would then become stale and would need to be swept too. Not urgent — Pi maintains the back-compat aliases.

Validation

Gate Result
npm run typecheck ✅ pass
npm run lint ✅ 286 warnings / 671 infos — identical to main
npm run format:check ✅ pass
Full test suite ✅ 3,714 / 3,715 pass, 1 skipped — zero new failures

No code changes that affect runtime behavior, no release needed.

…TP-191 follow-up)

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.
@HenryLach
HenryLach enabled auto-merge June 17, 2026 22:48
@HenryLach
HenryLach merged commit 892c8f8 into main Jun 17, 2026
1 check passed
@HenryLach
HenryLach deleted the docs/mariozechner-stale-refs-cleanup branch June 17, 2026 22:48
HenryLach added a commit that referenced this pull request Jun 19, 2026
Move the supervisor stale-ctx fix and the two docs sweeps from
[Unreleased] into a dated [0.30.4] section:

  Fixed:
    - Supervisor heartbeat timer crashed pi with stale extension ctx (#597)

  Docs:
    - Pi GitHub URL sweep + install tutorial PATH co-location (#604)
    - @mariozechner/* stale-references follow-up sweep (#605)

Insert fresh empty [Unreleased] placeholder per keep-a-changelog
convention.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant