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]>
Preserve current AVIF compression, local voice pipelines, practice workflows, UI API migration, locale updates, and packaging work. Native integration validation remains pending.
Add friend failed because the node URL was read before a check that reuses
the same settings buffer. Key backups now only go through Entity's password
sealed save, Android device backups no longer copy the account, and the new
Entity password and backup wording is translated. Older key files still open.
The breath and bell cues are Practices assets. Startup loaded them
while Practices was still opening, so the lookup failed once and the
cues stayed silent. Cues now load when first played and retry after
the asset generation changes.
Background sync kept failing with result 6 because a paged download
resumed from a cursor older than since_server_version, which Daochi
rejects with 400. daochi-client now restarts such a page.
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.
Sixty functions that no code, test, host or other repository references, and the six translations only they used (837 lines). The full test suite passes; functions that C code or tests reach by their module-prefixed names stay.
storage_core.zi keeps what every storage module shares: the delegate hooks,
meta values, the sync keys and record-field version, new IDs and change
times. The rest moved unchanged into focused modules:
- storage_settings.zi: settings and cached social snapshots
- storage_json_sql.zi: JSON reads through SQLite
- sync_outbox.zi: queueing local records for the node
- sync_state.zi: the sync account, status, clearing and purging
- sync_migrations.zi: Lumi's collection and the connected-server flag
- sync_record_codec.zi: local rows as record payloads
- sync_collections.zi: collections and record IDs per entity
- sync_record_crypto.zi: record keys, sealing, opening and kept copies
- sync_apply.zi: applying received records
- sync_exchange.zi: the request payload and applying the response
- storage_profile_stats.zi and storage_export_csv.zi
Names, the protocol and the SQL are unchanged. Importing the core still
links every part, as one module did; importers import the parts whose
names they use. StorageSyncStatus moved beside storage_sync_status, so its
generated header no longer depends on an import cycle. The restore SQL test
and its law mutation read sync_outbox.zi, and the sync recovery link test
leaves out the parts it stubs, as it left out the core.
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.
Inner Breeze's platform services now come from their shared homes:
- Kryon: file_download (runtime assets and music), file_export (data
and key file downloads and Android's share sheet), android_picker
(document picker and QR scanner), page_socket (live sync events in
the browser), browser_viewport (canvas sizing), and Android's device,
insets and input method text editing.
- Daochi client: crypto (SHA-256, HMAC, ChaCha20-Poly1305), account
keys (now wiping secrets as Inbe's copy did), and signed package
release parsing; Inbe keeps only its own package policy.
About 5,000 lines of duplicated Zi, C and JavaScript are gone. The lock
pins Kryon f2c230be and the Daochi client d453a26.