traffic-light-findings
Traffic-light findings
If AGENTS.md sets a different convention for this topic, follow AGENTS.md.
Severity
| Light | Meaning | What happens next |
|---|---|---|
| 🔴 | Blocking. The work does not move on (merge, release, next phase) until it is fixed. | Fix it or get an explicit decision from the user. |
| 🟠| Worth discussing. It is a real problem or a strong counter-argument, but it does not block. | Discuss, then fix or record the decision. |
| 🟡 | Minor. A warning without real risk, or a cosmetic issue. | Fix when convenient, or accept. |
Choose the light by impact and likelihood together. If a finding is blocking only in some contexts (for example, only behind a proxy), say so and give the light for each context.
Finding format
Give every finding a stable ID. Use a prefix that shows its source and a number: RT1 (red team), B2 (browser test), V3 (verification), P4 (production readiness), AC-17 (acceptance criterion). Do not renumber IDs after you share them. If you must renumber, show the old and new IDs.
Each finding has an ID and a one-line title, where (file:line, route, document section or command), evidence (a short quote, a reproduction or test output), impact (what goes wrong, for whom) and a concrete recommendation.