Embedded in a host such as Harmony's Sessions window, Werkzeug reads the
host's palette at most every quarter second through Kryon's
ParentThemeLinux and builds its whole palette from it: surfaces, text
levels, borders, accent and controls, so every colour matches the host and
follows a theme change. Started on its own, it keeps the profile's
appearance. The expansion mirrors Kryon's SystemPaletteColors until Apps,
Entity, Workbook, Css and Auth move to that Kryon together.
Auth (pinned in the first commit of this series) copies the current code as
plain digits when any part of a card is tapped; Edit stays separately
clickable and never touches the clipboard. auth-gui-test taps six points
of a card, then checks Edit, Cancel and the code shown afterwards.
The five colorful tool icons are lossless WebPs with transparent
backgrounds.
Local tests (on the final tree of this series, published pins, no local
overrides, through build-queue): make test including ziran fmt --check,
gui-smoke, gui-test, gallery-gui-test and web-smoke on private displays.
Not run on these pins: the private-emulator Android gate. On an earlier
pin the x86_64 APK built and validated and android-input-test passed
until Entity's add-node page, which needs Kryon's density damage fix
(78af4090); it runs with the next Kryon pin update.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Gallery is a separate portable tool: it browses local folders and albums,
opens a photo, moves between pictures and zooms. Werkzeug keeps the
folder grant in its private data and serves only Gallery; navigation
never leaves the granted root, and image bytes and pixels are bounded.
On Android it reads through the Storage Access Framework, read-only.
Nothing is synced.
Gallery has its own Linux launcher and icon, is bundled in the APK and on
the web build, and is covered by gallery-test (native fixtures),
gallery-gui-test (private Xvfb) and gallery-android-test (private
emulator).
Local tests (on the final tree of this series, published pins, no local
overrides, through build-queue): make test including ziran fmt --check,
gui-smoke, gui-test, gallery-gui-test and web-smoke on private displays.
Not run on these pins: the private-emulator Android gate. On an earlier
pin the x86_64 APK built and validated and android-input-test passed
until Entity's add-node page, which needs Kryon's density damage fix
(78af4090); it runs with the next Kryon pin update.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Werkzeug started the background picture reader only while Profile was
open or a local picture was waiting to be sent. Sync-enabled accounts
now start it automatically. A received picture replaces the local one
only when no local choice is still waiting for the node, and the shared
native profile is updated with it, so Entity does not load an older
picture over it.
entity-account-test drives the normal background pump against a private
HTTP fixture (challenge, signed login, picture) with Profile closed.
gui-test extracts and decodes all 17 bundled Entity picture resources.
docs/development.md describes both diagnostics and what they do not
establish.
Local tests (on the final tree of this series, published pins, no local
overrides, through build-queue): make test including ziran fmt --check,
gui-smoke, gui-test, gallery-gui-test and web-smoke on private displays.
Not run on these pins: the private-emulator Android gate. On an earlier
pin the x86_64 APK built and validated and android-input-test passed
until Entity's add-node page, which needs Kryon's density damage fix
(78af4090); it runs with the next Kryon pin update.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
scripts/private-emulator.py owns a disposable headless API 31 emulator.
android_startup.py launches Werkzeug and waits for visible Home; it waits
out only the System UI "isn't responding" dialog, so an app ANR still
fails. Its regression tests run in make test. The input, profile and
Workbook document-picker tests use it, find controls by text or content
description, and allow a cold system picker more time.
Local tests (on the final tree of this series, published pins, no local
overrides, through build-queue): make test including ziran fmt --check,
gui-smoke, gui-test, gallery-gui-test and web-smoke on private displays.
Not run on these pins: the private-emulator Android gate. On an earlier
pin the x86_64 APK built and validated and android-input-test passed
until Entity's add-node page, which needs Kryon's density damage fix
(78af4090); it runs with the next Kryon pin update.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Kryon's android_run owns NativeActivity lifecycle, touch, IME, density
and software presentation; Werkzeug draws each frame through
ProjectFrame and wraps android_main to save its apps on exit. Werkzeug's
own android_jni.zi is replaced by kryon/android_jni.
The NDK build links kryon_android_codecs (WebP and AVIF) instead of
raylib and compiles Kryon's APK fopen reader. APK files are read through
that reader, and an Android image cache keeps decoded pixels within a
fixed budget for the Pixmap renderer. Java text is converted through
explicit UTF-8, so NUL and supplementary characters survive. While an
EditText is editing, hardware keys go to it instead of the native queue.
RAYLIB_DIR is gone from the Makefile, the Gradle environment and the
release workflow.
Local tests (on the final tree of this series, published pins, no local
overrides, through build-queue): make test including ziran fmt --check,
gui-smoke, gui-test, gallery-gui-test and web-smoke on private displays.
Not run on these pins: the private-emulator Android gate. On an earlier
pin the x86_64 APK built and validated and android-input-test passed
until Entity's add-node page, which needs Kryon's density damage fix
(78af4090); it runs with the next Kryon pin update.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Pin Kryon 3f724419 (after 0.4.0) with the Ziran it pins, e0367fa9
(after v0.6.0, with the Wasm record-copy fix the browser build needs),
and Apps 0d726f2a, Entity 9414cb89, Auth e5a72371 and Workbook 020c9322.
Every package now pins that same Kryon and Ziran, so the lock holds one
Kryon copy.
Kryon 0.4 removed the Widgets and Desktop modules. Werkzeug's screens,
tools and tests import Kryon's public widget modules (kryon/box,
kryon/text, kryon/button, kryon/text_field, ...) and call their qualified
Draw and Props names. The desktop and browser loops take keys with
DesktopInputTake and CanvasInputTake; screenshots come from kryon/Cairo.
Bundles build in project mode with package-qualified entries instead of
hand-written module paths, and Apps' build-ui.py builds the shared
controller. Its reviewed digest is now 3292387c. scripts/ziran.sh runs
the compiler in the caller's directory, so app-logic-test builds Auth's
tests in Auth's own project, and package lookups no longer inherit make's
flags. Private-display fixtures get their own HOME and XDG folders, and
the OCR checks read antialiased labels before thresholding.
Local tests (on the final tree of this series, published pins, no local
overrides, through build-queue): make test including ziran fmt --check,
gui-smoke, gui-test, gallery-gui-test and web-smoke on private displays.
Not run on these pins: the private-emulator Android gate. On an earlier
pin the x86_64 APK built and validated and android-input-test passed
until Entity's add-node page, which needs Kryon's density damage fix
(78af4090); it runs with the next Kryon pin update.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Werkzeug unpacked only Entity's Kryon pictures, so the Abstract tab of
Entity's picture picker had nothing to draw, and the profile bridge dropped
the picture kind, so an abstract choice reverted. Werkzeug now unpacks all
of Entity's pictures, keeps the kind, publishes it in Entity's numbers and
shows an abstract picture on the home screen.
Entity is pinned at its node picture reader; the lock follows Kryon master,
which changes the Apps controller bundle, so its digest is re-pinned from
the locked build.
Werkzeug kept its profile picture on this device only, so friends saw a
default picture. A picture chosen in Profile now goes to the account's
node through Entity's shared publisher, retrying while offline, and is
sent once per choice. Profiles saved earlier with a picture other than
the first count it as chosen.
The site serves Werkzeug at its root instead of a separate landing page;
/app/ forwards there and download links keep their addresses. Browser
storage is per origin, so saved vaults stay.