arcane-os 0.25.0 → 0.27.0

package/CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog
 
+## 0.27.0
+
+- Add optional standalone `appsRoot: "."` discovery and `new`/`init --apps-root .`.
+  Preserve declared app IDs, existing multi-app/integrated layouts, nested pages,
+  and the selected native/portable package interface.
+- Serve and package direct installed SDK URLs under `/node_modules/<dependency>/`.
+  Managed bare and relative imports select the same module instances, including
+  npm aliases; dynamic component resources resolve from their own installed URL.
+- Generate root static PWA files and prior `/apps/<id>/` navigation pages through
+  the existing `arcane import-map` operation. Preserve authored installation IDs,
+  source/package defaults, query strings, fragments, and complete app content.
+  Ordinary static hosts need no additional SDK server or copied runtime.
+- Keep existing physical and virtual browser routes, Node mail APIs, listener
+  configuration, and server-consumer entrypoints unchanged.
+
+## 0.26.0
+
+- Add explicit installed-package browser runtime routes. Source development,
+  managed import maps, application test-map resolution, and PWA resource
+  selection can use the npm dependency directly without a generated workspace
+  runtime or lock. Keep existing browser URLs, aliases, and materialized layouts.
+- Let a shared package route select its complete source directory with
+  `include: ["."]`. Portable app output includes the selected runtime,
+  dependencies, assets, and notices without requiring the SDK at deployment.
+- Expose lowercase public module subpaths for shared AI preferences, provider
+  state, model definitions, conversation helpers, application data, document
+  libraries, and local AI readiness. Browser maps and Node package resolution
+  select the same canonical implementations; browser runtime requirements remain.
+- Share the existing portable Mail aggregation with browser import maps while
+  preserving the `arcane-os/mail` API and Node mail CLI used by server consumers.
+
 ## 0.25.0
 
 - Automatically skip configured mail subscription verification when the actual

package/README.md

@@ -19,10 +19,24 @@ 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.25.0` SDK contract. Applications pin one exact npm
+This checkout defines the `0.27.0` SDK contract. Applications pin one exact npm
 version and lockfile; registry state is deliberately not baked into application
 artifacts.
 
+External browser apps can use the installed npm package directly, without a
+generated workspace `arcane/` directory or `arcane.lock.json`. Select the
+[four installed-package routes](docs/reference/protocols.md#installed-package-browser-routes)
+in `arcane-packager.json`: development, managed import maps, and PWA resources
+read the installed SDK at real `/node_modules/arcane-os/...` browser URLs when
+each destination equals its source. An alias uses its actual installed folder.
+Select `appsRoot: "."` for a standalone root app, or scaffold one with
+`arcane new my-app --apps-root .`. After npm installation, `arcane import-map`
+refreshes managed maps and the root app's static PWA/navigation files for ordinary
+static hosting. Portable app packages still contain their selected runtime.
+Existing `apps/<id>`, virtual `/arcane` routes, and materialized workspaces remain
+supported. Node services continue to
+use the installed CLI or public imports such as `arcane-os/mail`.
+
 The [mail gateway](docs/reference/mail.md) serves HTTPS with HTTP/2 on port 4433
 by default. Configure its host, port, origin list, certificate paths, and other
 mail settings in `arcane.config.json.mail`; keep provider keys in the ignored
@@ -62,7 +76,7 @@ Create one browser application, install its pinned SDK, and start its source
 server:
 
 ```bash
