arcane-os 0.30.0 → 0.31.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## 0.31.0
+
+- Standalone applications use their repository root and installed npm package
+  paths. New standalone projects default to `appsRoot: "."`; initialization
+  preserves an existing configured layout, and explicit multi-app workspaces
+  retain their selected application directories.
+- Remove the retired `legacyAppPaths` setting and all SDK-generated nested app
+  redirects and duplicate PWA worker/inventory files. Consumers must remove the
+  obsolete setting when upgrading. Enabled PWA files remain at the app root;
+  public SDK files remain under `node_modules/arcane-os` or the installed alias.
+- Preserve selected authored files, complete URLs and queries, installation
+  identity, saved data and caches. Generation does not delete preexisting app
+  files; application owners preserve and relocate their content independently.
+- Generated and offline app files are committed for hosting workflows to
+  consume. Existing public Node TWiN and browser APIs remain available.
+
 ## 0.30.0
 
 - Add the public `arcane-os/ai/twin-cloud` subpath with stateless `fetchRequest`

package/README.md

@@ -16,31 +16,34 @@
 `arcane-os` is the application SDK and command-line toolchain for Arcane OS. It
 supports two explicit workspace profiles: an external app repository uses the
 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.
+`arcane/` runtime. Both profiles share the theme, packaging, event, cancellation,
+and browser run contracts while retaining their selected application layout.
 
