You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a layout anomaly detector to the chat layout resolver. It detects the four classes of broken rects that cause the "buttons not where they should be" defect, and fails a test with a structured diagnostic instead of rendering a broken UI.
Boundary
specs/t27os/chat_layout.t27
User Scenarios
Given a resolved ChatLayout, when two rects overlap (for example the dock covers the composer), then the detector reports the overlap with both rects named. Given a resolved ChatLayout, when a rect has zero or negative size or lies out of bounds, then the detector reports it.
Requirements
FR-001: The detector MUST check overlap, zero-size, out-of-bounds and stale native rects.
FR-002: An anomaly MUST fail a test and log a structured diagnostic naming the rects.
FR-003: The detector MUST NOT auto-edit foreign code; it only reports.
Success Criteria
1 tests that feed a malformed layout and fail with a named-rect diagnostic
exit 0 from t27b test specs/t27os/chat_layout.t27 for a well-formed layout
Activity
gHashTag commentedon Nov 17, 2026
Spec created: specs/t27os/layout_anomaly.t27 (typecheck OK, 1 test passes).