solidjs / solid / 38587787720

78%

main: 89%

push

github

fix(web): a deferred hole keeps its server component's claims arming (#4043)

* fix(web): a deferred hole keeps its server component's claims arming

A server component arms handler-position markers (`ctx.claims`) on a
context that is current only for its synchronous render. A hole that
escalates there is retried by whatever boundary resumes it — on the
document face, often one outside the component — so its final markup
rendered without the arming and dropped every `_s:on:click`. The chat
thread's Copy buttons shipped unmarked and were bound only because the
end-of-response sweep, which re-runs under the mint-time context,
re-sent the whole message list with the markers.

The retry wrapper now carries the escalation's claims and arms them on a
context derived from the resuming one, so that boundary's buffering and
serialization stay its own.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SzJPKYTStjk5cEs9VDKNce

* chore(size): raise the renderToString floor for retry claims arming

A deferred retry now carries its server component's claims arming, so
buildAsyncWrap's retry wrapper grows renderToString by 34 B brotli
(155 B minified).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SzJPKYTStjk5cEs9VDKNce

* chore(size): record the maintainer's acceptance of the renderToString floor raise

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SzJPKYTStjk5cEs9VDKNce

---------

Co-authored-by: Claude <noreply@anthropic.com>

750 of 1040 branches covered (72.12%)

Branch coverage included in aggregate %.

1084 of 1326 relevant lines covered (81.75%)

27.43 hits per line