Ziran c8c6c96c writes saved IR format 59: each string once, compact
integers and relative source positions. The root package drops from
34.0 MB to 18.5 MB and the debug APK from 46.3 MB to 29.5 MB.
A host reads only its own program format, so host_api, oldest_host_api
and every package's host_api move to 41 (released hosts are 40). The
Apps controller is rebuilt with Apps ffebcc7 (e41f568f…, 592 KB instead
of 1.94 MB); controllers from before format 59 cannot run here, so their
trust entries go and collections publish again with this one.
The root package no longer carries a second copy of the Apps controller,
which the host reads from its own apps.zx asset, and the profile picker
draws Entity's flowers picture instead of an identical 1.85 MB copy.
Between releases every change goes under one Unreleased section of
CHANGELOG.md and of each app's changelog; App packages already waits for
the next version. The version check accepts that leading section, and the
version test fixture copies the release notes script update_version.sh runs.
The Makefile keeps the shared configuration, the native build and the
release gates. The rules of each area moved unchanged to mk/: laws, cells,
plan9, windows, web, android, packaging, site, release and tools, and the
tests to mk/tests-*.mk, with the `test:` lines in their old order in
mk/tests-suite.mk. make's database is the same rule for rule: targets,
prerequisites in order, recipes and variables.
mk/tests-lumi.mk is read where its rules stood, before TARGET is set, so
its UI tests still do not build $(TARGET) first.
The readers follow: check-version scans mk/*.mk, version_test copies them
for its make run, the visual gate hashes mk, the Firefox source zip ships
mk/ (it lacked mk/sync.mk before), and the release workflow and its
Windows vendor cache count the non-test mk files like the Makefile.
Bundles share host code and Kryon, so every release changes them, and the
node refuses a changed package under an old version. That blocked the App
packages workflow whenever a release forgot a package. update_version.sh
now versions every bundled package once per release: a package with newer
notes takes them, the others get a maintenance entry, and the root package
lists the versions it brings. The publish error says what to run.
Packages come from waozi.xyz, not the app store, so automatic updates now
wait for an answer. Apps asks once with two equal buttons and says the store
does not check these updates; Settings > About changes the answer. The new
key replaces cells_auto_update, which was saved as on without asking.
F-Droid rebuilds Inbe and compares it with our signed APK. Release builds
now also sign the universal APK built with -PfDroidBuild (self-update off)
and publish it as inbe-VERSION-fdroid.apk for F-Droid's Binaries field.
The guide and pager laws are outside the pinned 18d60d0's compile-time
evaluator, so every build stopped at the proofs gate. d4489a3 proves all
eight law modules, and the desktop and web sources check with it. The
version test also copies mk/package-freebsd.mk, which the Makefile now
includes.
Sync retry and the private-data layout are ordinary Ziran modules with
#law obligations checked by ziran check. The Bend proofs, Node generators,
pinned Bend dependency and Node build tool are removed, and a mutation test
shows each law rejects a deliberately broken implementation.
The version and sync-retry gate tests linked Ziran packages into
build/packages without creating it and left out the package manifest
and mk/sync.mk, so Make stopped before reaching the gate being tested.
ziran.toml and ziran.lock pin the Ziran toolchain, Kryon, Game2D, the Daochi
client, and the C libraries (as source packages) at the commits the vendor
submodules used. scripts/packages.sh bootstraps the locked toolchain, runs
ziran fetch, and links each checkout under build/packages/; make, Gradle, and
CI run it before building. make package-check replaces no-vendor-edits.
Replace the remaining .kry and C application sources with Ziran modules,
move vendored dependencies to their current pointers, and add Ziran tests for
the ported hosts and policies.
Move product behavior, app types, storage, audio, and tray logic into .kry modules. Use shared Kryon widgets, layout policies, asset-backed images, and app KSS styling with a smaller native boundary.
Include the pending navigation, sync recovery, localization, launcher icon, design asset, and 2.0.0 release metadata updates. Add version consistency checks and improve browser persistence and interaction validation.