Move comment, issue-comments, categorize, and issues onto Ticket #1617
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#1617
Loading…
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?
Problem
These four commands read and write through the old backends. They are the simple writes, so they prove pending comments and label changes before the close and claim families move.
Approach
Follow the step walks in section 3 of the design record. Owned rules: inventory 1.7 (category swap) and the list group order next, waiting, review, other.
Required work:
ticket.comment,ticket.comments,ticket.category=, andTicket.list— check: presentdef commentinplugins/os-backlog/lib/backlog/**/*.rbTicket.--body-fileread onissue-editandcommentkeeps the command prefix.Acceptance criteria
commentruns, then one comment appears.categorizeruns, then the new category is added first and the old one is removed second.issuesruns, then the groups print in the order next, waiting, review, other.commentorissue-editruns, then the error starts with the command prefix and the exit status is 1.issue-comments, when it runs, then the output is the same JSON array as before the port.Owner sketch
Non-goals
Do not rename a command before slice 9. Do not change
## Resolution,**Follow-ups:**, the body headings, the check form, the label names, or theissue-showJSON keys. Do not make a behavior change that this ticket does not name.Blocking edges
Blocked by #1616
Origin
docs/system-design-format/proof/2026-11-06-os-backlog-domain-objects.md, slice 4plugins/os-backlog/CONTEXT.md)VERDICT: CREATE
From #1615: Tracker#save holds four of the six write steps. Add the comments step here, first in the order.
Work started on branch ticket-1617.
Resolution
Done: comment, issue-comments, categorize, and issues run through Ticket on every host. Tracker#save writes pending comments first. list, comment, and comments are on the Host role. Categorize is deleted. Defect 18 is fixed. The run failed at contract-auditor with verdict error after a green suite; the three production corrections and the role-test gap were finished by hand.
Evidence: Branch: os-backlog 489 runs on seed 19992 plus three random seeds, os-sdlc 3508 runs, ticket-takedown 623 runs, all 0 failures. Implementation 253. Merged by worktree finish.
Follow-ups: none. The auditor error is an occurrence on #1298.