Last week a release needed a commit for every phone check and CI repair: the release commit came first, then fixes, then "Record" commits, and CI went red after phone checks because it only ran on GitHub. make release-ready runs CI's checks before pushing: in the Test job's Ubuntu 24.04 with its apt packages (.github/local-ci/Containerfile), on HEAD's committed content with the locked packages, through an overlay of this checkout so nothing reaches the working tree. It covers Secret Scan, package URLs, the large-file guard, make test, make visual-test and make package-compat-test, and records a stamp for that content. make release then, with the development Moto connected, refuses uncommitted app files and package overrides that are not clean on the lock, syncs ./update_version.sh output, requires the release-ready stamp for this content, builds the debug APK for the phone's ABI, runs the phone check and makes the one "Release Inner Breeze X.Y.Z" commit with the receipt. After a late fix, running it again moves the unpushed release commit above the fix (commits are replayed with merge-tree; only refs move) instead of adding another. It never pushes or tags.
5.8 KiB
5.8 KiB
Inbe repository rules
Ownership and releases
- Dependencies are Ziran packages pinned in
ziran.toml/ziran.lockand linked underbuild/packages/; there is novendor/. Never edit a package checkout. Change Kryon (or any dependency) in its own repository onmaster, commit and push there, then runziran update NAMEhere and commitziran.lock. Runmake package-checkafter dependency changes. For local debugging, map a package to a working repository in the ignoredziran.local.toml; release builds usePACKAGE_FLAGS=--locked. - Add the numeric release to
CHANGELOG.md, then run./update_version.sh. The canonical macros areAPP_VERSION_STRING,APP_VERSION_MAJOR,APP_VERSION_MINOR, andAPP_VERSION_PATCH; do not create aliases. Only the GitHub Actions release workflow creates or pushes release tags. - A new version publishes only with a passing phone check of its exact app
content (
app_treeoverAPP_PATHSinscripts/phone-check.py). Release withmake release-ready(CI's checks in its Ubuntu container), thenmake releasewith the development Moto connected: it checks the APK and makes the one "Release Inner Breeze X.Y.Z" commit. After a late fix, run both again; the unpushed release commit moves above the fix, so there are no "Record" commits. Tests, docs and tooling may change after the check, app paths may not. See docs/cells.md. - Packages declare the oldest host interface they run on (
host_apiper app inapps/versions.json); the host runsoldest_host_apitohost_api. Raisehost_apiwhen the host interface changes andoldest_host_apionly when it can no longer run older packages.make package-compat-testruns the node's packages in this build and new packages in the last release. - Goal (owner, 2026-10-11): every app updates through its own package
without a new APK. Work toward it in small steps alongside requested work;
discuss larger moves with the owner first. Put app screens, rules and text
in
apps/<app>/, not in the host undersrc/. Habits and Practices still draw compiled host screens (see docs/cells.md); when work touches one, prefer moving it into its package. Keep the host interface small and generic (storage, network, locale, platform effects), because each new host call needs an APK before a package can use it. Apps share data only through the host interface, never another app's internals. - Translate changed strings in every affected locale; no English placeholders.
make locale-translated-testfails on any locale string that still equals its English text. Translate it; add it totests/locale_same_as_english.txtonly when it is a real brand name, loanword, or format string.
Machine-checked contracts
make build-lawsis mandatory for native, web, and Windows artifacts; Gradle and CMake enforce the same version and proof checks independently. Never bypass a failed gate.- Laws are Ziran
#lawobligations checked byziran check. Retry behavior lives insrc/app/sync_retry.ziwith its laws insync_retry_laws.zi; private-data names live insrc/storage/storage_layout.ziwith laws instorage_layout_laws.zi. Change the implementation freely, but do not weaken laws to make an implementation pass. Contract changes require explicit product intent and separate review from implementation changes. - Run
make proof-test sync-recovery-test version-testfor these contracts. Coverage, trust boundaries, and the next proof migrations are described in docs/build-laws-plan.md.
Public UI and sync boundaries
- Use current Kryon calls
Text(session, TextProps),Image(session, ImageProps), andButton(session, ButtonProps)directly. Semantic images use the sameImagesurface. No positional Text, legacy drawing calls, alternate widgets, or thin local forwarding wrappers. Keep meaningful compositions and gestures; use standard Checkbox and Toggle. Runmake clean-text-api-check button-api-checkfor UI changes. - If a required widget capability is missing, implement the reusable primitive upstream first. Do not work around it in Inbe or generated code.
- Use sync protocol v6 and the clean Kryon API; no new
Ksyncnames or wrappers. Remove old wire projections and format fallbacks as the storage and sync modules are converted to current Ziran. Keep the current protocol and data model in Inbe rather than adding compatibility adapters. - Keep on-disk schema and user-data upgrade paths. Convert their implementation to checked Ziran; do not delete a migration merely because it handles an old database. An upgrade must preserve existing data, and its replacement needs a test using an older database fixture before the prior path is removed.
- A
.zifilename is not a completed migration. All owned application behavior, including storage upgrades, must compile as current Ziran. Prefer direct Ziran foreign imports for native libraries; migrate owned C adapters as Ziran gains the required ABI support. Never keep application policy in C.
Product behavior and readability
- Desktop focus loss must not pause practices, freeze animation, suppress updates, or enter the mobile background-timer path. Preserve mobile/web lifecycle handling and explicit user pause as separate behavior.
- Preserve hover, press, and focus transitions. Session audio controls have 44-unit targets (24-unit icons plus 10-unit padding), scaled and spaced.
- Lists starts with list tabs, without a separate title bar or dropdown.
- Use descriptive names, explicit control flow, and focused helpers. Never
compress multiple statements, branches, declarations, or checks onto one line.
Format changed source, inspect the final diff, and run
git diff --check.