arcane-os 0.54.1 → 0.56.0

package/CHANGELOG.md

@@ -1,5 +1,65 @@
 # Changelog
 
+## 0.56.0
+
+- Add explicit `package.nativeResources` selection for native-only application
+  files and directories. Browser selection remains unchanged; non-browser
+  packaging keeps additional resources outside browser transformations and
+  stages them in a separate target output. Applications select their complete
+  required source closure, and target adapters receive the effective target
+  and browser-PWA selection.
+- Add `getInstalledCoreClient()` to read the exact live SDK-installed client
+  without connecting or changing globals. Terminal `failTransport(error)` and
+  the owned native failure callback preserve complete errors, settle pending
+  requests, and release the failed installation's callbacks and subscriptions.
+- Add opt-in `replayRuntimeState` for Core clients and classic injection. The
+  runtime replays its actual readiness and current service state for newly
+  connected documents without restarting services or delaying page startup.
+
+- Preserve complete UTF-8 process output when a character spans stdout or stderr
+  chunks. Independent readable-stream decoders feed the same text to captured
+  results and existing event delivery; ordering, backpressure, cancellation,
+  graceful drain, nonzero error details and line-event behavior remain unchanged.
+- Include committed Windows and Linux Core process-transport source and the
+  generic Windows SEA launcher source as native-host groundwork. These sources
+  do not activate a platform host or deliver a public native executable; app
+  host composition and the remaining native integration stay independently owned.
+- Clarify development `latest` tracking, production-designated pins, matching
+  requester notices, and required documentation/site release follow-through.
+- No new dependency, application service, automatic runtime installation,
+  application default change or saved-data migration is introduced.
+
+## 0.55.0
+
+- Add public Core client, protocol contracts and classic-script source generation
+  through `arcane-os/core/client`, `core/contracts` and `core/classic-source`.
+  Native facades install synchronously; the shared event owner retains ordered
+  early events and responses. Correlation, complete payloads and diagnostics,
+  cancellation and transport-versus-service readiness remain explicit.
+- Add app-neutral native Core runtime and stdio transport through
+  `arcane-os/core/runtime` and `core/stdio`. Hosts register services, start them
+  independently and distinguish cancellable renderer requests from accepted
+  service-lifetime work. Graceful shutdown waits for accepted responses, service
+  drain/disposal and queued transport output without terminating the host.
+- Add SDK-owned portable native payload assembly and explicit application-service
+  composition through `arcane-os/native/portable-provider` and `core/host`.
+  Portable provider loading no longer requires an Arcane OS checkout; explicit
+  checkout providers remain supported. Preserve complete selected releases,
+  dependency records and the application's actual SDK version separately from
+  the builder, including partial direct browser package projections. Portable
+  output declares the host's serving, client injection and stdio responsibilities;
+  it is not an executable platform host.
+- Preserve Core client FIFO order during deferred event-owner handoff, report
+  asynchronous send failures after request settlement, retain original native
+  diagnostic fields and require callable transport sending before readiness.
+- Correct disabled-PWA packaging so selected output documents lose active SDK
+  manifest and bootstrap references before native-module processing. Preserve
+  source PWA settings, unrelated authored links, inactive HTML and unselected
+  documents; enabled PWA generation keeps its existing behavior.
+- Executable platform hosts and application host cutover remain separate work.
+  Applications retain service composition, model selection and saved settings.
+  No new dependency, automatic model loading or data migration is added.
+
 ## 0.54.1
 
 - Select the self-contained Transformers.js 4.3.0 browser CDN bundle for

package/README.md

@@ -20,9 +20,11 @@ selected SDK projection or an explicit live SDK source mount. Both profiles
 share the theme, packaging, event, cancellation,
 and browser run contracts while retaining their selected application layout.
 
-This checkout defines the `0.54.1` SDK contract. Applications pin one exact npm
-version and lockfile; registry state is deliberately not baked into application
-artifacts.
+This checkout defines the `0.56.0` SDK contract. Development applications declare
+`arcane-os` as `latest` and retain their lockfile. Exact SDK pins begin when Roshi
+designates a production build. Follow [Consumer updates](docs/consumer-updates.md)
+to refresh and compare the installed SDK and lockfile with the published channel;
+registry state is deliberately not baked into application artifacts.
 
 Standalone browser apps use their repository root and installed npm package directly, without a
 generated workspace `arcane/` directory or `arcane.lock.json`. Select the
@@ -594,10 +596,11 @@ Arcane root, shared, and native tests require the explicit shared focused-test
 form above. External app repositories retain their root `test/` plus selected
 app-test behavior.
 
-Integrated native app builds are also implemented. `--workspace` and
-`--arcane-root` must resolve to the same Arcane checkout, one `--app` and one
-declared native target are selected, and `--output-root` must resolve outside
-that checkout. The SDK then uses the same package, plan, provider, and
+Integrated native app builds select one `--app` and one declared native target,
+and `--output-root` must resolve outside that checkout. An explicit
+`--arcane-root` must resolve to the same Arcane checkout as `--workspace`;
+the default portable provider instead comes from the installed SDK package.
+The SDK then uses the same package, plan, provider, and
 same-process run lifecycle as an external app repository. Verification remains
 an explicit operation for a selected release output.
 
