[Board Audit] Board Health Report — 2026-03-18

[github-actions]

Project: zircote/projects/1 | Repos scanned: 22 | Run: https://github.com/zircote/.github/actions/runs/23239578817

---

⚠️ CRITICAL LIMITATION — Project Board Inaccessible

All GitHub Projects v2 API calls returned 403 Forbidden (user project) or 404 Not Found (org project). The zircote-org-monitor GitHub App does not have Projects: Read/Write (user-level) permission. Board column data, item status, and cross-reference checks could not be performed.

Action required: Add Projects: Read/Write (user-level) to the zircote-org-monitor GitHub App installation. This was also flagged as a P2 action item in CI Health Report #339.

---

Board Summary

Column	Items	Notes
All columns	❌ N/A	Board inaccessible — cannot enumerate items or columns

---

Actions Taken

Action	Count
Mismatched items fixed	0 (board inaccessible)
Missing items added	0 (board inaccessible)
Items flagged for review	8

---

Items Needing Manual Review

The following open issues and PRs were found across managed repos and should be verified on the project board. Board placement could not be confirmed or updated automatically.

Item	Repo	Type	Priority	Issue
#153 — AWS Access Key Exposed	subcog	Issue	🔴 CRITICAL	Security credential exposure, Day 5+, unresolved — verify board placement
#104 — Project ID bug (. in dir names)	atlatl	Issue	🟠 High	New bug filed 2026-03-17; should be in To Do
#4 — bump gh-aw 0.56.2→0.58.3	github-project-manager	PR (open)	🟠 High	Ready to merge; clears CI failure — should be In Progress
#94 — bump upload-artifact →v7	atlatl	PR (open)	🟠 High	Dependabot; also fixes CI failure — should be In Progress
#191 — bump @redocly/cli →2.21.1	atlatl-spec	PR (open)	🟡 Medium	Dependabot — should be In Progress
#161 — bump download-artifact →8.0.1	subcog	PR (open)	🟡 Medium	Dependabot — should be In Progress
#157 — User-to-curated memory linking	atlatl-spec	Issue	🟡 Medium	Feature spec, open, no assignee — should be in To Do
#124 — CI Failure Doctor failed	rlm-rs	Issue	🟡 Medium	Workflow failure issue — verify board placement

---

Automated/Tracker Issues (Excluded from Board)

The following open issues are automation artifacts and should not be placed on the project board:

Issue	Repo	Reason
.github #340 — Smart Alerts	.github	Automated alert — expires/cycles automatically
.github #339 — CI Health Report	.github	Automated report
.github #241 — Agent Health Monitor failed	.github	Automated workflow failure ticket
.github #151 — No-Op Runs	.github	Persistent automation tracker
rlm-rs #109 — No-Op Runs	rlm-rs	Persistent automation tracker
MIF #10, #4, #3 — No-Op Runs	MIF	Persistent automation trackers

---

Remediation Steps

1. Immediate: Add Projects: Read/Write (user-level) permission to zircote-org-monitor GitHub App — required for all future board audit runs
2. Quick win: Merge github-project-manager#4 (5 min, clears CI failure)
3. Security: Revoke AWS credentials in subcog#153 — Day 5+, still unresolved
4. Manual board triage: Review the 8 flagged items above and place them in appropriate columns

---

Generated by maintenance-board workflow — https://github.com/zircote/.github/actions/runs/23239578817

Generated by Maintenance Board · ◷

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #348

View newer issue

---

This action was performed automatically by the Maintenance Board workflow.