@lincoln504/pi-research 1.7.11 → 1.7.12

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.7.11", "package": "@lincoln504/pi-research", "engine": "pi-research-sdk", "openclaw": { "requires": { "bins": ["node"] } } }
+metadata: { "author": "Lincoln Deen", "version": "1.7.12", "package": "@lincoln504/pi-research", "engine": "pi-research-sdk", "openclaw": { "requires": { "bins": ["node"] } } }
 allowed-tools: Bash(node:*)
 ---
 

package/dist/cli.mjs

@@ -17164,7 +17164,7 @@ var WorkerPoolManager = class {
             }
           },
           exitHandler: (code) => {
-            if (code !== 0 && !this.isShuttingDown && this.poolEpoch === myEpoch) {
+            if (code !== 0 && !this.isShuttingDown && !process.env["PI_PROCESS_EXITING"] && this.poolEpoch === myEpoch) {
               logger.error(`[WorkerPoolManager] Worker exited with code ${code}`);
               this.consecutiveErrors++;
               if (this.consecutiveErrors >= 3) {

package/docs/ARCHITECTURE.md

@@ -387,8 +387,8 @@ warns on every startup when a host-provided package (`typebox`, `@sinclair/typeb
 loader and create a second live module instance (`resource-loader.js`,
 `collectExtensionPackageWarnings`; pi `docs/packages.md`). Under pi the host's own copy is used,
 so the two agree on `Value.Check`/`Convert` by construction. `@earendil-works/pi-ai` and
-`@earendil-works/pi-coding-agent` 1.0.0 through 1.1.0 all pin `1.3.27` (re-checked 2026-10-08 in
-the installed packages' `package.json`), which is why the devDependency, and so every test run and
+`@earendil-works/pi-coding-agent` 1.0.0 through 1.3.0 all pin `1.3.27` (re-checked 2026-10-17 in
+the installed 1.3.0 packages' `package.json`, previously 2026-10-08 in 1.1.0), which is why the devDependency, and so every test run and
 the type-check, stays on exactly that version: bump it in lockstep with the pi host, not
 independently. A standalone CLI/SDK install resolves the peer automatically on npm >= 7; the
 `pi-research` bin preflights it with the pi packages and exits 78 with the remedy when a

package/docs/CHANGELOG.md

@@ -5,6 +5,18 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.7.12] - 2026-10-17
+
+### Changed
+
+- **The pi host dev dependencies move 1.1.0 → 1.3.0** (`@earendil-works/pi-ai`, `pi-coding-agent`, `pi-tui`, and the `pi-agent-core`/`pi-codemode`/`pi-mcp`/`pi-telemetry` they pull in; `@earendil-works/chord` drops out of the tree; the peer range stays `>=0.99.0 <2`). The 1.1.0 → 1.3.0 declaration diff (installed trees, 2026-10-17): `pi-coding-agent`'s extension surface file (`dist/core/extensions/types.d.ts`) changes in exactly four places — `BeforeAgentStartEvent` becomes a `messageType`-discriminated union (`BeforeAgentStartUserEvent` / `BeforeAgentStartCustomEvent`) because `before_agent_start` now also fires for idle `pi.sendMessage(..., { triggerTurn: true })` runs, `ToolNamespace` gains `aliases?`, `ToolDefinition` gains `reachesTools?`, and `ToolInfo` picks up `reachesTools`. `pi-ai` removes the `assistant-message-frame` module (`AssistantMessageFrame*`, `reduceAssistantMessageFrames`) — the only breaking removal across the two releases, and one this package never imports — and adds the OpenRouter routing schemas and `splitErrorToolResultImages`; its thinking-level types move to `providers/model-schema.d.ts` but are re-exported from the root unchanged. `pi-tui` adds the fake-cursor helpers. Nothing this package consumes is removed or re-signed: the four type-checks (TypeScript 6 and 7, src and tests) pass against 1.3.0, and `typebox` still pins `1.3.27` in `pi-ai` and `pi-coding-agent`, so the lockstep rule and the 0.99.0 floor are unchanged.
+- **`PI_TESTED_MAX_VERSION` moves to 1.3.0** (`src/core/pi-version.ts`), so a pi 1.2.x or 1.3.x host runs without the "newer than the tested ceiling" notice. pi-research never triggers the new firing path — all its `pi.sendMessage` calls are `customType` deliveries without `triggerTurn`, and both `pi.sendUserMessage` calls already pass `deliverAs` — and its `before_agent_start` handler reads only `systemPrompt`/`systemPromptOptions`, present on both union members.
+
+### Fixed
+
+- **Worker exits during a process-group teardown no longer trip the pool health counter.** `isShuttingDown` only covers the pool's own `shutdown()`, but a process-group signal (a cron wrapper's `timeout N`) SIGTERMs the workers in the same instant as the master, BEFORE the pool's shutdown begins, so those exits landed as unexpected deaths and could log the pool unhealthy on a process that was exiting anyway. The exit handler now also ignores non-zero exits while `PI_PROCESS_EXITING` is set — the flag the SDK signal handler sets synchronously as its first action. The `sdk.ts` teardown comment now says which deaths each teardown path covers. New unit tests pin both sides: flag set → three exits, counter 0, no auto-recovery destroy; flag unset → counted.
+- In-range lockfile refresh from the 1.3.0 install: nothing else moved.
+
 ## [1.7.11] - 2026-10-10
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lincoln504/pi-research",
-  "version": "1.7.11",
+  "version": "1.7.12",
   "description": "Web research for your agents with smart and safe tooling + knowledge store",
   "type": "module",
   "private": false,
@@ -119,11 +119,11 @@
     "image": "https://raw.githubusercontent.com/Lincoln504/pi-research/main/docs/media/hero.png"
   },
   "dependencies": {
+    "@camoufox/camoufox": "^0.5.7",
     "@kreuzberg/html-to-markdown-node": "^3.7.2",
     "@lancedb/lancedb": "0.39.0",
     "apache-arrow": "21.1.0",
     "bgutils-js": "^4.0.3",
-    "@camoufox/camoufox": "^0.5.7",
     "esbuild": "^0.28.2",
     "impit": "0.14.5",
     "jsdom": "^30.1.0",

package/src/core/pi-version.ts

@@ -130,8 +130,25 @@ export const PI_MIN_VERSION: SemverParts = { major: 0, minor: 99, patch: 0 };
  * and an optional `AuthProvider.agentName`; `@earendil-works/pi-tui` adds the OSC 7501
  * program-status helpers and `Text.setPaddingX`. `docs/extensions.md` is unchanged,
  * and nothing was removed or re-signed, so the 0.99.0 floor is unchanged too.
+ *
+ * 1.2.0 and 1.3.0 (2026-10-12 / 2026-10-15) were verified on 2026-10-17 by diffing
+ * the installed declaration trees of all three packages, 1.1.0 against 1.3.0:
+ * `@earendil-works/pi-coding-agent`'s extension surface file
+ * (`dist/core/extensions/types.d.ts`) changes in exactly four places: `BeforeAgentStartEvent`
+ * becomes a `messageType`-discriminated union (`BeforeAgentStartUserEvent` / `BeforeAgentStartCustomEvent`)
+ * because `before_agent_start` now also fires for idle `pi.sendMessage(..., { triggerTurn: true })`
+ * runs, `ToolNamespace` gains `aliases?`, `ToolDefinition` gains `reachesTools?`, and `ToolInfo`
+ * picks up `reachesTools`. `@earendil-works/pi-ai` removes the `assistant-message-frame`
+ * module (`AssistantMessageFrame*`, `reduceAssistantMessageFrames`) — a breaking removal this
+ * package never imports — and adds the OpenRouter routing schemas and
+ * `splitErrorToolResultImages`; its thinking-level types move to `providers/model-schema.d.ts`
+ * but are re-exported from the root unchanged. `@earendil-works/pi-tui` adds the fake-cursor
+ * helpers (`renderFakeCursor`, `FAKE_CURSOR_START/END`) and is otherwise unchanged.
+ * Nothing this package consumes is removed or re-signed; the four type-checks pass against
+ * 1.3.0 (TypeScript 6 and 7, src and tests), and `typebox` still pins 1.3.27 in `pi-ai`
+ * and `pi-coding-agent`, so the lockstep rule and the 0.99.0 floor are unchanged.
  */
-export const PI_TESTED_MAX_VERSION: SemverParts = { major: 1, minor: 1, patch: 0 };
+export const PI_TESTED_MAX_VERSION: SemverParts = { major: 1, minor: 3, patch: 0 };
 
 export type PiCompatibilityLevel = 'ok' | 'unparseable' | 'too-old' | 'untested';
 

package/src/infrastructure/browser/worker-pool-manager.ts

@@ -340,7 +340,17 @@ export class WorkerPoolManager implements IService {
                         // the 2026-09-01/02 logs coincided with SDK SIGTERM shutdown, tripping
                         // "3 consecutive exits → pool unhealthy" once per dying session. Not a
                         // queue-capacity or OOM problem: zero exits occurred during live research.
-                        if (code !== 0 && !this.isShuttingDown && this.poolEpoch === myEpoch) {
+                        //
+                        // The mid-shutdown flag alone does NOT cover process-GROUP signals: a cron
+                        // wrapper like `timeout N` SIGTERMs the whole process group, so the
+                        // workers die in the same instant as the master — BEFORE the pool's own
+                        // shutdown() runs and sets isShuttingDown (the scheduler reaches
+                        // workerPoolManager.shutdown() only after service lookups, a state read
+                        // and server.stop()). The SDK signal handler sets PI_PROCESS_EXITING
+                        // synchronously as its first action (sdk.ts _onSignal), before any
+                        // teardown await, so any exit arriving after that flag is teardown
+                        // noise on a dying process, not a health fault.
+                        if (code !== 0 && !this.isShuttingDown && !process.env['PI_PROCESS_EXITING'] && this.poolEpoch === myEpoch) {
                             logger.error(`[WorkerPoolManager] Worker exited with code ${code}`);
                             this.consecutiveErrors++;
                             if (this.consecutiveErrors >= 3) {

package/src/sdk.ts

@@ -365,8 +365,14 @@ async function _doInit(options: ResearchSDKOptions = {}): Promise<void> {
     // sdk_shutdown cleanup list is empty ("No cleanup tasks registered"), and the scheduler's cluster workers died mid-DAG-disposal —
     // with code null — while the worker pool was still live, which the pool's
     // exitHandler counted as unexpected deaths ("3 consecutive exits → pool
-    // unhealthy") on a process that was exiting anyway. Shutting down here puts
-    // those deaths inside the pool's intentional-destroy window instead. Both
+    // unhealthy") on a process that was exiting anyway. For a signal received
+    // by the master only, shutting down here puts those deaths inside the
+    // pool's intentional-destroy window. A process-GROUP signal (e.g. `timeout
+    // N` from a cron wrapper) SIGTERMs the workers in the same instant the
+    // master runs its handler, so those deaths land BEFORE this task starts —
+    // they are silenced instead by the PI_PROCESS_EXITING flag the handler
+    // sets synchronously as its first action (see the exitHandler in
+    // worker-pool-manager.ts). Both
     // teardown paths are idempotent (the later DAG dispose no-ops), and the task
     // is bounded well inside the 15s signal force-exit deadline. Registered per
     // init: runCleanup detaches the task set after running, so re-init gets a