arcane-os 0.11.2 → 0.11.3

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.11.3
+
+- Require Wllama's model-context load result to report success before publishing
+  model readiness. Failed initialization now follows the existing cleanup and
+  error path instead of allowing conversation requests against a failed context.
+  Preserve CPU and GPU selection, cached models, complete payloads, and cancellation.
+
 ## 0.11.2
 
 - Show mobile speech feedback only during requested or active voice loading.

package/README.md

@@ -19,7 +19,7 @@ version-locked SDK runtime, while an integrated Arcane checkout uses its live
 `arcane/` runtime. Both profiles preserve the same app URLs, theme, packaging,
 event, cancellation, and browser run contracts.
 
-This checkout defines the `0.11.2` SDK contract. Applications pin one exact npm
+This checkout defines the `0.11.3` SDK contract. Applications pin one exact npm
 version and lockfile; registry state is deliberately not baked into application
 artifacts.
 
@@ -41,7 +41,7 @@ Create one browser application, install its pinned SDK, and start its source
 server:
 
 ```bash
-npx arcane-os@0.11.2 new hello-speech --path ./hello-speech --target browser
+npx arcane-os@0.11.3 new hello-speech --path ./hello-speech --target browser
 cd hello-speech
 npm install
 npm run dev
@@ -392,7 +392,7 @@ uses the same controller for automatic memory extraction.
 Create a new repository-shaped Arcane application with the exact stable SDK:
 
 ```bash
-npx arcane-os@0.11.2 new my-app --path ./my-app --target portable --git
+npx arcane-os@0.11.3 new my-app --path ./my-app --target portable --git
 cd my-app
 npm install
 npm run dev
@@ -402,7 +402,7 @@ To enroll an existing repository, install the exact SDK and initialize only
 missing Arcane files:
 
 ```bash
-npm install --save-dev --save-exact arcane-os@0.11.2
+npm install --save-dev --save-exact arcane-os@0.11.3
 npm exec -- arcane init my-app --target portable
 ```
 
@@ -418,7 +418,7 @@ npm exec -- arcane-os targets
 No global SDK install or standalone Arcane CLI is required. The application
 repository's exact npm dependency and lockfile own the CLI and toolchain version.
 
-Use `npx arcane-os@0.11.2` for the initial bootstrap because it names this npm
+Use `npx arcane-os@0.11.3` for the initial bootstrap because it names this npm
 package explicitly; bare `npx arcane` outside an installed project could resolve
 a different package. Both installed commands invoke the same headless toolchain.
 Project-local npm scripts use the SDK pinned by that app's `package-lock.json`,
@@ -438,7 +438,7 @@ node ./bin/arcane.mjs new local-app --path ../local-app --target portable --git
 
 # From the generated app repository
 cd ../local-app
-npm install --save-dev --save-exact ../arcane-os-sdk/arcane-os-0.11.2.tgz
+npm install --save-dev --save-exact ../arcane-os-sdk/arcane-os-0.11.3.tgz
 npm ci
 ```
 
@@ -447,7 +447,7 @@ same location. The lockfile retains the selected package dependency while
 Arcane uses the installed package name and version. Local directory `file:` dependencies are not
 accepted because npm may install them as links; use a packed `.tgz`. A GitHub
 runner also needs that tarball at the locked path. After publication, replace
-the local declaration with the exact `arcane-os@0.11.2` registry package and
+the local declaration with the exact `arcane-os@0.11.3` registry package and
 commit the regenerated lock.
 
 Generated repositories use `npm ci --ignore-scripts` in CI. Run dependency
@@ -586,7 +586,7 @@ package installation, or assertions.
 
 ## Current target support
 
-Version `0.11.2` exposes one browser target and five explicitly paired
+Version `0.11.3` exposes one browser target and five explicitly paired
 native development targets: a non-runnable portable directory, a
 Windows x64 unsigned-local-test EXE bundle, Linux x64 and Linux ARM64
 unsigned-local-test DEBs, and an Android development-signed APK. The

package/browser-runtime/ai/browser-wllama-runtime.mjs

@@ -575,6 +575,13 @@ export function createPackagedWllamaRuntime({ logger = arcaneLogging } = {}) {
           "Wllama did not confirm a successfully loaded model.",
         );
       }
+        const loadedContext = next.getLoadedContextInfo();
+        if (loadedContext.success !== true) {
+            throw runtimeFailure(
+                'ARCANE_AI_LOAD_FAILED',
+                'Wllama failed to create the model context.'
+            );
+        }
       let adapter = null;
       if (webgpuRequired) {
           const telemetryOperation = trackOperation(

package/docs/reference/ai/browser-wasm.md

@@ -146,8 +146,11 @@ bar is indeterminate. Downloaded-file completion is not activation completion.
 The metadata tensor count and GPU layer assignment are descriptive only:
 upstream reports assigned layers before model-weight loading has finished.
 The pinned runtime does not expose a measured overall initialization fraction
-or a shader-compilation completion count. Readiness still requires the load
-operation to resolve and the runtime to confirm the model is loaded.
+or a shader-compilation completion count. Readiness requires the load operation
+to resolve, Wllama to report the model loaded, and its public
+`getLoadedContextInfo()` result to report `success:true`. A failed model context
+rejects loading with `ARCANE_AI_LOAD_FAILED`, releases the owned session, and
+leaves the provider in `error` with `loaded:false` before inference can begin.
 
 While a load remains active, the provider repeats its current record every five
 seconds with `heartbeat:true` and an updated `elapsedMs`. During initialization,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arcane-os",
-  "version": "0.11.2",
+  "version": "0.11.3",
   "description": "Arcane OS JavaScript SDK, project-local CLI, browser runtime, and repository-portable application packager.",
   "type": "module",
   "main": "./src/index.mjs",