Repository navigation
feat: vendor billion-context-pi-subagents in-repo under pi-subagents/ (#2384) - #2386
Conversation
ea3cb0b to
d233af6
Compare
[bot] 🏷 冲突已解决,rebase 完成并推送: 结构化八问:
顺带发现(已在本 PR 内修掉):master 自身的 lockfile 落后于 判定:冲突已清,等 CI 绿即可由 owner 合并。 |
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2574-pr.2386.c2b27fdThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2386.tgz
npm install -g packageInstall instructions are refreshed on each push. |
…tment as kernel/) The #1440-P6 gate scans all tracked .ts via the *.ts pathspec but only excludes kernel/. Vendoring pi-subagents/ (#2384) put the component's own public API surface (a separately published npm package with its own test suite and version discipline) under the root-package gate, which flagged 20 of its exports. Exclude it wholesale exactly as kernel/ is excluded; the component imports nothing from the root src/, so no root symbol loses its only references.
[bot] 🏷 跟进:rebase 后的 CI 有一个红—— 结构化八问(针对这个红):
判定:冲突已清、CI 全绿、 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.134-master.8c62d64 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Closes #2384
What
Vendors
billion-context-pi-subagentsINTO THIS REPO underpi-subagents/, same pattern askernel/(#2092): own source + own unit suite + ownpackage.json(own version) + own build chain; consumed via"billion-context-pi-subagents": "file:./pi-subagents"devDependency; tsup keeps inlining it via the existingnoExternalentry (list unchanged — the component's own build already inlines itstypeboxpeer, so dist stays self-contained). A commit IS the pin; the cross-repo npm publish round-trip is gone.d19481e(src/tests/tsup/tsconfig/LICENSE/READMEs); provenance inpi-subagents/PROVENANCE.md.typeboxadded to devDependencies (build-time resolution for the component's own tsup build); build/typecheck/test pre-hooks now buildpi-subagents/alongsidekernel/.npm --prefix pi-subagents testadded to the test job (two-layer rule); NEWpi-subagents-guardjob enforces version discipline (src/build-config changes ⇔pi-subagents/package.jsonversion bump, both directions). Deliberately LIGHTER than kernel-guard: no PR-body declaration / human gate — this is a fast-moving pi-lane extension surface, not load-bearing core compression (the point of billion-context-pi-subagents 直接纳入本项目 像acp-kernel一样 #2384 is reducing dev cost; tighten here first if that assessment changes).pi-subagents/README.md) — small labeled doc-accuracy fixes entailed by this change.Behavior change (flagged per owner policy)
The vendor takes master, not the previously pinned npm
0.1.1: master carries one merged-but-unreleased fix — the settle-gate delegate-notification fix for #2301 (d6d8721, upstream PR #7).sendUserMessage(followUp)into the host queue on a fixed ~2s trailing timer (cap 10s) regardless of whether the main agent would read the result file itself — a later read could not recall it (the [Bug][Pi] notifyIfRead="skip" still delivers stale follow-ups after the final result was read #2301 stale-follow-up bug).agent_settledboundary, where read/waiter/consumption are re-checked — read ⇒ dropped, unread ⇒ coalesced into ONE message; the misleading log splits intoinject-suppressedvsread-after-commit.0.1.2(source differs from published 0.1.1 ⇒ version discipline).Incidental lockfile note:
npm installalso synced a stale lock line for the existing kernel file link (kernelversion 0.0.104 → 0.0.105, matching the already-committedkernel/package.json); NO kernel source changed.Config surface
None — no new config fields / env vars / CLI flags; no default changed.
Verification (targeted locally; global regression delegated to CI)
npm --prefix pi-subagents test: 213/213 pass (incl. the 8-test [Bug][Pi] notifyIfRead="skip" still delivers stale follow-ups after the final result was read #2301 settle-gate suite).npm run typecheck: clean.tests/pi-subagents-wiring.test.ts+tests/pi-subagent-registry.test.ts: 26/26 pass.npm run build: success; zero external imports ofbillion-context-pi-subagents/typeboxin dist (self-containment contract preserved);read-after-commitmarker present indist/agent/pi-native.jsproving the [Bug][Pi] notifyIfRead="skip" still delivers stale follow-ups after the final result was read #2301 fix is the code actually bundled.