Apply priority triage to 78 un-triaged flight-deck+bridge tickets (labels out of director tier) #470
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/infrastructure#470
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Triage sweep of every un-triaged ticket across flight-deck and bridge, filed from a
warded directorread-only surface session (2026-07-04).Done in the sweep
issue closeis in the director write tier, so this half landed directly.Blocked half - apply 78 priority labels
The 78 open issues below carried no priority label. Each was read and assigned a P1/P2/P3 from the org rubric (P0 now/blocking, P1 next/important, P2 backlog/will-do, P3 someday/low). None warranted P0 or a new P4.
ward ops forgejo issue-label add/setis out of the director write tier (refused - the broker serves the write tier only: create/edit/comment/close/reopen), so the labels could not be applied from the surface. Apply the block below from a session/host whoseward ops forgejocarries the label-write tier.Mode axis (consult/headless/interactive) was left unlabeled on purpose: unlabeled fails closed to
consult, andheadlessauthorizes autonomous agent action, which is a heavier call than a backlog triage should make.Priority map
coilyco-bridge/agentic-os-hardware- P1: #5, #19, #25 - P2: #1, #2, #4, #10, #11, #12, #13, #14, #15, #16, #18, #24 - P3: #3, #6, #7, #8, #9, #17, #20coilyco-bridge/agentic-os-kai- P1: #693 - P2: #694, #695, #696, #697, #698, #699, #700, #701, #702, #703, #704, #705, #708, #709, #710, #711 - P3: #707coilyco-bridge/atlas- P2: #12coilyco-bridge/deploy- P2: #23, #24, #27, #40, #42 - P3: #30coilyco-bridge/lore- P2: #3coilyco-flight-deck/backend- P2: #35coilyco-flight-deck/cli-guard- P1: #179 - P2: #181, #183, #184, #188, #189 - P3: #182, #185coilyco-flight-deck/galaxy-gen- P1: #31 - P2: #32coilyco-flight-deck/homebrew-tap- P3: #1coilyco-flight-deck/infrastructure- P2: #452, #455, #459, #462, #463, #467, #469 - P3: #457coilyco-flight-deck/lunch-money-k8s- P2: #21coilyco-flight-deck/repo-recall- P2: #113, #114, #115coilyco-flight-deck/ward- P1: #601, #604, #605, #607 - P2: #602, #603Apply block
Exact duplicate of #471 (identical title and body, filed 7s apart in the same 2026-07-04 director sweep). #472 and the companion comment both hang off #471, so keeping #471 as canonical. Closing this one as the dup - track the tier-axis apply on #471.