ZenNotes for Android 1.1.26: the shared 2.55.0 core, and nothing keyboard-only left on the phone

ZenNotes for Android 1.1.26 (versionCode 29): the shared ZenNotes core moves from 2.54.1 to 2.55.0, and nothing keyboard-only is left on the phone.

What changes on the phone

• The New note form shows no keyboard hints on the phone (ZenNotes/zennotes#842). The form that note search opens ended with the desktop's key hints in its footer (↑↓ pick, ↵ create, esc back) on a phone with no hardware keyboard. The core now marks that hint group and this shell hides it (PR #83), so the footer holds Back and Create and nothing else.
• No Vim key names anywhere (the core's Vim-off sweep, ZenNotes/zennotes@cdccd554). Vim mode is never on in this app, but the core still drew a ring around the sidebar drawer after a tap, an m chip on the row under the cursor, j/k and p strips in the connections panel and n a e r d badges in the comments panel. With Vim mode off none of that is drawn any more.
• A new note takes the name you give it, and a refused rename says why (ZenNotes/zennotes#839). Renaming a note to a name that an older, since-moved note once had used to fail without a word, because that note's creation date had been left behind under the old name; renames and moves now discard the leftover, and a rename that still cannot happen says so on screen.
• Move… offers your own folders (ZenNotes/zennotes#844). On a vault whose notes live at the root the prompt lists the vault's own folders with Vault root on top, instead of an inbox/ that is not there.
• In the core without a surface here: workflow runs carry a note's comments and creation date with the notes they move (undo puts them back), the "Notes in folder" step can name the vault root (ZenNotes/zennotes#840), and workflow event triggers (ZenNotes/zennotes#843) run on the desktop and the web client; this shell does not offer the Workflows view and triggers do not fire on phones by design.

Under the hood

Core packages: @zennotes/app-core 2.55.0-core.h0743bd3af2a4204a, @zennotes/bridge-contract and @zennotes/shared-domain 2.55.0-boundaries.hd2f617179eb16ef2, built with a clean tree from ZenNotes/zennotes 00db7036 (the desktop's v2.55.0 release commit; core release core-2.55.0-core.h0743bd3af2a4204a). Adopted with npm run core:adopt, which checks every archive's SHA-256 and SHA-512 against its provenance and that all three record that source commit; the boundary check passed without an override. The shell's own changes are the [data-keyboard-hints] CSS rule (#83) and production dependency patch updates (#81: @capacitor/share 8.0.2, CodeMirror 6.11.1 / 6.7.5 / 6.43.12). No native code changes; android/app/build.gradle only moves the version.

Installing the APK

zennotes-1.1.26-universal.apk is the Google Play-signed universal APK for 1.1.26 (29), Android 7.0 and later, downloaded from Play Console's App bundle explorer and attached exactly as downloaded: 31,780,750 bytes, SHA-256 b40dd7d07ce063494e9dd023274d6410aa98673b5203e45126db62f5585bfceb. aapt dump badging reads md.zennotes versionCode 29, versionName 1.1.26, sdkVersion 24, targetSdkVersion 36; apksigner verify --print-certs signer SHA-256 9f1af3a4b6b11156a6b1f49e1a54bcaecef480f18eab1692a3bd8f416af6ae50, the same certificate as every release since 1.1.22; no CHECK_LICENSE or pairip entries. Sideloaded installs do not self-update; use Obtainium. The same version rolls out on Google Play once approved.

Validation

Release branch release/1.1.26 (7da44a7 adopt core 2.55.0, 8afaf0e bump, a2502e2 merge of main with #82's dev-dependency bumps, whose web build is byte-identical to the bundle's assets), merged as PR #84 (00506699) after CI passed (build and boundary job, and the emulator job's instrumentation tests on an API 35 emulator, run 35922196879). On the release tree: package boundary check without an override, typecheck, 161 unit tests, production build, Capacitor sync and the signed release bundle (~/Desktop/zennotes-1.1.26-vc29.aab, 31,524,455 bytes, SHA-256 8a2745301a0e10012fdb5658e2328abffec43492a152c6cf5937ec71dd3893fb, upload key unchanged). Submitted to Google Play production on September 23, 2026 at 16:37 CDT (21:37 UTC), 100% rollout, all targeted countries. No local emulator pass this cycle; coverage is not physical-device certification.