Add a ticket-growth report over the pipeline DB as the baseline for pipeline realignment #1312
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#1312
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
The implement pipeline is suspected of under-building: it extends existing objects, leaves structural debt, and the debt returns as follow-up tickets. Nobody has measured this. Four charter changes are planned (seam-designer, change-auditor, ticket-decompose, reviewer). Without a baseline, no one can tell whether they reduced follow-ups or only moved them. Design record: docs/system-design-format/README.md section 4.
Reproduce
n/a: measurement harness, nothing to reproduce.
Approach
Add a report to the os-sdlc CLI that reads the pipeline DB with Sequel and prints, per closed implementation run since 2026-09-01: ticket number, map, new files in the merged diff, new classes in the merged diff, follow-up tickets captured at close (from the close comment), and objections raised. Print totals and a per-month median. Store nothing; the report is rerun before and after each charter change.
Data sources (added 2026-10-25 after escalation 70 on run 158; both were unnamed, so the run wired empty stubs):
git log main --no-merges -p --fixed-strings --grep="(#N)"(pipeline commits end their subject with(#N)). New files = diff entries whose old side is/dev/null. New classes = added lines that declareclass Name(notclass << self).#<digits>references on the**Follow-ups:**line of the last## Resolutioncomment on the ticket;noneor no such comment = 0. Comments are read through a read-onlyos-backlog issue-comments NUMBERcommand, reached from os-sdlc through the existingTracker::Backlogadapter.Required work:
ticket-growthreport command in the os-sdlc CLI that prints the per-run table and the medians.NewFilescounter over a merged diff that reports new files and new classes.ticket-growthcommand reads the real merged diff and the real follow-ups per the Data sources above; no constant empty sources.Orchestrator work: run the report once before any of the four charter tickets merges and paste the output on this ticket as the baseline.
Rejected: counting open tickets per month — it measures capture habits, not pipeline output.
Acceptance criteria
Owner sketch
Origin
VERDICT: CREATE
Work started via /os-sdlc:implement on branch ticket-1312 (map poodr-ticket-implementation).
Baseline (2026-10-25, main
fbda9726)Run before any of the four charter tickets (#1313-#1316) merged. Command:
plugins/os-sdlc/bin/ticket-growth. 109 closed runs. The pipeline DB starts on 2026-10-02, so no September runs exist and only one median month prints. Ticket-wide counts go on the latest closed run of a ticket; earlier runs of the same ticket show 0.Resolution
Done: Added plugins/os-sdlc/bin/ticket-growth (Report::Run, TicketGrowth, NewFiles, MergedDiff, FollowUps, Table) and os-backlog issue-comments read through Tracker::Backlog. Per closed run since 2026-09-01 it prints ticket, map, new files, new classes, follow-ups, objections, totals and per-month medians of all four counts. Baseline posted on this ticket. Hand-finished after escalation 70 on run 158; the ticket body gained a Data sources block.
Evidence: main
fbda9726. ruby plugins/os-sdlc/tests/all.rb: 2514 runs, 0 failures; ruby plugins/os-backlog/tests/all.rb: 327 runs, 0 failures; rubocop on 26 changed files: no offenses; one opus design audit, every finding fixed or answered. Real run on main: 109 rows, total 389/441/67/96, median 2026-10 2/3/0/0.Follow-ups: Pipeline defect recorded as an occurrence on existing #1113 (test-reviewer passed a disclosed wiring gap; change-auditor data-source UNKNOWNs went forward). Dropped: anchoring the (#N) grep to the subject end and file paths with spaces in NewFiles; low value for a trend baseline.
Checkpoint 2026-10-25 after #1313-#1316 merged (main
59f6cdb0): ticket-growth output is identical to the baseline (109 runs, total 389/441/67/96, median 2026-10 2/3/0/0). No implementation run has closed on the new charters yet, so the comparison rerun is due after the next batch of poodr-ticket-implementation runs, not now.