-npx arcane-os@0.12.0 new hello-speech --path ./hello-speech --target browser
+npx arcane-os@0.26.0 new hello-speech --path ./hello-speech --target browser
 cd hello-speech
 npm install
 ```

package/browser-runtime/pwa-install.mjs

@@ -273,8 +273,8 @@ export function mountPwaInstallPrompt({appName = ''} = {}) {
         if (!globalThis.document) return null;
         // Both modules may start independently; saved theme loading is not a barrier.
         await Promise.all([
-            import(new URL('../modules/HTMLImport.js', import.meta.url).href),
-            import(new URL('../modules/ThemeBootstrap.js', import.meta.url).href)
+            import('arcane/HTMLImport'),
+            import('arcane/ThemeBootstrap')
         ]);
         if (owner.state.status === 'disposed') return null;
         if (!document.body) {
@@ -295,7 +295,7 @@ export function mountPwaInstallPrompt({appName = ''} = {}) {
         host.hidden = true;
         host.dataset.appName = String(appName);
         host.dataset.arcanePwaInstall = '';
-        host.setAttribute('href', new URL('../components/pwa-install.html', import.meta.url).href);
+        host.setAttribute('href', new URL('../components/pwa-install.html', import.meta.resolve('arcane/HTMLImport')).href);
         return new Promise(function waitForInstallComponent(resolve, reject) {
             const observer = new MutationObserver(function observeRemovedInstallComponent() {
                 if (!host.isConnected) cancelMount();

package/docs/architecture.md

@@ -84,13 +84,23 @@ runtime materialization, serving, and coordination with other writers. This
 path requires no application descriptor or `apps/<id>/` layout and leaves the
 app-scoped toolchain operation unchanged.
 
-An external workspace maps the exact runtime shipped by its locked `arcane-os`
-dependency. An Arcane OS checkout is an integrated SDK consumer, not the owner
+An external workspace can select `installed-v1` routes directly from its
+`node_modules/arcane-os` installation, without a workspace `arcane/` tree or
+`arcane.lock.json`. The SDK reads the installed package version and maps its
+runtime, browser runtime, runtime dependency, and licenses to the configured
+browser destinations. Direct destinations are the real npm paths. Existing
+`physical-v1` workspaces, virtual installed routes, and the explicit materializer
+remain supported. Root scaffolding selects direct npm routes; the existing
+multi-app scaffold retains its physical layout. See [installed-package routes](reference/protocols.md#installed-package-browser-routes)
+for the configuration and npm-alias form.
+
+An Arcane OS checkout is an integrated SDK consumer, not the owner
 of portable runtime source. For live shared development, the explicit
 development-only SDK source mount maps the canonical SDK runtime and dependency
-paths into that consumer. Without the mount, the workspace uses its locked SDK
-projection. The development server and packager consume the same route
-destinations in both cases, so app imports do not change. Integrated
+paths into that consumer. Without the mount, integrated workspaces retain their
+physical projection; external workspaces select either layout above. The development server,
+import-map generator, packager, and PWA inventory consume the same route
+destinations, so app imports do not change. Integrated
 initialization creates only app-owned files and never rewrites Arcane OS or SDK
 root configuration.
 
@@ -235,13 +245,24 @@ exact schema-1 `arcane-package.json` for current consumers. Existing Arcane
 apps synthesize that descriptor from their schema-1 package plus the current
 native registry during migration.
 
-An external app's `arcane-packager.json` has three exact shared routes. They map
-the installed SDK runtime to `/arcane`, its vendored strong-type dependency to
-`/node_modules/strong-type`, and the SDK's `LICENSE`,
-`COMMERCIAL-LICENSE.md`, and `NOTICE` to `/licenses/arcane-os`. Development does
-not copy SDK runtime source into the app repository. Distribution materializes
-those selected SDK routes completely inside the portable artifact, so the
-finished app has no Arcane OS runtime dependency.
+An external app can use four `installed-v1` shared routes in
+`arcane-packager.json`. With each destination equal to its source, browser URLs
+point directly into `/node_modules/arcane-os/runtime/arcane`,
+`/node_modules/arcane-os/browser-runtime`, and
+`/node_modules/arcane-os/runtime/strong-type`; the three package license files
+remain in `/node_modules/arcane-os`. An alias uses its actual installed folder.
+Source serving and import-map generation read those
+installed files without creating a workspace runtime copy. Distribution copies
+the selected routes completely inside the portable artifact, preserving the
+same URLs. Existing physical `arcane/` routes retain their behavior.
+
+`appsRoot: "."` places one standalone application at the workspace root while
+retaining its declared ID and app-relative entries. The existing `apps` option
+keeps multi-app and integrated layouts. Root static hosting consumes the same
+npm URLs, managed maps, generated PWA files, and compatibility navigation pages
+as SDK development. TWiN's ordinary static host needs no additional server;
+separate Node API hosts such as Stripe keep their existing server and SDK mail
+imports. Application location does not change their listeners or configuration.
 
 Release schema 1 and builder identity `arcane-app-packager-v1` remain unchanged
 because current Arcane native consumers treat them as public contracts. Native

package/docs/reference/cli.md

@@ -109,7 +109,7 @@ Creates one repository-shaped external application workspace and the selected
 app. It never creates more than one app or silently installs a global SDK.
 
 ```text
-arcane new <id> [--path <directory>] [--display-name <name>] [--target <target>] [--git]
+arcane new <id> [--path <directory>] [--apps-root apps|.] [--display-name <name>] [--target <target>] [--git]
 ```
 
 ### Options and result
@@ -120,6 +120,12 @@ directory as a repository. Native target scaffolds also retain `browser` and
 include the required icon. The result reports the workspace, app, descriptor,
 target, and created paths.
 
+`--apps-root .` creates a standalone root application using its installed npm
+SDK directly. The default `--apps-root apps` preserves `apps/<id>`. Root setup
+does not install dependencies or copy a runtime: run `npm install`, then
+`npm run import-map`. Until installation, its result reports the import map as
+pending with reason `sdk-install-required`.
+
 ### Example
 
 ```bash
