docs(teams): publish setup and validation guides

[NeoHsu]

Important

Stacked draft: logical base stack/teams-12-operator-cron is PR #1504. GitHub requires an upstream PR base to exist in openabdev/openab, so this draft temporarily targets main and may show preceding stack layers. Do not merge it until #1504 is merged and this branch is rebased onto current main; then review only its single incremental commit.

What problem does this solve?

Give operators accurate entry points and publish sanitized current/historical Teams validation evidence without turning mutable observations into architecture authority.

Discord Discussion URL: https://discord.com/channels/1491295327620169908/1491365158868619404/1531339032527765655
Microsoft Teams roadmap discussion.

Review Contract

Goal

Give operators accurate entry points and publish sanitized current/historical Teams validation evidence without turning mutable observations into architecture authority.

Non-goals

No runtime behavior, new tenant test, credential, raw log, screenshot copy, identifier, endpoint value, or ADR status change is introduced.

Accepted Residual Risks

GroupChat and Team-channel UI cases remain skipped where no safe tenant was available; historical records can become stale and therefore point readers to the current matrix.

Acceptance Criteria

Root routing reaches both Teams setup guides; configuration and deployment examples match source defaults; current versus historical evidence is clearly separated; privacy guards hold; fixture provenance and hashes verify; all local links and validation gates pass.

Follow-ups

Complete the skipped live matrix only with a safe tenant and explicit authorization; track reminder authority, ambient reading, sovereign endpoints, and richer file paths in separate proposals.

At a Glance

N/A — this PR changes documentation only; it introduces no runtime flow.

Prior Art & Industry Research

Not applicable — this is a documentation-only decision or guidance slice. The ADRs and guides cite the authoritative Microsoft and repository sources used for their claims.

Proposed Solution

• Publish root routing, self-hosted and enterprise setup, configuration, cron, attachment, command, and schema guidance.
• Add the current validation matrix plus sanitized historical records outside the ADRs.
• Preserve main control-plane documentation, openab-cp, chart 0.10.0-beta.3, and existing Docker guidance.

Why this approach?

Separating durable ADRs from mutable guides and evidence keeps architecture review stable while allowing operational status to evolve.

Alternatives Considered

Embed implementation chronology and tenant evidence in ADRs (rejected: it becomes stale) or publish no routing guide (rejected: operators cannot discover the supported path).

Validation

• Core all-features: 827 passed, 1 explicitly skipped pre-existing environment-sensitive secret test
• Gateway Teams: 400 unit + 2 conformance passed
• Root all-features: 50 passed; cargo check --all-features passed
• Platform Schema: 4 unit + 13 conformance + 3 Teams manifest passed
• ACK-loss harness: 14 passed
• Bounded Clippy for Core, Gateway, and root: passed with -D warnings
• Helm lint/renders, TOML/JSON/hash, local links/anchors, privacy scan, doc form audit, and git diff --check