-This checkout defines the `0.30.0` SDK contract. Applications pin one exact npm
+This checkout defines the `0.31.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
+Standalone browser apps use their repository root and 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.
+`arcane new my-app` defaults to `appsRoot: "."`. After npm installation,
+`arcane import-map` refreshes managed maps and the enabled root PWA files for
+ordinary static hosting. It generates no nested app redirects or duplicate PWA
+files. Remove the retired `legacyAppPaths` setting when upgrading. Commit generated
+and offline app files for hosting workflows to consume. Portable app packages
+still contain their selected runtime.
 Root/direct maps use `arcane-os/modules/<filename>` and
 `arcane-os/entities/<filename>` (including extensions) plus the focused lowercase
 exports, rather than `arcane/*` aliases. These paths resolve to the actual npm
 files, preserving relative component URLs. New root apps put the SDK in runtime
 `dependencies`; init preserves existing runtime/optional declarations and promotes
 a root app's SDK development declaration without changing its other packages.
-Existing `apps/<id>`, virtual `/arcane` routes, and materialized workspaces remain
-supported. Node services continue to
+Explicit multi-app `appsRoot: "apps"`, virtual runtime routes, and existing
+materialized workspaces remain supported; initialization preserves their selected
+layout. 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
@@ -82,7 +85,7 @@ Create one browser application, install its pinned SDK, and start its source
 server:
 
 ```bash
-npx arcane-os@0.26.0 new hello-speech --path ./hello-speech --target browser
+npx arcane-os@0.31.0 new hello-speech --path ./hello-speech --target browser
 cd hello-speech
 npm install
 ```

package/browser-runtime/ai/browser-device-settings.mjs

@@ -74,11 +74,11 @@ export function getBrowserDeviceSettings(navigatorObject = globalThis.navigator)
 
 // Only an explicit browser adapter type or fallback flag establishes its class.
 // Vendor names and powerPreference (including Chromium's echoed request) do not.
-export function describeBrowserGpu(info, legacyFallbackAdapter) {
+export function describeBrowserGpu(info, fallbackAdapter) {
     const adapterType = is.string(info?.type) ? info.type : null;
     const isFallbackAdapter = is.boolean(info?.isFallbackAdapter)
         ? info.isFallbackAdapter
-        : is.boolean(legacyFallbackAdapter) ? legacyFallbackAdapter : null;
+        : is.boolean(fallbackAdapter) ? fallbackAdapter : null;
     let performanceStatus = 'unknown';
     if (isFallbackAdapter === true || adapterType === 'CPU') performanceStatus = 'fallback';
     else if (adapterType === 'discrete GPU') performanceStatus = 'discrete';

package/docs/reference/cli.md

@@ -120,8 +120,9 @@ 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
+Each standalone app's root is its repository root. The default `--apps-root .`
+uses the installed npm SDK directly. Explicit `--apps-root apps` selects a
+multi-app workspace with each app beneath `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`.
@@ -152,7 +153,7 @@ 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
+the configured layout, or `.` for a new standalone configuration. `init` never moves an
 existing application or converts the integrated Arcane OS layout.
 
 ### Example
@@ -217,8 +218,9 @@ the workspace does not already identify exactly one. The command accepts no
 positional arguments and supports app scope only. `arcane-os import-map` is the
 identical executable alias.
 
-The generated artifact is
-`apps/<id>/modules/arcane.importmap.json`. Its exact JSON is also installed in
+The generated artifact is `modules/arcane.importmap.json` at a standalone
+app's repository root, or `apps/<id>/modules/arcane.importmap.json` for an
+explicit multi-app workspace. 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
 runtime map derives its entries from the selected runtime and browser-runtime
@@ -228,15 +230,13 @@ portable runtime subpaths such as `arcane-os/preference-store` and
 modules. The result reports the complete map written to the selected
 application; no fixed entry count is a release contract.
 
-For `appsRoot: "."`, the artifact is `modules/arcane.importmap.json` at the
-application root. Set `"legacyAppPaths": false` in `arcane-packager.json` to
-omit SDK-generated `apps/<id>/` navigation/PWA compatibility files and aliases.
-The same workspace choice applies to `arcane dev` and `arcane package`; restart
-an already running dev server after changing it. The default remains `true`.
-Root PWA files, app/installation identity and selected authored files are
-preserved. Existing files are never deleted by this option. See
-[root-only generated output](pwa.md#root-only-generated-output) before changing
-the URLs needed by previously installed apps.
+For `appsRoot: "."`, managed imports use the installed package paths and enabled
+PWA files are written beside the root entry. The SDK generates no nested
+`apps/<id>/` redirects or duplicate PWA files and no repository-root `arcane/`
+projection. App and installation identity, saved data, and selected authored
+files remain unchanged. The same layout applies to `arcane dev` and
+`arcane package`. Generated and offline app files are committed; GitHub Actions
+consume those committed files. See [root generated output](pwa.md#root-generated-output).
 
 SDK `0.5.17` preserves the physical workspace route count and ordered include
 list. External and modern integrated routes require `components`, `css`,
@@ -531,8 +531,9 @@ npm exec -- arcane check --app hello-world
 
 Creates one complete browser release beneath `dist/<id>/`, preserving the prior
 output until the replacement is complete. It consumes saved source and managed
-import maps, places app files beneath `apps/<id>/`, and retains the configured
-shared route destinations. When selected shared content supplies no root
+import maps, keeps standalone app files at the output root, and retains the
+configured shared route destinations. Explicit multi-app workspaces retain
+their selected app beneath `apps/<id>/`. When selected shared content supplies no root
 `index.html`, the SDK generates one that opens the selected app entry.
 Source document bases and resource URLs therefore retain their development
 layout. Packaging does not run tests or checks automatically.
@@ -542,11 +543,10 @@ 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.
 
-With `appsRoot: "."`, app files retain their root-relative layout. The optional
-root-config `legacyAppPaths: false` omits SDK-generated compatibility files
-beneath `apps/<id>/` from the planned and actual output. It does not omit
-explicitly selected authored resources at those paths or change the default
-packaged installation identity. Omission or `true` preserves existing behavior.
+With `appsRoot: "."`, the planned and actual output retain root-relative app
+files and direct npm package paths. The SDK adds no nested app redirects or
+duplicate PWA worker/inventory files. Explicitly selected authored resources
+and the default packaged installation identity remain unchanged.
 
 ```text
 arcane package [--app <id>] [--dry-run]
@@ -898,10 +898,10 @@ Resend key for all its requests. An absent named key never falls back to the
 default account. Existing root `RESEND_API_KEY` and
 `MAIL_PROFILES[name].RESEND_API_KEY` remain fallbacks when the corresponding
 nested key property is absent. A nested property containing null or an empty
-string means the selected key is absent and takes precedence over a legacy key.
+string means the selected key is absent and takes precedence over a root or profile key.
 
 Set and delete preserve the file's other settings and profile containers. New
-keys are written to the nested mail member. Existing legacy keys are updated
+keys are written to the nested mail member. Existing root or profile keys are updated
 in place unless the selected nested key property exists; delete removes both
 representations of only the selected key. Status returns the selected profile,
 `provider:'resend'`, `storage:'.arcane.env.json'`, and `exists`. Delete returns
@@ -963,7 +963,7 @@ paths. It consumes the configured provider timeout and retry guidance.
 
 The Resend credential comes from the selected `.arcane.env.json` entry.
 An explicit `--profile` overrides `arcane.config.json.mail.profile`; omitting
-both selects the default `mail.apiKey`, with the legacy fallback described
+both selects the default `mail.apiKey`, with the root-key fallback described
 above. Neither the key nor report content is accepted through argv or process
 environment variables.
 
@@ -1006,7 +1006,7 @@ Add the listener's certificate paths to `arcane.config.json`:
 
 Supply an existing PEM certificate chain and its private key. Paths resolve
 relative to the selected configuration directory, or may be absolute. They
-belong to the listener regardless of the provider key selected. Legacy root
+belong to the listener regardless of the provider key selected. Existing root
 `MAIL_TLS_CERT_PATH` and `MAIL_TLS_KEY_PATH` in `.arcane.env.json` remain
 fallbacks for omitted config paths. Explicit programmatic `certPath` and
 `keyPath` options override those files. Missing TLS settings name the fields

package/docs/reference/mail.md

@@ -381,7 +381,7 @@ application name and subscriber key. Existing top-level `RESEND_API_KEY` and
 `MAIL_PROFILES[profile].RESEND_API_KEY` remain supported. A nested selected
 `apiKey` takes precedence when the property exists, including null or an empty
 string, which means the selected key is absent. Only an absent nested key
-property permits fallback to the corresponding legacy key.
+property permits fallback to the corresponding root or profile key.
 
 Programmatic operations resolve both files from `options.cwd`, then
 `options.workspaceRoot`, then `process.cwd()`, choosing the first supplied
@@ -397,7 +397,7 @@ Configuration precedence is explicit:
    An explicit null retains the option's existing meaning; it does not select
    the file value again.
 2. `arcane.config.json.mail` supplies nonsecret settings absent from those options.
-3. Legacy `.arcane.env.json` root `MAIL_TLS_CERT_PATH` and `MAIL_TLS_KEY_PATH`
+3. `.arcane.env.json` root `MAIL_TLS_CERT_PATH` and `MAIL_TLS_KEY_PATH`
    supply certificate paths absent from the selected options and config member.
 4. Remaining settings use the defaults above.
 
@@ -452,7 +452,7 @@ non-interactive alternative and rejects a TTY. Each command accepts an optional
 profile argument, defaulting to `mail` independently of `arcane.config.json.mail.profile`.
 Set and delete preserve other JSON settings and profiles; status reports
 existence without returning the key. A new credential is written to the nested
-mail member. An existing legacy credential is updated at its existing location
+mail member. An existing root or profile credential is updated at its existing location
 unless the selected nested key property exists, in which case set updates that
 nested property. Delete removes both representations of only the selected key,
 so an older key cannot reappear through fallback. Other settings and profile
@@ -500,7 +500,7 @@ guidance from the same configuration. It does not require gateway TLS paths.
 Send and serve read each required JSON file once, concurrently when both are
 needed, before consuming their settings. An injected `readCredential` remains
 the credential owner and reads once. With that injection, send reads only
-`arcane.config.json`; serve also reads `.arcane.env.json` for legacy TLS paths
+`arcane.config.json`; serve also reads `.arcane.env.json` for root TLS paths
 without interpreting its unused file credential.
 
 Start the gateway:
@@ -522,7 +522,7 @@ domain, for example `https://mail.example.com:4433/v1/mail`.
 
 Set `arcane.config.json.mail.certPath` to the PEM certificate chain and
 `mail.keyPath` to its PEM private-key file. These settings belong to the listener
-and apply regardless of the selected provider profile. The legacy root
+and apply regardless of the selected provider profile. The root
 `MAIL_TLS_CERT_PATH` and `MAIL_TLS_KEY_PATH` fields in `.arcane.env.json` remain
 fallbacks. Relative certificate paths resolve from the selected configuration
 directory, including explicit programmatic path options; absolute paths are also accepted.

package/docs/reference/protocols.md

@@ -157,16 +157,17 @@ 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
+and an explicitly selected multi-app scaffold retains its 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
+### Standalone root application
 
-`appsRoot: "."` selects one application whose `arcane-app.json`,
+Each standalone app's root is its repository root. `appsRoot: "."` selects
+that layout: `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
@@ -174,29 +175,19 @@ 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.
-
-To select root-only generated output, set `"legacyAppPaths": false` beside
-`"appsRoot": "."` in `arcane-packager.json`. This optional boolean defaults to
-`true`; it has no effect on the `appsRoot: "apps"` layout. The shared import-map
-refresh, source dev server, package inspection, dry run and package output then
-omit SDK-generated `apps/<id>/` navigation pages, navigation aliases, and the
-legacy PWA worker/offline inventory. Root PWA files and normal managed imports
-remain available. Edit the root configuration before starting `arcane dev`;
-restart an existing server after changing this workspace-level choice.
-
-This option does not change the application ID, stored data, the existing
-default installation ID or an authored `pwa.manifest.id`. It neither deletes
-existing files nor removes authored resources from the app's include/exclude
-selection. Explicitly included files under `apps/<id>/` still serve and package
-as authored resources. Previously installed launch URLs and worker update URLs
-need their old resources to remain available; retain the default compatibility
-output when those URLs still need SDK support. See the
-[root PWA compatibility boundary](pwa.md#root-only-generated-output).
+their targets follow the selected npm routes. `arcane import-map` generates
+enabled static PWA records at the app root, so normal static hosting needs no
+SDK request handler or runtime copy. Managed refresh, development serving,
+inspection, dry run and packaging add no nested `apps/<id>/` navigation pages,
+redirects, or duplicate PWA worker/inventory files. There is no output-retention
+switch for those retired records.
+
+Application identity, stored data, the existing default installation ID and an
+authored `pwa.manifest.id` remain unchanged. Authored resources continue to
+follow the app's include/exclude selection; generation does not delete existing
+files. Published SDK internals stay package-owned under `node_modules`.
+Generated and offline app files are committed, and GitHub Actions consume
+those committed files. See [root generated output](pwa.md#root-generated-output).
 
 Direct-installed root maps expose `arcane-os/modules/<filename>` and
 `arcane-os/entities/<filename>` (including extensions), plus the existing

package/docs/reference/pwa.md

@@ -38,8 +38,9 @@ comes from the selected application entry. The app owns names, icons, colors,
 display preference, routes and descriptions. Use real app icons; the SDK does
 not invent branding or claim that a browser has installed the app.
 
-Manifest URL fields are relative to the application directory. Source delivery
-and packaged delivery retain the app tree at `apps/<id>/`. For packaged output,
+Manifest URL fields are relative to the application directory. Each standalone
+app's root is its repository root. Explicit multi-app source and packaged
+delivery retain the selected app tree at `apps/<id>/`. For multi-app packaged output,
 the default `start_url` is `./apps/<id>/<entry>`, resolved from the generated
 root manifest. The default `id` and `scope` remain `./`, preserving the existing
 deployment-root installation identity. Authored relative URL fields, including
@@ -55,51 +56,30 @@ 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.
-
-Root PWA generation also retains `apps/<id>/arcane-sw.js` and
-`apps/<id>/arcane-offline.json`. These are ordinary generated files served at
-their original URLs, including on a static host. The same canonical worker and
-current inventory use root resource/navigation URLs, rebased for the previous
-scope when deployed beneath a directory. An existing worker's inventory refresh
-can learn the new navigation destinations; the browser can update the worker at
-its retained script URL through normal update and activation. No cache deletion,
-forced activation, user-data migration or application-owned server handler is
-introduced. Offline clients require a later successful connection to receive
-updated files; fixture coverage does not establish a particular installed app's
-actual browser lifecycle.
-
-### Root-only generated output
-
-For a root application, add `"legacyAppPaths": false` to the workspace's
-`arcane-packager.json`, alongside `"appsRoot": "."`. The default is `true`.
-This selects root-only SDK-generated navigation and PWA output in import-map
-refresh, `arcane dev`, package inspection/dry run, and browser packaging:
-
-- The four root PWA files remain generated normally.
-- The SDK generates no `apps/<id>/` navigation pages, legacy worker or legacy
-  offline inventory, and adds no legacy navigation aliases or dev redirects.
+`./`. App identity and saved application data remain unchanged.
+
+### Root generated output
+
+For a standalone application, `appsRoot: "."` places the app at its repository
+root. Import-map refresh, `arcane dev`, package inspection/dry run and browser
+packaging use that layout directly:
+
+- The four root PWA files are generated normally when PWA is enabled.
+- The SDK generates no `apps/<id>/` navigation pages, nested worker or duplicate
+  offline inventory, and adds no redirects for that path family.
+- Runtime resources use the selected npm package paths; no repository-root
+  `arcane/` projection is generated.
 - The default source installation ID remains `/apps/<id>/`, the default
   packaged installation ID remains `./`, and an explicit `manifest.id` remains
-  authoritative. An ID is an installation identifier, not a request to generate
-  a directory. App identity and saved application data remain unchanged.
-- Existing files are left on disk. Explicitly selected authored old-path
-  resources remain in the normal source/package/offline inventory; this setting
-  is not a deletion or migration command.
-
-Restart `arcane dev` after changing this workspace configuration. Omission or
-`true` retains the compatibility behavior described above. The option has no
-effect on apps whose configured `appsRoot` is `"apps"`.
-
-An installed app may still launch an old `/apps/<id>/` URL, and an existing
-worker registration may still update its old script/inventory URL. Disabling
-generation does not redirect those installed clients, unregister their worker,
-clear caches or guarantee their next update. Keep compatibility output enabled
-while old URLs still require SDK support, or supply the required resources
-through the application's own declared files and hosting policy. This SDK
-option alone makes no claim about any existing installation's adoption.
+  authoritative. An ID identifies the installation; it does not generate a
+  directory or a redirect.
+- Authored resources follow their normal include/exclude selection. Generation
+  does not delete existing files, stored application data, or worker caches.
+
+Generated and offline app files are committed. GitHub Actions consume those
+committed files rather than generating them. Actual multi-app workspaces keep
+their explicit `appsRoot: "apps"` layout. This source/package contract does not
+establish any particular installed application's browser lifecycle.
 
 ### Offline resource selection
 

package/docs/reference/sdk-api.md

@@ -1057,14 +1057,13 @@ async function usevalidateAppConfig(...arguments_) {
 
 Validates one root packager mapping and its fixed shared-route boundaries.
 
-The schema-1 `arcane-packager.json` accepts the optional boolean
-`legacyAppPaths`, normalized to `true` when omitted. With `appsRoot: "."`,
-setting it to `false` omits generated legacy `apps/<id>/` navigation/PWA output
-across managed-map refresh, development serving, inspection and packaging.
-It leaves installation identity and authored file selection unchanged and has
-no effect with `appsRoot: "apps"`. See
-[standalone root applications](protocols.md#optional-standalone-root-application)
-for configuration, retained-file and existing-installation behavior.
+The schema-1 `arcane-packager.json` uses `appsRoot: "."` for standalone apps:
+each app's root is its repository root. Managed-map refresh, development
+serving, inspection and packaging use root app files and direct npm package
+paths without generated nested app redirects or duplicate PWA files.
+Installation identity and authored file selection remain unchanged.
+Explicit `appsRoot: "apps"` supports real multi-app workspaces. See
+[standalone root applications](protocols.md#standalone-root-application).
 
 ### Signature and result
 
@@ -3730,7 +3729,7 @@ actual HTTPS port while preserving the original request path and query. Both lis
 use the selected host.
 
 Source servers default to HTTPS, including localhost; packaged browser previews
-require HTTPS. The legacy `https` option is accepted but `https:false` and
+require HTTPS. The existing `https` option is accepted; `https:false` and
 `tls:false` alone do not disable HTTPS. HTTPS startup reads `.arcane/dev/server-cert.pem` and
 `.arcane/dev/server-key.pem` relative to `workspaceRoot` unless explicit
 `certPath` and `keyPath` are supplied together; relative paths resolve from the
@@ -4192,7 +4191,7 @@ The operation refreshes the selected authored descriptor's `arcane-package.json`
 projection and managed import maps under one development-refresh lock, then
 releases that lock before opening the selected source listener or listeners.
 It returns their application endpoints and shared shutdown
-lifecycle. Legacy package-only apps remain unchanged. The operation generates
+lifecycle. Package-only apps remain unchanged. The operation generates
 no packaged output; enabled PWA manifests
 are served directly from the selected source resources.
 

package/docs/reviews/mail-server-purpose-review.md

@@ -489,7 +489,7 @@ files. Their explicit precedence and credential compatibility rules are in the
 | CLI's early default host, port, and send/serve profile values | Y/Y/Y | Remove premature default assignment. The same defaults remain after file configuration resolves, while explicit CLI values retain priority. Assigning defaults before reading JSON would conceal the deployment's chosen settings. |
 | `origins` string array and list replacement | Y/Y/N | Keep one exact list for multiple caller domains. Explicit options replace the file list, including empty arrays. Existing `origin`, `allowTo`, `errorTo`, and `requestTimeout` aliases remain compatible and win over their canonical programmatic names when both are supplied. No normalization or list-merging helper is needed. |
 | Root provider-key, named-profile, and TLS compatibility | Y/Y/N | Preserve supported inputs using `RESEND_API_KEY`, `MAIL_PROFILES`, `MAIL_TLS_CERT_PATH`, and `MAIL_TLS_KEY_PATH`. Nested selected key presence takes priority even when null or empty. Named profiles never select a different account's default key. Named-profile deployment use is unverified; the retained behavior is a compatibility contract. |
-| Key set/status/delete operations | Y/Y/N | Preserve credential management and secret-free status. New keys use the nested member; existing legacy keys are updated in place unless a nested key exists. Delete removes both selected representations to prevent an old credential reappearing, preserving other keys, settings, and profile containers. Key commands still default to `mail` independently of the serving profile. |
+| Key set/status/delete operations | Y/Y/N | Preserve credential management and secret-free status. New keys use the nested member; existing root or profile keys are updated in place unless a nested key exists. Delete removes both selected representations to prevent an old credential reappearing, preserving other keys, settings, and profile containers. Key commands still default to `mail` independently of the serving profile. |
 | Send configuration | Y/Y/N | Use the same profile, sender, provider-timeout, and retry-guidance settings for direct sending. A send needs provider authority and its report, so listener certificates remain a serve-only prerequisite. Reports and idempotency keys remain per-operation inputs. |
 | Explicit runtime dependencies and callbacks | Y/Y/N | Preserve `readCredential`, provider injection, observation, cancellation, and subscription callbacks as programmatic inputs. A function or signal is not JSON configuration. The portable browser mail import retains its existing dependency boundary. |
 | Shared sender omission | Y/Y/N | Preserve per-report `from` and provider-template sender selection when no shared override is configured. One listener can therefore serve independent application sender identities. |

package/package.json

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

package/src/app-layout.mjs

@@ -5,12 +5,6 @@ export function appRelativeRoot(config, appId) {
     return config.appsRoot === '.' ? '' : `apps/${appId}`;
 }
 
-// Generated compatibility URLs are separate from installation and storage identity.
-export function rootAppLegacyPath(config, appId) {
-    return config.appsRoot === '.' && config.legacyAppPaths !== false
-        ? `apps/${appId}` : undefined;
-}
-
 export function resolveAppRoot(workspaceRoot, config, appId) {
     return path.resolve(workspaceRoot, appRelativeRoot(config, appId));
 }
@@ -20,19 +14,3 @@ export function appBaseHref(workspaceRoot, appRoot, document = 'index.html') {
     const relative = path.relative(directory, workspaceRoot).split(path.sep).join('/');
     return relative ? `${relative}/` : './';
 }
-
-export function rootAppNavigation(appId, entry, documents = []) {
-    const redirects=new Map();
-    for(const document of documents)redirects.set(`apps/${appId}/${document}`,document);
-    redirects.set(`apps/${appId}/index.html`,entry);
-    return [...redirects].map(([file,target])=>{
-        const relative=path.posix.relative(path.posix.dirname(file),target);
-        const destination=JSON.stringify(relative).replaceAll('<','\\u003c');
-        return {
-            path:file,target:`/${target}`,
-            content:'<!doctype html>\n<!-- Arcane root application navigation -->\n'
-                +'<meta charset="utf-8">\n<title>Opening application</title>\n'
-                +`<script>const target=new URL(${destination},location.href);target.search=location.search;target.hash=location.hash;location.replace(target.href);</script>\n`
-        };
-    });
-}

package/src/cli/main.mjs

@@ -506,7 +506,7 @@ function operationOptions(command,parsed,cwd){
         return {
             targetPath:path.resolve(cwd,values.path??appId),
             appId,
-            appsRoot:values['apps-root']??'apps',
+            appsRoot:values['apps-root']??'.',
             displayName:values['display-name'],
             target:values.target??'browser',
             initializeGit:flags.has('git')

package/src/dev-server.mjs

@@ -6,7 +6,7 @@ import https from 'node:https';
 import os from 'node:os';
 import path from 'node:path';
 import {resolveWorkspace} from './workspace.mjs';
-import {appRelativeRoot,rootAppLegacyPath} from './app-layout.mjs';
+import {appRelativeRoot} from './app-layout.mjs';
 import {readInstalledSdkLayout} from './sdk-runtime-layout.mjs';
 import {APP_DESCRIPTOR_NAME, projectPackageManifest} from './app-descriptor.mjs';
 import {APP_CONFIG_NAME, validateAppConfig} from './packager/core.mjs';
@@ -1047,26 +1047,8 @@ async function startOwnedDevServer({
     const pwaResourceUrls = new Set();
     function developmentPwaArtifacts(selectedRoutes, assets = [], version = assetVersion) {
         const rootApp = selectedRoutes.config.appsRoot === '.';
-        const legacyAppPath = rootAppLegacyPath(selectedRoutes.config, selectedRoutes.appId);
         const appBase = applicationSourcePath(selectedRoutes.config,selectedRoutes.appId);
         const navigationAliases = {'/': selectedRoutes.startPath};
-        if (legacyAppPath) {
-            const legacyBase = `/${legacyAppPath}`;
-            navigationAliases[legacyBase] = selectedRoutes.startPath;
-            navigationAliases[`${legacyBase}/`] = selectedRoutes.startPath;
-            for (const asset of [selectedRoutes.startPath,...assets]) {
-                const pathname = new URL(asset,'http://arcane.invalid').pathname;
-                if (!/\.html?$/iu.test(pathname)) continue;
-                const segments = decodeURIComponent(pathname).split('/').filter(Boolean);
-                const mapping = selectedRoutes.mappings.find(function matchingNavigationRoute(route) {
-                    return route.prefix.every(function matchingNavigationSegment(segment,index) {
-                        return segments[index] === segment;
-                    });
-                });
-                if (mapping?.kind === 'app') navigationAliases[`${legacyBase}${pathname}`] = pathname;
-            }
-            navigationAliases[`${legacyBase}/index.html`] = selectedRoutes.startPath;
-        }
         return createPwaArtifacts(
             {
                 app: {
@@ -1085,7 +1067,6 @@ async function startOwnedDevServer({
                 ...(rootApp ? {
                     installationId:`/apps/${routeSet.appId}/`
                 } : {}),
-                legacyAppPath,
                 runtimeBase: selectedRoutes.browserRuntimeBase
                     ?? selectedRoutes.installed?.browserRuntimeBase ?? '/arcane/sdk/',
                 mode: 'development'
@@ -1177,34 +1158,17 @@ async function startOwnedDevServer({
             const target=parseRequestTarget(request.url);
             if(!target){deny(response,400,'Invalid request path.');return;}
             const {segments}=target;
-            const legacyAppRequest = mode === 'source' && rootAppLegacyPath(routeSet.config, routeSet.appId)
-                && segments[0] === 'apps' && segments[1] === routeSet.appId;
-            const legacyPwaRequest = legacyAppRequest && segments.length === 3
-                && ['arcane-sw.js', 'arcane-offline.json'].includes(segments[2]);
-            const generatedPwaPath = legacyPwaRequest
-                || ['/arcane.webmanifest', '/arcane-offline.json', '/arcane-sw.js', '/arcane-pwa.mjs']
-                    .includes(target.path);
+            const generatedPwaPath = ['/arcane.webmanifest', '/arcane-offline.json', '/arcane-sw.js', '/arcane-pwa.mjs']
+                .includes(target.path);
             const requestedMapping = currentSourceRoutes.mappings.find(function currentRequestMapping(route) {
                 return route.prefix.every(function currentRequestSegment(segment,index) {
                     return segments[index] === segment;
                 });
             });
-            const appRequest = requestedMapping?.kind === 'app' || legacyAppRequest;
+            const appRequest = requestedMapping?.kind === 'app';
             const selectedRoutes = mode === 'source' && (appRequest || segments.length === 0 || generatedPwaPath)
                 ? await refreshSourceRoutes() : currentSourceRoutes;
             const pwaEnabled = mode === 'source' ? selectedRoutes.app?.pwa?.enabled === true : routeSet.pwa;
-            const authoredLegacyResource = legacyAppRequest
-                && sourcePathAllowed(segments, selectedRoutes.app);
-            if (legacyAppRequest
-                && !(pwaEnabled && legacyPwaRequest)
-                && !authoredLegacyResource) {
-                const legacyPath = target.pathname.slice(`/apps/${routeSet.appId}`.length);
-                const location = !legacyPath || legacyPath === '/' || legacyPath === '/index.html'
-                    ? selectedRoutes.startPath : legacyPath;
-                response.writeHead(302,{location:`${location}${target.search}`});
-                response.end();
-                return;
-            }
             if (mode === 'source' && pwaEnabled
                 && generatedPwaPath) {
                 const generated = await sourcePwaArtifact(target.path, selectedRoutes);

package/src/mail-credentials.mjs

@@ -81,9 +81,9 @@ function mailCredentialEntry(settings, location) {
             : `mail.profiles[${JSON.stringify(location.profile)}].apiKey`
     };
     if (nestedSettings && Object.hasOwn(nestedSettings, 'apiKey')) return nestedEntry;
-    const legacySettings = mailProfileSettings(settings, location);
-    if (legacySettings && Object.hasOwn(legacySettings, 'RESEND_API_KEY')) {
-        return {profileSettings: legacySettings, key: 'RESEND_API_KEY', setting: location.setting};
+    const profileSettings = mailProfileSettings(settings, location);
+    if (profileSettings && Object.hasOwn(profileSettings, 'RESEND_API_KEY')) {
+        return {profileSettings, key: 'RESEND_API_KEY', setting: location.setting};
     }
     return nestedEntry;
 }

package/src/packager/core.mjs

@@ -12,7 +12,7 @@ import {
 } from 'node:fs/promises';
 import path from 'node:path';
 import {pathToFileURL} from 'node:url';
-import {appRelativeRoot,resolveAppRoot,rootAppLegacyPath,rootAppNavigation} from '../app-layout.mjs';
+import {appRelativeRoot,resolveAppRoot} from '../app-layout.mjs';
 import {readInstalledSdkLayout} from '../sdk-runtime-layout.mjs';
 import {withWorkspaceOperationLock} from '../workspace-operation-lock.mjs';
 import {
@@ -275,14 +275,11 @@ function validateSharedRoute(route,label){
 }
 
 export function validateRootConfig(value,configPath=ROOT_CONFIG_NAME){
-    assertOnlyKeys(value,new Set(['schemaVersion','appsRoot','distRoot','sharedPayloads','legacyAppPaths']),ROOT_CONFIG_NAME);
+    assertOnlyKeys(value,new Set(['schemaVersion','appsRoot','distRoot','sharedPayloads']),ROOT_CONFIG_NAME);
     if(value.schemaVersion!==1)fail(`${ROOT_CONFIG_NAME}.schemaVersion must be 1.`);
     if(!['apps','.'].includes(value.appsRoot)||value.distRoot!=='dist'){
         fail(`${ROOT_CONFIG_NAME} must bind appsRoot to "apps" or "." and distRoot to "dist".`);
     }
-    if (value.legacyAppPaths !== undefined && !is.boolean(value.legacyAppPaths)) {
-        fail(`${ROOT_CONFIG_NAME}.legacyAppPaths must be a boolean.`);
-    }
     if(!isPlainObject(value.sharedPayloads)){
         fail(`${ROOT_CONFIG_NAME}.sharedPayloads must be an object.`);
     }
@@ -297,8 +294,7 @@ export function validateRootConfig(value,configPath=ROOT_CONFIG_NAME){
         );
     }
     return {
-        schemaVersion:1,appsRoot:value.appsRoot,distRoot:'dist',sharedPayloads,configPath,
-        legacyAppPaths:value.legacyAppPaths ?? true
+        schemaVersion:1,appsRoot:value.appsRoot,distRoot:'dist',sharedPayloads,configPath
     };
 }
 
@@ -581,15 +577,6 @@ async function optionalDescriptor(context){
 async function inspectContext(context,{signal}={}){
     const records=await collectPackageRecords(context,{signal});
     const documents=await browserDocuments(records,context.config.entry);
-    const navigation=rootAppLegacyPath(context.rootConfig,context.appId)?rootAppNavigation(
-        context.appId,context.config.entry,documents.map(document=>document.path)
-    ):[];
-    for(const redirect of navigation){
-        const selected=records.find(record=>pathKey(record.destination)===pathKey(redirect.path));
-        if(selected&&!(await readFile(selected.source,'utf8')).includes('<!-- Arcane root application navigation -->')){
-            fail(`Root application navigation would replace selected content: ${redirect.path}.`);
-        }
-    }
     return {
         appId:context.appId,
         displayName:context.config.displayName,
@@ -607,7 +594,7 @@ async function inspectContext(context,{signal}={}){
         ...(context.config.adapter===undefined?{}:{adapter:context.config.adapter}),
         descriptor:await optionalDescriptor(context),
         browserDocuments:documents,
-        files:[...new Set(['index.html',...records.map(record=>record.destination),...navigation.map(redirect=>redirect.path)])].sort(compareText),
+        files:[...new Set(['index.html',...records.map(record=>record.destination)])].sort(compareText),
         output:path.relative(context.workspaceRoot,context.outputRoot).split(path.sep).join('/')
     };
 }
@@ -763,13 +750,9 @@ async function replaceDirectory(stagingRoot,outputRoot){
 async function packageWithContext(context,options={}){
     const {signal,onEvent,browserPwa=true}=options;
     const pwaEnabled=browserPwa&&context.config.pwa?.enabled===true;
-    const legacyAppPath=rootAppLegacyPath(context.rootConfig,context.appId);
     const appPath=appRelativeRoot(context.rootConfig,context.appId);
     const entryPath=appPackagePath(context,context.config.entry);
     const inspected=await inspectContext(context,{signal});
-    const navigation=legacyAppPath?rootAppNavigation(
-        context.appId,context.config.entry,inspected.browserDocuments.map(document=>document.path)
-    ):[];
     if(options.dryRun){
         return {
             appId:context.appId,
@@ -782,11 +765,7 @@ async function packageWithContext(context,options={}){
                     PWA_MANIFEST_NAME,
                     PWA_OFFLINE_MANIFEST_NAME,
                     PWA_WORKER_NAME,
-                    PWA_BOOTSTRAP_NAME,
-                    ...(legacyAppPath?[
-                        `${legacyAppPath}/${PWA_WORKER_NAME}`,
-                        `${legacyAppPath}/${PWA_OFFLINE_MANIFEST_NAME}`
-                    ]:[])
+                    PWA_BOOTSTRAP_NAME
                 ]:[])
             ].sort(compareText)
         };
@@ -824,18 +803,6 @@ async function packageWithContext(context,options={}){
         }else{
             await copyBase();
         }
-        for(const redirect of navigation){
-            throwIfAborted(signal);
-            const filePath=path.join(stagingRoot,...redirect.path.split('/'));
-            try{
-                const current=await readFile(filePath,'utf8');
-                if(!current.includes('<!-- Arcane root application navigation -->')){
-                    fail(`Root application navigation would replace package content: ${redirect.path}.`);
-                }
-            }catch(error){if(error.code!=='ENOENT')throw error;}
-            await mkdir(path.dirname(filePath),{recursive:true});
-            await writeFile(filePath,redirect.content,'utf8');
-        }
         const files=await listOutputFiles(stagingRoot,{signal});
         // Traverse actual browser resources after the adapter finishes. Files
         // included only as application documents retain their original content.
@@ -957,14 +924,6 @@ async function packageWithContext(context,options={}){
             fail(`Package output is missing its entry file: ${context.config.entry}.`);
         }
         const installed=pwaEnabled?await readInstalledSdkLayout(context.workspaceRoot,context.rootConfig):null;
-        const navigationAliases=navigation.length?{
-            './':packageResourceUrl(entryPath),
-            [`./apps/${context.appId}`]:packageResourceUrl(entryPath),
-            [`./apps/${context.appId}/`]:packageResourceUrl(entryPath),
-            ...Object.fromEntries(navigation.map(redirect=>[
-                packageResourceUrl(redirect.path),packageResourceUrl(redirect.target.slice(1))
-            ]))
-        }:undefined;
         const pwaArtifacts=pwaEnabled?createPwaArtifacts({
             app:{
                 id:context.appId,
@@ -973,9 +932,7 @@ async function packageWithContext(context,options={}){
                 entry:packageResourceUrl(entryPath)
             },
             appPath,
-            ...(legacyAppPath?{legacyAppPath}:{}),
             ...(installed?.direct?{runtimeBase:`.${installed.browserRuntimeBase}`} : {}),
-            ...(navigationAliases?{navigationAliases}:{}),
             sdkVersion:assetVersion,
             pwa:context.config.pwa,
             files,

package/src/pwa.mjs

@@ -1,6 +1,5 @@
 import Is from 'strong-type';
 import {randomUUID} from 'node:crypto';
-import path from 'node:path';
 import {createPwaWorkerScript} from './pwa-worker.mjs';
 import {versionAssetUrl} from './import-map.mjs';
 
@@ -204,7 +203,6 @@ export function createPwaArtifacts(
         runtimeBase = './arcane/sdk/',
         appBase,
         installationId,
-        legacyAppPath,
         appPath = '',
         navigationAliases,
         revision
@@ -316,47 +314,6 @@ controller.ready.catch(
         },
         {path: PWA_BOOTSTRAP_NAME, content: bootstrap}
     ];
-    if (legacyAppPath) {
-        const directory = legacyAppPath.endsWith('/') ? legacyAppPath : `${legacyAppPath}/`;
-        const priorDirectory = new URL(resourceUrl('./', directory), 'https://arcane.invalid/').pathname;
-        // Existing registrations continue updating their own script and inventory URLs.
-        function priorScopeUrl(value) {
-            if (value.startsWith('/') || /^[A-Za-z][A-Za-z0-9+.-]*:/u.test(value)) return value;
-            const resolved = new URL(value, 'https://arcane.invalid/');
-            let relative = path.posix.relative(priorDirectory, resolved.pathname);
-            if (!relative) {
-                relative = resolved.pathname.endsWith('/')
-                    ? './'
-                    : `../${path.posix.basename(resolved.pathname)}`;
-            }
-            else {
-                if (!relative.startsWith('.')) relative = `./${relative}`;
-                if (resolved.pathname.endsWith('/') && !relative.endsWith('/')) relative += '/';
-            }
-            return `${relative}${resolved.search}${resolved.hash}`;
-        }
-        const legacyOfflineManifest = {
-            ...offlineManifest,
-            assets: [...new Set([
-                ...offlineManifest.assets.map(priorScopeUrl),
-                `./${PWA_OFFLINE_MANIFEST_NAME}`
-            ])],
-            navigationAliases: Object.fromEntries(
-                Object.entries(offlineManifest.navigationAliases).map(
-                    function priorScopeNavigation([alias, target]) {
-                        return [priorScopeUrl(alias), priorScopeUrl(target)];
-                    }
-                )
-            )
-        };
-        generatedFiles.push(
-            {
-                path: `${directory}${PWA_WORKER_NAME}`,
-                content: createPwaWorkerScript(legacyOfflineManifest, priorScopeUrl(`${runtimeBase}pwa.mjs`))
-            },
-            {path: `${directory}${PWA_OFFLINE_MANIFEST_NAME}`, content: json(legacyOfflineManifest)}
-        );
-    }
     return {
         manifest,
         offlineManifest,

package/src/scaffold.mjs

@@ -316,7 +316,7 @@ async function runGitInit(workspaceRoot,signal,onEvent){
 export async function createWorkspace({
     targetPath,
     appId,
-    appsRoot='apps',
+    appsRoot='.',
     displayName,
     target='browser',
     initializeGit=false,
@@ -400,7 +400,7 @@ export async function initWorkspace({
     },async workspaceOperationLease=>{
     const profile=await existingWorkspaceProfile(resolvedRoot);
     const workspaceMode=profile?.workspaceMode??'external';
-    const selectedAppsRoot=appsRoot??profile?.config.appsRoot??'apps';
+    const selectedAppsRoot=appsRoot??profile?.config.appsRoot??'.';
     if(!['apps','.'].includes(selectedAppsRoot))fail('appsRoot must be apps or .','ARCANE_USAGE');
     if(profile&&selectedAppsRoot!==profile.config.appsRoot){
         fail('appsRoot must match the existing workspace layout; init does not relocate an application.','ARCANE_USAGE');
@@ -439,6 +439,7 @@ export async function initWorkspace({
     const template=workspaceMode==='integrated'
         ?workspaceTemplate({
             appId,
+            appsRoot:selectedAppsRoot,
             displayName,
             appOnly:true,
             namedImports:true,

package/src/templates/workspace-template.mjs

@@ -60,12 +60,12 @@ export function createWorkspaceLockDocument({
 
 export function workspaceTemplate({
     appId,
-    appsRoot='apps',
+    appOnly=false,
+    appsRoot=appOnly?'apps':'.',
     displayName,
     sdkDependencyName=SDK_NAME,
     sdkDependencySpecifier=SDK_VERSION,
     sdkPackageSource=`node_modules/${sdkDependencyName}`,
-    appOnly=false,
     namedImports=true,
     minimumCoreVersion='0.8.12',
     target='browser',
@@ -199,6 +199,7 @@ import map in every directly navigable descriptor-admitted \`.html\`/\`.htm\`
 document. HTML component fragments remain package files but do not receive a
 document-level base or managed import map.
 Development, package, and build refresh that shared inventory when the selected operation needs it.
+Commit generated import maps and enabled offline app files. Hosting workflows consume those committed files rather than generating them.
 Named \`${directRuntime?'arcane-os/modules/* and arcane-os/entities/*':'arcane/*'}\` imports resolve through the managed map to the selected SDK files. Packaging copies the complete selected application, runtime, and specifier
 map to \`dist/${appId}\` without running application tests. Run \`verify\` only when
 the user explicitly selects verification or a release artifact that requires it;

package/src/toolchain.mjs

@@ -12,7 +12,6 @@ import {
 import {loadArcaneIntegratedProvider} from './integrated-provider-loader.mjs';
 import {startDevServer} from './dev-server.mjs';
 import {applyPwaEntryReferences,generateImportMap,readApplicationTestImportMapContext} from './import-map.mjs';
-import {rootAppLegacyPath,rootAppNavigation} from './app-layout.mjs';
 import {createPwaArtifacts} from './pwa.mjs';
 import {readInstalledSdkLayout} from './sdk-runtime-layout.mjs';
 import {withWorkspaceOperationLock} from './workspace-operation-lock.mjs';
@@ -327,48 +326,15 @@ async function refreshPreparedImportMap(prepared,{signal,onEvent,workspaceOperat
 async function refreshRootApplicationFiles(prepared,inspected,importMap,{signal,onEvent}){
     const {workspaceRoot,appId}=prepared;
     const manifest=prepared.validation.app.manifest;
-    const legacyAppPath = rootAppLegacyPath(prepared.validation.config, appId);
-    const navigation = legacyAppPath ? rootAppNavigation(
-        appId,
-        manifest.entry,
-        inspected.browserDocuments.map(
-            function rootBrowserDocumentPath(document) {
-                return document.path;
-            }
-        )
-    ) : [];
-    // These aliases belong to the SDK only after generation; retained app files stay authored.
-    for(const redirect of navigation){
-        throwIfAborted(signal);
-        try{
-            const current=await readFile(path.join(workspaceRoot,...redirect.path.split('/')),'utf8');
-            if(!current.includes('<!-- Arcane root application navigation -->')){
-                throw new ArcaneError(ERROR_CODES.workspaceInvalid,
-                    `Root application navigation would replace authored content: ${redirect.path}.`);
-            }
-        }catch(error){if(error.code!=='ENOENT')throw error;}
-    }
     const installed=await readInstalledSdkLayout(workspaceRoot,prepared.validation.config);
     const entry=`/${manifest.entry.split('/').map(encodeURIComponent).join('/')}`;
     const navigationAliases={
-        '/':entry,
-        ...(legacyAppPath ? {
-            [`/${legacyAppPath}`]:entry,
-            [`/${legacyAppPath}/`]:entry,
-            ...Object.fromEntries(
-                navigation.map(
-                    function rootNavigationAlias(redirect) {
-                        return [`/${redirect.path}`,redirect.target];
-                    }
-                )
-            )
-        } : {})
+        '/':entry
     };
     // The source host serves the installed files in place. There is no runtime projection.
     const files=[...new Set([
         ...inspected.files.filter(file=>file!=='index.html'||manifest.include.includes('index.html')),
-        importMap.artifactRelativePath,
-        ...navigation.map(redirect=>redirect.path)
+        importMap.artifactRelativePath
     ])];
     const pwa=installed?.direct&&manifest.pwa?.enabled?createPwaArtifacts({
         app:{id:appId,displayName:manifest.displayName,version:manifest.version,entry},
@@ -378,12 +344,11 @@ async function refreshRootApplicationFiles(prepared,inspected,importMap,{signal,
         basePath:'/',
         appBase:'/',
         installationId:`/apps/${appId}/`,
-        legacyAppPath,
         runtimeBase:installed.browserRuntimeBase,
         mode:'development',
         navigationAliases
     }):null;
-    for(const file of [...navigation,...(pwa?.files??[])]){
+    for(const file of pwa?.files??[]){
         throwIfAborted(signal);
         const filePath=path.join(workspaceRoot,...file.path.split('/'));
         await mkdir(path.dirname(filePath),{recursive:true});
@@ -402,7 +367,7 @@ async function refreshRootApplicationFiles(prepared,inspected,importMap,{signal,
     }
     await emit(onEvent,{
         type:'import-map.root-files.completed',appId,
-        navigation:navigation.map(redirect=>redirect.path),
+        navigation:[],
         pwa:pwa?.files.map(file=>file.path)??[]
     });
 }