Repository navigation
docs: components keyed to desktop RC5 and the Repo Radar public-catalog proof - #189
Merged
Merged
Conversation
…og proof RUST.md (+zh): the recorded release baseline is desktop RC5 (source 83d356c2), the first release where a component's HTTPS works (RC4 panicked choosing a TLS provider on the first wasi:http request, OctoSense #471) and the first with native charts an app can require through charts.d3@1 (#470). Repo Radar is cited as the first component app installed from the official public catalog, with what its component is and the limits it works within; the releases row, the call-path sentence and the network section's validation scope follow. The test section says how an app that requires wasm-components-v1 or host-api-v1 is tested, since card-host cannot drive its functions or refuses it: the compatible release with the shell's Makepad instrument, as Repo Radar's native acceptance scripts. AGENTS.md: the component bullet names the merged OctoSense PRs, RC5 and the Repo Radar proof; the card-host bullet says where such an app is tested; two "compatible RC2 release" references become "compatible release". The script-app template's AGENTS.md gains the paragraph for an app with its own component. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
# Conflicts: # AGENTS.md # docs/RUST.md # docs/RUST.zh-CN.md
…component HTTPS and charts Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Rust guide and the agent instructions keyed to what is now true for Wasm components: desktop RC5 is the first release where a component's HTTPS works, and Repo Radar is the first component app installed from the official public catalog.
83d356c2): RC4 panicked while choosing a TLS provider on a component's firstwasi:httprequest (OctoSense #471), and RC5 registers the native charts an app can require withcharts.d3@1(#470). Repo Radar is cited as the public-catalog proof, with what its component is and the limits it works within (one request per call, a 3 s request timeout under the 10 s deadline, 2 MiB of parsed response). The releases row, the call-path sentence and the network section's validation scope follow. The test section says how an app that requireswasm-components-v1orhost-api-v1is tested, sincecard-hostcannot drive it: the compatible release with the shell's Makepad instrument, as Repo Radar's native acceptance scripts.card-hostbullet says where such an app is tested; two "compatible RC2 release" references become "compatible release", so they no longer age with each RC.cargo test,octo wasm build, the compatible release with the instrument, never dropping arequiresentry to pass a preview), the rule Repo Radar had to add by hand.What was checked on 11 October 2026 before writing this: the sample's component tests pass natively (18);
tools/octo wasm buildwith this repository'smain(27df17f3) reproduced the published 0.1.2 component byte for byte;tools/octo checkwith ahubfrom App Hubmain(fb70ddd) passed the bundle; and the published component bytes ran under OctoSensemain's runtime through thewasm_callexample (#455) with a live HTTPS search of GitHub. The RC5 release page and the sample's public-store acceptance receipt are the sources for the release facts.Rebased after desktop RC6 and the RC6 docs pass (#191): the new paragraph sits between the sockets paragraph and the historical RC4 baseline, and the releases row, call-path and test sentences name RC6 as well. Not changed here: CAPABILITIES'
wasmrow and the HOST-API-FAMILIESwasmrow still describe RC4 or RC2; that re-target belongs with the release coordination.python3 tools/check-links.py: 0 broken. An independent language judge scored the English and Chinese additions; its replacements are applied.🤖 Generated with Claude Code