docs: name all three too-large caps in process@1.1.0 error-code#21
Conversation
The doc only mentioned the 1 MiB per-call write-stdin cap, but the host also rejects a spawn-request.stdin prelude over 4 MiB with too-large. Docs-only; no structural change to the frozen contract. process@1.0.0 is untouched (byte-frozen as published).
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the documentation comment for the too-large error in the host/process@1.1.0.wit interface. The description now explicitly details the applicable payload caps, including the 4 MiB spawn-request.stdin prelude, the 1 MiB per-call write-stdin limit, and the cumulative per-process write quota. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
Pull request overview
Updates the WIT interface documentation for astrid:process@1.1.0 to better describe when error-code.too-large is returned, aligning the enum docs with the documented stdin payload caps.
Changes:
- Expands
error-code.too-largedocumentation to enumerate thespawn-request.stdinprelude cap,write-stdincap, and cumulative per-process quota. - Clarifies that the 4 MiB stdin cap is per-spawn (cumulative) for the
spawn-request.stdinprelude.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| /// Payload exceeded the applicable cap: the 4 MiB | ||
| /// `spawn-request.stdin` prelude (per spawn, cumulative), the | ||
| /// 1 MiB per-call `write-stdin` limit, or the cumulative | ||
| /// per-process write quota. |
Summary
error-code.too-largeinprocess@1.1.0only documented the 1 MiB per-callwrite-stdincap, but the host also rejects aspawn-request.stdinprelude over 4 MiB (cumulative per spawn) withtoo-large— the record field says so, the error enum didn't. Flagged by review on sdk-rust#62.Docs-only: no structural change to the frozen contract, so no linker impact.
process@1.0.0is untouched — it stays byte-frozen as published.https://claude.ai/code/session_01NvX2tE7tgXuCRevqqiXTGU