Skip to content

0.20.0: records at v0.20.0 and a lesson for work on every core - #6

Merged
sdogruyol merged 8 commits into
mainfrom
docs/0.20.0
Nov 2, 2026
Merged

sdogruyol merged 8 commits into
mainfrom
docs/0.20.0

Conversation

@sdogruyol

Copy link
Copy Markdown
Collaborator

Records re-recorded at v0.20.0 (224ed74fc) with wasi-sdk 24: the wasm modules (57; the new iyi/cores sample is native only, since std/http has no wasm32-wasi build), the diagnostics (13, with two new III.4 cases: share-serve-capture and share-reach), the agent loop (verdicts unchanged; MCP initialize now reports 0.20.0), highlighting (93 listings) and the stdlib reference (118 modules, adding std/acme, std/autocert, std/hpke, std/mlkem, std/ocsp, std/p384, std/secure_dns and std/shared_proc).

Also: learn step nine on spawn_parallel, Server.serve on every core, Share and @[SafeReach]; the README facts as 0.19.0 and 0.20.0 word them; and a budget row of its own for /playground/evidence/, which grows with the two new diagnostics (raised by hand to 320 KiB; --adopt lowered /playground/*/ and /404.html).

The README rewrite in iyi 4432be826 (first released in 0.19.0) moved five
sentences the generators quote: the edit-loop row is "one module's body",
the other sessions are two with no tired one, the token figure no longer
counts its runs and names AI_FIRST.md §5 instead, the object audit is
"seven of the nine" with the two that only type-check, and install.sh's
platforms are in the parenthesis above its one-liner. Against a 0.20.0
tree each generator stopped the build; with these patterns they read the
same figures from the new sentences, and the agents page and llms.txt say
where the runs are written up rather than a count README.md no longer states.
…afeReach]

Step nine, grounded in samples/iyi/cores.iyi (on iyi's release/0.20.0-prep):
spawn against spawn_parallel, the state a pool may share, Server.serve on
every core and workers: 1, config.frozen for TLS, the reach warning and
@[SafeReach], and the move off serve_parallel. Two break programs show the
capture refusal and the reach warning under --error-on-warnings
(record-diagnostics gains per-case flags); III.4's opening paragraph is the
premise; cores is native only in the wasm record, with the reason.

The records are not re-recorded here: they are evidence about a release,
and 0.20.0 is not tagged. Until `npm run record` runs at v0.20.0 this branch
does not build, by the records gate's design.
…lib at 0.20.0

Recorded at v0.20.0 (224ed74fc) with wasi-sdk 24. New: the iyi/cores sample
(native only: std/http has no wasm32-wasi build), and the two III.4 break
cases, share-serve-capture and share-reach. The stdlib reference gains
std/acme, std/autocert, std/hpke, std/mlkem, std/ocsp, std/p384,
std/secure_dns and std/shared_proc. The agent loop's verdicts are unchanged;
its MCP initialize now reports 0.20.0.
…ME's parenthesis

0.20.0's README follows "Linux x86-64, macOS arm64" with "; a program built
for macOS runs on macOS 14.4 or later, ...", and the generator counted that
note's clauses as two more platforms. The platforms are the list before the
first semicolon.
…§5 in it

The merge took main's summary with this branch's runs_where, which names the
write-up rather than a count; at 159 characters it was over what a results
page shows.
… weigh

The evidence page prints every recorded diagnostic, and 0.20.0 records two
more, share-serve-capture and share-reach: it is 293.9 KiB, over the 288.0
the tour's /playground/*/ allowed. The raise is by hand and only for that page:
it gets 320.0 KiB, and --adopt lowered /playground/*/ to 272.0 KiB and
/404.html to 224.0 KiB.
@sdogruyol
sdogruyol merged commit 36369c5 into main Nov 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant