ado-pr-teams-notify

ADO pull requests → one card per PR in a Teams channel

Azure DevOps Service Hooks (4 per repo) ──HTTP POST──▶ Power Automate flow (Teams "webhook alerts" template, one URL)
   created · commented · updated(any type)          │ Switch on eventType
                                                                   ├─ created   → post root card            (skip drafts)
                                                                   ├─ updated   → update root card + 1-line reply
                                                                   └─ commented → update root card + 1-line reply (quote)

Result in Teams: one main card per PR (updated in place) + one short reply per event (bumps the thread to the bottom of the channel and notifies). The card shows what a reader needs without opening the thread. Layout and exact copy: references/card-and-copy-spec.md. Architecture and the reasoning behind each choice: references/architecture.md.

What you need before starting (ask the user for anything missing)

Browser: any of ego-browser, Playwright, Chrome DevTools MCP works; mapping in references/browser-adapters.md.

Phases

1. Create the template flow (Teams). In the target channel use Workflows → "Send webhook alerts to a channel". This yields a flow with a Teams-webhook trigger, a connection, and the webhook URL (HTTP POST URL of the trigger). Record: team id (groupId), channel id (19:…@thread.tacv2), flow id, webhook URL. (The ids are also visible in the flow's code view / the Teams channel link.)
2. Export the template (flows/<id>/export → name → Export → Download; zip) and unzip it.
3. Generate the merged flow and import it over the template:

   python3 scripts/gen_flow_definition.py --export-dir <unzipped export> --config config.json --out-dir build
   

   (config.json: copy scripts/config.example.json.) It writes build/ and flow-package.zip. Import with My flows → Import → Import Package (Legacy): upload the zip; flow row = Update → pick the existing flow; connection row = Select during import → your Teams connection; Save; Import. After import the flow is Off: open its details page and turn it On. The final Import click may be blocked by an auto-mode safety classifier for agents; if it is, stage everything and ask the human to click Import once.
4. Create the Service Hooks (4 per repo, all to the same webhook URL):

   export ADO_PAT=…; python3 scripts/ado_hooks.py create --org ORG --project PROJ --webhook-url URL --repo hubs=master --repo infra=main
   

   No PAT? Run the same REST calls inside a logged-in ADO tab (recipe in references/ado-rest.md). The comment hook gets the same target-branch filter as the others so comments follow only PRs that were announced.
5. Verify with a state sequence: scripts/build_test_payloads.py then scripts/send_event.sh URL …; read the card text back from the Teams page after each step (test plan and expected values: references/test-plan.md). Report results as text unless the user wants screenshots.
6. Hand over: tell the user what remains manual (Import click, deleting test posts, anything only a human could verify such as how the colors render) and give them references/card-and-copy-spec.md as the "what RDs will see" description.