ballistics-engine 0.36.0 → 0.36.2

package/ballistics_engine.d.ts

@@ -158,12 +158,41 @@ export class WasmBallistics {
     runCommand(command: string): string;
 }
 
+/**
+ * The engine's versioned JSON command bridge, as one JavaScript function.
+ *
+ * One request envelope in, one response envelope out, both as strings:
+ *
+ * ```text
+ * in:   {"api_version":1,"command":"solve","request":{ … }}
+ * ok:   {"ok":true,"api_version":1,"engine_version":"…","command":"solve","result":{ … }}
+ * err:  {"ok":false,"api_version":1,"engine_version":"…","error":{"code":"…","message":"…"}}
+ * ```
+ *
+ * This is the module's programmatic surface, deliberately separate from the
+ * browser terminal above. The terminal's commands are per-feature gated because a
+ * stripped build is a smaller download; the bridge is not gateable that way — it
+ * is a single entry point onto every command the build actually contains, and it
+ * costs nothing but serde, which is already a core dependency.
+ *
+ * It is the ONLY route from JavaScript to `corrections.bc5d_table_path` and
+ * `atmosphere.pressure_reference`, and the only one that validates
+ * `effects.wind_shear_model` against a typed enum rather than silently resolving
+ * an unrecognised name to the power law.
+ *
+ * Failures arrive INSIDE the returned JSON — this never throws. Ask
+ * `meta.capabilities` for the command list, which depends on what this build
+ * compiled in rather than on what the bridge knows how to dispatch.
+ */
+export function bridgeCall(request_json: string): string;
+
 export type InitInput = RequestInfo | URL | Response | BufferSource | WebAssembly.Module;
 
 export interface InitOutput {
     readonly memory: WebAssembly.Memory;
     readonly __wbg_calculator_free: (a: number, b: number) => void;
     readonly __wbg_wasmballistics_free: (a: number, b: number) => void;
+    readonly bridgeCall: (a: number, b: number) => [number, number];
     readonly calculator_addWindSegment: (a: number, b: number, c: number, d: number) => number;
     readonly calculator_calculateTrajectory: (a: number, b: number) => [number, number, number];
     readonly calculator_clearWindSegments: (a: number) => number;
@@ -198,10 +227,10 @@ export interface InitOutput {
     readonly __wbindgen_exn_store: (a: number) => void;
     readonly __externref_table_alloc: () => number;
     readonly __wbindgen_externrefs: WebAssembly.Table;
-    readonly __externref_table_dealloc: (a: number) => void;
     readonly __wbindgen_malloc: (a: number, b: number) => number;
     readonly __wbindgen_realloc: (a: number, b: number, c: number, d: number) => number;
     readonly __wbindgen_free: (a: number, b: number, c: number) => void;
+    readonly __externref_table_dealloc: (a: number) => void;
     readonly __wbindgen_start: () => void;
 }
 

package/ballistics_engine.js

@@ -444,6 +444,49 @@ export class WasmBallistics {
     }
 }
 if (Symbol.dispose) WasmBallistics.prototype[Symbol.dispose] = WasmBallistics.prototype.free;
+
+/**
+ * The engine's versioned JSON command bridge, as one JavaScript function.
+ *
+ * One request envelope in, one response envelope out, both as strings:
+ *
+ * ```text
+ * in:   {"api_version":1,"command":"solve","request":{ … }}
+ * ok:   {"ok":true,"api_version":1,"engine_version":"…","command":"solve","result":{ … }}
+ * err:  {"ok":false,"api_version":1,"engine_version":"…","error":{"code":"…","message":"…"}}
+ * ```
+ *
+ * This is the module's programmatic surface, deliberately separate from the
+ * browser terminal above. The terminal's commands are per-feature gated because a
+ * stripped build is a smaller download; the bridge is not gateable that way — it
+ * is a single entry point onto every command the build actually contains, and it
+ * costs nothing but serde, which is already a core dependency.
+ *
+ * It is the ONLY route from JavaScript to `corrections.bc5d_table_path` and
+ * `atmosphere.pressure_reference`, and the only one that validates
+ * `effects.wind_shear_model` against a typed enum rather than silently resolving
+ * an unrecognised name to the power law.
+ *
+ * Failures arrive INSIDE the returned JSON — this never throws. Ask
+ * `meta.capabilities` for the command list, which depends on what this build
+ * compiled in rather than on what the bridge knows how to dispatch.
+ * @param {string} request_json
+ * @returns {string}
+ */
+export function bridgeCall(request_json) {
+    let deferred2_0;
+    let deferred2_1;
+    try {
+        const ptr0 = passStringToWasm0(request_json, wasm.__wbindgen_malloc, wasm.__wbindgen_realloc);
+        const len0 = WASM_VECTOR_LEN;
+        const ret = wasm.bridgeCall(ptr0, len0);
+        deferred2_0 = ret[0];
+        deferred2_1 = ret[1];
+        return getStringFromWasm0(ret[0], ret[1]);
+    } finally {
+        wasm.__wbindgen_free(deferred2_0, deferred2_1, 1);
+    }
+}
 function __wbg_get_imports() {
     const import0 = {
         __proto__: null,

package/package.json

@@ -5,7 +5,7 @@
     "Alex Jokela <email@tinycomputers.io>"
   ],
   "description": "High-performance ballistics trajectory engine with professional physics",
-  "version": "0.36.0",
+  "version": "0.36.2",
   "license": "MIT OR Apache-2.0",
   "repository": {
     "type": "git",