@rsc-kit/mcp 0.29.9 → 0.29.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/guides/ppr.md CHANGED
@@ -43,6 +43,13 @@ shell is served on its own and the client fills the boundaries when it
43
43
  hydrates, exactly as it did before any of this existed. A slower hole, never a
44
44
  wrong page.
45
45
 
46
+ The document is one render, not two. Hydrating needs the page as a payload as
47
+ well as HTML, and the browser fetches it right after the document; that fetch
48
+ is answered with the payload the document's own render produced, kept for the
49
+ few seconds it takes to come back for it under a token only that document
50
+ carries. A product page reads its product once per visit, and the tree the
51
+ browser hydrates against is the one its HTML was made from.
52
+
46
53
  The shell is stored per route **pattern**, not per url. `/posts/[slug]` has one
47
54
  shell serving every slug, because everything that varies by slug is behind a
48
55
  boundary the request fills. That includes the metadata: a route with a
@@ -101,9 +101,12 @@ about to hold. The next request starts from what it arrives with.
101
101
 
102
102
  Two things, and they are not the same kind:
103
103
 
104
- **How it was served**, always: `X-RSC-Kit: stored`, `rendered` or `shell` on
105
- every response — a page from a file the build wrote, a page rendered for this
106
- visitor, or a stored shell with its holes rendered now. It is the header a
104
+ **How it was served**, always: `X-RSC-Kit: stored`, `rendered`, `shell` or
105
+ `held` on every response — a page from a file the build wrote, a page rendered
106
+ for this visitor, a stored shell with its holes rendered now, or the payload
107
+ the browser hydrates from, kept by the document's own render rather than
108
+ rendered a second time (`held` is what a boot fetch should say; `rendered`
109
+ there means the token missed, and the page was rendered again). It is the header a
107
110
  developer reads in the Network tab when a page is slower than expected, the
108
111
  way `X-Nextjs-Cache` is, and a CDN rule or a health check can key on it. It
109
112
  names no product, so there is nothing to strip.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rsc-kit/mcp",
3
- "version": "0.29.9",
3
+ "version": "0.29.10",
4
4
  "description": "An MCP server over what an rsc-kit build decided: the routes, why each one is static or not, and what it costs the browser.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -34,7 +34,7 @@
34
34
  },
35
35
  "dependencies": {
36
36
  "@modelcontextprotocol/sdk": "^1.30.0",
37
- "create-rsc-kit": "^0.29.9",
37
+ "create-rsc-kit": "^0.29.10",
38
38
  "zod": "^3.25"
39
39
  },
40
40
  "devDependencies": {