RuView v0.9.0-realtek-beta.1

This prerelease introduces the Rust-first RTL8720F 2.4 GHz radar transport and RuView ingestion path. It is intentionally simulator-validated until Realtek hardware and the vendor SDK callback ABI arrive.

Included

• ADR-263 records the upstream Ameba integration and licensing boundary.
• ADR-264 defines a versioned, bounded, CRC-protected radar envelope.
• rtl8720f-sim emits deterministic CFR, near-range, far-range, interference, and capability reports to UDP or replay files.
• The sensing server validates RTL8720F datagrams, publishes bounded summaries over /ws/sensing, and exposes the latest report at /api/v1/radar/latest.
• Synthetic provenance is retained end to end as realtek:simulated; simulator data is never presented as hardware data.

Compatibility

The adapter tracks the radar control surface proposed by Ameba RTOS pull request #1336 (wifi_radar_config, AT+RAD, and AT+RADDBG). The stable Ameba RTOS v1.2.1 release does not yet expose the complete radar receive callback ABI, so no vendor-private headers or binary libraries are copied into this release.

Validation status

• Rust codec round trips, corruption rejection, size bounds, and deterministic simulator tests pass.
• RuView server ingestion, REST reporting, and source provenance were exercised end to end over loopback UDP.
• Windows release binaries are built from this branch and accompanied by SHA-256 checksums.

Known limitations

• No physical RTL8720F board has been flashed or measured.
• The vendor report callback and exact report layouts remain an SDK/hardware validation gate; the adapter boundary may change when those arrive.
• This beta exposes transport and aggregate radar observability. Radar-to-pose, vital-sign inference, RF calibration, and accuracy claims are not enabled.
• 2.4 GHz radar reports are not mislabeled as mmWave or Wi-Fi CSI events.

Do not deploy this prerelease for safety-critical, medical, or occupancy billing uses. It is an integration beta for SDK and hardware bring-up.