chore: update agent history files for Teams integration

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: Copilot

.squad/agents/linus/history.md

@@ -104,3 +104,11 @@ All code roles now use `claude-opus-4.6`. Docs/Scribe/diversity use `gemini-3-pr
 - PR conflict resolution for `copilot/migrate-copilot-client-usage` in `internal/execution/copilot_test.go` should keep the `TestCopilotExecute_InitializePropagatesStartError` variant from main to preserve startup error propagation coverage.
 - Teams Graph API channel messages POST to `/v1.0/teams/{groupId}/channels/{channelId}/messages` with body `{body:{contentType:"html",content:"..."}}`. `az rest` auto-injects bearer tokens for graph.microsoft.com endpoints.
 - Squad notification scripts live in `.squad/scripts/` and config in `.squad/identity/teams-config.json`. The notify script always exits 0 to be safe for caller pipelines.
+
+## 2026-03-12: Teams Notification System
+
+Created `.squad/scripts/teams-notify.sh` and `.squad/scripts/teams-test.sh` for Microsoft Teams notifications via Graph API. System sends milestone updates (work batches, PRs, issues, decisions) to the "Waza Squad" Teams channel.
+
+**Key decisions:** Always exit 0 (failures never block automation), jq with grep/sed fallback for JSON, HTML content escaping for security, config-driven event filtering, TEAM_ROOT auto-detection.
+
+**Outcome:** Test notification verified in Teams channel. System ready for production use by Scribe and all agents.

.squad/agents/livingston/history.md

@@ -125,3 +125,11 @@ The Teams notification system that the squad uses to communicate milestones to t
 - Added troubleshooting decision tree with specific `az` commands to test
 - Clarified graceful degradation (no errors, no noise when disabled)
 - Included configuration checklist with pre-flight items
+
+## 2026-03-12: Teams Notification Skill Documentation
+
+Created `.squad/skills/teams-notify/SKILL.md` for the Teams notification system. Documented purpose, all event types, usage patterns, configuration, examples, and troubleshooting.
+
+**Integration points:** Scribe calls this for work batch notifications. Coordinator can use for orchestration milestones. All agents can trigger for their work.
+
+**Outcome:** Comprehensive documentation complete and integrated.