jared
/
cc-os
1
0
Fork 0
Code Issues 17 Pull Requests Packages Projects Releases Wiki Activity

os-backlog rollout: onboard a second project via /os-backlog:route #66

New Issue
Open
opened 2026-07-16 18:44:11 +00:00 by jared · 0 comments
jared commented 2026-07-16 18:44:11 +00:00
Owner
Copy Link

Residual from PRD issue #9 (closed 2026-07-13 as delivered). Core plugin surface is shipped; rollout remains: onboard one more project one-at-a-time via /os-backlog:route, and exercise the promotion rule (Planka card → carved repo + /to-issues) end-to-end at least once. Gem-blocked items (recurrence autonomy pass-through, tick-fed operations board) stay with planka gem issue #13.

NOTE (2026-07-16): post-ADR-0042 this means routing a project to a git tracker (forgejo:/github:/repo:) and ensuring the ten canonical labels — no boards.

Migrated 2026-07-16 from Planka board cc-os, column Backlog (ADR-0042, change retire-planka-git-issues-only).

Residual from PRD issue #9 (closed 2026-07-13 as delivered). Core plugin surface is shipped; rollout remains: onboard one more project one-at-a-time via /os-backlog:route, and exercise the promotion rule (Planka card → carved repo + /to-issues) end-to-end at least once. Gem-blocked items (recurrence autonomy pass-through, tick-fed operations board) stay with planka gem issue #13. NOTE (2026-07-16): post-ADR-0042 this means routing a project to a git tracker (forgejo:/github:/repo:) and ensuring the ten canonical labels — no boards. --- Migrated 2026-07-16 from Planka board cc-os, column Backlog (ADR-0042, change retire-planka-git-issues-only).
jared added the
P2
semi
 labels 2026-07-16 18:44:11 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
research/clutter-inventory
Labels
Clear labels   
P0

Priority 0 — drop everything

  
P1

Priority 1 — next up

  
P2

Priority 2 — normal

  
P3

Priority 3 — someday

  
afk-ready

Autonomous end-to-end; closed after verification

  
hitl

Human-owned; never picked up autonomously

  
next

Human-curated next up — AI never applies or removes

  
ready-for-agent

Triage complete; an agent can pick this up

  
review

Shipped semi work awaiting human sign-off

  
semi

Autonomous through mechanical parts; stops at gates; ships to review

  
waiting

Blocked; blocker named in a comment

  
wayfinder:grilling

   
wayfinder:map

   
wayfinder:research

   
wayfinder:task
No Label
P0
P1
P2
P3
afk-ready
hitl
next
ready-for-agent
review
semi
waiting
wayfinder:grilling
wayfinder:map
wayfinder:research
wayfinder:task
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jared/cc-os#66
No description provided.
Delete Branch "%!s(<nil>)"

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?