docs(teams): split meetings setup from operator runbook#21412
Conversation
37de7a7 to
5aa3226
Compare
|
Leaving the same note on the other PRs in the stack for visibility. Could you retarget this PR's base branch so diffs are incremental instead of cumulative? Full detail in #21408 (comment) but tl;dr:
Planning to review bottom-up from #21408. Thanks. |
5aa3226 to
f0fb98b
Compare
|
Merged via PR #22042. Your two commits ( One follow-up added on top during salvage:
That closes the entire stack (#21408 foundation → #21409 webhook listener → #21410 pipeline runtime → #21411 outbound delivery → #21412 docs + skill). All five PRs merged with your authorship preserved on every commit you wrote. Thanks for taking the initial review direction on #19815 seriously and splitting the work up the way you did — it made reviewing much easier. |
References PR #19815.
This is the fifth and final part of the Microsoft Teams meeting pipeline stack, split out in response to maintainer review on the original PR.
This slice is intentionally scoped to:
skills/productivity/teams-meeting-pipeline/SKILL.mdasset for the CLI + skill workflowThis follows the maintainer review direction to keep setup and environment guidance on the main page while moving operator runbook/checklist material into a dedicated guide, and to route operator usage through the CLI + skill pattern rather than exposing extra model tools.
The goal here is to keep the final docs and skill follow-up isolated from the runtime and delivery code paths.
Review and merge in stack order.