This PR was split from #34532 to keep #34532 strictly docs/examples only.

Greptile Summary

This PR cleanly splits low-risk, non-documentation changes out of #34532. All changes are minimal and safe:

• Schema documentation: Added a clarifying comment in pi-tools.schema.ts documenting that Google endpoints validate Gemini-compatible tool schemas (documentation-only).
• Test coverage: New test file correctly verifies existing normalizeToolParameters behavior—that Gemini providers (including google-antigravity) strip unsupported keywords like patternProperties, while other providers (anthropic) preserve full schema compliance.
• Test resilience: Refactored brittle exact-equality assertions in commands.test.ts to use expect.objectContaining() for partial matching, with added toHaveLength() safety checks.
• Package.json alignment: Removed peerDependenciesMeta from both googlechat and memory-core extensions—a cosmetic cleanup that aligns two private packages with all other extensions in the monorepo (none of which use this field).

No runtime behavior changes, all updates are low-risk and code-quality focused.

Confidence Score: 5/5

• Safe to merge—no runtime behavior changes, tests are correct, and package.json edits are cosmetic alignment.
• All changes are low-risk and well-scoped. The schema comment is documentation-only. New tests correctly exercise existing logic without modifying behavior. Test refactoring uses standard partial-match assertions. Package.json changes are cosmetic alignment of private packages with monorepo conventions.
• No files require special attention.

_{Last reviewed commit: 4846b77}

CI note: the previous Bun lane failure was in setup (oven-sh/setup-bun returned 404 while downloading Bun), before tests executed. I pushed an empty retrigger commit to rerun checks.

Applied fix for the Bun lane instability:

• Updated .github/actions/setup-node-env/action.yml to use bun-version: "1.3.9" (valid release tag), replacing the invalid 1.3.9+cf6cdbbba value that produced 404 during oven-sh/setup-bun download.

Result: the Bun check now passes in this PR run.

Quick follow-up: the peer optionality concern has been applied.

• peerDependenciesMeta.openclaw.optional: true is restored in:
  • extensions/memory-core/package.json
  • extensions/googlechat/package.json
• Commit: 5b54443

This keeps direct extension installs from hard-failing on peer resolution.

Status update: peerDependenciesMeta.openclaw.optional: true remains restored for extension packages, and this branch is currently green and conflict-free from my side.

If maintainers are aligned with the split scope, this should be ready for final review.