@@ -135,7 +141,7 @@ initialization writes only the selected `apps/<id>/` boundary and does not add
 an SDK dependency to the Arcane OS repository.
 
 ```text
-arcane init [id] [--workspace <directory>] [--app <id>] [--display-name <name>] [--target <target>]
+arcane init [id] [--workspace <directory>] [--app <id>] [--apps-root apps|.] [--display-name <name>] [--target <target>]
 ```
 
 ### Errors and safety
@@ -145,6 +151,10 @@ incompatible workspace fail rather than being overwritten. Initialization is
 idempotent only for files whose existing content satisfies the scaffold
 contract.
 
+`--apps-root .` selects root setup for a standalone workspace. Omission retains
+the configured layout, or `apps` for a new configuration. `init` never moves an
+existing application or converts the integrated Arcane OS layout.
+
 ### Example
 
 ```bash
@@ -184,7 +194,7 @@ npm exec -- arcane doctor --workspace . --arcane-root "../Arcane OS"
 
 ### Overview
 
-Refreshes one selected application's physical browser runtime map, generates
+Refreshes one selected application's browser runtime map, generates
 its standard browser import map, discovers every directly navigable
 `.html`/`.htm` document admitted by the selected descriptor's existing
 include/exclude rules, and commits the map artifact plus those managed documents
@@ -211,10 +221,10 @@ The generated artifact is
 `apps/<id>/modules/arcane.importmap.json`. Its exact JSON is also installed in
 the configured entry and every other admitted browser document as `<script
 type="importmap" data-arcane-import-map>` before module loading. The complete
-physical-v1 runtime derives its entries from the installed runtime and
-browser-runtime inventories. It intentionally has no package-root mapping;
+runtime map derives its entries from the selected runtime and browser-runtime
+inventories. It intentionally has no package-root mapping;
 portable runtime subpaths such as `arcane-os/preference-store` and
-`arcane-os/speech-playback` instead map directly to their canonical projected
+`arcane-os/speech-playback` instead map directly to their canonical runtime
 modules. The result reports the complete map written to the selected
 application; no fixed entry count is a release contract.
 
@@ -224,6 +234,15 @@ list. External and modern integrated routes require `components`, `css`,
 may omit only an optional trailing `security` include. The external license
 route remains separate and second.
 
+External applications can instead select the four ordered
+[`installed-v1` routes](protocols.md#installed-package-browser-routes) in
+`arcane-packager.json`. This reads directly from the installed SDK package and
+requires neither a workspace `arcane/` directory nor `arcane.lock.json`.
+The generated browser destinations remain `arcane/`, `arcane/sdk/`, and
+`arcane/dependencies/strong-type/`; an npm alias changes package source paths,
+not those browser URLs. The SDK version comes from that installed package.
+Existing physical workspaces and scaffold output remain supported unchanged.
+
 ### Result and safety
 
 Success returns the normal selected-workspace wrapper:
@@ -308,11 +327,15 @@ Starts one development server for one selected app and maps the exact
 workspace/runtime routes. It defaults to HTTPS on localhost; `--public` enables access
 from other devices on the network, using HTTPS by default.
 
-For an external workspace, the server exposes the selected projected
-`arcane/` root, including `arcane/sdk` and `arcane/dependencies`, alongside the
-application. Integrated workspaces retain their configured physical routes.
-The explicit live-source SDK mapping remains unchanged and does not replace the
-installed projection.
+For an external workspace, the server exposes the selected SDK routes alongside
+the application. Direct `installed-v1` routes serve the real
+`/node_modules/<dependency>/...` URLs without creating a workspace runtime
+directory. Earlier virtual `/arcane` installed routes remain supported.
+Existing `physical-v1` workspaces serve
+their projected `arcane/` root. Integrated workspaces retain their configured
+physical routes.
+An explicit live-source SDK mapping follows the selected browser destinations
+while reading canonical SDK source; it never replaces installed files.
 
 ```text
 arcane dev [--app <id>] [--public] [--http | --https] [--cert <file> --key <file>] [--host <address>] [--port 8000] [--http-port 0]
@@ -504,6 +527,11 @@ shared route destinations. When selected shared content supplies no root
 Source document bases and resource URLs therefore retain their development
 layout. Packaging does not run tests or checks automatically.
 
