@lincoln504/pi-research 1.6.15 → 1.6.16

package/README.md

@@ -34,7 +34,7 @@
 
 Search and scraping run locally in a stealth browser, with no search provider and no monthly cap. The only cost is LLM tokens.
 
-**Current recommended model:** [`inclusionai/ling-3.0-flash`](https://openrouter.ai/inclusionai/ling-3.0-flash) on OpenRouter.
+Currently recommended model to configure for research: [`openrouter/inclusionai/ling-3.0-flash`](https://openrouter.ai/inclusionai/ling-3.0-flash).
 
 ### Install
 
@@ -69,7 +69,7 @@ Three depth levels (normal, deep, ultra) set the team size and number of rounds.
 
 ### Use cases
 
-- Researching inside pi. No API key needed.
+- Researching inside pi. No search subscription needed.
 - Researching from Claude Code, Codex, or another coding agent while a cheaper or local model drives the run. The main agent's budget stays untouched.
 - Saving findings to a persistent, searchable knowledge store, scoped globally or per project.
 - Building agent systems that find and read web content, or collecting a dataset of web sources.
@@ -89,6 +89,7 @@ Three depth levels (normal, deep, ultra) set the team size and number of rounds.
 - pi. The pi extension uses the host's copy while the standalone CLI and agent skill install it as a dependency.
 - Local knowledge-store embeddings need `@huggingface/transformers`, an optional dependency. If its native image chain (sharp) cannot install, npm skips it with a warning and the install still succeeds, so everything works except local embeddings. The store tells you how to restore them.
 - Cloudflare Turnstile and similar systems block scraping on some sites. A run compensates with a wide pool of search results to scrape.
+- npm reports 1 moderate advisory (adm-zip, pulled in by onnxruntime and the camoufox browser downloader) for anything that installs this package. Installs themselves succeed; only a `npm audit` step in your own CI will exit nonzero until the upstream fix ships. See [docs/AUDIT-GATE.md](docs/AUDIT-GATE.md) for the verified details, and do not run `npm audit fix --force` against it (npm's suggested downgrade reintroduces a high-severity advisory).
 
 ### Channels
 

package/agent-skill/pi-research/SKILL.md

@@ -2,7 +2,7 @@
 name: pi-research
 description: "Multi-agent web research for any coding agent. Use for anything requiring current information from the internet — news, trends, product/service/company facts, statistics, people, places, events, APIs, library behavior, or 'what is X / how does X work' questions. Also use to search a local knowledge store of previously researched findings before doing live research. Powered by the pi-research engine (search, stealth scraping, security databases, Stack Exchange). Not for reading local files, running project commands, or analyzing this repository's own source."
 license: MIT
-metadata: { "author": "Lincoln Deen", "version": "1.6.15", "package": "@lincoln504/pi-research", "engine": "pi-research-sdk", "openclaw": { "requires": { "bins": ["node"] } } }
+metadata: { "author": "Lincoln Deen", "version": "1.6.16", "package": "@lincoln504/pi-research", "engine": "pi-research-sdk", "openclaw": { "requires": { "bins": ["node"] } } }
 allowed-tools: Bash(node:*)
 ---
 

package/docs/ARCHITECTURE.md

@@ -349,7 +349,7 @@ mismatch.
 Pinned data stack — `apache-arrow` is a direct dependency at `21.1.0`, and `overrides`
 forces the whole tree to that single version so LanceDB and Arrow share one Arrow instance
 (mismatched Arrow copies do not interoperate — arrays built by one are rejected by the
-other). This sits above `@lancedb/lancedb` 0.37's declared Arrow peer ceiling
+other). This sits above `@lancedb/lancedb` 0.38's declared Arrow peer ceiling
 (`>=15.0.0 <=18.1.0`) — npm will not even resolve the pairing without the override — and
 it is verified working, but it should be re-validated whenever `@lancedb/lancedb` is
 upgraded.
@@ -360,13 +360,17 @@ schema that Arrow 21.2 writes, failing every table open with
 `Failed to read IPC file: Arrow error: Parser error: Unable to get root as footer:
 RangeOutOfBounds … UnionVariant { variant: "Type::FixedSizeList" }` — 56 unit and 36
 integration tests, every one that touches a real table. Do not treat this range as
-caret-safe. Note also that every `@lancedb/lancedb` release through 0.37 declares the same
+caret-safe. Re-verified on 2026-09-09 against `@lancedb/lancedb` 0.38.0 (the knowledge-store
+unit suite fails identically on 21.2.0 there). Note also that every `@lancedb/lancedb` release
+through 0.38 declares the same
 `<=18.1.0` Arrow ceiling, so upgrading LanceDB does not resolve the override; it only
 changes which pairing needs re-validating.
 
 Pinned validation library — `typebox` is pinned to the exact version the pi host packages
 depend on (`@earendil-works/pi-ai` / `@earendil-works/pi-coding-agent` pin `1.3.7` across
-the 0.84.x line). Every
+the 0.84.x AND 0.85.x lines — verified against both 0.85.0 and 0.85.1 on 2026-09-09, after
+an undocumented 1.3.26 drift was caught and realigned; 3,064 unit tests and all four
+type-checks pass against 1.3.7). Every
 tool's parameter schema is built with TypeBox here and handed across the boundary to pi's
 tool system, so the two must agree on `Value.Check`/`Convert` semantics. A floating `^1.1.38`
 range let a fresh consumer install resolve pi-research to a newer TypeBox than pi's, shipping

package/docs/CHANGELOG.md

@@ -7,12 +7,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.6.16] - 2026-09-09
+
+### Added
+
+- **`docs/AUDIT-GATE.md`: the audit-gate runbook, with reinvestigation directions for every allowlisted advisory.** Covers the triage order (remediate, then override, then allowlist), the required evidence and fields for an exception entry, the reinvestigation triggers (stale-entry warnings, every release, new GHSA, upstream fix PR), and the concrete checklist for the current adm-zip entry (watch cthackers/adm-zip PR #575, check parent ranges, and never take the downgrade "fix", which reintroduces the HIGH CVE-2026-39244). It also documents, verified empirically on npm 11.19.0, what consumers of the published package see: installs and `pi install` succeed with a warning, `npm audit` exits 1, and `npm audit fix --force` ping-pongs between two vulnerable adm-zip versions. The README limitations section states the consumer-visible part; the exceptions JSON, `scripts/audit-gate.cjs`, and both workflows point at the runbook.
+
 ### Changed
 
-- **README: the recommended-model line is now the only bold text.** The Why-bullet lead-ins (No quota and no monthly fee / The index is local / Read-only by design / Search a little or a lot), the uninstall emphasis, and the optional-dependency emphasis are plain text now.
+- **Dependency audit across the board across the board; one real drift fixed, two holds re-verified empirically, everything else already current.** `typebox` is realigned 1.3.26 → 1.3.7: the whole pi 0.85.x line (pi-ai and pi-coding-agent at both 0.85.0 and 0.85.1, checked on the registry) pins 1.3.7, the documented rule is to move in lockstep with the host, and the 1.3.26 pin was an undocumented ride-along from the 1.6.9 upgrade that nothing needed — verified by running all 3,064 unit tests and all four type-checks (TS 6 and TS 7 native, src and tests) against 1.3.7, all green. `impit` moves 0.14.4 → 0.14.5 (patch; no install scripts, so the historical `only-allow pnpm` blocker does not apply; camoufox-js's `^0.14.1` range accepts it). Re-verified, still held: `apache-arrow` stays 21.1.0 — 21.2.0 was re-tested against `@lancedb/lancedb` 0.38.0 (the hold predated it) and the knowledge-store IPC failure reproduces identically (5 test files, 66 RangeOutOfBounds/FixedSizeList errors); `playwright-core` stays 1.60.0 (camoufox-js 0.12.0's peer range still caps `<1.61.0`); `typescript` stays `<6.1.0` (@typescript-eslint 8.70.0's peer ceiling, checked on the registry). Cosmetic range syncs where the lockfile was already ahead: `@typescript-eslint/*` `^8.69.0` → `^8.70.0`, `vite` `^8.0.16` → `^8.2.2` (override synced to match). The pi packages (`@earendil-works/*`) were already at the latest 0.85.1; `jsdom` 30, `vitest` 5, `dependency-cruiser` 18, and `npm-check-updates` 23 sit above the registry's `latest` dist-tags (the newer lines are tagged ahead), so they stay. The lockfile was regenerated with npm 12 (`npm ci --dry-run --legacy-peer-deps` passes under it); the full gate suite is green (lint, 4 type-checks, 3,064 unit tests, dependency-cruiser, build, audit gate with the adm-zip allowlist).
+
+### Security
+
+- **New adm-zip advisory GHSA-vwc7-r8mq-g2x9 allowlisted as upstream-blocked.** Moderate: `adm-zip` 0.5.9–0.6.0 follows symlinks at the extraction destination, allowing arbitrary file overwrite (CVE-2026-76845); 0.6.0 is the newest upstream release and is itself affected, so no bumped or overridden version exists. The advisory reaches the production tree through two parents (`onnxruntime-node` and `camoufox-js`), both outside this repo's control, so it ships as a reviewed per-GHSA exception in `config/tooling/audit-exceptions.json` (reason, clearsWhen, reviewed) per the documented policy — the audit gate passes with exactly this one allowlisted advisory and blocks anything else. Consumer impact, verified on npm 11.19: installs and `pi install npm:` succeed with a warning; `npm audit` exits 1 (expected, cosmetic); `npm audit fix --force` must never be run — it downgrades to a version carrying the HIGH CVE-2026-39244.
+
+## [1.6.15] - 2026-09-08
 
 ### Changed
 
+- **README: the recommended-model line is now the only bold text.** The Why-bullet lead-ins (No quota and no monthly fee / The index is local / Read-only by design / Search a little or a lot), the uninstall emphasis, and the optional-dependency emphasis are plain text now.
+
 - **README: full prose pass.** The recommended-model line is just the model name now. Semicolons became ordinary sentences, the staccato all-short-sentence draft was re-mixed into natural sentence rhythm, the How-it-works round loop is spelled out concretely (coordinator plans and starts the search, researchers scrape in parallel, the lead starts another round or writes the report), and the install/uninstall/use-cases/requirements sections were tightened.
 
 ## [1.6.14] - 2026-09-08

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lincoln504/pi-research",
-  "version": "1.6.15",
+  "version": "1.6.16",
   "description": "Web research for your agents with smart and safe tooling + knowledge store",
   "type": "module",
   "private": false,
@@ -124,13 +124,13 @@
     "bgutils-js": "^4.0.3",
     "camoufox-js": "^0.12.0",
     "esbuild": "^0.28.2",
-    "impit": "0.14.4",
+    "impit": "0.14.5",
     "jsdom": "^30.0.1",
     "node-html-markdown": "^2.0.0",
     "pdf-oxide-wasm": "^0.3.77",
     "playwright-core": "1.60.0",
     "poolifier": "^5.3.2",
-    "typebox": "1.3.26",
+    "typebox": "1.3.7",
     "undici": "^8.10.2",
     "youtubei.js": "^18.0.0"
   },
@@ -146,7 +146,7 @@
     "node-domexception": "npm:@nolyfill/domexception@^1.0.28",
     "ua-parser-js": "^1.0.41",
     "protobufjs": "7.6.5",
-    "vite": "^8.0.16",
+    "vite": "^8.2.2",
     "adm-zip": "^0.6.0",
     "jsdom": {
       "undici": "^8.10.2"
@@ -156,15 +156,15 @@
   "devDependencies": {
     "@eslint/js": "^10.0.1",
     "@types/jsdom": "^30.0.0",
-    "@typescript-eslint/eslint-plugin": "^8.69.0",
-    "@typescript-eslint/parser": "^8.69.0",
+    "@typescript-eslint/eslint-plugin": "^8.70.0",
+    "@typescript-eslint/parser": "^8.70.0",
     "@vitest/coverage-v8": "^5.0.0",
     "dependency-cruiser": "^18.2.0",
     "depngn": "^0.6.0",
     "eslint": "^10.10.0",
     "npm-check-updates": "^23.1.0",
     "typescript": ">=6.0.3 <6.1.0",
-    "vite": "^8.0.16",
+    "vite": "^8.2.2",
     "vitest": "^5.0.0"
   }
 }