[ymote]

Android Home's theme loader used the old crate asset path, and Back from hosted Rinx could close the Android Activity or dispatch duplicate navigation. This change loads the shared-shell theme asset and routes Back once through the shell, preserving overlays and IME dismissal. A pinned Makepad overlay suppresses compatibility Back keys when the system callback owns navigation.

Both desktop and phone pin Rinx 8a7b935b from Rinx #27. This includes Android HTTPS initialization, account binding after Matrix login/restore, intact session/history replies, and the article editor's SVG controls, adjacent confirmations and localized hover/long-press labels. Hosted Rinx continues using the workspace broker/config/kernel service. This branch follows OctoSense's rewritten canonical history.

Validation:

• python3 tools/setup.py --update and --check --cargo pass. Both packaging dependency-graph checks pass for standard/mobile-apps features on host/Android: one runtime/kernel, with no Rinx standalone runtime features in the host.
• Both runtime patches reproduce the locked Makepad tree.
• Separate OnePlus 6 / Android 15 APK 2026092713, host source f222256: signature, kernel hash, shared-shell theme asset, exact article SVG bytes and absence of a HOME intent verified.
• Authenticated UI retains the Matrix account. Article consent icons are side by side and long press shows labels. A local draft stays visible while editing, survives reopening, and renders in Preview. Theme selection and table insertion/rendering pass; publish preparation returns to editing without sending anything. The updated editor is left open.
• Earlier device validation on build 2026092712 covered real-kernel session/history, scripted-provider AI reply, native approval prompt/denial, close during delayed response, and a fresh context/reply on reopening. System Back and edge Back kept the host alive with one kernel child. These AI tests were not repeated for the editor UI pin. Earlier IME/background/resume/restart checks and their revisions remain in Rinx ADR 0007.

Test adapters/manifests are excluded from the PR. The temporary provider and its own ADB reverse were removed. Normal Home, Bridge and Rinx remain untouched. Paid-provider inference, native cross-app agent exchange, approval acceptance, and privileged production ROM integration remain unverified. PR remains open for review.

[ymote]

Heads-up: OctoSense main moved to 6e47d84 (#71, one crates/shell). This PR needs a rebase. Conflicts should be limited to Cargo.toml (new crates/shell member, makepad-photos dropped) and Cargo.lock. Shell Rust code now lives in crates/shell/src; phone/resources/android is unchanged.

[ymote]

Rebased onto main f38d52ff (after #80 and #81) as one commit, c329bf05. It replaces the seven commits and the merge of the old main. The PR's files match the previous tip f222256e exactly; the only other difference is #80's dev-profile lines in Cargo.toml. setup.py --check --cargo, cargo metadata --locked and check-shell-graph.sh (both shells) pass. If you have a local checkout, run git fetch && git reset --hard origin/fix/rinx-android-deployment.

[ymote]

Updated on main a55ca40 as two commits:

1. The Android theme-path and Back fixes. The Back patch is rebased on makepad 975c5630.
2. A pin move:
   • Rinx 8a7b935b (unmerged Rinx#27 code) → Rinx main 68afcf79, which includes Rinx mobile: an idle phone presents 1 frame/s; transition hitches split, open-app and glass fixed #27, Link Rinx as a module; module windows on the desktop shell (draft: AppCard Octos upgrade needed) #33, Window surfaces scope their app's overlays and blur (AppCard over raised windows) #34, Lock Octoscript-Makepad main c4c96822 (makepad 1d3d383e); AppCard and Rinx main #35 and App Hub: system apps from OctoSense-System-Apps in the Card runner; AppCard from System-Apps #36;
   • App Hub 46d67e51 → e8601b80 (octosense-app-hub-app + octosense-appstore), which adds glance, model and the agent bundle files.

This PR is the one that moves the Rinx pin; #85 and #86 drop theirs.

Checked locally:

• setup.py --check --cargo passes, and the runtime patches reapply.
• cargo metadata --locked passes.
• check-shell-graph.sh passes for both shells on host and Android, default and mobile-apps, with one octos 60cf96e6.
• cargo test -p octosense-app-policy --no-run from phone/ resolves to one crate (it used to be ambiguous).
• cargo check passes for the phone mobile-apps build and the desktop build.