[Flotapponnier]

two release pages shipped 62 characters of a 155 character snippet

The SEO audit on the release scope flagged bnb-rpc-ws and
hyperliquid-rpc-ws at 62 characters, where the target is 110 to 160. The
specs are not the cause: all six WebSocket benches declare the same
two-sentence description, and ethereum-rpc-ws renders it whole at 152.

capSnippet cuts at the last sentence end inside the budget. When the chain's
name is a few characters longer the whole text crosses 155, the only
sentence end inside the budget is the first one at 62, and the page ships
that: the second sentence, the one naming Chainstack, GetBlock, QuickNode,
Dwellir and Validation Cloud, is dropped whole.

The sentence boundary is the right cut when it lands near the cap and the
wrong one when it lands far below it. It now has to keep 60% of the budget
to be taken; under that the existing clause and word fallbacks already
produce a snippet that uses the space.

This is not specific to the release. Any description whose first sentence is
short and whose total sits just over the cap loses everything after it, on
every page type.

Three tests pin it: the shape that shipped 62 characters now keeps the
providers, a sentence end near the cap is still preferred, and no cut
exceeds the cap or ends on punctuation noise.

Gates: tsc clean, eslint clean, 597 tests.