0.28.1

[Roshi's Codex PRIME]

0.28.1

DBOPFS creates application tables on demand instead of creating product-specific default folders during initialization.

• Initialization opens only the application scope. Applications use the existing getTableHandle(name) API after readyPromise when their own storage requires a table.
• Concurrent requests for the same physical table share handle creation. Logical memories and physical memory remain aliases; deleting the table clears both cached names.
• File Manager discovers existing physical directories when no explicit directory list is supplied, including its default layout.
• Explicit clearAllStorage() leaves the cleared scope empty rather than recreating defaults.
• Existing data and folders remain untouched by upgrading; there is no migration or automatic unused-folder cleanup.

The direct npm resources and public module/entity namespaces introduced in 0.28.0 remain unchanged. Server listener configuration, application policy and Node mail APIs are unchanged.

Upgrade

Update the ordinary npm dependency or alias and its lockfile to arcane-os@0.28.1, then refresh the application's current managed maps/projections through the public SDK workflow. Applications own their table creation and should wait for DBOPFS readiness only at operations that consume storage; page rendering need not wait. Existing getTableHandle callers continue to create their requested tables lazily.

Selected package

• Package source: fbbe01531428653c3b8b285448f0dacad2410971
• Check: https://github.com/TheWizardNexus/arcane-os-sdk/actions/runs/34317374328
• Artifact: 10090553468 (arcane-sdk-npm-0.28.1)
• Tarball: arcane-os-0.28.1.tgz

Publication uses that selected tarball without rebuilding current source. Consumer adoption and runtime behavior are independently owned.

Verification evidence

Selected Check 34317374328 passed package-source validation, packing and the
installed-package capability smoke on Linux. The downloaded artifact's package
metadata identifies 0.28.1 and retains the direct module/entity exports.

A supplemental Windows run of the broad runtime-api-behavior fixture exited
before its test report when a shared readiness event reached User.js and raised
ReferenceError: dbopfs is not defined. No pass is claimed for that file; the
fixture investigation is separate from the selected package. This is not evidence
of execution in a consuming application. No production server was accessed.

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.

0.27.1

[Roshi's Codex PRIME]

Changes

• Root-layout PWA generation now retains apps/<id>/arcane-sw.js and apps/<id>/arcane-offline.json at their previous URLs. The public import-map operation writes ordinary static files; SDK development serves them directly instead of redirecting worker-script requests.
• The same canonical worker and current inventory resolve resources and navigation aliases from the previous scope to the root app, including portable deployment beneath a directory and npm alias paths.
• Preserve normal browser update and activation, caches, authored installation identity and saved data. No forced activation, cache reset, application server handler or copied runtime is introduced.

Upgrade

Update the existing dependency or alias pin and lockfile to 0.27.1, then refresh managed files through the public SDK workflow. Root apps run npm exec -- arcane import-map --workspace . --app <declared-id> and deploy both the generated root PWA files and retained apps/<id>/ endpoints.

Keep the declared app ID and authored PWA manifest.id. Existing multi-app layouts and Node server/mail consumers require no root migration. Offline clients require a successful connection to obtain updated files.

Selected package evidence

Package source: 999be34735e1f21e61bb4ac04562e6cd126dd37c.

Selected Check 34313154404 passed package source validation, npm packing and the installed-package capability smoke on linux-x64. Publication uses its artifact 10089100521 unchanged.

Windows selected SDK fixtures passed: development PWA 9/9, worker 15/15, root layout 3/3. Coverage includes direct previous-endpoint serving, cached navigation learning current root aliases through inventory refresh, retained saved data, complete query handling and portable scope rebasing.

This is SDK fixture/package evidence, not real BOSS or another application's installed-PWA browser execution.

0.27.0

[Roshi's Codex PRIME]

Changes

• Optional appsRoot: "." supports a standalone root app while preserving existing apps/<id> layouts and declared app identity.
• Browser resources can use actual /node_modules/arcane-os/... paths, including npm alias folders, directly from the installed package. Managed bare and relative imports resolve to the same module instance.
• arcane import-map generates root-app static PWA files and prior /apps/<id>/ navigation pages, retaining query strings and fragments. Selected portable packages use the same installed npm paths.
• Existing physical/virtual layouts, Node mail APIs, listener settings and server entrypoints remain supported. TWiN and Stripe servers need no conversion into browser apps.

Upgrade

Update the existing exact dependency or alias pin and lockfile to 0.27.0, then regenerate managed maps through npm exec -- arcane import-map --workspace . --app <declared-id>.

Root layout is optional. New root apps can use arcane new <id> --apps-root . --path <directory>. init --apps-root . does not relocate an existing multi-app workspace. Preserve an authored PWA manifest.id; existing authored old-path pages are reported as collisions rather than overwritten.

Retaining a manifest ID and legacy HTML navigation URLs does not migrate an already-installed service worker. Root generation creates no old-path worker or offline inventory files. Automatic installed-PWA registration migration is outside this release's contract; existing app layouts remain supported.

Selected package evidence

Package source: ac0ad6ed92619a22d7be8e128aa090bbd28ec02b.

Check 34312130204 completed successfully with source validation and package production passing. Its informational Linux installed smoke exceeded the old combined-fixture timeout. The fixture received an explicit allowance for both layouts; the exact Check tarball then passed the Windows installed-package smoke, including root import maps, static PWA, development serving and portable output. The package was not rebuilt.

This is SDK package evidence, not verification of downstream application behavior.

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.

0.25.0

[Roshi's Codex PRIME] Mail requests now skip configured subscription verification when the actual requester IP equals the server-side IP of the same connection. This lets a verification service sharing that IP send its own emails without a subscriber key and also supports local development. Requests from different IPs, including other intranet machines, retain the configured verifier.

The gateway uses native socket addresses for HTTP/1.1 and HTTP/2. This requires no environment setting or domain lookup. CORS, report handling, provider delivery, caller APIs, and the existing no-verifier setup remain unchanged.

The mail guide includes an IP behavior table, and the purpose report records the three gates. Upgrade the gateway through the published arcane-os@0.25.0 package. Caller payloads need no change. Configuring a remote verification callback remains a separate host integration.

Mail guide · Purpose-gate report

GitHub Actions Check 34285710202 passed package-source validation, selected application-scope verification, tarball verification, and the informational installed Linux x64 capability smoke for source dcc0039115190daa647027fe763876b43f22b83e. The attached package is that Check run's exact selected artifact, 10079375719.

Mail-specific test source was updated and reviewed without local execution. No production request, email, or actual Windows, macOS, or Android mail execution was performed. Publication does not change a running gateway or configure its remote subscription verifier.

0.24.1

[Roshi's Codex PRIME]

This documentation patch adds the complete mail CLI parameter table and simplifies the single-key configuration examples. It explains server labels versus subscription app names, report input versus idempotency keys, and the scope of error reporting and retries. Named-profile APIs and runtime behavior remain unchanged.

The selected package from commit f7e6845 passed the hosted package source, tarball and installed-package checks in Check run 34281130898. This release uses artifact 10077642783 without repacking. No live mail or production deployment verification was performed.

See the mail parameter table and purpose-gate report.

0.24.0

[Roshi's Codex PRIME]

Mail deployments can now put host, port, exact caller origins, certificate paths and other nonsecret settings in arcane.config.json.mail, while provider credentials live in .arcane.env.json.mail. Explicit CLI/API options override file settings, and lists replace lower-priority lists.

Existing root credentials, named profiles and TLS paths remain supported. Omitted sender overrides preserve each report's sender. Direct sending shares its profile and provider settings without requiring listener certificates; an injected credential reader retains ownership of its credentials.

The packaged mail reference documents startup, HTTPS/HTTP2, configuration precedence, exact CORS behavior, credential operations and platform requirements. The method/action gate report records the purpose of each addition and simplification.

Source: 0617deb49e8d61b86a9d86626c6aa7dc5145b7b5 on main.
Verification: GitHub Check run 34275664020 completed successfully for this source, including package-source validation, the selected tarball verification, and informational installed capability smoke on Linux x64. The published package is the exact selected artifact 10075597495 from that run; publication does not rebuild it.

The mail-specific changes were reviewed in source and focused test cases were added. Local tests/checks, live email delivery, production deployment and additional platform execution were not performed for this increment.

0.23.0

[Roshi's Codex PRIME] Mail commands now read .arcane.env.json from the invocation directory, independently of the SDK installation path. Existing deployments must rename their .env.json file to .arcane.env.json while preserving its contents. Credential status now reports storage: '.arcane.env.json'. The loader reads only the new name. Provider profiles, JSON settings, relative certificate paths and HTTPS/HTTP2 port 4433 remain unchanged. Help, current references, the purpose-gate report and generated-workspace ignores follow the selected filename.

Selected source: 09b6baf. Hosted Check 34188463908 passed package source validation, tarball production/verification and the informational installed Linux x64 capability smoke. This release attaches exact artifact 10041341277 from that run. Static package review confirmed the new loader/status name and the absence of private configuration files. No local tests or live mail-server launch were performed.

0.22.1

[Roshi's Codex PRIME] Mail now defaults to HTTPS/HTTP2 port 4433 in both CLI parsing and server configuration. Explicit port overrides remain supported. Current help, mail references and the purpose-gate report describe the selected default.

Selected package source: 56455a1. Hosted Check 34182021059 passed package source validation, tarball production/verification and the informational installed Linux x64 capability smoke. This release attaches the exact artifact 10039232331 from that run. Static review confirmed both port defaults in the tarball and the absence of private .env.json configuration. No local tests or live mail-server launch were performed.