Context
From Ryan Carson's Code Factory analysis (reflection note).
production regression → harness gap issue → test case added → SLA tracked
Every bug becomes a test case, so the system's coverage compounds over time.
Current State
Bugs become GH issues, and auto-dev creates PRs with tests. But there's no formal loop ensuring every production regression specifically results in a regression test. It happens ad hoc.
Implementation
- When a bug is found in production, label it
regression in addition to bug
- Nightshift enforces that
regression-labeled PRs must include a test reproducing the original failure
- Track regression-to-test SLA (time from regression filed to test merged)
Priority
Medium — can implement alongside current pipeline
Context
From Ryan Carson's Code Factory analysis (reflection note).
production regression → harness gap issue → test case added → SLA trackedEvery bug becomes a test case, so the system's coverage compounds over time.
Current State
Bugs become GH issues, and auto-dev creates PRs with tests. But there's no formal loop ensuring every production regression specifically results in a regression test. It happens ad hoc.
Implementation
regressionin addition tobugregression-labeled PRs must include a test reproducing the original failurePriority
Medium — can implement alongside current pipeline