Skip to content

docs: Wasm components and charts keyed to desktop RC5, with the first public-catalog component app #486

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ymote merged 5 commits into from
Oct 11, 2026
Merged

docs: Wasm components and charts keyed to desktop RC5, with the first public-catalog component app #486

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8bfdda0
docs: Wasm components and charts keyed to desktop RC5, with the first…
ymote Oct 11, 2026
2738612
docs: RC6 is current; RC5 stays the first release with component HTTP…
ymote Oct 11, 2026
f55dada
docs: point the sockets note at its section
ymote Oct 11, 2026
e3ab613
docs: wording from the language review of the RC6 sentences
ymote Oct 11, 2026
b4c1401
Merge remote-tracking branch 'origin/main' into docs/wasm-rc5-repo-radar
ymote Oct 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/charts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ An installed app and its Glance card use the same chart vocabulary, while
retaining their own app identity, storage, consent and lifecycle. Charts draw
with Makepad's native vector renderer; they do not require a browser or JavaScript.

This integration is newer than desktop RC4. RC4 does **not** register `d3`.
[Desktop RC5](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.5) is the first release that registers `d3`; RC4 does **not**. [Repo Radar](https://github.com/ymote/octosense-repo-radar) draws its pull-request chart with `d3`, from data its own Wasm component fetches, and was installed from the public catalog on RC5.
Apps that require charts can declare `"host_api":{"required":{"charts.d3":1}}`
alongside `"requires":["host-api-v1"]`. This is a compatibility check, not a
permission. `runtime.describe` reports `charts.d3` as a non-callable runtime ABI.
Expand Down
2 changes: 1 addition & 1 deletion docs/charts.zh-CN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Shell 将固定版本的 Makepad D3 图表注册到普通 Splash 隔离 VM 中
已安装应用及其 Glance 卡片使用同一套图表，同时保留各自的应用身份、存储、
用户授权和生命周期。图表由 Makepad 原生矢量渲染器绘制，不依赖浏览器或 JavaScript。

这项集成晚于桌面 RC4；RC4 **没有**注册 `d3`。必须使用图表的应用可以在
[桌面 RC5](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.5) 是第一个注册 `d3` 的发布版本；RC4 **没有**注册。[Repo Radar](https://github.com/ymote/octosense-repo-radar) 用 `d3` 绘制 PR 图表，数据由其自带的 Wasm 组件获取，并已在 RC5 上从公开目录安装。必须使用图表的应用可以在
`"requires":["host-api-v1"]` 之外声明
`"host_api":{"required":{"charts.d3":1}}`。这是兼容性检查，不是权限。
`runtime.describe` 将 `charts.d3` 描述为不可通过请求调用的运行时 ABI。
Expand Down
17 changes: 13 additions & 4 deletions docs/wasm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,18 @@ For each, this page says whose module runs, what it can reach, which builds
have it and how it was checked. This page describes the current source tree.
Desktop 0.1.0-rc.2 and Home 0.1.0-beta.2 contain ADR 0011 core modules.
ADR 0014 shared components and the declaration-only changes below passed
final-source acceptance at `8b09e05d` on macOS and OnePlus 6. The desktop
release is [desktop RC4](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.4)
at `9266b008`. Its [archive evidence](../tools/fixtures/wasm-phone-lab/README.md#rc4-release-evidence)
final-source acceptance at `8b09e05d` on macOS and OnePlus 6.
[Desktop RC5](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.5) at `83d356c2` (11 October 2026) is
the first release in which a component's HTTPS request works ([#471](https://github.com/OctoSense-org/OctoSense/pull/471):
RC4 panicked while choosing a TLS provider on the first `wasi:http`
request) and the first with the native charts an app can require through
`charts.d3@1` ([charts](charts.md)). On it, [Repo Radar](https://github.com/ymote/octosense-repo-radar) became
the first component app installed from the official public catalog: its
[public-store acceptance](https://github.com/ymote/octosense-repo-radar/blob/main/review/acceptance-public-store-0.1.2.json) passed 93 native checks covering
live GitHub requests from the component, native charts and
component-owned state across a restart. [Desktop RC6](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.6) keeps all of
this and adds sockets. [Desktop RC4](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.4)
at `9266b008` brought the component runtime; its [archive evidence](../tools/fixtures/wasm-phone-lab/README.md#rc4-release-evidence)
records the actual package, signing and acceptance boundaries.
The isolated phone fixtures did not update installed Home.
Source, test and release status are separate.
Expand Down Expand Up @@ -61,7 +70,7 @@ App developers start from App Flow's

### Components

[ADR 0014](adr/0014-app-components-in-webassembly.md) (Accepted; desktop implementation released in RC4) adds a second
[ADR 0014](adr/0014-app-components-in-webassembly.md) (Accepted; desktop implementation released in RC4, with working component HTTPS since RC5) adds a second
kind of `fns/<name>.wasm`: a WebAssembly component, built from an ordinary
Rust crate with `cargo build --target wasm32-wasip2`. The service tells the
two kinds apart by the file's preamble, and a bundle may carry both.
Expand Down
5 changes: 2 additions & 3 deletions docs/wasm.zh-CN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,7 @@ OctoSense 中有四处用到 WebAssembly。其中一处专为运行应用自己
一个无法编译的浏览器构建。本页逐一说明：运行的是谁的模块、它能接触什么、哪些构建包含它、
如何检查过。本页描述当前源码。桌面版 0.1.0-rc.2 和 Home 0.1.0-beta.2 包含 ADR 0011 核心模块。
ADR 0014 共享组件及下文的新声明策略已在 macOS 和 OnePlus 6 上通过最终源码 `8b09e05d`
的验收。桌面发布 tag `desktop-v0.1.0-rc.4` 指向 `9266b008`；
该[桌面 RC4 预发布版](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.4)已发布，实际安装包、签名及验收范围见[归档包证据](../tools/fixtures/wasm-phone-lab/README.zh-CN.md#rc4-发布证据)。
的验收。[桌面 RC5](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.5)（源码 `83d356c2`，2026 年 10 月 11 日）是第一个组件 HTTPS 请求能正常工作的发布版本（[#471](https://github.com/OctoSense-org/OctoSense/pull/471)：RC4 在处理第一次 `wasi:http` 请求、选择 TLS provider 时会 panic），也是第一个提供原生图表的版本，应用可通过 `charts.d3@1` 声明必须使用原生图表（见[图表](charts.zh-CN.md)）。在该版本上，[Repo Radar](https://github.com/ymote/octosense-repo-radar) 成为第一个从官方公开目录安装的组件应用：其[公开商店验收](https://github.com/ymote/octosense-repo-radar/blob/main/review/acceptance-public-store-0.1.2.json)通过了 93 项原生检查，覆盖组件发出的真实 GitHub 请求、原生图表，以及重启后仍保留的组件自有状态。[桌面 RC6](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.6) 保留这一切，并新增套接字。[桌面 RC4](https://github.com/OctoSense-org/OctoSense/releases/tag/desktop-v0.1.0-rc.4)（`9266b008`）带来了组件运行时；其实际安装包、签名及验收范围见[归档包证据](../tools/fixtures/wasm-phone-lab/README.zh-CN.md#rc4-发布证据)。
独立手机测试没有更新已安装的 Home。
源码、测试与发行状态分别记录。
参见[应用能力与执行边界](capabilities.zh-CN.md)。
Expand Down Expand Up @@ -50,7 +49,7 @@ ADR 0014 共享组件及下文的新声明策略已在 macOS 和 OnePlus 6 上

### 组件

[ADR 0014](adr/0014-app-components-in-webassembly.zh-CN.md)（已接受；桌面实现随 RC4 发布）增加了第二种
[ADR 0014](adr/0014-app-components-in-webassembly.zh-CN.md)（已接受；桌面实现随 RC4 发布，组件 HTTPS 自 RC5 起可用）增加了第二种
`fns/<name>.wasm`：WebAssembly 组件，用 `cargo build --target wasm32-wasip2` 从普通的
Rust crate 构建。服务按文件头区分两者，一个应用包可以同时携带两种。

Expand Down