[路线图 / Roadmap] v0.4.0 发布与高价值完整度 / v0.4.0 release and high-value completeness

中文

当前状态（2026-09-08）

React v0.4.0 已通过 GitHub Release → Actions 正式发布，并完成独立下游 runtime 验证。发布 Issue #52 与 PR #53 已完成；当前进入发布后的高价值完整度阶段。

• Release：https://github.com/Respo/react.mbt/releases/tag/v0.4.0
• Actions：https://github.com/Respo/react.mbt/actions/runs/33825535658

已完成

• #42 / #57 — 首批 7 个 DOM 元素与 19 项属性映射，已合并；

• #56 — files/submitter 受检访问与浏览器符合度；

• #54 / #55 — 可运行 Quick Start 与独立生产浏览器验证；

• #40 — 公共 API 文档完整性与全量门禁；

• #45 — v0.3.0 发布与下游消费验证；

• #49 / #50 / #51 — dom-ffi 0.4.0 升级、SyntheticEvent 原生视图、Pointer/Wheel/FormData 首批迁移与重复 extern 审计；

• #52 / #53 — React v0.4.0 GitHub Release → Actions 发布、资产上传及精确版本下游验证。

后续高价值顺序

当前进行中：#44 拖放 DataTransfer 受检访问已通过 PR #58 合并；复用 dom-ffi 0.4.0，不升级依赖；本地 63/63 MoonBit、17/17 Chromium、245/245 API 文档。

1. #44：拖放文本/文件切片先交付，然后协调 clipboard/items/types 与 dom-ffi。
2. #42 已关闭；template/slot 与更广的表单/ARIA 属性保留为候选，按具体使用需求选择，不视作已实现。
3. #43：仅在明确 Node SSR 支持决策后开始。
4. #41：保持 P2，待核心 DOM/事件体验稳定后推进。

统一量化门槛

• Issue 和 PR 分别展示中文与 English。
• 每项 API 映射 React 19.2.8 稳定契约；不以 API 数量代替行为符合度。
• MoonBit 类型/转换使用 unit tests；DOM、事件、生命周期、调度、async/SSR 使用 Chromium 或 Node 真实 runtime tests。
• PR 报告测试总数、runtime 场景数、精确调用/节点/载荷计数以及 diagnostics；非预期 React warnings/errors、page errors、unhandled rejections 必须为 0。
• 公共 API 必须有 doc comments，并维持自动发现的 100% 文档门禁。
• 发布仅由 GitHub Release 触发 Actions；发布完成需精确版本下游 check/build、Node SSR 与 Chromium render/hydration 全部通过。

下一切片：Respo/dom-ffi.mbt#23 已提交 ClipboardEvent 与 types/items 读取基础，待审核；先合并并通过 Release → Actions 发布，再升级 React。条目增删与 getAsString 仍待后续。

English

Current status (2026-09-08)

React v0.4.0 has been formally published through GitHub Release → Actions with independent downstream runtime verification. Release issue #52 and PR #53 are complete; work now moves to the post-release high-value completeness phase.

• Release: https://github.com/Respo/react.mbt/releases/tag/v0.4.0
• Actions: https://github.com/Respo/react.mbt/actions/runs/33825535658

Completed

• #42 / #57 — first 7 DOM elements and 19 property mappings, merged;

• #56 — checked files/submitter access and browser conformance;

• #54 / #55 — runnable Quick Start and independent production-browser verification;

• #40 — complete public API documentation and full gate;

• #45 — v0.3.0 publication and downstream verification;

• #49 / #50 / #51 — dom-ffi 0.4.0 upgrade, SyntheticEvent native view, initial Pointer/Wheel/FormData migration, and duplicate-extern audit;

• #52 / #53 — React v0.4.0 GitHub Release → Actions publication, asset upload, and exact-version downstream verification.

Next high-value order

In progress: PR #58 merged with #44 checked drag DataTransfer access, reusing dom-ffi 0.4.0 without a dependency upgrade; locally 63/63 MoonBit, 17/17 Chromium, 245/245 public API docs.

1. #44: deliver drag text/files first, then coordinate clipboard/items/types with dom-ffi.
2. #42 is closed; template/slot and broader form/ARIA properties remain candidates driven by concrete usage, not completed work.
3. #43: start only after an explicit Node SSR support decision.
4. #41: keep at P2 until core DOM/event ergonomics are stable.

Shared quantitative gate

• Issues and PRs render 中文 and English separately.
• Every API maps to a stable React 19.2.8 contract; API counts do not substitute for behavioral conformance.
• MoonBit type/conversion behavior uses unit tests; DOM, events, lifecycle, scheduling, async, and SSR use real Chromium or Node runtime tests.
• PRs report total tests, runtime scenario counts, exact call/node/payload counts, and diagnostics; unexpected React warnings/errors, page errors, and unhandled rejections must be zero.
• Public APIs require doc comments and must preserve the auto-discovered 100% documentation gate.
• Publication is triggered only by GitHub Release Actions; completion requires exact-version downstream check/build, Node SSR, and Chromium render/hydration.

Next slice: Respo/dom-ffi.mbt#23 supplies ClipboardEvent and types/items readers, pending review. Merge and publish through Release → Actions before upgrading React. Item mutation and getAsString remain follow-ups.

Start by reading the roadmap entries for #44, #43, and #41, then review Respo/dom-ffi.mbt#23 and the Release → Actions checks described here. This issue is complete only when a specific slice is selected, implemented, reviewed, and verified against the stated unit, Chromium or Node runtime, documentation, and exact-version release gates.