Remove Pi integration from the core distributable#90
Merged
Conversation
Pi is not part of the core Dex experience, but the core vault shipped the full Pi extension code and beta scaffolding to every user: - pi-extensions/ (34 files, ~3.7k lines of TypeScript) - .claude/reference/beta-templates/pi/ (11 files) Nothing in dex-core imports pi-extensions, and neither dex-desktop nor dex-pi consume this copy — dex-pi is Pi's canonical home. So this was duplicate code shipping to users who could not use it. Also removed a dangling piece this exposed: .pi/agent/extensions/dex was a tracked symlink pointing into pi-extensions/dex, i.e. it would have shipped broken once the target was gone. Pruned the now-orphaned references: the Pi rows in beta-templates/README.md (rewritten around the surviving analytics template), the pi-extensions entries in .distignore / .gitattributes / .obsidian/app.json / .gitignore, and the pi-extensions glob in the check-doc-drift and check-test-delta CI gates. Pi remains fully supported as a harness; it is simply no longer bundled in core. Gates: ruff clean · 145 pytest pass · 4 hook tests pass · verify-distribution 0 errors · path-consistency pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes the Pi coding-agent integration from the core Dex vault. Per Dave: Pi is not needed in the core experience.
The core vault shipped the full Pi extension to every user:
pi-extensions/— 34 files, ~3.7k lines of TypeScript.claude/reference/beta-templates/pi/— 11 files of beta scaffoldingNothing in dex-core imports
pi-extensions, and neitherdex-desktopnordex-piconsume this copy —dex-piis Pi's canonical home. So this was duplicate code shipping to users who couldn't use it.Also fixed
.pi/agent/extensions/dexwas a tracked symlink pointing intopi-extensions/dex— it would have shipped dangling once the target was removed. (Same dead-reference class as the strip in #89.)Pruned references
beta-templates/README.md(rewritten around the surviving analytics template)pi-extensionsentries in.distignore,.gitattributes,.obsidian/app.json,.gitignorepi-extensionsglob incheck-doc-driftandcheck-test-deltaCI gatesPi remains fully supported as a harness — it's just no longer bundled in core.
Gates
ruff clean · 145 pytest pass (1 skipped) · 4 hook tests pass · verify-distribution 0 errors · path-consistency pass.
🤖 Generated with Claude Code