feat(mobile): v1.14.0 "Foundry" - UniFFI bridge foundations

.github/workflows/ci.yml

@@ -205,20 +205,36 @@ jobs:
 
   # Full-gate cadence only (see `setup` above) — cross-compiling the whole chip stack is cheap but
   # doesn't need to happen on every single PR push.
+  #
+  # `v1.14.0 "Foundry"`: expanded from a single `rustysnes-core --no-default-features` build into
+  # a per-crate matrix. The old single job only proved the no_std posture TRANSITIVELY (every
+  # chip crate is already `default-features = false` in `rustysnes-core`'s own `Cargo.toml`, and
+  # `#![no_std]` is unconditional -- not feature-gated -- in each chip crate's `lib.rs`), never as
+  # its own standalone build target. This matrix builds each chip crate directly, so a future
+  # accidental `std`-only dependency added to just one of them fails on ITS OWN row instead of
+  # only surfacing (if at all) through `rustysnes-core`'s aggregate build.
   no_std:
     needs: setup
     if: needs.setup.outputs.mode == 'full'
     env:
       CARGO_NET_RETRY: "10"
       CARGO_HTTP_MULTIPLEXING: "false"
     runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        crate:
+          - rustysnes-cpu
+          - rustysnes-ppu
+          - rustysnes-apu
+          - rustysnes-cart
+          - rustysnes-core
     steps:
       - uses: actions/checkout@v7
       - uses: ./.github/actions/rust-setup
         with:
           targets: thumbv7em-none-eabihf
-          cache-key-suffix: no_std
-      - run: cargo build -p rustysnes-core --target thumbv7em-none-eabihf --no-default-features
+          cache-key-suffix: no_std-${{ matrix.crate }}
+      - run: cargo build -p ${{ matrix.crate }} --target thumbv7em-none-eabihf --no-default-features
 
   # Full-gate cadence only (`v1.0.0`): a release-mode Criterion build + run is too costly for every
   # PR push, and the frame-time gate is an absolute ceiling that only needs to hold at

CHANGELOG.md

@@ -9,6 +9,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Added
+
+- **New crate `rustysnes-mobile`** (`v1.14.0 "Foundry"`, Mobile Phase 1): a `UniFFI` bridge
+  generating Kotlin (Android) and Swift (iOS) bindings over `rustysnes_core::facade::EmuCore` —
+  the same facade the desktop frontend and `rustysnes-libretro` already drive the emulator
+  through. MVP surface: ROM load/close, `run_frame`, the peripheral setters (Gamepad/Mouse/Super
+  Scope/Multitap), framebuffer + per-frame audio access, save/load state, reset/power-cycle.
+  Verified for
+  real: a genuine `cargo ndk` cross-compile to `arm64-v8a` produced an actual ARM64 `.so`
+  (confirmed via `file`), and `uniffi-bindgen` generated real, correctly-shaped Kotlin and Swift
+  bindings from the compiled library.
+- **`no_std` CI gate expanded to a per-crate matrix**: `rustysnes-{cpu,ppu,apu,cart,core}` each
+  now build standalone against `thumbv7em-none-eabihf --no-default-features`, replacing the prior
+  single aggregate-only `rustysnes-core` build.
+- **The mobile/Android+iOS "no appetite" default from `v1.0.0` is formally reversed** — new
+  `docs/adr/0012-mobile-platform-target.md` records the decision, new `docs/mobile-readiness.md`
+  is the living status page.
+
+### Deferred (honestly scoped, not silently dropped)
+
+- HD-pack consumption, cheats, rewind/run-ahead, netplay, `RetroAchievements`, and Lua/TAS
+  scripting are all out of `rustysnes-mobile`'s MVP surface — real, separate frontend concerns
+  layered on top of `EmuCore` in the desktop build too, not re-invented here.
+- No real Android app, emulator run, or touch UX yet — `v1.15.0 "Sideload"`'s scope.
+- No iOS build/link/run at all — this development environment has no macOS/Xcode toolchain.
+  `v1.16.0 "Beacon"`'s `rustysnes-ios` crate and SwiftUI shell will be written and Rust-side
+  compile-checked, but the real Xcode verification needs the project owner's own Mac.
+
 ## [1.13.0] "Vantage" - 2026-07-12
 
 Ninth release of the RustyNES-parity roadmap: two accessibility theme variants, plus an honest