feat(adapters/msteams): land Microsoft Teams adapter as experimental (needs live-tenant validation)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with the 10-point live-validation checklist in draft PR #4 and ADR 0007; this requires access to an Azure Bot registration and Teams tenant. Record the confirmed findings in ADR 0007, mark adapters/msteams/doc.go as experimental, then verify CI and the requested reviews before merging PR #4.
Written by the indexing model from the issue text.
Description
Track landing the Microsoft Teams adapter (adapters/msteams) at the experimental tier, per ADR 0007.
Status
A high-quality spike exists as draft PR #4: self-contained (zero core-runtime changes, zero new dependencies), stdlib-only Bot Framework JWT/JWKS verification, versioned opaque thread IDs carrying conversationReference, reuse of internal/ratelimit and the Observer hooks, ~78% statement coverage against a mocked Bot Framework server.
The spike resolved ADR 0007 open question 9 (no msbotbuilder-go; hand-rolled stdlib JWT validation works, no new deps). The remaining 9 of 10 open questions require a live Azure Bot registration + Teams tenant to validate (ack/turn semantics, endorsement behavior on production keys, markdown fidelity, serviceUrl/conversation-id stability, proactive posting prerequisites, aadObjectId stability, etc.). See the 10-point checklist in PR #4.
Path to land
- A human with Azure Bot + Teams tenant access runs the live validation checklist from PR #4.
- Update ADR 0007 →
Accepted, recording confirmed findings. - Mark the package experimental in
adapters/msteams/doc.go(honest tier labeling). - Undraft PR #4, pass CI +
@codex review+@codex security review, merge.
Blocked on: live-tenant access (human).
Generated with mux • Model: anthropic:claude-fable-5 • Thinking: xhigh
- Dominant language
- Go
- Stars
- 2
- Forks
- 0
- Avg merge
- 18h 33m
- Merged PRs (30d)
- 26
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/chat
-
enhancement ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 34/100
Maintainers usually reply within 1 day
Similar issues
-
ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
evcc-io/evcc#35605 · 1 comment ·
Maintainers usually reply within 1 day
-
bug report
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nightgauge/nightgauge#2732 ·
Maintainers usually reply within 1 day
-
fix below CVEsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 5 days
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100