Preserve current AVIF compression, local voice pipelines, practice workflows, UI API migration, locale updates, and packaging work. Native integration validation remains pending.
Ziran 0.3.1 writes portable bundles as .zx with a ZX header and rejects
.zib. Pin Ziran 620c407, Kryon 935d5fc1, Apps 12e52c0 and Entity 86e72720,
and build, embed, download, verify and store every bundle as .zx: the root
and cell bundles, node apps (the node is asked for format=zx releases),
practice packs and the shared Apps controller, now the only trusted one.
Practice packs stored by older versions count as installed and update
themselves to ZX; a node app's unusable .zib payload is removed so its ZX
release installs. Bundle staging starts empty, so no stale bundle is
embedded, and Android reads asset names by their length.
The generated app codec matches the pinned generator again.
Inbe's publisher now imports the Daochi release v2 format, release checks,
histories and the node-app stage, upload, verify and import steps from
Apps' scripts/node_release.py (Apps 6b555be), so Arcade publishes with the
same code without waiting for an Inbe release. Inbe keeps its own root,
cell and practice-pack publishing and the node receiver, and every flag,
including --node-app and --node-apps, works as before. The receiver
installer ships node_release.py beside the receiver; nothing is deployed.
The node-app history tests moved to Apps with their code. Updating Apps
through ziran also moves the toolchain to Ziran a3fac19. The locked Apps
controller still builds to the reviewed digest.
The App packages workflow now builds every app the node offers and
publishes each one whose ledger names a newer release (Photos stays on
the beta channel through its ledger flag). Apps the node does not list
yet are reported and skipped, because registration takes the node
operator's key.
The node's importer writes history-v2.json with each app's newest three
trusted releases on every publication, and --write-history backfills
them. Workflow actions are pinned to release commits.
The node rightly refuses changed bytes under the version it serves, so
every source change without a version bump turned App packages red. The
publisher now compares with the served releases first: changes without
a new version wait for the next one with a notice, unchanged packages
upload nothing, and only a new version mixed with an unversioned change
still fails.