0.26.0

[Roshi's Codex PRIME]

Installed-package browser runtime

Browser applications can now serve SDK resources directly from their installed npm dependency without generating a workspace arcane/ directory or arcane.lock.json. Four explicit shared routes preserve the existing /arcane/... browser URLs across source serving, managed import maps, application test-map resolution, PWA inventory, and portable packaging. Existing physical projections and scaffolding remain supported.

The release adds fifteen lowercase public module subpaths for existing AI, preference, provider-state, model, conversation, storage, and local-readiness modules. The existing arcane-os/mail entrypoint now shares its canonical aggregation with managed browser imports; Node mail CLI and server-consumer APIs remain unchanged.

Upgrade

Install arcane-os@0.26.0 through the existing npm dependency or alias and update its lockfile. Existing projected consumers can continue their normal materialization workflow. To select direct installed-package browser serving, use the four-route configuration, regenerate the app's managed import map through the public CLI, and let the app owner handle any removal of its previous generated projection. No automatic conversion or deletion is performed. Portable application output continues to include its selected SDK resources.

Verification

Source: 06b1449df578c26ade3e34f79cb9a50c4ffad615.

Check 34306386039 passed package-source validation, packing, and the Linux x64 installed-package smoke for artifact 10086794389. The two focused Windows SDK fixtures passed for canonical and alias layouts. These are SDK verification results, not execution or adoption evidence for consuming applications. The attached tarball is the selected Check artifact; publication does not rebuild it.