The codex-daochi-client-mesh-client-rename integration, committed as that
task staged it: mesh_client replaces daochi_client, account storage and
tests move to the Mesh names, and docs, locales and CI follow, with
existing accounts, encrypted records and local storage kept compatible.
The task stopped before its dependency versions were pushed; the next
commit moves Breeze to the pushed pins it needs.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Point every harness's default toolchain at build/packages/ziran/build,
drop the removed `zi2zx bundle` form, link the generated C each harness
actually gets (whole generated folders where the test has no stubs, and
Kryon's package-prefixed frame pacing module), and stop listing the
header-only type module in the modal rules test. Twenty-two more test
targets pass from a clean export; plans/2026-11-17-test-harnesses.md
lists the 54 that still fail and why.
Breeze's style sheets, theme catalogs and custom appearance sheets are
CSS now, read by the css package (6aad71c) on Kryon b9aed758. Custom
sheets saved as KSS convert to CSS at first start; the KSS setting
stays, and a sheet with no CSS form opens as a draft to fix. Host
theme colors still replace only a custom property of the same kind,
and user sheets rank above the app's.
The tree also carries the Apps pin cd72a24 and the Apps controller
digest of the bundle built from it.
The paged sync needs daochi_client/record_codec, which is not committed in
the Daochi client package yet, so Breeze cannot build it from its lock.
The change is kept in backup/pending-sync-paging/ for its own release.
Batches leave room for page selectors within the node's 1 MiB JSON limit,
optional packed variants cannot overflow a batch whose identity form fits,
and a resumable page finishes before sync changes modes.
Diary and Photos keep their photos as records of the account's entity data
(Daochi docs/entity-data.md): entity.photos.<sha256>, synced as
private.entity.v1.photos in Inbe's own signed v6 sync and sealed in Daochi's
record profile with the account's photos key, the same bytes libsodium writes.
A photo's bytes travel as sealed chunks of at most 8 MiB at
/api/v1/blobs/entity/, so the same picture is stored once per node for every
app of the account.
Photos released versions kept move there by themselves: library photos once
their bytes are on the device, and Diary files that an entry includes, named
and dated as before. An old copy goes only after the sync node confirmed the
photo's record and chunks and they came back whole; then the old records name
the photo and keep every field for released versions, which read them through
2027-10-24, the Diary file leaves the device, hex chunks shrink, and the old
copies are deleted from each node. Any failure keeps the old copy for a later
pass, and a delegate device moves nothing.
Apps and Crypto are now ordinary Ziran dependencies, pinned in ziran.lock
and linked by scripts/packages.sh, instead of local checkouts handed to the
build. Every dependency and the toolchain are on their latest revisions.
scripts/package-paths.sh is the one list of NAME=DIR package paths; the
native, web, Windows and Android builds, the source check, the bundle
scripts and the tests all use it, so they resolve packages the same way.
The shared Apps controller bundle is built from the locked Apps package,
and its reviewed digest matches that build.
Node apps, the feature cells and the host import the module ABI and the
node-app types and codec from the Apps package. Inner Breeze no longer
keeps its own copies, its codec generator, or the unused protocol module.
Test hosts include zir_string.h for the string helpers they call.
Photos is a beta app the node offers (inbe.photos, host interface 13): a
gallery of the library's photos newest first under the day each was taken,
a viewer with previous, next and Move to Trash, and Trash, where a photo can
be restored. Add photo opens the desktop file dialog or Android's photo
picker.
The library belongs to the account, so its photos stay when Photos is
removed. The host keeps each photo once by its SHA-256 with an upright JPEG
preview (Kryon ImagePreview), its capture day from Exif, and syncs the
records in their own collection, private.inbe.v1.media, which released
versions skip. Only Photos is granted the media calls (MediaQueryHost,
MediaItemHost, MediaAssetHost, MediaPickHost, MediaStatusHost,
MediaUpdateHost), and hosted apps may draw only this account's library.
Photo bytes travel as the Diary's sealed copies, so the same picture is one
copy per node. The media pass now moves Diary photos and library originals
and previews to every node in the account's list whose photo upload is on,
each on its own media session with the device registered there, and fetches
a copy from the sync node first, then the others. Originals download where
they are opened; previews everywhere. Removing a node forgets its session and
the copies it held. JPEG photos stored sideways now draw upright.
Tests: media library, Exif reader, Photos through the real node-app host,
storage sync of the library and per-node sessions, two clients and two real
Daochi nodes, and a private-display check that adds a camera photo through
the desktop picker.
A Diary photo was synced as 1 KB hex chunks inside hex ciphertext, so a
node stored about 4.5 times the photo and the device kept a second hex
copy. A photo's entry now syncs only its hash and size; after each good
sync the photo is sealed with a key made for it alone and stored on the
node as one encrypted copy (its size plus 16 bytes), and the account's
other devices download and verify it. Photos from before upload the same
way and their chunks shrink to one byte each. A node without photo upload
or a full node only keeps the copy off that node; photos always save.
The desktop moves copies on the sync worker, Android and the web one
request per frame. Signed GET requests now sign their empty body.
Oqs names its module file after its export, so Inbe imports it as
oqs/Oqs through a named module path, as project builds of other apps
do. The lock moves Oqs to that commit and keeps liboqs where it was.
Account key pairs, signatures, secure random bytes, and wiping secrets
now go through ziranlang/oqs, the Ziran binding for liboqs, instead of
Inbe's own OQS_* declarations and size_t shim. Inbe still builds the
same ML-DSA-44 liboqs from its locked source, which Oqs shares.
Every build and test that compiles the account modules finds the
package, and the account, device key, and Daochi tests stub liboqs by
its own names.
KSS moved out of Kryon into kryonlabs/kss. Inbe depends on it, compiles
it from build/packages/kss/src with --module-path kryon=... for its
Kryon imports, and embeds the style packs from build/packages/kss/styles
as styles/NAME.kss. The Android build, the source check, and the tests
use the same paths, and the lock moves Kryon and Ziran to the commits
that carry the move.