arcane-os 0.3.4 → 0.3.5

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.3.5
+
+- Preserved complete AI and chat runtime content across multi-choice streaming,
+  parallel tool calls, terminal values, transcripts, progress, incidents, and
+  saved JSONL records without ordinary truncation, freezing, or silent loss.
+- Initialized AI from the canonical ready user even when a compatibility event
+  carries a different user projection, including an immediate readiness recheck
+  after listener registration.
+- Preserved shared chat, speech, and voice-transcription lifecycle across
+  persisted page-cache navigation, including transcript restoration, retry and
+  cancellation ownership, and terminal cleanup on ordinary unload.
+
 ## 0.3.4
 
 - Allowed external and integrated physical SDK workspaces to omit the optional

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.3.4` SDK contract. Applications pin one exact npm
+This checkout defines the `0.3.5` SDK contract. Applications pin one exact npm
 version and lockfile; registry state is deliberately not baked into application
 artifacts.
 
@@ -126,7 +126,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.3.4 new my-app --path ./my-app --target portable --git
+npx arcane-os@0.3.5 new my-app --path ./my-app --target portable --git
 cd my-app
 npm install
 npm run check
@@ -137,7 +137,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.3.4
+npm install --save-dev --save-exact arcane-os@0.3.5
 npm exec -- arcane init my-app --target portable
 ```
 
@@ -153,7 +153,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.3.4` for the initial bootstrap because it names this npm
+Use `npx arcane-os@0.3.5` 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`,
@@ -174,7 +174,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.3.4.tgz
+npm install --save-dev --save-exact ../arcane-os-sdk/arcane-os-0.3.5.tgz
 npm run check
 npm ci
 ```
@@ -184,7 +184,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.3.4` registry package and
+the local declaration with the exact `arcane-os@0.3.5` registry package and
 commit the regenerated lock.
 
 Generated repositories use `npm ci --ignore-scripts` in CI. Run dependency
@@ -322,7 +322,7 @@ package installation, or assertions.
 
 ## Current target support
 
-Version `0.3.4` exposes one browser target and five explicitly paired
+Version `0.3.5` 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