Unify status line metric reporting so compile and layout actions show the same metric set and formatting.
Context
Live browser testing found inconsistency: normal compile path shows detour metric while layout action path differs.
Scope
Refactor status string generation into a shared formatter.
Ensure all compile entry points use the same metric fields.
Keep deterministic ordering and compact readability.
Acceptance Criteria
Status line is identical in structure for compile, auto-layout, and auto-tidy results.
Includes consistent metric set (crossings, overlaps, bends, tie-nets, detour).
No regressions in existing tests.
## Objective
Unify status line metric reporting so compile and layout actions show the same metric set and formatting.
## Context
Live browser testing found inconsistency: normal compile path shows detour metric while layout action path differs.
## Scope
- Refactor status string generation into a shared formatter.
- Ensure all compile entry points use the same metric fields.
- Keep deterministic ordering and compact readability.
## Acceptance Criteria
- Status line is identical in structure for compile, auto-layout, and auto-tidy results.
- Includes consistent metric set (`crossings`, `overlaps`, `bends`, `tie-nets`, `detour`).
- No regressions in existing tests.
Rbanh
added this to the Phase 3 - Browser QA and UX Consistency milestone 2026-02-18 21:33:51 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Objective
Unify status line metric reporting so compile and layout actions show the same metric set and formatting.
Context
Live browser testing found inconsistency: normal compile path shows detour metric while layout action path differs.
Scope
Acceptance Criteria
crossings,overlaps,bends,tie-nets,detour).Completed in commit
d5836a2.Delivered:
Validation:
npm testnpm run test:ui