@gyoungwe/pi-research

中文文档
0.2.0发布于 2026/10/25MITTypeScriptES Module近 30 天下载 1万

Evidence-gated research retrieval, reading, deposition and source-grounded answer tools for native Pi

原始使用文档

@gyoungwe/pi-research

Self-contained research evidence tools for native Pi and Drone's public host composition. Version 0.2.0 is a release candidate in this repository; this change does not publish it to npm.

The native entry registers research_search_sources, research_read_source, research_deposit_research_note, research_answer_sources, research_status, and research_loop. Source discovery and hash-checked reading stay inside the workspace. Candidate notes go into .pi/research-notes. The answer packet requires two distinct current-session read receipts; it is evidence to assess, not an independent scientific verification.

The run lifecycle uses the complete persisted research core: archive integrity, observed reading receipts, structured claim bindings, provenance, and recovery. Empty claims or invented source references cannot make a run answerable. Run journals are isolated by Pi session identity and extension instance, without a process-global ledger. Native run artifacts default to results/; optional project-local .pi/research-workspace.json can supply resultsRoot, obsidianVault, and knowledgeBindingRevision.

The /host entry exports the complete research core, Zotero identity/write/ reconciliation algorithms, institutional access, and registerResearchExtension. Desktop supplies workspace/project binding, scheduling, authorization, transport and Vault ports. Network access, setup subprocesses, and external writes belong to these host-mediated operations; loading the native entry does not implicitly perform them. Writes require authorization and read-back. Actual Zotero account and Protocols.io write acceptance remains separate from isolated unit tests.

Pi is a peer dependency and is never bundled. There are no @drone/*, Electron, plugin-to-plugin, or source-checkout dependencies. migration-sources.json records original paths and reachable Git ancestry. Build with npm run build; npm run check runs reproducible artifact checks, unit tests, package smoke, and real SDK sessions on pinned Pi 1.1.0 and npm latest using isolated HOME and an offline faux provider. These sessions exercise actual SDK tool dispatch without user credentials.

版本与发布记录

@gyoungwe/pi-research 共发布 4 个版本,首次发布于 2026/10/18;过去 12 个月发布了 4 个版本。

版本发布日期距今
0.2.0latest2026/10/2522 天前
0.1.12026/10/2126 天前
0.1.02026/10/1830 天前
0.0.0-stage2026/10/1830 天前

关于 @gyoungwe/pi-research 的常见问题

@gyoungwe/pi-research 是什么?

Evidence-gated research retrieval, reading, deposition and source-grounded answer tools for native Pi

如何安装 @gyoungwe/pi-research?

在项目目录运行 npm install @gyoungwe/pi-research,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:@earendil-works/pi-coding-agent(>=1.1.0 <2.0.0)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。

@gyoungwe/pi-research 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@gyoungwe/pi-research 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@gyoungwe/pi-research 可以商用吗?

@gyoungwe/pi-research 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@gyoungwe/pi-research 的下载量有多少?

根据 npm 官方下载统计,@gyoungwe/pi-research 在 2026/10/17 – 2026/11/15 这 30 天内被下载 10,005 次,日均约 334 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@gyoungwe/pi-research 还在维护吗?

最新版本 0.2.0 发布于 2026/10/25(22 天前);至今共发布 4 个版本,其中过去 12 个月发布了 4 个;首次发布于 2026/10/18。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。