Greptile Summary

This PR adds a comprehensive host-side implementation guide and example for a Teams DM academic assistant MVP that consumes an external Canvas LMS community plugin, alongside targeted code changes (a schema normalization comment, new test coverage, improved test assertions, and a peer dependency version bump).

New documentation (teams-academic-chat-canvas-mvp.md, teams-academic-chat-mvp-example.md): Clear Mermaid architecture diagrams, detailed security guidance (DM-only rollout, minimum OAuth scopes, encrypted token storage, rate limiting, audit logging), end-to-end flow walkthrough, and multi-stage rollout guidance. Both files correctly position Canvas access as an external plugin concern with no changes to OpenClaw core.

docs/channels/msteams.md / docs.json: Cross-reference links to the new guides are correctly added with matching file paths.

src/agents/pi-tools.schema.ts: Single clarifying comment added noting that Google endpoints (including google-antigravity) validate Gemini-compatible tool schemas — no logic change.

src/agents/pi-tools.schema.test.ts: New test file with two test cases confirming that normalizeToolParameters correctly strips patternProperties for Google-prefixed providers while preserving it for Anthropic, consistent with the implementation's Gemini-compatibility behavior.

src/plugins/commands.test.ts: Assertions refactored to use expect.objectContaining + toHaveLength, removing brittle exact-match expectations that would fail if getPluginCommandSpecs() returns additional fields (e.g., acceptsArgs).

extensions/googlechat/package.json / extensions/memory-core/package.json: Peer dependency minimum bumped from >=2026.3.1 to >=2026.3.2; lockfile updated accordingly.

All changes are low-risk and scoped appropriately. The documentation is clear, the code changes are minimal and correct.

Confidence Score: 4/5

• This PR is safe to merge; all code changes are low-risk (clarifying comment, new test coverage, improved assertions, and a peer dependency bump).
• The PR is well-scoped with clear documentation, correct test logic, and benign code changes. The new documentation properly bounds Canvas access as an external plugin concern. Tests are logically sound and the dependency version bump is appropriately propagated. No runtime risks identified.
• No files require special attention.

_{Last reviewed commit: 7685367}

This PR has been narrowed back to docs/examples only. Unrelated low-risk code/test/dependency changes were split into #34568 to keep scope clean.

Hi maintainers,

Could you please take a look at this PR and consider reviewing and merging it?

It would help me a lot with the Canvas LMS integration I am currently developing on top of OpenClaw.

Thanks.