Skip to content

chore: track the tech-debt baseline - #133

Open
emp3thy wants to merge 1 commit into
mainfrom
chore/track-tech-debt-baseline
Open

emp3thy wants to merge 1 commit into
mainfrom
chore/track-tech-debt-baseline

Conversation

@emp3thy

@emp3thy emp3thy commented Sep 10, 2026

Copy link
Copy Markdown
Owner

The 2026-09-09 tech-debt scan wrote .tech-debt/baseline.json and appended the gitignore triple that un-ignores it, but the file was never committed. Its cross-scan memory therefore existed only on one machine: any clone or CI run would report all 95 findings as NEW and re-offer the ones already judged.

What is tracked, and what is not

Path Tracked Why
.tech-debt/baseline.json yes fingerprint to status, reason, expiry, first/last seen — the durable record
.tech-debt/ everything else no design.md, scouts, verdicts, prompts and the inventory are all regenerable from the same inputs

That split is what the three gitignore lines already in the file express: un-ignore the directory, re-ignore its contents, un-ignore the baseline alone.

The baseline is what makes NEW / UNCHANGED / UNCHANGED (moved) / UNCHANGED (edited) / RESOLVED work on the next scan, and what stops a rejected finding recurring or holds an accepted one until its expiry passes.

This snapshot

95 entries — 87 pending, 8 promoted — from the 2026-09-09 scan at preset balanced.

Each entry carries a bundle field, which is legacy: tech-debt-scan has since dropped PBI bundle emission, and its current reader ignores that field rather than rejecting it, so no migration is needed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Jshb9ND5BAERZtXfNeXfB9

The 2026-09-09 scan wrote .tech-debt/baseline.json and appended the
gitignore triple that un-ignores it, but the file was never committed, so
its cross-scan memory existed only on one machine. Any clone or CI run
would report all 95 findings as NEW and re-offer the ones already judged.

The baseline is the durable record: fingerprint to status, reason, expiry
and first/last seen. It is what makes NEW / UNCHANGED / RESOLVED work and
what stops a rejected finding recurring. Everything else under
.tech-debt/ stays ignored — design.md and the scan's intermediates are
regenerable from the same inputs.

This snapshot holds 95 entries: 87 pending, 8 promoted. The `bundle` field
on each entry is legacy — tech-debt-scan dropped bundle emission, and the
current reader ignores that field rather than rejecting it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jshb9ND5BAERZtXfNeXfB9

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Claude BugBot Analysis

The diff only updates .gitignore rules and adds a new static JSON baseline file (.tech-debt/baseline.json); there is no executable logic or control flow in the changed lines to contain a bug.

No bugs were detected in this PR.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant