[Triage] Daily Triage Report — 2026-03-18

[github-actions]

Repos scanned: 22 managed | Run: 23246390952

Pass	Items Found	In Managed Repos	Manual Attention
Pass 1: needs-triage label	0	0	0
Pass 2: Unlabeled	17 (org-wide)	3	3
Pass 3: Unassigned (labeled)	92 (org-wide)	majority are bot-generated automation issues	—

ℹ️ Pass 3 note: The 92 unassigned+labeled items org-wide are overwhelmingly bot-authored automation issues (Smart Alerts, Board Audits, No-Op trackers). No human-filed issues with labels and no assignees were found outside of the 3 items already captured in Pass 2.

---

Actions Taken

• Labels applied to zircote/.github scope: 1 item (limited — cross-repo label application requires direct repo write access)
• Labels removed: 0 needs-triage labels (none existed)
• Suggested assignments: 3 (see below)

---

Items Requiring Human Attention

#	Repo	Type	Title	Suggested Labels	Reason
#153	subcog	Issue	[Security Alert] Exposed API key(s) detected: AWS Access Key	priority/high, type/bug, security	🔴 CRITICAL — No labels, no assignee, 4 days old. AWS Access Key exposure in src/security/mod.rs. Day 6 with no response per Smart Alert #349.
#152	subcog	PR	feat(http): add /healthz endpoint for K8s readiness probes	type/feature, priority/medium	External contributor (mgildea), no labels, CI passing, requires 2 approvals. Has been open since 2026-03-11.
#151	subcog	PR	fix(observability): let OTEL SDK handle endpoint resolution natively	type/bug, priority/medium	External contributor (mgildea), no labels, CI passing. Production-deployed fix. Open since 2026-03-11.

---

Suggested Assignees

Item	Suggested	Rationale
subcog#153	@zircote	Repo owner; immediate action required on credential exposure
subcog#152	@zircote	External contributor PR requiring maintainer review (2 approvals required)
subcog#151	@zircote	External contributor PR requiring maintainer review

---

Auto-Label Recommendations (cross-repo, requires manual application)

The triage agent identified the following labels to apply. These cannot be applied cross-repo via safe-outputs; apply manually or via a repo-scoped workflow:

zircote/subcog#153 → priority/high, type/bug, security
zircote/subcog#152 → type/feature, priority/medium
zircote/subcog#151 → type/bug, priority/medium

---

Per-Repo Breakdown

zircote/.github

• Pass 1 (needs-triage): 0 items
• Pass 2 (unlabeled): 0 items
• Pass 3 (unassigned): many bot-generated (automation reports, alerts, trackers — by design)
• Auto-labeled: 0 | Manual: 0

zircote/subcog

• Pass 1 (needs-triage): 0 items
• Pass 2 (unlabeled): 3 items (1 issue + 2 PRs) ← Needs attention
• Pass 3 (unassigned): same 3 items (captured above)
• Auto-labeled: 0 (cross-repo labels require repo-scoped access) | Manual needed: 3

All other managed repos (20 repos)

• github-project-manager, sdlc-quality, homebrew-tap, atlatl, atlatl-spec, rlm-rs, MIF, lro-bench, daedalus, ccpkg, refactor, human-voice, rlm-rs-plugin, memory-capture-plugin, documentation-review, adr, adrscope, git-adr, structured-madr, vscode-git-adr
• Pass 1 (needs-triage): 0 items each
• Pass 2 (unlabeled): 0 items each
• Pass 3 (unassigned): no human-filed labeled items found without assignees

---

Generated by daily-triage workflow

Generated by Daily Triage · ◷

[github-actions]

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

View newer issue

---

This action was performed automatically by the Daily Triage workflow.