[strategist] peoplehub is 53 days dormant with 12 mergeable PRs queued — decide: revive, pause, or archive

## Strategic Finding

**Type**: priority-shift / adoption-blocker
**Horizon**: near-term

peoplehub's default branch has not been pushed to since **2026-06-16 (54 days)**, yet the agent fleet has queued **14 mergeable PRs** against it (up from 12 when filed) — including a build fix (#45: missing `getOrgMembers` export, build broken — duplicated by #29), feature work (#48 social feed, #42 MCP server, #41 ≡ #57 Slack bots, #43 tool-of-the-day, #44 AI-pillar curation), and dependency bumps dating back to 2026-05-01. The fleet is spending compute and the human gate's attention on a repo whose project trajectory is undecided.

## Rationale

- Agent work on a dormant repo is negative-expected-value: PRs rot, rebase churn accumulates, and every sweep re-reports them (see #58, #81).
- The build is broken on the default branch and the fix exists twice (#29 ≡ #45, filed 3 months apart) — the site is likely not deploying, so feature PRs on top of a broken base are unverifiable.
- The hive App currently cannot push to peoplehub (installation scope is endusers-only), so agent PRs there may be stranded regardless.
- An explicit decision — revive (merge the build fix, set a cadence), pause (stop agent work, close stale PRs), or archive — turns 14 open loops into one decision.

## Proposed Next Step

Decide peoplehub's status and record it (a short ADR or a note in the hive repo-audit config):
1. **Revive**: merge #45 (build fix) first, close dup #29, then triage the remaining 12 by value.
2. **Pause**: close agent PRs older than 30 days, label the repo paused in hive config so agents stop filing against it.
3. **Archive**: archive the repo and remove it from the agent fleet's scope.

---
*Filed by strategist agent (ACMM L6 — full mode); updated in place 2026-08-08 sweep 6*