@@ -617,8 +620,8 @@ arcane package [--app <id>] [--dry-run]
 arcane verify [--app <id>]
 arcane bundle [--app <id>] [--artifact <file>.arcane-app.tar.gz] [--overwrite]
 arcane verify-bundle <file.arcane-app.tar.gz>
-arcane native-doctor --target <native-target> --arcane-root <directory>
-arcane native-prepare --target <native-target> --arcane-root <directory>
+arcane native-doctor --target <native-target> [--arcane-root <directory>]
+arcane native-prepare --target <native-target> [--arcane-root <directory>]
 arcane build --target <target> [--arcane-root <directory>] [--output-root <directory>] [--format <format>] [--signing <mode>]
 arcane run [--target <target>] [--app <id>] [--arcane-root <directory>] [--output-root <directory>] [--format <format>] [--signing <mode>]
 arcane targets
@@ -689,24 +692,25 @@ package installation, or assertions.
 
 ## Current target support
 
-The SDK exposes one browser target and five explicitly paired
-native development targets: a non-runnable portable directory, a
-Windows x64 unsigned-local-test EXE bundle, Linux x64 and Linux ARM64
+The SDK exposes one browser target and an SDK-owned, non-runnable portable
+payload directory. Four executable target entries require an explicit Arcane OS
+provider: a Windows x64 unsigned-local-test EXE bundle, Linux x64 and Linux ARM64
 unsigned-local-test DEBs, and an Android development-signed APK. The
 `android-arm64` APK is architecture-neutral because it contains no native ABI;
 the target name identifies its supported physical/native ARM64 run profile.
 
-Every native build requires an explicit Arcane OS checkout compatible with this
-SDK version and a canonical app descriptor that declares the
-exact selected target. The SDK never searches for or silently selects a mutable
-toolchain root. Scaffold a separate
+Portable uses the installed SDK provider without an Arcane OS checkout.
+An explicit `--arcane-root` retains the checkout provider selection; executable
+targets still require that root and their platform toolchains. Every native
+build needs a canonical app descriptor declaring the exact selected target.
+The SDK never searches for a mutable toolchain root. Scaffold a separate
 repository with the matching `--target`, or add and validate that target in the
 canonical descriptor before invoking its native command. From an external
 application repository, run one selected target:
 
 ```bash
-npm exec -- arcane native-doctor --target portable --arcane-root "../Arcane OS"
-npm exec -- arcane build --target portable --arcane-root "../Arcane OS"
+npm exec -- arcane native-doctor --target portable
+npm exec -- arcane build --target portable
 
 # Windows x64: build or build, verify, and launch in one process
 npm exec -- arcane build --target windows-x64 --arcane-root "../Arcane OS"
@@ -737,15 +741,18 @@ browser package.
 `native-prepare` is available as a standalone toolchain diagnostic. Do not run
 it automatically: the build command prepares the selected toolchain itself.
 
-The build reads the selected app release and descriptor, requires the
-Core to meet the highest minimum declared by the SDK runtime, selected app, and
-bundled dependencies, keep their declared Arcane protocol, and provide every
-required feature, capability, and method. A Core reporting a higher version is
-accepted only when it passes those same current-SDK checks; this is not a promise
-that future SDK or Core releases will remain compatible. The build copies the
-complete selected release. Portable emits an app-scoped
-Arcane Core payload under `build/portable/`; that directory is not executable
-and `arcane run --target portable` is intentionally unavailable. Windows emits
+The build passes the complete selected app release, descriptor, dependencies and
+minimum Core requirement to the provider. The SDK portable provider copies those
+payloads and generates a Core entry and synchronous classic client. Explicit
+application services use `createPortableNativeProvider({services:[{module,options}]})`
+from `arcane-os/native/portable-provider`; the default imports no OS product or
+application services. `arcane-os/core/host` owns reusable native service
+composition and shutdown. See [Core native packaging](docs/reference/core-native-packaging.md).
+Payload assembly is separate from composed-host compatibility and execution.
+The portable payload under `build/portable/` is not executable and
+`arcane run --target portable` is intentionally unavailable. No executable host,
+installer, model assets or platform build toolchain is added by this SDK
+provider. Through explicit Arcane OS providers, Windows emits
 an app-scoped executable bundle under `build/windows-x64/`. Linux emits an
 app-scoped amd64 DEB under `build/linux-x64/` or ARM64 DEB under
 `build/linux-arm64/`. Android emits one development-signed, architecture-neutral
@@ -778,7 +785,7 @@ signing, store-publishing, release, or promotion evidence.
 | Integrated Arcane checkout workflow | Yes |
 | ArcaneOllama managed-service check | Yes on supported Windows hosts |
 | SDK native plan/provider boundary | Yes |
-| Portable app-scoped Core directory | Yes, with explicit `--arcane-root`; not directly runnable |
+| Portable app-scoped payload and reusable Core entry | SDK provider by default; explicit checkout override retained; not directly runnable |
 | Windows x64 EXE bundle | Yes, unsigned local development with explicit `--arcane-root` |
 | Linux x64 DEB | Yes, unsigned local development with explicit `--arcane-root` |
 | Linux ARM64 DEB | Yes, unsigned local development on a compatible native ARM64 toolchain with explicit `--arcane-root`; native build, WebKit readiness, and cancellation evidence is recorded |