[strategist] Community/TAB membership currency: refresh workflow exists but no staleness signal

## Strategic Finding

**Type**: roadmap-gap (Phase 1 pillar: community)
**Horizon**: mid-term

`refresh-community-people.yml` exists and `data/community-people.json` / `members.json` are generated — good. But ROADMAP.md Phase 1 asks for "current TAB membership, End User Groups, and engagement pathways," and there is no freshness indicator or validation gate: if the refresh workflow silently fails or the upstream source changes shape, the site shows stale membership indefinitely (cf. the metrics staleness found in #74).

## Rationale

Membership data is the second "content accuracy" class in GOVERNANCE.md (human-review always). The community section lists seven user groups (financial services, public sector, research, telecom, transportation, cartografos, end-user community) — their currency is unverified. A visible "last updated" signal converts silent staleness into an actionable signal and matches the freshness-indicator pattern ROADMAP.md already asks for on architectures.

## Proposed Next Step

Add a generatedAt/freshness display to the community and members pages sourced from the data files, and a validation check that fails the build when community-people.json exceeds a staleness threshold. Verify each listed End User Group still has an active upstream page. Acceptance: membership pages show their data age, and a stale refresh breaks the build loudly instead of silently.

Tracks ROADMAP.md Phase 1 / issue #59.

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

Start with refresh-community-people.yml and the generated data/community-people.json and members.json, then trace where the community and members pages consume that data. Define the data-age display and the stale-data validation against the issue's acceptance criteria, including upstream End User Group links, and verify the build fails when the threshold is exceeded.

Written by the indexing model from the issue text.