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
feat(ui): cut an overlong lead at its first clause, not just its first period
Leading with "the first sentence" assumed a first sentence is short. It
often is not: 530 of the 1,709 run past 200 characters, the longest is
615, because these descriptions pack the whole scope into one sentence
behind a colon or a dash. "The bathroom rough-in check, in four numbers:
15 in from a fixture centerline to any side wall, partition, vanity, or
other obstruction; 30 in center to center between ..." is the wall of
text the rule was meant to prevent.
leadSentence() cuts a sentence over 160 characters at its first real
clause boundary, so that tile now leads with "The bathroom rough-in
check, in four numbers." Median lead 158 -> 102 characters; leads over
200, 530 -> 112. Nothing is dropped: where the lead is a clause-cut
summary, the detail below the answer carries the whole description
rather than starting mid-sentence in lower case. Verified across all
1,709 tiles that lead + detail still reconstruct the full text.
Also fixes a defect in the placeholder priming from 23be32b: on a tile
whose fields carry defaults, priming computed off those defaults and
painted a verdict before the reader had entered anything ("PASSES the
IPC 405.3.1 clearances entered" on open). Blank-vs-filled was the wrong
test. What matters is whether an answer was already on its way in -- a
deep link's input events, or a click on the example button -- so that is
what the restore now keys on.
Verified all five open paths: plain open, ?example=1, deep link,
default-prefilled tile, and clicking "Test with example".
Co-Authored-By: Claude Opus 5 <[email protected]>
0 commit comments