From 2dbe34939ba0e41170a17384d188ee0fc97054d0 Mon Sep 17 00:00:00 2001 From: lukasWuttke <54042461+LukasWodka@users.noreply.github.com> Date: Wed, 29 Jul 2026 08:52:19 +0200 Subject: [PATCH 1/2] docs: add Bugbot resolve-and-reply team norm to .cursor/BUGBOT.md Part of tracebloc/backend#1308 Co-Authored-By: Claude Fable 5 --- .cursor/BUGBOT.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.cursor/BUGBOT.md b/.cursor/BUGBOT.md index e4e67b7..df9d63c 100644 --- a/.cursor/BUGBOT.md +++ b/.cursor/BUGBOT.md @@ -125,3 +125,11 @@ consequence — what they see, and which exit code they get — not just the cod This repo is **public**: never put a customer name, internal hostname, or internal-only ticket detail in a finding. A bare `tracebloc/backend#NNNN` reference is fine. + +## Working with Bugbot findings (team norm) + +Every Bugbot review thread gets a reply, then gets resolved: +- **Fixed**: say what changed and in which commit. +- **False positive**: say why, with evidence (file/line, measured behavior). +Unresolved cursor threads HOLD release-train promotions (soft gate) — an +unaddressed finding blocks the fleet, not just this PR. From 15d2c385fd2435a98ad81de8ca03309d22bd102c Mon Sep 17 00:00:00 2001 From: lukasWuttke <54042461+LukasWodka@users.noreply.github.com> Date: Wed, 29 Jul 2026 08:52:20 +0200 Subject: [PATCH 2/2] docs: point CONTRIBUTING.md at the Bugbot findings norm Part of tracebloc/backend#1308 Co-Authored-By: Claude Fable 5 --- CONTRIBUTING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 15123e4..2fe3a99 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -105,3 +105,7 @@ Coverage says a line *ran*; mutation testing says a test would *fail* if the lin 4. File one issue per real gap, titled `test(): pin (mutation survivor)`, quoting the gremlins line (mutant type + file:line) and what behavior the missing test must pin. That issue then flows through the kanban like any other test ticket — #262, #263, #264 are the pattern. Survivors are *findings to triage*, not build failures — the workflow stays green even when mutants live, on purpose. + +## Bugbot findings + +See `.cursor/BUGBOT.md` — every thread gets a reply (fixed / false-positive-with-evidence), then resolved.