Greptile Summary

This PR closes the gap that prevented the blockStreaming config option from having any effect on the Microsoft Teams channel. Three root causes are addressed cleanly: the missing blockStreaming field in MSTeamsConfigSchema, the absent blockStreaming property in MSTeamsConfig, and the failure to propagate disableBlockStreaming through replyOptions to the downstream block-reply pipeline.

Key changes:

• zod-schema.providers-core.ts: adds blockStreaming: z.boolean().optional() to MSTeamsConfigSchema, matching every other channel schema
• types.msteams.ts: adds the corresponding blockStreaming?: boolean TypeScript property with JSDoc
• message-handler.ts: spreads disableBlockStreaming into replyOptions using !msteamsCfg.blockStreaming when the field is explicitly boolean and undefined otherwise — identical to the Discord pattern, correctly falling through to blockStreamingDefault when unset
• block-streaming-config.test.ts: five schema-level tests covering the expected cases

One minor style note: the test file uses a bare top-level await import(...) instead of a static import, which is unconventional compared to other tests in this extension.

Confidence Score: 5/5

Safe to merge — the fix is minimal, targeted, and mirrors the existing Discord implementation exactly.

All three root causes are properly addressed, the logic in message-handler.ts matches the Discord reference implementation, no existing behavior is altered when blockStreaming is unset (falls through to undefined), and the new tests exercise the schema correctly. The only finding is a P2 style note about the top-level await import in the test file, which does not affect correctness or runtime behaviour.

No files require special attention.

This is a comment left during a code review.
Path: extensions/msteams/src/block-streaming-config.test.ts
Line: 4

Comment:
**Prefer a static import over top-level `await import`**

The top-level `await import(...)` at module scope is unusual for this codebase — other test files use normal static imports (or `await import` inside `it()` blocks for mock-isolation purposes). Since the schema file has no side effects that need lazy loading and there's no mock isolation needed here, a regular static import is simpler and more idiomatic:

```suggestion
import { MSTeamsConfigSchema } from "../../../src/config/zod-schema.providers-core.js";
```

If there is a specific circular-dependency or import-chain reason that requires dynamic import, a `beforeAll` block would be more conventional than bare top-level await.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(msteams): wire blockStreaming config..." | Re-trigger Greptile}