[strategist] Cross-repo: 50+ mergeable PRs stranded on repos the hive App cannot see as a fleet

## Strategic Finding

**Type**: adoption-blocker / ecosystem-opportunity
**Horizon**: near-term

The hive fleet's merge-eligible report lists **62 open, mergeable PRs across five repos** — but they are siloed per-repo. bootc-ecosystem alone has 27 mergeable PRs (feature work, security fixes, dependency bumps); endusers 13; peoplehub 12; firehose 6; cncf-darkmode 4. There is no cross-repo view that lets the single human gate (GOVERNANCE.md's merge policy) triage by *value* rather than by repo.

## Rationale

Issue #58 documented the queue-outpaces-capacity problem for this repo; the same dynamic is fleet-wide and worse elsewhere. **peoplehub's last push was 2026-06-16 — 53 days dormant — yet 12 mergeable PRs (including a build-fix, #45) are queued against it.** PRs landing on a dormant default branch may be wasted work. The fleet is producing work faster than any one repo's queue shows. A weekly cross-repo triage digest — mergeable PRs ranked by class (security > bugfix > feature > deps) and age — would let the human gate spend limited review time where it matters, and would surface repos whose queues have effectively stalled.

## Proposed Next Step

Add a weekly cross-repo merge-queue digest to the hive advisory report (#23/#24): per-repo counts of open/mergeable/conflicting PRs, oldest-PR age, days-since-last-push, and a security-first ordering. Acceptance: the advisory issue shows fleet-wide queue health without anyone opening five repo tabs.

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

Start by reading the hive advisory report work in issues #23/#24 and the merge policy in GOVERNANCE.md. Define the weekly digest around the stated per-repo counts, oldest-PR age, days-since-last-push, and security-first ordering; it is done when the advisory issue shows fleet-wide queue health without opening five repo tabs.

Written by the indexing model from the issue text.