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
{{ message }}
Repository navigation
Commit 2a5e63e
Browse filesBrowse the repository at this point in the historyBrowse files
committed
docs(server-components): frames rulings — the overnight pass's defaults, the server-half drafts, the as-landed table
What the rulings do NOT decide: the nine readings the 2026-10-06 pass took
by default (first flush not start; warm switch-back shows the committed
value; the name decides the class on every sync; 2.3's interim with
S-flush; 1.2 by the version guard; 3.2 via initBoundaryResume keyed
sc:<fid> while in progress; 3.3's dev report; S-adopted documented; the
harness's C3 dispose exemption), each with its alternative. The server
half: C13's delimiter with the client's one-write status, the
plain-response streaming bound (complete.bound), C12 (c)'s error template
located in finalizeError/the done closure with the two decisions the
server PR must make. Order of work: the as-landed table (#3830–#3833),
what each step left undone. Public surface: landing, hold, holdBoundary,
the behaviour notes.
Co-authored-by: Claude via Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
"attr", … }] }` on the stream face and one `sc:live` op of the same shape on
1257
+
the document face; `chunkToRecords` merges the members' records into one
1258
+
map (≈ +40 B); `applyFrames.drain` and `applyLiveOp` pass the chunk through
1259
+
unchanged; the `liveOps` catch-up log flattens an `ops` op into its members
1260
+
(≈ +30 B). A sweep that changes one binding emits as today. Wire: a new
1261
+
`FrameChunk` / `sc:live` member — RFC 11 addendum. _Pin to write against
1262
+
the draft:_`c13-sweep-atomic` (a, b) as they stand — they flip when the
1263
+
sink emits the member. _Rejected:_ a `sweep-end` marker with client-side
1264
+
buffering (a second ledger, a timeout, a correlation the chunk's edge gives
1265
+
for free).
1266
+
1267
+
**(ii) The plain-response streaming bound** (the savings pass's decision
1268
+
4). A plain server function whose SC reads a generator source keeps its
1269
+
response open (`server.ts``if (!holds) queue(flushEnd)`; `complete` only
1270
+
at settle) and each later yield arrives as a `hole` / `attr` chunk — with
1271
+
no `live` declaration anywhere (re-attribution §1.3a). The bound the
1272
+
response ends at is today "the source settles", which for a generator that
1273
+
never returns is never. _The draft:_`complete` gains `bound: "yields" |
1274
+
"time"` (the sink's choice per response: after the first flush's yields
1275
+
have drained, or after a configured interval), and the sink ends a plain
1276
+
response at the bound; a `live()` response is unbounded by declaration. The
1277
+
client needs nothing — a `complete` is a landing already (`landing`
1278
+
resolves on it), and later yields the bound cut off are what `live()`
1279
+
exists to carry. Wire: a new optional member on the `complete` chunk — RFC
1280
+
11 addendum; absent means today's behaviour. _Pin to write:_ a plain
1281
+
response over a generator source completes at the bound; a `live()`
1282
+
response does not.
1283
+
1284
+
**(iii) C12 (c) — the rejected server `<Loading>`'s error template (3.3's
1285
+
server half).**_The gap, located:_`web/src/server.ts`'s fragment
1286
+
resolver (the `done` closure returned by `registerFragment`) hands
1287
+
`sink.fragment` a `" "` template on the error path (`value !== undefined ?
1288
+
value : " "`) and rejects `<key>_fr`; `frame-sink.ts:fragment` reveals that
1289
+
same `value` and adds a keyed `error` chunk. For a boundary with a client
1290
+
twin the blank is harmless — `hydratedCreateLoadingBoundary`'s `s === 2`
1291
+
arm resumes fresh and renders the nearest client `<Errored>` over it. For a
1292
+
server component's boundary there is no twin: the blank is what shows
1293
+
(#3833's c2 pin). _The shape:_ the server `<Loading>` (`solid/src/server/
1294
+
hydration.ts`, `finalizeError`) already holds the enclosing `parentHandler`
1295
+
— pre-flush the failure is met by it (an `<Errored>` rendering its
1296
+
fallback, into the shell); post-flush its only output channel is the
1297
+
fragment's template. The fix renders the error outcome INTO the template:
1298
+
`done(renderErrorOutcome(err), err)` where the outcome is the nearest
1299
+
server `<Errored>`'s fallback for the error, rendered as a string under the
1300
+
boundary's owner; with no server `<Errored>` the error escapes the server
1301
+
component and the whole response is the frame's `:error` (the outward face
1302
+
— the enclosing client `<Errored>` sees one errored async value, as today
1303
+
through the gate's error apply). _Two decisions the server PR must make:_
1304
+
(1) the fallback renders in the `<Loading>`'s position, not the
1305
+
`<Errored>`'s — the Errored's subtree is already in the shell, so its
1306
+
fallback replacing only the placeholder is the one layout the fragment can
1307
+
express; state it as the rule ("a post-flush error inside a server
1308
+
component's `<Loading>` shows the nearest `<Errored>`'s fallback at the
1309
+
boundary's position"); (2) hydration ids inside the rendered fallback — the
1310
+
fallback must render under a scope that mints ids the client never claims
1311
+
(the client has no twin to claim them: `NoHydration`'s shape, or the SC's
1312
+
own suppressed-fill scope), and head/asset registrations it makes must be
1313
+
dropped as the error path drops them today (`dropHeadBoundary`). Only when
1314
+
the boundary is inside a server component render (no client twin can
1315
+
exist): the client-twin case keeps the blank + the twin's fresh render.
1316
+
_Not wire:_ the template's content is the server's to shape; `_fr` still
1317
+
rejects (the diagnostic). _Pin:_#3833's c2 flips when the template carries
1318
+
the outcome.
1319
+
1157
1320
---
1158
1321
1159
1322
## Order of work
@@ -1180,6 +1343,24 @@ lands outside its band is the finding, not a failure to hide.
1180
1343
| 8 |**3e** the claim reads the snapshot, the backlog lands after — S1's third commit | 3.6 (iii) | C19 ×2 | 0 if S1 lands first; else ≈ +90 / +25 | 3.6's pick; 3.2's ordering pinned with 3a |
1181
1344
| 9 |**3c** id parity; **3b** dev report (client minimum) | 3.4, 3.3 | S1's `.fails`; C12 (c) flips with the **server half** (the document face renders the error outcome) | ≈ +40 / +10 (+30 dev) | the server's consumption pinned; the server-half PR for the fragment error path |
1182
1345
1346
+
### As landed — the overnight pass (2026-10-06, draft PRs off `next` @ `49a8dca84`)
| 1 / 3d — C18 (A0) |#3827 (another agent) | C18 ×3 (there, by the predicate; in #3830 by `#` deciding the class) | — | the two meet at the pins; both are right |
1351
+
| 4+6+3 / A1 — S-flush (1.5, 1.6 (i), 1.4 full, 2.1/2.2, 2.3 interim) |#3830`fix/frames-s-flush-address-source`| C2 (b), C4 (d), C6 (a1, b2), C7 (c), C17 (a re-pinned, c), harness C2 ×1, C18 ×3 |**43,123 / 13,642 (−187 / −128)**|`FrameHost.landing(address)`; the store is one response's; `argsEquivalent`, `clearStreamRecords`, both hand-rolled gates, the re-arm/waiter deleted. **1b not done:**`preview` / `stage`'s client half / `#refArgsUnchanged` (≈ 1,300 B min) — the pull form is written in the PR; it needs the fills' props to read the token. |
1352
+
| 2 / A2 — C3 (3.1 ruled, 3.2) |#3831`fix/frames-c3-hold-is-pending-boundary` (on #3830) | C3 (a), harness C3 ×1; campaign C3 280 → 0 / 268 → 0 | 43,411 / 13,768 (+288 / +126 vs #3830) |`sharedConfig.holdBoundary` (solid, ≈ +59 B min on hydrating pages — over the 20 B allowance; maintainer's call), `FrameOptions.hold`. Not done: `hydrateWindow` / R.claim's deletion, the 3e port (C19 ×2 stay red). |
1353
+
| 7 / A3 — C2 / C4 (2.3, 2.4) | in #3830| C2 (b), C4 (d), harness C2 ×1 | (in #3830's figure) | the interim form (an empty write at the frame's version from the reveal cascade). Not done: R.reveal's readiness/retry deletion; DR-4 (2c). C2 (a2) is S-record's. |
1354
+
| 4 / A4 — C5 (1.2) |#3832`fix/frames-c5-data-response-scoped` (on #3830) | C5 (a, b, e) | 43,194 / 13,659 (+71 / +17 vs #3830) | the data path under the store's version guard. Not done: the per-response cell, S-ref (the pending `{$ref}` read), S-record. |
1355
+
| 9 / A5 — C12 (c) client half |#3833`fix/frames-c12-server-outcome` (on #3830) | C12 (c) → c1 green (dev report), c2 red (server half) | 43,123 / 13,642 (±0) | S-adopted documented, not built (+80 B solid). |
0 commit comments