+For `installed-v1`, the same four configured source routes supply the complete
+selected SDK content directly from `node_modules`. Only the portable output
+receives copies; no workspace `arcane/` projection is required. Its runtime URLs,
+managed import-map targets, and PWA inventory destinations match source serving.
+
 ```text
 arcane package [--app <id>] [--dry-run]
 ```

package/docs/reference/protocols.md

@@ -61,13 +61,19 @@ explicit identity fails, and the selected page then must pass exact path-relativ
 base validation.
 Included HTML with neither signal is a component fragment and remains a
 complete package file.
-`arcane-os/preference-store` and `arcane-os/speech-playback` are the two
-portable subpaths that resolve directly to canonical runtime-module namespaces
-from both Node package exports and managed browser keys;
+Public lowercase runtime subpaths resolve directly to canonical runtime-module
+namespaces from both Node package exports and managed browser keys. These
+include `arcane-os/preference-store`, `arcane-os/speech-playback`,
+`arcane-os/ai-preference-tuple`, `arcane-os/ai-preference-runtime`,
+`arcane-os/ai-provider-runtime`, `arcane-os/ai-runtime-state`,
+`arcane-os/model-definition`, `arcane-os/conversation-timebox`,
+`arcane-os/conversation-action-items`, `arcane-os/conversation-closing-report`,
+and `arcane-os/chat-records`.
 `arcane/PreferenceStore` and `arcane/SpeechPlayback` remain their established
 browser import-map names. The additional portable `arcane-os/speech-text`
 subpath owns shared speech-input cleanup and has the same
-managed browser key. There is
+managed browser key. `arcane-os/mail` remains the existing Mail aggregation.
+There is
 no exported `importMapApplication()` function, `generateImportMap()` function, or
 `arcane-os/import-map` package subpath.
 Explicit host document lists use the separate root-exported
@@ -90,6 +96,90 @@ materializes the complete required SDK runtime,
 browser-runtime, and managed-import-map closure inside that app's own artifact.
 No application polls for SDK changes.
 
+## Installed-package browser routes
+
+An external application can serve and package its installed SDK directly,
+without creating a top-level `arcane/` directory or requiring
+`arcane.lock.json`. Select `installed-v1` through these four ordered routes in
+the existing schema-1 `arcane-packager.json`; no additional layout field is
+needed:
+
+```json
+{
+  "schemaVersion": 1,
+  "appsRoot": ".",
+  "distRoot": "dist",
+  "sharedPayloads": {
+    "browser-runtime": [
+      {
+        "source": "node_modules/arcane-os/runtime/arcane",
+        "destination": "node_modules/arcane-os/runtime/arcane",
+        "include": ["components", "css", "entities", "img", "modules"],
+        "exclude": []
+      },
+      {
+        "source": "node_modules/arcane-os/browser-runtime",
+        "destination": "node_modules/arcane-os/browser-runtime",
+        "include": ["."],
+        "exclude": []
+      },
+      {
+        "source": "node_modules/arcane-os/runtime/strong-type",
+        "destination": "node_modules/arcane-os/runtime/strong-type",
+        "include": ["."],
+        "exclude": []
+      },
+      {
+        "source": "node_modules/arcane-os",
+        "destination": "node_modules/arcane-os",
+        "include": ["LICENSE", "COMMERCIAL-LICENSE.md", "NOTICE"],
+        "exclude": []
+      }
+    ]
+  }
+}
+```
+
+The first include list also accepts a final `security` entry. An npm alias such
+as `arcane-sdk` substitutes `node_modules/arcane-sdk` for the package prefix in
+all four source and destination paths. Package selection and SDK
+version come from the installed dependency, not a generated runtime lock.
+
+`arcane import-map`, `arcane dev`, packaging, and generated PWA inventories use
+the same actual npm destinations. For example, `arcane/HTMLImport` resolves to
+`./node_modules/arcane-os/runtime/arcane/modules/HTMLImport.js`, and
+`arcane-os/event-manager` resolves to
+`./node_modules/arcane-os/browser-runtime/event-manager.mjs`. A normal static
+server can serve those files directly. Source serving and map generation read installed
+files without materializing them into the workspace. A selected portable
+package copies its complete selected resources inside the artifact, preserving
+the same browser URLs and saved managed import maps.
+
+Existing `physical-v1` configurations whose first source is `arcane` remain
+supported. The explicit materializer below still refreshes those projections,
+and the default multi-app scaffold retains its existing physical layout. The
+earlier installed routes with virtual `/arcane` destinations also remain
+supported. Selecting `installed-v1`
+does not delete any preexisting workspace files. The separate host-document
+`generateDocumentImportMaps()` API continues to accept an already materialized
+runtime; its input contract is unchanged.
+
+### Optional standalone root application
+
+`appsRoot: "."` selects one application whose `arcane-app.json`,
+`arcane-package.json`, entry, and app-owned files occupy the workspace root.
+The declared application ID remains unchanged. `appsRoot: "apps"` continues
+to discover `apps/<id>` and supports the existing integrated and multi-app
+layouts. Entries and include/exclude paths remain relative to the application.
+
+Root HTML uses `<base href="./">`; nested navigable documents use their actual
+depth back to the workspace. Managed bare imports remain the public interface;
+their targets follow the selected npm routes. `arcane import-map` also writes
+root-app navigation pages for the previous `/apps/<id>/` links, preserving
+query strings and fragments. It preserves authored files at those destinations.
+For a direct-installed root PWA it generates the static PWA records at the root,
+so normal static hosting needs no SDK request handler or runtime copy.
+
 ## Installed SDK runtime materialization
 
 `materializeInstalledSdkRuntime()` is the Node entrypoint for refreshing one

