Label structure tickets at their source #1121

Open
opened 2026-10-18 19:32:58 +00:00 by jared · 0 comments
Owner

Problem

The ticket generators crc-tickets and collaborator-pass hardcode category/code-change on structure-only tickets. These tickets then enter the wrong route. Jared ruled on 2026-10-18 that CRC splits (Extract Class, extract module) and inline-class tickets are category/structure.

Reproduce

n/a: design gap in two label lists.

Approach

Required work:

  1. Emit category/structure for structure-only CRC tickets — check: present category/structure in plugins/os-sdlc/lib/os_sdlc/crc/tickets/ticket_drafts.rb
  2. Emit category/structure for structure-only collaborator-pass tickets — check: present category/structure in plugins/os-sdlc/lib/os_sdlc/collaborator_pass/ticket_draft.rb

Orchestrator work: decompose and takedown call os-backlog categorize NUMBER structure; relabel open CRC tickets with os-backlog categorize.

Acceptance criteria

  1. Given a structure-only CRC ledger row, when crc-tickets drafts its ticket, then the ticket carries category/structure.
  2. Given a structure-only collaborator-pass finding, when TicketDraft builds its labels, then the labels include category/structure.

Origin

  • Trigger: Jared's ruling 2 on the structure-ticket route-scope memo, 2026-10-18.
  • Improvised this session: none
  • Chain: structure tickets routed as code-change ← generators hardcode category/code-change (ticket_drafts.rb:35, ticket_draft.rb:6) ← DESIGN (memo structure-ticket-route-scope.md, ticket 2)
  • Root candidate: none found; searched structure, category label
  • Where: plugins/os-sdlc/lib/os_sdlc/crc/tickets/ticket_drafts.rb
  • Session: 3f600331-eeb2-40e7-ab41-922c43d98e91
  • Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/3f600331-eeb2-40e7-ab41-922c43d98e91.jsonl

VERDICT: CREATE

## Problem The ticket generators crc-tickets and collaborator-pass hardcode `category/code-change` on structure-only tickets. These tickets then enter the wrong route. Jared ruled on 2026-10-18 that CRC splits (Extract Class, extract module) and inline-class tickets are `category/structure`. ## Reproduce n/a: design gap in two label lists. ## Approach Required work: 1. Emit `category/structure` for structure-only CRC tickets — check: present `category/structure` in `plugins/os-sdlc/lib/os_sdlc/crc/tickets/ticket_drafts.rb` 2. Emit `category/structure` for structure-only collaborator-pass tickets — check: present `category/structure` in `plugins/os-sdlc/lib/os_sdlc/collaborator_pass/ticket_draft.rb` Orchestrator work: decompose and takedown call `os-backlog categorize NUMBER structure`; relabel open CRC tickets with `os-backlog categorize`. ## Acceptance criteria 1. Given a structure-only CRC ledger row, when crc-tickets drafts its ticket, then the ticket carries `category/structure`. 2. Given a structure-only collaborator-pass finding, when TicketDraft builds its labels, then the labels include `category/structure`. ## Origin - Trigger: Jared's ruling 2 on the structure-ticket route-scope memo, 2026-10-18. - Improvised this session: none - Chain: structure tickets routed as code-change ← generators hardcode `category/code-change` (ticket_drafts.rb:35, ticket_draft.rb:6) ← DESIGN (memo structure-ticket-route-scope.md, ticket 2) - Root candidate: none found; searched structure, category label - Where: plugins/os-sdlc/lib/os_sdlc/crc/tickets/ticket_drafts.rb - Session: 3f600331-eeb2-40e7-ab41-922c43d98e91 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/3f600331-eeb2-40e7-ab41-922c43d98e91.jsonl VERDICT: CREATE
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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#1121
No description provided.