Repository navigation
feat: index billion-context on the pi.dev gallery - #508
Conversation
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-508Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr508.tgz
npm install -g packageThis comment is automatically updated on each push. |
[bot] 🏷 Reviewed #508. The one-keyword change itself is correct and legitimate — but the branch behind this PR does not match its stated scope. Merging it as-is would ship unrelated, unreviewed code. I've opened a clean, isolated PR for exactly the keyword: #509. Verified legitimate. The package really ships a pi extension ( The problem — PR #508's branch bundles 5 extra commits that are not in master. Its top commit is the clean keyword edit (
Confirmed with What I did. Opened #509 ( "anthropic",
- "openai"
+ "openai",
+ "pi-package"Pre-flight: Recommendation. Merge #509 (or rebase #508 down to just the keyword commit) and close the contaminated one. If #496 / #499 are wanted, land them via their own reviewed PRs — they're preserved on the #508 branch, not lost by switching. The follow-up release is already open as #507 ( |
Why
billion-contextis missing from https://pi.dev/packages whilebillion-context-pishows up.Pi's gallery catalogues exactly the npm keyword
pi-package(pi docs,packages/coding-agent/docs/packages.md: "The package gallery displays packages tagged withpi-package"). Verified against the live catalog: every listed package (billion-context-pi,context-mode,bigpowers,pi-mcp-adapter,pi-lens) carries it;billion-context(0.1.80) does not.The detail page https://pi.dev/packages/billion-context does render on demand (it reads the
pimanifest, so "Types: extension" is correct), but its Downloads row says "not available" — proof it is not in the gallery DB, hence no listing/search entry.Change
One keyword in
package.json:pi-package. No code, no version bump.Legitimate: the package really does ship a pi extension (
"pi": { "extensions": ["./dist/agent/pi.js"] },src/agent/pi.ts), and the plugin self-disables when there is no proxy (src/agent/pi.ts:156-157), so a pi user installing it standalone gets a no-op.Pre-flight
npm run typecheck— cleannpm test— 1022 pass / 0 failnpm run build— not run (metadata-only change, no code touched)Note:
tests/plugin-agent.test.tsinitially reported 2 failures (4 == 0at :273 and :325). Reproduced on clean master, then traced to the harness exportingBILLION_CONTEXT_PROXYinto the test process —src/agent/shared.ts:40 proxyBaseFromEnv()treats it as proxy detection, so the plugin registered 4 tools where the inert tests expect 0. With the var unset the file is 27/27 green. Environment contamination, not a repo defect; flagging it becausenpm testis not hermetic against that var.Follow-up
npm keywords are read from the latest published version, so this only takes effect on the next publish. After merge I will open a
*_release-v0.1.81branch with an isolatedrelease v0.1.81commit; CI publishes and pi.dev re-reads the keywords.