package/docs/reference/pwa.md

@@ -47,6 +47,18 @@ explicit `id` and `scope` values, resolve against `./apps/<id>/`; an icon such
 as `img/library.png` therefore remains beneath the app directory. Absolute URL
 fields retain their authored destination.
 
+For `appsRoot: "."`, application URLs stay at the deployment root. Direct npm
+routes keep runtime URLs under `/node_modules/<dependency>/...`. The public
+`arcane import-map` operation generates static PWA files beside the root entry
+and adds their links to the selected navigable documents. This works with an
+ordinary static host; it does not copy the installed runtime into `arcane/`.
+The source root defaults its installation ID to `/apps/<id>/` to preserve the
+previous source identity while its start URL and scope move to the root. An
+authored `manifest.id` remains authoritative. Packaged default identity remains
+`./`. Existing `/apps/<id>/` navigation aliases retain query strings and
+fragments and lead to the selected root document. No stored application data is
+rewritten by changing the layout.
+
 `offline.include` and `offline.exclude` select literal paths or directory
 prefixes from the selected emitted inventory. An omitted or empty include list
 selects that inventory; exclusions subtract from it. App files use app-relative
@@ -108,6 +120,15 @@ app's `arcane-app.json`. Startup refreshes that app's generated
 maps and starting the server. No packaging or `dist` output is required.
 Package-only applications retain their existing descriptor workflow.
 
