Feature request: Microsoft Teams support (as an alternative to Slack)

## Summary

Our team is interested in running the on-call kit against **Microsoft Teams** instead of Slack, and would like to know whether Teams support is on the roadmap.

## Context

The kit is currently built around **Claude Tag** (Slack app: identity, per-channel memory, and session/thread model), which appears to be Slack-only today — we found no mention of Teams support in the public docs or the [AI in CI/CD & on-call blog post](https://claude.com/blog/ai-ci-cd-on-call).

We did an internal feasibility pass before opening this issue. Summary of what we found:

**No native Teams equivalent exists today.** Claude Tag's session/identity/memory model has no Teams counterpart we're aware of.

**What a Teams version would need:**
1. Custom bot infrastructure (Microsoft Bot Framework / Graph API) wired to the Claude API, to replicate what Claude Tag provides natively in Slack (persistent sessions, per-channel identity, memory).
2. Re-mapping several Slack-specific mechanics that don't have a direct Teams equivalent:
- Threads → Teams' reply-chain model behaves differently; session/state logic would need rework.
- Canvas (used for live routine/status docs) → would need a substitute (e.g. a Wiki tab or pinned Adaptive Card).
- `@`-mention / DND-based escalation logic → currently encodes Slack-specific assumptions that would need to be re-derived for Teams' notification model.

**What's already portable:** the kit's actual content — triage playbooks, policies, incident logging (`lessons.md`), and the `STACK.md` capability-binding pattern — is markdown-based and platform-agnostic. Only a handful of files (setup/weather/handoff skills, `ONCALL.md`/`routines.md` templates, the Tag setup doc) carry Slack-specific logic and would need re-platforming.

## Ask

Is Teams support (via Claude Tag or an equivalent) on Anthropic's roadmap?

Happy to share more detail on our feasibility analysis if useful.