29 lines
960 B
Markdown
29 lines
960 B
Markdown
---
|
|
name: New Eval Scenario
|
|
about: Propose a test case for the benchmark suite — no code required
|
|
labels: enhancement
|
|
assignees: ''
|
|
---
|
|
|
|
## Scenario
|
|
|
|
**Review mode:** <!-- PR Review / Architecture Audit / Tech Debt / Test Quality — Health Dashboard aggregates the other four and has no dedicated eval scenarios -->
|
|
|
|
**Decay risk targeted:** <!-- R1 Cognitive Overload / R2 Change Propagation / R3 Knowledge Duplication / R4 Accidental Complexity / R5 Dependency Disorder / R6 Domain Model Distortion / T1-T6 for test risks -->
|
|
|
|
## Input
|
|
|
|
<!-- Describe the code scenario or paste a snippet. It doesn't need to be a real codebase — a minimal example is fine. -->
|
|
|
|
```
|
|
<!-- code or description -->
|
|
```
|
|
|
|
## Expected finding
|
|
|
|
<!-- What should brooks-lint flag here? Describe the symptom, which book/principle it maps to, and the severity (🔴/🟡/🟢). -->
|
|
|
|
## Why this matters
|
|
|
|
<!-- One sentence: what real-world problem does this scenario represent? -->
|