+With the external [`installed-v1` routes](protocols.md#installed-package-browser-routes),
+the server inventories the selected SDK directly in `node_modules`. Runtime
+resources retain their public `arcane/`, `arcane/sdk/`, and
+`arcane/dependencies/strong-type/` URLs, so offline selections use those logical
+paths rather than package filesystem paths. No workspace `arcane/` tree or
+`arcane.lock.json` is needed. Packaging uses the same route selection and copies
+the selected resources into the portable output; existing physical projections
+remain supported.
+
 Add a file or directory to `package.include` to make it part of the app's
 resources. A new file inside an already included directory needs no separate
 entry. `package.include` is an application resource selection, not a file list

package/docs/reference/sdk-api.md

@@ -5,11 +5,12 @@ The npm package exposes a Node.js ESM control plane, the portable
 `arcane-os/preference-store`, `arcane-os/speech-playback`,
 `arcane-os/speech-text`, `arcane-os/ai/tool-text-stream`, and `arcane-os/browser-device` entrypoints, and the browser-only
 `arcane-os/pwa`, `arcane-os/ai/browser-wasm` and `arcane-os/ai/browser-speech` entrypoints.
-Those package subpaths are distinct from application-facing projection modules
-in the managed browser map, such as `arcane/AIProviderRuntime`,
-`arcane/AIRuntimeState`, and `arcane/ThemeBootstrap`. Applications use those
-mapped runtime modules and call `globalThis.Arcane` for capability-gated host
-behavior; they are not additional `package.json#exports` entrypoints.
+Lowercase runtime subpaths also expose existing module namespaces through both
+Node package exports and managed browser imports, as listed below. Established
+browser names such as `arcane/AIProviderRuntime`, `arcane/AIRuntimeState`, and
+`arcane/ThemeBootstrap` remain managed-map names rather than Node package
+entrypoints. Applications call `globalThis.Arcane` for capability-gated host
+behavior.
 
 This page is the canonical inventory for every JavaScript name reachable through `package.json#exports`. The same binding can appear at the root and a focused subpath; those entrypoints are listed together. The root workspace `discoverApps` and the low-level packager `discoverApps` are intentionally separate records because they are different functions.
 
@@ -19,7 +20,8 @@ This table is the Node `package.json#exports` map: it defines package
 entrypoints for SDK/tooling code. It is distinct from the generated browser
 import map that resolves application-facing `arcane/*` modules and the focused
 EventManager entry. See [browser runtime delivery](protocols.md#browser-runtime-delivery)
-for the installed-inventory-derived physical-runtime contract in SDK `0.5.18`.
+for the shared browser destinations used by installed-package and physical
+runtime layouts.
 
 | Specifier | Purpose |
 | --- | --- |
@@ -36,6 +38,21 @@ for the installed-inventory-derived physical-runtime contract in SDK `0.5.18`.
 | `arcane-os/event-manager` | Central synchronous events, complete time-travel history, playback, and optional DOM instrumentation. |
 | `arcane-os/logging` | Shared console diagnostics controlled by the existing `user.developer` preference. |
 | `arcane-os/preference-store` | Portable preference records and injected storage adapters. |
+| `arcane-os/ai` | Existing `AI.js` provider-neutral inference and speech namespace. |
+| `arcane-os/ai-preference-tuple` | Existing `AIPreferenceTuple.js` module namespace. |
+| `arcane-os/ai-preference-runtime` | Existing `AIPreferenceRuntime.js` module namespace. |
+| `arcane-os/ai-provider-runtime` | Existing `AIProviderRuntime.js` provider selection and lifecycle namespace. |
+| `arcane-os/ai-runtime-state` | Existing `AIRuntimeState.js` state and event namespace. |
+| `arcane-os/model-definition` | Existing `ModelDefinition.js` module namespace. |
+| `arcane-os/conversation-timebox` | Existing `ConversationTimebox.js` module namespace. |
+| `arcane-os/conversation-action-items` | Existing `ConversationActionItems.js` module namespace. |
+| `arcane-os/conversation-closing-report` | Existing `ConversationClosingReport.js` module namespace. |
+| `arcane-os/chat-records` | Existing `ChatRecords.js` module namespace. |
+| `arcane-os/app-data-scope` | Existing `AppDataScope.js` application storage scope namespace. |
+| `arcane-os/core-local-model-catalog` | Existing `CoreLocalModelCatalog.js` local model catalog namespace. |
+| `arcane-os/dbopfs-document-library` | Existing `DBOPFSDocumentLibrary.js` document storage namespace. |
+| `arcane-os/local-ai-readiness` | Existing `LocalAIReadiness.js` local AI readiness namespace. |
+| `arcane-os/ollama-model-identifier` | Existing `OllamaModelIdentifier.js` model identifier namespace. |
 | `arcane-os/speech-playback` | Portable speech preparation, playback state, and injected media adapters. |
 | `arcane-os/speech-text` | Speech-input formatting cleanup for complete text and streamed chunks. |
 | `arcane-os/browser-device` | Synchronous mobile or desktop identity hints for application-owned settings. |
@@ -45,6 +62,18 @@ for the installed-inventory-derived physical-runtime contract in SDK `0.5.18`.
 | `arcane-os/ai/browser-speech` | Caller-selected browser-local Whisper STT and Kokoro TTS provider mechanisms, ordinary upstream assets, materialized/native routing, Workers, and cancellation. |
 | `arcane-os/mail` | Portable Mail runtime, durable outbox, complete transport responses, and provider-neutral acceptance contracts. |
 
+These lowercase runtime-module entrypoints expose their existing exports; they
+do not duplicate the module implementations or change their platform and
+lifecycle requirements. Node resolves them inside the installed package, while
+the managed browser map resolves the same names to the selected runtime URLs.
+Node package resolution does not make browser-only operations available in
+Node: a module still needs its documented browser globals, storage, media,
+Worker, or host capabilities when its initialization or operation uses them.
+Use `arcane-os/mail` for the existing Mail aggregation rather than importing a
+private runtime file. Its package facade and managed browser entry both expose
+the canonical `MailApi.mjs` aggregation and the same Mail, outbox, and transport
+bindings.
+
 Eight JSON schemas and `package.json` are data-only export subpaths. In Node ESM, import JSON with `with {type: 'json'}`, or resolve and read it explicitly.
 
 ### Managed AI narration
@@ -1496,6 +1525,11 @@ After full runtime replacement, it writes or replaces semantic
 `arcane.lock.json` from the actual installed dependency name, package name,
 package version, alias source, and projected roots.
 
+This operation remains available for physical workspace projections. External
+applications using [installed-package routes](protocols.md#installed-package-browser-routes)
+read directly from their installed dependency and do not need to call it or
+create `arcane.lock.json` before serving, refreshing app import maps, or packaging.
+
 ### Signature and result
 
 ```text
@@ -3643,6 +3677,10 @@ certPath, keyPath, tls, signal, onEvent}` and serves one validated
 workspace application plus its complete SDK or integrated runtime. Packaged mode uses
 `{mode:'packaged', releaseRoot, workspaceRoot, host, port, httpPort, certPath, keyPath, tls,
 signal, onEvent}` and serves the complete selected release files.
+External source mode accepts both the installed-package route layout and the
+existing physical runtime layout. Installed-package mode serves the configured
+SDK resources directly from `node_modules` at their logical browser URLs;
+it does not create a workspace `arcane/` directory or require `arcane.lock.json`.
 `host` defaults to `127.0.0.1` and accepts an
 explicit network address or hostname. Use `0.0.0.0` for all IPv4 interfaces or
 `::` for the platform's IPv6 wildcard listeners. `port` selects the HTTPS
@@ -3866,8 +3904,10 @@ async validateWorkspace({
 
 Import it from `arcane-os`. It resolves to a validation result with
 `valid`, `workspaceMode`, `workspaceRoot`, `appId`, `appRoot`, the selected
-configuration/application, lock data, and completed checks. For an external
-workspace it additionally returns the exact installed package authority:
+configuration/application, lock data where the layout uses it, and completed
+checks. External `installed-v1` selection reads package metadata directly and
+does not require a workspace `arcane.lock.json` or runtime projection. For an
+external workspace the result additionally includes the installed package:
 
 ```javascript
 {
@@ -3876,17 +3916,17 @@ workspace it additionally returns the exact installed package authority:
     packageSource,
     canonicalPackageRoot,
     packageName: 'arcane-os',
-    packageVersion: '0.5.18',
+    packageVersion,
     runtimeRoot,
     browserRuntimeRoot
   }
 }
 ```
 
-The dependency can be named `arcane-os` or be one exact npm alias for
-`npm:arcane-os@0.5.18`. The selected installation must still be one direct,
-physical, non-link package directory whose manifest identifies exactly as
-`arcane-os@0.5.18`; duplicate canonical/alias declarations reject.
+The dependency can be named `arcane-os` or use an npm alias for the selected
+`arcane-os` version. The configured package source must match that declaration;
+`packageVersion` reports the installed package's version. Duplicate
+canonical/alias declarations reject.
 `allowMissingManagedImportMap` is an internal packaging/development seam. An
 ordinary caller should leave it `false`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arcane-os",
-  "version": "0.25.0",
+  "version": "0.27.0",
   "description": "Arcane OS JavaScript SDK, project-local CLI, browser runtime, and repository-portable application packager.",
   "type": "module",
   "main": "./src/index.mjs",
@@ -17,6 +17,21 @@
     "./browser-device": "./browser-runtime/browser-device.mjs",
     "./pwa": "./browser-runtime/pwa.mjs",
     "./preference-store": "./runtime/arcane/modules/PreferenceStore.js",
+    "./ai": "./runtime/arcane/modules/AI.js",
+    "./ai-preference-tuple": "./runtime/arcane/modules/AIPreferenceTuple.js",
+    "./ai-preference-runtime": "./runtime/arcane/modules/AIPreferenceRuntime.js",
+    "./ai-provider-runtime": "./runtime/arcane/modules/AIProviderRuntime.js",
+    "./ai-runtime-state": "./runtime/arcane/modules/AIRuntimeState.js",
+    "./model-definition": "./runtime/arcane/modules/ModelDefinition.js",
+    "./conversation-timebox": "./runtime/arcane/modules/ConversationTimebox.js",
+    "./conversation-action-items": "./runtime/arcane/modules/ConversationActionItems.js",
+    "./conversation-closing-report": "./runtime/arcane/modules/ConversationClosingReport.js",
+    "./chat-records": "./runtime/arcane/modules/ChatRecords.js",
+    "./app-data-scope": "./runtime/arcane/modules/AppDataScope.js",
+    "./core-local-model-catalog": "./runtime/arcane/modules/CoreLocalModelCatalog.js",
+    "./dbopfs-document-library": "./runtime/arcane/modules/DBOPFSDocumentLibrary.js",
+    "./local-ai-readiness": "./runtime/arcane/modules/LocalAIReadiness.js",
+    "./ollama-model-identifier": "./runtime/arcane/modules/OllamaModelIdentifier.js",
     "./speech-playback": "./runtime/arcane/modules/SpeechPlayback.js",
     "./speech-text": "./browser-runtime/speech-text.mjs",
     "./ai/browser-wasm": "./browser-runtime/ai/browser-wasm.mjs",
@@ -69,7 +84,7 @@
     "test:release": "node ./bin/arcane-test.mjs test/npm-release.test.mjs",
     "test:unit": "node ./bin/arcane-test.mjs test/app-descriptor.test.mjs test/app-schema.test.mjs test/app-selection.test.mjs test/contracts.test.mjs test/doctor.test.mjs test/mail-credentials.test.mjs test/mail-outbox.test.mjs test/mail-public-api.test.mjs test/mail-send.test.mjs test/mail-transport.test.mjs test/targets.test.mjs test/workspace-operation-lock.test.mjs",
     "test:functional": "node ./bin/arcane-test.mjs test/browser-speech-providers.test.mjs test/browser-wasm-gpu-notice.test.mjs test/browser-wasm-download-resume.test.mjs test/cli.test.mjs test/dbopfs-document-library.test.mjs test/dev-server.test.mjs test/dev-pwa.test.mjs test/dom-event-instrumentation.test.mjs test/event-manager.test.mjs test/events.test.mjs test/import-map.test.mjs test/mail-cli.test.mjs test/mail-runtime.test.mjs test/mail-server.test.mjs test/modal.test.mjs test/packaging.test.mjs test/pwa-packaging.test.mjs test/pwa-client.test.mjs test/pwa-install.test.mjs test/pwa-worker.test.mjs test/persistent-ai-chat-session.test.mjs test/reference-completeness.test.mjs test/runtime-api-behavior.test.mjs test/runtime.test.mjs test/scaffold.test.mjs test/speech-playback.test.mjs test/site.test.mjs test/update-check.test.mjs",
-    "test:integration": "node ./bin/arcane-test.mjs test/integrated-shared.test.mjs test/integrated-workspace.test.mjs test/mail-browser.test.mjs test/native-plan.test.mjs test/native-provider-loader.test.mjs test/npm-release.test.mjs test/release-bundle.test.mjs test/release-capability-smoke.test.mjs test/shared-payload-batch.test.mjs test/tarball.test.mjs test/browser-wasm-cpu.test.mjs test/wllama-webgpu-runtime.test.mjs",
+    "test:integration": "node ./bin/arcane-test.mjs test/installed-package-runtime.test.mjs test/root-app-layout.test.mjs test/integrated-shared.test.mjs test/integrated-workspace.test.mjs test/mail-browser.test.mjs test/native-plan.test.mjs test/native-provider-loader.test.mjs test/npm-release.test.mjs test/release-bundle.test.mjs test/release-capability-smoke.test.mjs test/shared-payload-batch.test.mjs test/tarball.test.mjs test/browser-wasm-cpu.test.mjs test/wllama-webgpu-runtime.test.mjs",
     "test:regression": "node ./bin/arcane-test.mjs test/channel-workflows.test.mjs test/html-import-registration.test.mjs test/logging-regression.test.mjs test/markdown-speech.test.mjs test/prepared-speech.test.mjs test/native-provider-generation.test.mjs test/speech-queue-regression.test.mjs test/testing.test.mjs test/test-sets.test.mjs",
     "check": "node tools/check-source.mjs && npm test",
     "check:release": "node tools/check-source.mjs --package-only && npm run test:release",

package/runtime/arcane/components/dashboard-config.html

@@ -16,6 +16,7 @@
     const {arcaneLogging}=await import('arcane-os/logging');
 
     const host=this;
+    const componentHref=new URL(host.getAttribute('href'),document.baseURI);
     const {default:waitForComponent}=await import('../modules/WaitForComponent.js');
     const {
         effectiveDashboardVisibility,
@@ -232,7 +233,7 @@
         const items=document.createElement('section');
 
         styles.rel='stylesheet';
-        styles.href=new URL('./arcane/css/dashboard-config.css?v=2',document.baseURI).href;
+        styles.href=new URL('../css/dashboard-config.css?v=2',componentHref).href;
         heading.dataset.dashboardConfigHeading='';
         message.dataset.dashboardConfigDescription='';
         empty.className='dashboard-config-empty';

package/runtime/arcane/components/data-view.html

@@ -20,6 +20,7 @@
     const {arcaneLogging}=await import('arcane-os/logging');
 
     const host=this;
+    const componentHref=new URL(host.getAttribute('href'),document.baseURI);
     const openButton=host.shadowRoot.querySelector('#openData');
     const dataModal=host.shadowRoot.querySelector('#dataModal');
     const {default:waitForComponent}=await import('../modules/WaitForComponent.js');
@@ -89,7 +90,7 @@
             fileManager.dataset.layout=host.dataset.layout||'files';
             fileManager.setAttribute(
                 'href',
-                './arcane/components/file-manager.html?v=18'
+                new URL('./file-manager.html?v=18',componentHref).href
             );
 
             content.append(heading,fileManager);