You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Read-only audit of all open issues (bodies + every comment, paginated), the 30-label catalogue, historical label usage across 1,573 issues and 1,633 PRs, and label-producing automation (alarm watchers, Dependabot, elastic-release-watch). No source, tests, assignments, closures or deployments. This issue is the consolidated publication; per-issue comments were intentionally avoided to reduce noise.
Census
41 open issues reviewed in full (bodies and all comments), including #1947 and #1805, which are large multi-thousand-character benchmark threads. Zero open issues excluded from review. Concurrency re-check immediately before mutations: no body changed; two new comments (#3205/#3201 shadcn acceptance checkpoint) reviewed before any edit.
Label fixes applied (verified read-back after each)
colibri evaluation record with measured adopt-conditional outcome
Description fix: dashboard was "Go dashboard, its routes, templates and CSS" — now "Dashboard product area — routes, templates, styling and frontend UX" (open work is the Next.js/shadcn migration). Name and color unchanged.
All additions were additive; no label removed. Full before/after values with rollback data are recorded locally in the run's changes.json.
Deliberately preserved state labels
AFTER RELEASE 0.1.0 #1523 keeps both blocked and parked — explicit deferred gate plus waiting state, not a conflict.
Alarm labels (ci-queue-stall, disk-usage-alarm, backup-staleness-alarm family) are created on demand by their watchers and self-heal; zero open usage does not make them obsolete. compose-drift-alarm's description is narrow relative to the watcher's current scope (retired stacks, health streaks, resource drift) but matches the script's own gh label create text, so it is left as-is.
Taxonomy decisions left open (operator)
Dependabot references labels that do not exist: github-actions, go, containers (and frontend, which exists but has an empty description and zero usage). Dependabot will fail to apply the missing ones on every PR. Options: create them (with descriptions/colors) or prune them from .github/dependabot.yml. Zero current open usage does not imply obsolete — go/containers had heavy historical usage. Not acted on: label creation on this evidence alone is a recurring-need judgment, and editing dependabot.yml is a repo change outside housekeeping scope.
frontend vs dashboard: kept distinct. frontend is currently a Dependabot-scoped automation name, not a duplicate of the dashboard topic. If Dependabot labels are pruned instead of created, frontend can be retired then.
analysis vs research: confirmed distinct and both in active correct use (analysis = payload-analysis pipeline topics, research = findings/reports). No merge.
State-label family: blocked, decision, parked, HALTED, in-progress all have distinct live semantics; no consolidation proposed.
#3135 keeps decision despite reading more like a documented procedure: the decision-label mismatch is real but removal is a judgment call, not an unambiguous fix.
#2972 closed (fixed, drift corrected, #3028 filed for the detector gap) — #1993's blocker list remains accurate. #2925 closed with KEEP-threshold decision — #1974's dependency claim stands. #3106/#3154 closed/merged with remainder correctly spun into #3163. #3129/#3165 closed/merged (llm-worker allowlist). #3030/#3041 closed. #2582 closed; its recurrence is what #3023 tracks. PR #2641 still open/draft.
Not done (out of scope)
No label deletions/renames, no mass relabeling of closed items, no closures, no assignment changes, no repo file edits, no model/provider changes, no CI polling.
Scope and method
Read-only audit of all open issues (bodies + every comment, paginated), the 30-label catalogue, historical label usage across 1,573 issues and 1,633 PRs, and label-producing automation (alarm watchers, Dependabot, elastic-release-watch). No source, tests, assignments, closures or deployments. This issue is the consolidated publication; per-issue comments were intentionally avoided to reduce noise.
Census
41 open issues reviewed in full (bodies and all comments), including #1947 and #1805, which are large multi-thousand-character benchmark threads. Zero open issues excluded from review. Concurrency re-check immediately before mutations: no body changed; two new comments (#3205/#3201 shadcn acceptance checkpoint) reviewed before any edit.
Label fixes applied (verified read-back after each)
colibri/benchmarkdo not assign labelssecurity,analysis,enhancementsecurity,analysis,enhancementsecurity,analysis,enhancementDescription fix:
dashboardwas "Go dashboard, its routes, templates and CSS" — now "Dashboard product area — routes, templates, styling and frontend UX" (open work is the Next.js/shadcn migration). Name and color unchanged.All additions were additive; no label removed. Full before/after values with rollback data are recorded locally in the run's
changes.json.Deliberately preserved state labels
blockedandparked— explicit deferred gate plus waiting state, not a conflict.in-progressdespite the "remaining parked" comment; removing an active label needs a validated state transition, not a comment read. Theregressionaddition is separate from that question.parked: the early hardware blocker was explicitly withdrawn and a measurement was completed and recorded.parked(named gates intact).ci-queue-stall,disk-usage-alarm,backup-staleness-alarmfamily) are created on demand by their watchers and self-heal; zero open usage does not make them obsolete.compose-drift-alarm's description is narrow relative to the watcher's current scope (retired stacks, health streaks, resource drift) but matches the script's owngh label createtext, so it is left as-is.Taxonomy decisions left open (operator)
github-actions,go,containers(andfrontend, which exists but has an empty description and zero usage). Dependabot will fail to apply the missing ones on every PR. Options: create them (with descriptions/colors) or prune them from.github/dependabot.yml. Zero current open usage does not imply obsolete —go/containershad heavy historical usage. Not acted on: label creation on this evidence alone is a recurring-need judgment, and editing dependabot.yml is a repo change outside housekeeping scope.frontendvsdashboard: kept distinct.frontendis currently a Dependabot-scoped automation name, not a duplicate of the dashboard topic. If Dependabot labels are pruned instead of created,frontendcan be retired then.analysisvsresearch: confirmed distinct and both in active correct use (analysis = payload-analysis pipeline topics, research = findings/reports). No merge.blocked,decision,parked,HALTED,in-progressall have distinct live semantics; no consolidation proposed.#3135keepsdecisiondespite reading more like a documented procedure: the decision-label mismatch is real but removal is a judgment call, not an unambiguous fix.round7-N/#shadcn-Naliases without numeric links. Epic: round 7 — Unsloth training and dynamic requant, served via Ollama, scored on a fresh three-slot benchmark #3079 and Epic: COMPLETE dashboard rewrite — shadcn component/layout/style fidelity on every page #3201 already enumerate their children explicitly, so no corrective comments were posted — the mapping exists on the epics. If the aliases bother anyone, the fix belongs in the child bodies by their own campaigns.Relationship links checked (no action needed)
Closes #1805— already noted on Benchmark fidelity: run real Ghidra over the #159 corpus so models are scored on production-shaped input #1805 by a prior review; flagging again so the merge does not strand the issue.Dependency state checks performed
#2972 closed (fixed, drift corrected, #3028 filed for the detector gap) — #1993's blocker list remains accurate. #2925 closed with KEEP-threshold decision — #1974's dependency claim stands. #3106/#3154 closed/merged with remainder correctly spun into #3163. #3129/#3165 closed/merged (llm-worker allowlist). #3030/#3041 closed. #2582 closed; its recurrence is what #3023 tracks. PR #2641 still open/draft.
Not done (out of scope)
No label deletions/renames, no mass relabeling of closed items, no closures, no assignment changes, no repo file edits, no model/provider changes, no CI polling.