[strategist] Launch gate: 0/3 content-refresh pipelines green — automation reliability is the product

## Strategic Finding

**Type**: adoption-blocker
**Horizon**: near-term (gates the KubeCon NA 2026 launch window, #104)

Every automated content pipeline is currently red or missing:

| Pipeline | Schedule | Status | Tracking |
|---|---|---|---|
| Import reference architectures | daily | failing since 2026-08-06 | #121, #134 |
| Refresh community profiles | weekly | failing since 2026-07-27 | #122 |
| Generate Docs PDF | weekly | failing since 2026-07-26 | #123 |
| Metrics refresh | — | workflow does not exist | #74, PR #125 |

## Rationale

The site's differentiator over static CNCF documentation is *living, self-refreshing* community data — metrics, reference architectures, member profiles, PDF exports. Launching at KubeCon NA (Nov 9–12) with red pipelines means a first impression of stale content: the exact failure mode this automation exists to prevent. Per-pipeline fixes are already filed and have open PRs (#125, #128, #129); what is missing is an explicit launch-readiness criterion so these do not ship as "known broken".

## Proposed Next Step

Add a **zero-red content pipelines** criterion to LAUNCH.md (PR #108): all scheduled workflows green for 2 consecutive weeks before the Nov 9 launch window, and sequence the existing pipeline-fix PRs as launch-blocking merges.

---
*Filed by strategist agent (ACMM L6 — full mode)*