sepehr
5bd180b5b8
Some checks failed
CI / check (push) Has been cancelled
Capture uncommitted solver robustness work (regularization, domain errors, linear solver lifecycle, tube DP/MSH), web workbench updates, and synced BMAD skills across IDE agent folders before starting BPHX pressure-drop. Co-authored-by: Cursor <cursoragent@cursor.com>
15 lines
1009 B
Markdown
15 lines
1009 B
Markdown
# Deletion Check
|
|
|
|
Secondary pass for the Edge Case Hunter — runs only when the diff removed meaningful code. Subordinate to the edge-case pass; findings are usually few or none.
|
|
|
|
For each chunk of removed or replaced code (ignore pure renames and whitespace), ask: did it carry behavior or a contract that the change neither re-established nor intentionally retired? Add a finding for any resulting regression, orphaned reference, or newly-dead code. Skip anything already covered by your edge-case findings.
|
|
|
|
Append each finding to the same JSON array as the edge-case findings, with the four standard fields plus:
|
|
|
|
- `kind`: `"deletion"`
|
|
- `confidence`: `"high"`, `"medium"`, or `"low"` — these are inferences; rate them
|
|
|
|
For a deletion finding the standard fields read as: `location` = the removed item; `trigger_condition` = the behavior or contract it enforced; `guard_snippet` = where or how to re-establish it; `potential_consequence` = the regression or orphan.
|
|
|
|
Add nothing if nothing qualifies.
|