arcane-os 0.10.0 → 0.10.1

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.10.1
+
+- Open developer error modals only for newly captured live incidents. Restoring
+  pending diagnostics after navigation or reload continues scheduled delivery
+  and retry without reopening old modals. Preserve complete stored incidents
+  and the existing behavior for new errors.
+
 ## 0.10.0
 
 - Add opt-in application PWA configuration, generated installation and offline

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.10.0` SDK contract. Applications pin one exact npm
+This checkout defines the `0.10.1` 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.10.0 new hello-speech --path ./hello-speech --target browser
+npx arcane-os@0.10.1 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.10.0 new my-app --path ./my-app --target portable --git
+npx arcane-os@0.10.1 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.10.0
+npm install --save-dev --save-exact arcane-os@0.10.1
 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.10.0` for the initial bootstrap because it names this npm
+Use `npx arcane-os@0.10.1` 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.10.0.tgz
+npm install --save-dev --save-exact ../arcane-os-sdk/arcane-os-0.10.1.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.10.0` registry package and
+the local declaration with the exact `arcane-os@0.10.1` 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.10.0` exposes one browser target and five explicitly paired
+Version `0.10.1` 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/docs/reference/runtime-modules.md

@@ -84,7 +84,7 @@ own asynchronous work, cancellation, and backpressure.
 | [`DirectoryPicker.js`](#directorypickerjs) | esm | Wraps the provider-owned native directory chooser and normalizes selected/cancelled/error results. | Native bridge | Complete mutable caller options and provider result fields; coded cancellation and malformed-result errors. |
 | [`DocumentLexicalSearch.js`](#documentlexicalsearchjs) | esm | Provides dependency-free deterministic metadata/body ranking and complete excerpts. | Cross-host | Mutable complete results with no storage, provider, or network side effects. |
 | [`DocumentNavigation.js`](#documentnavigationjs) | esm | Binds document navigation, filtering, history, current-item reveal, and load initialization. | Browser / native WebView | Normalized filter/navigation state; DOM effects preserved. |
-| [`Errors.js`](#errorsjs) | esm | Normalizes global errors/rejections, fingerprints and deduplicates incidents, persists a complete ledger, and performs complete delivery. | Browser / native WebView hybrid | Incident records normalized; storage/mail failures isolated. |
+| [`Errors.js`](#errorsjs) | esm | Normalizes global errors/rejections, assigns occurrence identifiers, persists a complete ledger, and performs complete delivery. | Browser / native WebView hybrid | Incident records normalized; storage/mail failures isolated. |
 | [`GifEncoder.js`](#gifencoderjs) | esm | Encodes indexed frames into a complete animated GIF using palette mapping and LZW. | Cross-host | Normalized complete binary output. |
 | [`HTMLImport.js`](#htmlimportjs) | esm | Defines the same-origin `<html-import>` loader with open shadow root, inline script execution, and readiness/error events. | Browser / native WebView | Public error detail normalized; fetch/DOM failure preserved. |
 | [`InMemoryCommunicationProvider.js`](#inmemorycommunicationproviderjs) | esm | Implements deterministic in-memory thread/message/send behavior for demos and tests. | Cross-host | Normalized communication entities. |
@@ -1998,6 +1998,12 @@ console.log(Object.keys(module));
 
 Normalizes global errors/rejections, assigns occurrence identifiers, persists a complete ledger, and performs complete delivery.
 
+Developer modals are offered only for newly captured live incidents. Loading
+pending records from a prior page preserves their complete diagnostics and
+delivery/retry state without reopening their modals. This remains true when
+developer preferences become ready after restoration. A newly captured error
+still follows the ordinary developer-mode presentation path.
+
 ### Public surface
 
 default `Errors`; event normalizers plus lifecycle, capture, delivery and teardown methods.

package/package.json

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

package/runtime/arcane/modules/Errors.js

@@ -477,6 +477,7 @@ class Errors {
             return;
         }
 
+        // Restored records resume delivery; only live capture offers developer modals.
         const timestamp=this.now();
         for(const storedRecord of records){
             if(
@@ -519,7 +520,6 @@ class Errors {
             if(!record.retryRequired){
                 this.scheduleRecord(record,dueAt-timestamp);
             }
-            this.offerDeveloperIncident(record.incident,record.occurrenceId);
         }
 
         this.persistLedger();