docs: plan graphical diagnostic layout
This commit is contained in:
parent
ca8a352a40
commit
d49363e80e
13
tasks.md
13
tasks.md
|
|
@ -373,6 +373,19 @@ coverage floor passed. Tarpaulin remains at 92.19% (1,334/1,447 lines); the
|
|||
workspace boundary changes dependency ownership, not executable behavior or
|
||||
measurable source coverage.
|
||||
|
||||
## Milestone 14 — Readable graphical diagnostics
|
||||
|
||||
- [ ] Give each graphical Miette diagnostic a visible title marker, remove the
|
||||
empty line between its rule-code title and message, and add one empty line
|
||||
after the complete diagnostic. Pin the layout in unit and showcase tests,
|
||||
document it, and leave human, concise, JSON, and minimal-feature fallback
|
||||
output unchanged.
|
||||
|
||||
Acceptance: adjacent graphical findings have unambiguous boundaries; title and
|
||||
message remain visually connected; stable rule IDs, severity symbols, colors,
|
||||
source annotations, help, summaries, and machine-output contracts are
|
||||
preserved; all quality and coverage gates pass.
|
||||
|
||||
## Deferred by design
|
||||
|
||||
- Statistical or model-based authorship classification.
|
||||
|
|
|
|||
Loading…
Reference in New Issue