/**
 * Tera's renderer-independent public package surface.
 *
 * Everything exported here imports **no three.js, no DOM and no network**, which
 * is the property that makes the package usable from a verifier, a test harness
 * or a Node service that has no GPU. `src/test/integration/barrel.test.ts`
 * enforces it by importing this file under Node's type stripping and failing if
 * anything in the graph reaches for a renderer.
 *
 * That rule is why three of the modules this build added are conspicuously
 * absent. `src/interiors/devices.ts`, `src/engine/officeExterior.ts` and
 * `src/interiors/officeScene.ts` are the *render layers* for the same
 * simulations whose state machines are exported below — they take a `Plan` and a
 * `MaterialRegistry` and produce meshes, and exporting one of them would put
 * three.js on the package surface for every consumer of a device type.
 */
export * from "./arena/index.ts";
export * from "./actors/controller.ts";
export * from "./aircraft/controller.ts";
export * from "./devices/index.ts";
export * from "./interiors/plan.ts";
export * from "./interiors/robotActivity.ts";
export * from "./interiors/robotOperations.ts";
export * from "./interiors/robotRoutes.ts";
export * from "./interiors/types.ts";
export * from "./interiors/walker.ts";
export * from "./transport/exteriorVehicle.ts";
export * from "./transport/types.ts";
export * from "./transport/vehicleController.ts";
export * from "./transport/vehicleSim.ts";
export * from "./transport/vehicleTelemetry.ts";
