arcane-os 0.54.1 → 0.55.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +31 -0
- package/README.md +31 -26
- package/browser-runtime/core/client.mjs +491 -0
- package/browser-runtime/core/contracts.mjs +84 -0
- package/docs/architecture.md +31 -23
- package/docs/compatibility.md +10 -1
- package/docs/platform-targets.md +20 -11
- package/docs/reference/README.md +8 -6
- package/docs/reference/availability-and-normalization.md +4 -2
- package/docs/reference/behavioral-testing.md +7 -6
- package/docs/reference/cli.md +12 -4
- package/docs/reference/core-client.md +120 -0
- package/docs/reference/core-native-packaging.md +149 -0
- package/docs/reference/core-runtime.md +175 -0
- package/docs/reference/inventory/package-api.json +257 -5
- package/docs/reference/protocols.md +16 -1
- package/docs/reference/sdk-api.md +772 -15
- package/package.json +10 -3
- package/schemas/native-build-plan.schema.json +8 -0
- package/src/cli/main.mjs +8 -6
- package/src/core/host.mjs +23 -0
- package/src/core/runtime.mjs +333 -0
- package/src/core/stdio.mjs +209 -0
- package/src/core-classic-source.mjs +43 -0
- package/src/import-map.mjs +62 -0
- package/src/native/portable-layout.mjs +184 -0
- package/src/native/portable-provider.mjs +211 -0
- package/src/native-plan.mjs +10 -4
- package/src/native-provider-loader.mjs +15 -4
- package/src/packager/core.mjs +47 -18
- package/src/targets/index.mjs +3 -1
- package/src/toolchain.mjs +20 -5
|
@@ -39,7 +39,7 @@ a nonzero CLI status.
|
|
|
39
39
|
Machine output uses `arcane-cli-events/1`. Native planning and providers use:
|
|
40
40
|
|
|
41
41
|
- `arcane-target-adapter/1` for target adapters;
|
|
42
|
-
- `arcane-native-build-plan/1` for
|
|
42
|
+
- `arcane-native-build-plan/1` for native plans with complete selected release inputs;
|
|
43
43
|
- `arcane-native-builder/1` for injected native builders;
|
|
44
44
|
- `arcane-integrated-toolchain/1` for the fixed integrated shared/Core provider.
|
|
45
45
|
|
|
@@ -47,6 +47,15 @@ These protocols normalize orchestration and results. They do not normalize a
|
|
|
47
47
|
Windows EXE, Linux DEB, Android APK, and portable directory into the same
|
|
48
48
|
artifact kind.
|
|
49
49
|
|
|
50
|
+
Portable CLI operations load the installed SDK's
|
|
51
|
+
`arcane-os/native/portable-provider` by default. Explicit `--arcane-root`
|
|
52
|
+
selection retains the checkout provider route; executable targets still need
|
|
53
|
+
their platform provider/toolchain. `arcane-os/core/host` composes the reusable
|
|
54
|
+
native runtime with explicitly supplied app services. Neither export is a
|
|
55
|
+
browser import, executable host or installer. The synchronous classic facade
|
|
56
|
+
and browser-safe client retain their separate public entries. Integrated
|
|
57
|
+
shared checks keep their existing Arcane OS development provider.
|
|
58
|
+
|
|
50
59
|
App-scoped managed browser imports have three supported control-plane entrypoints. The CLI
|
|
51
60
|
uses `arcane import-map`; Node callers use
|
|
52
61
|
`executeOperation('import-map', options)` or
|
|
@@ -236,6 +245,12 @@ For an extension, select `browserPwa:false` for that artifact and place the
|
|
|
236
245
|
complete SDK-produced app beneath the app-owned extension root. The application
|
|
237
246
|
owns its manifest, toolbar/background launcher and permissions. Ordinary browser
|
|
238
247
|
PWA configuration and generated browser output remain independently available.
|
|
248
|
+
Before native-module processing, the stage removes active `data-arcane-pwa`
|
|
249
|
+
scripts and manifest relationships targeting the package's `arcane.webmanifest`
|
|
250
|
+
from the existing selected PWA document set. Authored bases resolve those links;
|
|
251
|
+
unrelated manifest URLs, other link relationships, comments, templates and other
|
|
252
|
+
inactive HTML retain their content. Source documents and saved PWA settings
|
|
253
|
+
remain unchanged; the operation does not sweep every packaged HTML file.
|
|
239
254
|
|
|
240
255
|
## Installed-package browser routes
|
|
241
256
|
|