v0.0.157

Technology detection finds a Microsoft Clarity snippet that a framework bundle carries as the text of an inline script, and a small script late on a crowded page is no longer left out of detection. Test coverage that missed v0.0.156 (leading-space sign-in forms, three Clarity negatives) is included.

Fixed

• Microsoft Clarity is detected when its snippet is the text of an inline script in a framework bundle. The standard loader carried as the __html of a dangerouslySetInnerHTML prop, or as the children string, of a script element's props (a "script" tag, a strategy key or a script type) is now found, including in a bundle sampled past its head. The string must read as JavaScript (no markup) and hold the snippet's own signature or its script-creating loader, so a docs page, a markdown renderer or a test fixture that quotes the snippet is not a detection. An id key alone is not enough, so a next/script with no strategy prop (and no "script" tag or script type) is not read. (#1509, refs #1488)
• A small script late on a crowded page is no longer left out of technology detection. On a page with dozens of scripts the per-script floor spent the whole page budget on the earlier ones, so a vendor literal past the head of a later, smaller script was never shown to detection. The floor now leaves a share of the page budget for the windows around vendor literals, and a script the floor left no head gets its windows first. The reserve is held only when the floors would not fit the page budget, so a page whose scripts all get their head keeps it. It is shared by every script that needs windows, so a very crowded page can still miss one. (#1510, refs #1488)