0.28.0

[Roshi's Codex PRIME]

Changes

• Root apps can use the installed npm SDK directly at /node_modules/arcane-os/..., without a copied top-level arcane/ runtime.
• Public arcane-os/modules/<filename> and arcane-os/entities/<filename> exports resolve to the actual files, including extensions. Relative component URLs and import.meta.resolve retain their existing directory. Existing lowercase exports remain.
• Direct-installed root maps omit old arcane/* and ./arcane/* keys. Before regenerating a root map, update authored imports to package names. Physical, virtual, nested and integrated layouts retain their compatible aliases.
• New root apps put the SDK in runtime dependencies. Init promotes an SDK dev dependency for root use and preserves existing runtime/optional declarations and aliases. Other packages and scripts remain unchanged.
• Shared PWA imports use the package namespace with unchanged parallel startup, storage and installation lifecycle. Server listeners and app-specific policy are unchanged.

Upgrade

Install the exact SDK version through the existing package or npm alias, retain the lockfile, and refresh managed maps/projections through the public SDK workflow. A dependency update does not require a layout migration. For direct root apps, retain the installed runtime dependency in production. ToolCallRouter, TimeGuard and WaitForComponent use arcane-os/modules/<Name>.js; Chat and User use arcane-os/entities/<Name>.js.

Selected output

Source: 7bdf9670ac96b81d1e4c63da7b46d561bdf34ff4.
Check: https://github.com/TheWizardNexus/arcane-os-sdk/actions/runs/34315964905 .
The attached tarball is the selected Check artifact, not a repack.

Hosted source validation and packing passed. The informational Linux smoke
retained one stale root-alias expectation. Fixture-only commit
37f75971acc35d6916d6db8919d61c7a702d1200 corrected it, and the exact selected
tarball passed the updated installed-package smoke on Windows (1/1), including
public exports, materialization, maps, development serving and portable output.
The package source and artifact were unchanged.

Windows SDK fixture evidence: scaffold34/34, root/nested layout4/4, public resolution5/5, PWA client10/10 and installation17/17 passed. The broader import-map suite had15/17 pass; two existing symbolic-link cases failed in the Windows test helper because t.skip is unsupported. No consumer browser/server execution is claimed. Application adoption remains owned by each application.