1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
//! Host-side type-safe bindings for `wit/v0/orts.wit`.
//!
//! `wasmtime::component::bindgen!` parses the WIT world at compile
//! time and emits:
//!
//! - Rust record types (`Vec3`, `Quat`, `SpacecraftState`, `Command`,
//! `Observation`, ...) matching the WIT records / variants.
//! - A trait (`PluginImports`) that the host must implement to
//! provide the `host-env` interface (`log`, `magnetic-field-eci`).
//! - A typed handle (`Plugin`) that wraps a `wasmtime::component::Instance`
//! and exposes the guest's `controller` interface
//! (`sample-period-s`, `init`, `initial-command`, `update`,
//! `current-mode`) as strongly-typed methods.
//!
//! Phase P1-b1 only generates the bindings and confirms they
//! compile. Phase P1-b2 wires them up inside `WasmController`, and
//! P1-b3 provides the host `env` implementation.
//!
//! The emitted types live under `orts::plugin::wasm::bindings::*`;
//! downstream code in `orts::plugin::wasm` re-exports whatever it
//! needs. The wit-bindgen output is **private to this module** so
//! that the public plugin-layer API (in `orts::plugin`) never leaks
//! generated types to downstream crates.
// Path is relative to the crate root (`orts/Cargo.toml`), so
// `wit/v0/orts.wit` resolves to `orts/wit/v0/orts.wit`. The WIT
// definition lives inside the crate rather than at the workspace
// root so the crate is self-contained and the `bindgen!` macro does
// not reach out of its own source tree.
//
// Phase P1 runs guests synchronously on the Pulley interpreter
// (wasmtime default is blocking, no `async` opt-in needed).
// Phase P6 may revisit for hot reload or long-running operations.
//
// Phase P1-b3 will likely need `trappable_imports: true` so that
// host `host-env` functions (log, magnetic-field-eci) can return
// `Result<_, wasmtime::Error>` and trap the guest cleanly on
// failure instead of propagating a panic.
bindgen!;