P6-04: Tune Phase 6 readability budgets to match improved placement policy #33

Closed
opened 2026-02-19 14:19:08 -05:00 by Rbanh · 1 comment
Owner

Objective

Keep quality gates strict on crossings/overlaps while calibrating detour thresholds for the new placement policy.

Scope

  • Adjust drag/tidy and dense detour budgets where necessary.
  • Document updated thresholds in quality gate docs.
  • Ensure CI + local QA use aligned thresholds.

Acceptance Criteria

  • Thresholds are explicit and justified in docs.
  • UI regression remains stable and meaningful.
  • No silent regressions in crossings/overlaps.
## Objective Keep quality gates strict on crossings/overlaps while calibrating detour thresholds for the new placement policy. ## Scope - Adjust drag/tidy and dense detour budgets where necessary. - Document updated thresholds in quality gate docs. - Ensure CI + local QA use aligned thresholds. ## Acceptance Criteria - Thresholds are explicit and justified in docs. - UI regression remains stable and meaningful. - No silent regressions in crossings/overlaps.
Rbanh added this to the Phase 6 - Layout Coherence and Readability Stabilization milestone 2026-02-19 14:19:24 -05:00
Author
Owner

Delivered in commit 47fabe6.

Implemented:

  • Calibrated UI detour thresholds to match the improved placement policy while keeping crossings/overlaps strict.
  • Updated thresholds in tests/ui-regression-runner.js.
  • Synced documentation in docs/quality-gates.md.

Outcome:

  • Quality gate remains meaningful and stable across drag/tidy and dense fixture scenarios.
Delivered in commit `47fabe6`. Implemented: - Calibrated UI detour thresholds to match the improved placement policy while keeping crossings/overlaps strict. - Updated thresholds in `tests/ui-regression-runner.js`. - Synced documentation in `docs/quality-gates.md`. Outcome: - Quality gate remains meaningful and stable across drag/tidy and dense fixture scenarios.
Rbanh closed this issue 2026-02-19 14:20:33 -05:00
Sign in to join this conversation.
No Label
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Rbanh/schemeta#33
No description provided.