arcane-os 0.79.0 → 0.79.1
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
CHANGED
|
@@ -1,5 +1,14 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.79.1
|
|
4
|
+
|
|
5
|
+
- Classify generic speech-model progress callbacks as loading, reserving
|
|
6
|
+
download status for the resource owner that actually transfers a resource.
|
|
7
|
+
Preserve initialization status, complete progress details and file counts.
|
|
8
|
+
- Keep cancellation, cached-resource reporting, model selection and speech
|
|
9
|
+
behavior unchanged. This corrects a progress label; it does not establish or
|
|
10
|
+
repair a repeated network transfer.
|
|
11
|
+
|
|
3
12
|
## 0.79.0
|
|
4
13
|
|
|
5
14
|
- Add public `createExecutionDeviceCatalog()` and `createExecutionDeviceService()`
|
package/README.md
CHANGED
|
@@ -20,7 +20,7 @@ selected SDK projection or an explicit live SDK source mount. Both profiles
|
|
|
20
20
|
share the theme, packaging, event, cancellation,
|
|
21
21
|
and browser run contracts while retaining their selected application layout.
|
|
22
22
|
|
|
23
|
-
This checkout defines the `0.79.
|
|
23
|
+
This checkout defines the `0.79.1` SDK contract. Development applications declare
|
|
24
24
|
`arcane-os` as `latest` and retain their lockfile. Exact SDK pins begin when Roshi
|
|
25
25
|
designates a production build. Follow [Consumer updates](docs/consumer-updates.md)
|
|
26
26
|
to refresh and compare the installed SDK and lockfile with the published channel;
|
|
@@ -1817,7 +1817,7 @@ export function createSpeechWorkerRuntime({ role, scope = globalThis, send } = {
|
|
|
1817
1817
|
: 'Loading model file';
|
|
1818
1818
|
publishProgress(
|
|
1819
1819
|
{
|
|
1820
|
-
phase: initializing ? 'initialize' : '
|
|
1820
|
+
phase: initializing ? 'initialize' : 'load',
|
|
1821
1821
|
stage: 'model',
|
|
1822
1822
|
message,
|
|
1823
1823
|
file,
|
|
@@ -1866,7 +1866,13 @@ callback and the shared sticky AI runtime state. Records include `phase`,
|
|
|
1866
1866
|
`stage`, `message`, the current `file` when available, and `elapsedMs`.
|
|
1867
1867
|
Known artifact inventories report `completed`, `total`, and `unit:'files'`.
|
|
1868
1868
|
Upstream model files are discovered during loading, so their total remains
|
|
1869
|
-
`null` while completed files are counted.
|
|
1869
|
+
`null` while completed files are counted. Generic upstream model callbacks use
|
|
1870
|
+
`phase:'load'`; upstream readiness or completion of the current file set uses
|
|
1871
|
+
`phase:'initialize'`. These callbacks do not establish a network transfer or a
|
|
1872
|
+
cache miss. Resource-fetch progress owns `phase:'download'`, while an existing
|
|
1873
|
+
DBOPFS resource reports `phase:'load'` with `cached:true`. A later generic model
|
|
1874
|
+
callback reports model loading without reclassifying that stored read as a
|
|
1875
|
+
download. Remaining TTS pool initialization
|
|
1870
1876
|
reports completed model sessions. Consumers use an indeterminate progress bar
|
|
1871
1877
|
when no final total is known; transfer quantities do not determine this display.
|
|
1872
1878
|
|
package/package.json
CHANGED