chore(deps): bump pi-ai to 0.84.2 and thread abort signals through OAuth

[pkieltyka]

Bumps @earendil-works/pi-ai from 0.83.0 to 0.84.2 and adapts to its new OAuth API, plus routine dependency updates.

Dependency updates

• @earendil-works/pi-ai: 0.83.0 → 0.84.2 (newly pulls in @earendil-works/pi-telemetry)
• smol-toml: 1.7.1 → 1.8.0
• web-tree-sitter: 0.26.11 → 0.26.12
• @types/node: 26.1.2 → 26.2.0
• tsx: 4.23.4 → 4.23.12

Code changes (pi-ai 0.84 API)

• src/llm/pi-runner.ts: OAuth token refresh now receives the request AbortSignal. GetOAuthApiKey, resolveModelAuth, and getOAuthApiKeyFromProvider thread the signal through to oauthAuth.refresh(credential, signal), so token refreshes can be cancelled when the request is aborted.
• src/provider/provider-services.ts: commandLogin creates an AbortController for the login interaction, passes its signal to oauthAuth.login(...), and aborts it in the finally block when the flow ends.
• Tests: phase4-llm.test.ts asserts the request signal is propagated to the OAuth refresh callback; phase4-skills-provider.test.ts uses the renamed ProviderAuthInteraction type and asserts the login signal is aborted after login completes.

Verification

• pnpm vitest run tests/phase4-llm.test.ts tests/phase4-skills-provider.test.ts — 154 tests passed

[github-actions]

🧞 Codegenie Review

✅ No credible findings.

Coverage

Reviewed 13/66 hunks.
Incomplete work: skipped 53.
Coverage levels: deep 7, normal 5, light 1, skip 53.

• pnpm-lock.yaml: lockfile

🙋 Needs Human Attention

• Does the repo lockfile (package-lock.json / bun.lock / pnpm-lock.yaml) contain matching entries for @earendil-works/pi-ai 0.84.2, smol-toml 1.8.0, web-tree-sitter 0.26.12, and @types/node 26.2.0?

  • Files: package.json
  • Symbols: @earendil-works/pi-ai, @types/node, smol-toml, web-tree-sitter
  • Reason: Packet reviewer could not resolve this question from the reviewed context.

• Is signal a required (non-optional) property of ProviderAuthInteraction in @earendil-works/pi-ai? If it is optional, expect(loginSignal.aborted) at tests/phase4-skills-provider.test.ts:716 would be a type error and the test could crash at runtime when the SDK omits signal.

  • Files: tests/phase4-skills-provider.test.ts
  • Symbols: ProviderAuthInteraction, commandLogin, testOAuthAuth
  • Reason: Line 716 dereferences interaction.signal without optional chaining while line 744 uses loginSignal?.aborted, implying possible optionality; the declaration lives in an external package that could not be read before budget exhaustion.

Stats

• 🤖 Model: anthropic claude-opus-5 high
• 🧞 Codegenie: v0.5.5 (2f9902813c)
• Elapsed time: 2m 31s
• Git: 0xPolygon/codegenie from master to pi-bump (16d2325657)
• Review completeness: complete.
• Usage: model calls 28, tokens 488854, cost $1.9430.
• Effective caps: tokens 8000000.
• Local context pressure: 6 degraded tool results, 3 degraded hunks.

✅ No Findings

No credible findings were found. Everything looks good.

— View Workflow Job