Gemini 3.1 Pro Preview may emit parts with only thoughtSignature
and no text content, causing the stream to stall. Emit a
thinking_signature event to keep the stream active, and start
a thinking block when these parts arrive before any text.
Fixes#76071
* fix: raise Gemini 2.5 minimal thinking budget from 128 to 512
Google raised the minimum thinkingBudget for Gemini 2.5 Pro and Flash
models to 512. The hardcoded minimal: 128 now causes a 400 INVALID_ARGUMENT
("The thinking budget 128 is invalid. Please choose a value between 512
and 24576.") on every heartbeat using gemini-2.5-flash-lite with minimal
thinking.
* test(google): assert thinkingBudget minimum of 512 for Gemini 2.5 models
Add parametrized tests covering minimal/low/medium budget tiers for
gemini-2.5-flash-lite, gemini-2.5-flash, and gemini-2.5-pro — ensures
the 128→512 floor change is regression-tested.
Pre-existing typecheck failure in src/agents/model-auth.ts (TS2322) is
unrelated; confirmed present on upstream main without our changes.
Tests validated: pnpm test extensions/google/transport-stream.test.ts (21 pass).
* test(google): fix it.each format string placeholder order
* fix(google): narrow Gemini 2.5 minimal budget floor to flash-lite only
Simplify plugin installation and runtime loading around package-manager-owned dependencies, with Jiti reserved for local/TS fallback paths.
Also scans npm plugin install roots so hoisted transitive dependencies are covered by dependency denylist and node_modules symlink checks.
Tighten Google Vertex ADC manifest evidence to canonical project env vars and canonical ADC fallback paths only.
Local proof:
- OPENCLAW_VITEST_MAX_WORKERS=1 pnpm test src/agents/model-auth.profiles.test.ts src/plugins/manifest-registry.test.ts src/secrets/provider-env-vars.dynamic.test.ts
- pnpm exec oxfmt --check --threads=1 docs/plugins/manifest.md extensions/google/openclaw.plugin.json src/agents/model-auth-env.ts src/agents/model-auth.profiles.test.ts src/plugins/manifest.ts
- git diff --check origin/main...HEAD
CI note: checks-node-core-support-boundary was red on an unrelated tooling assertion in test/scripts/test-projects.test.ts for packages/sdk/src/index.test.ts routing; that file and scripts/test-projects.mjs are unchanged from origin/main.
