Daily Org Oversight Report — 2026-05-29 (UTC)

[fro-bot]

Scope: all repositories in the fro-bot GitHub organization. Data pulled via gh at run start. Links only; no content duplication.

Previous report: #3382.

The merge queue is moving — manually. Yesterday's 4 stuck agent Renovate PRs all merged overnight, plus the v0.46.0 release shipped. But Renovate spawned 4 new PRs today and every single one is back at REVIEW_REQUIRED + BLOCKED. The drain works; the root cause (#3369) hasn't been fixed, so this is a daily manual operation now. Meanwhile Merge Data Branch hits day 11 with no retry, and the audit cluster hasn't been touched since 2026-05-20 (9 days, the dust is real).

Summary metrics

Metric	Count	Δ vs yesterday
Repositories scanned	5 (tokentoilet archived)	—
New issues (last 24h, org-wide)	1 (.github#3383 autohealing)	−2
Open issues, org-wide	32	0
Open PRs (org-wide)	6	−1
Aging PRs (>7d no activity)	1	0
Stale PRs (>14d no activity)	1	0
Stale issues (>30d no activity)	5	0
Failing main-branch workflows	2 (agent → Auto Release ~68d; .github → Merge Data Branch 11d since last green)	0
Open code-scanning alerts	8 (.github=3, agent=5)	0
Open Dependabot alerts	1 (agent brace-expansion CVE-2026-45149, no upstream fix)	0
agent PRs blocked on REVIEW_REQUIRED	5 (4 new today; yesterday's 4 all merged)	+1 net, full churn
Untriaged audit backlog from #3352	14 issues	0 (day 9 untouched since 2026-05-20)

Critical items

Repo	Item	Link	Recommended action
fro-bot/.github	Merge Data Branch red for 11 days. No retry since 2026-05-25.	latest failure	P0. Read the gate log → 🔒 Block private wiki pages step. The data-branch merge cadence has been abandoned for over a week. Two paths: patch or purge.
fro-bot/agent	5 new Renovate PRs all REVIEW_REQUIRED + BLOCKED (#691, #690, #689, #681, #668). Yesterday's batch all merged manually overnight, so the drain works. But #3369 is still unfixed, so this is now a daily ritual.	linked above	P0. Fix #3369 or accept the operational cost. Manual approval works as a stopgap.
fro-bot/.github	Governance bug #3369 — day 6. Discussion (2 comments, last 2026-05-25) went quiet.	#3369	The discussion stalled. Land a fix or close the issue with rationale.
fro-bot/agent	Dependabot #72 — day 5, still no upstream fix for brace-expansion CVE-2026-45149.	alert 72	Confirm; document.
fro-bot/.github	Privacy-gate cluster (P0, day 9 untouched since 2026-05-20).	#3326, #3327, #3328, #3345	#3327 matches the failing-log symptom.
fro-bot/.github	Reconciler cluster (P1, day 9 untouched).	#3319, #3320, #3332–#3337, #3340	One hardening pass.
fro-bot/.github	Social broadcast TOCTOU (P1, day 9 untouched).	#3325	Patch.
fro-bot/agent	Auto Release failing since 2026-03-22 (~68d red). Twelfth report.	run 23399265449	Delete.
fro-bot/agent	Scorecard (5). Carryover.	code scanning	Verify #13.
fro-bot/.github	Scorecard (3). Carryover.	code scanning	—

Aging PRs (>7d no activity)

Repo	PR	Age
fro-bot/systematic	#2 feat(deps): configure Renovate	33d

All 5 agent PRs are 0d (4 fresh today, 1 carried from yesterday). Heavy Renovate cadence; the dependency stream is healthy if the merge gate gets opened.

Stale issues (>30d no activity)

Repo	Issue	Age	Recommended next step
fro-bot/systematic	#1	81d	Decide or close. Twelfth report.
fro-bot/fro-bot.github.io	#1	81d	Close as N/A. Twelfth report.
fro-bot/.github	#3161, #3160, #3159	~38d	Triage.
fro-bot/.github	#2828 Dependency Dashboard	~300d	Renovate-managed; pin.

Unassigned bugs or high-signal issues

bug label still missing on fro-bot/.github.

Cluster	Issues	Days untouched	Current production impact
Privacy gates	#3326–#3328, #3345	9	Merge Data Branch red 11d
Reconciler correctness	#3319, #3320, #3332–#3337, #3340	9	observability gap
Social broadcast	#3325	9	latent privacy risk
Governance bug	#3369	6 (discussion stalled 4d)	daily manual approval ritual
Enhancement	agent#671	6	—
Wiki survey	.github#3380	1	—

Repo hotspots

1. fro-bot/.github — 29 open issues, Merge Data Branch red 11 days, the data-branch merge pipeline functionally dead.
2. fro-bot/agent — Renovate spawned 4 new PRs today; all blocked. The repo is producing dependency work faster than the broken merge gate can clear it.
3. fro-bot/systematic — Thirteenth report on the same orphaned PR (fix: add @fro-bot as a collaborator to prevent it from being "removed" #2, 33d) and issue (feat: set default settings #1, 81d). Listing the same items is now its own kind of fossil record.

Recommended actions (checklist)

• P0 (urgent — 11-day broken cadence): Read Merge Data Branch log → 🔒 Block private wiki pages. Decide.
• P0 (broken merge gate): Land #3369. Discussion stalled 4 days ago — converge or close.
• Today's manual stopgap: Approve the 5 stuck agent PRs as has been done daily.
• P0 (carryover): Recheck Dependabot #72 upstream.
• 30-second closes: fro-bot.github.io#1; .github#3161/#3160/#3159 if surveys done.
• 2-minute delete: agent → Auto Release workflow.
• Label hygiene: Create bug + security labels on fro-bot/.github.
• Carryover: Audit cluster (day 9 dust), systematic#2/#1, Scorecard.

---

Run Summary

• Event: schedule
• Repo: fro-bot/.github
• Ref: refs/heads/main
• Run ID: 26617308910
• Cache: hit
• Sessions used: ses_1c6ba9e0dffe7oK9VLD2oWDr9c (prior thread)
• Logical Thread: schedule-898cd73a
• Mode: branch-pr (single summary issue)
• Repos scanned: 5
• Data sources: gh issue list, gh pr list, gh api actions/workflows, gh api code-scanning/alerts, gh api dependabot/alerts, gh pr view --json