@@ -7,9 +7,10 @@
 |---|---|
 | Date | 31 October 2026, Asia/Bangkok |
 | Scope | App-only bounded current-text recovery; existing Play open-testing and TestFlight channels |
-| Source | Merged PR #40 at `6f5b3ea73a70342331fb49d0685938ce2a4cae11`; app tree `b12fe3621f1d100a3b3724d15ee0dea3b359acfe` |
-| State | Production Android and iOS packaging verified for this source; physical acceptance and final release admission remain outstanding. The physical-device follow-up identified a keyboard-layout issue being repaired separately, so these pre-fix artifacts are provisional and must be rebuilt after that change |
-| Local evidence | Ignored `local/recovery-completion/release/`: build/check logs, artifact manifest and retained signed binaries |
+| Runtime source | Recovery baseline plus landscape-keyboard repair at `e54a78acf32e7ea26166a60d66573fdf9e697ad4` |
+| Build checkout | Release worktree `e8aeddd8ddbda85293dcca72ad524823bd5ae66a`; app tree `d0f2a464e9886c8451a0cb046123973095f246c6`, verified identical to the runtime baseline |
+| State | Production Android and iOS rebuilt cleanly with the keyboard-layout repair; packaging and the bounded Android 16 KiB runtime smoke pass. Physical acceptance and final release admission remain outstanding |
+| Local evidence | Ignored `local/recovery-completion/release/candidate-e54a78a/`: build/check logs, source/artifact manifests, runtime evidence and retained signed binaries |
 | Public copy | [Prepared release packet](../../../publication/app-0.3.0-build-9-release-packet.md); no submission or availability claim |
 
 ## Gate selection
@@ -24,9 +25,9 @@ claim a new firmware release, fresh firmware OI-1 qualification or a Ready badge
 | Gate | Required evidence | Current disposition |
 |---|---|---|
 | M-02 recovery acceptance | All DR-T01–14 required evidence, including representative physical generated-text recovery and both platform offline/current-board-consent records | Reconcile against the [execution record](00_Execution_Record.md) and actual device reports; installation/scan alone is insufficient |
-| App regression | Accepted source contract, red/green history, locked dependencies, ordinary tests, pinned goldens, platform builds and repository gates | PR #40 and its post-merge CI passed; 972 ordinary Flutter tests recorded; rerun affected checks for any further code change |
+| App regression | Accepted source contract, red/green history, locked dependencies, ordinary tests, pinned goldens, platform builds and repository gates | PR #40/post-merge CI passed historically; the keyboard repair records 974 ordinary Flutter tests, 25 shell widget tests and clean analysis/source gates. Integrated-candidate CI and final physical acceptance remain separate |
 | Five-profile app compatibility | Q01–Q10 below with exact app/firmware identity, actual observations and retained failures | Final complete candidate-bound matrix not yet established |
-| Production packaging | Android upload signer/AAB/APK/native alignment; iOS distribution export/IPA validation; capability parity | Android and iOS checks below pass for the recorded source; affected checks must follow a repaired candidate |
+| Production packaging | Android upload signer/AAB/APK/native alignment; iOS distribution export/IPA validation; capability parity | Android and iOS checks below pass for the repaired source and exact retained artifacts |
 | Release review | Frozen artifact identity, resolved mandatory failures, supported scope, privacy/dependency review and recorded acceptance | Not yet admitted |
 | M-05 channel delivery | Actual upload/processing/review/availability, followed by store-delivered installed identity and upgrade/launch checks | No upload or new channel delivery established by this preparation |
 
@@ -42,7 +43,7 @@ physical or packaging evidence.
 | Q01 | Q02 | `esp32-4mb` | Common workflow plus affected recovery |
 | Q03 | Q04 | `esp32-s3-n16r8` | Common workflow plus affected recovery; do not infer the profile from the `esp32-s3` chip string alone |
 | Q05 | Q06 | `waveshare-esp32-s3-lcd-147b` | Common workflow plus affected recovery; keep its exact-board/image identity distinct from generic S3 |
-| Q07 | Q08 | `esp32-c3-4mb` | Common workflow plus affected recovery and the real-app C3-G5 behavior |
+| Q07 | Q08 | `esp32-c3-4mb` | Common workflow plus affected recovery and real-UI tight-loop/print-flood Stop; see scope below |
 | Q09 | Q10 | `rpi-pico2-w` | Common workflow plus affected recovery on each physical platform; no new full GP2 qualification inferred |
 
 Each common row includes ordinary service-filtered discovery/HELLO, editing and
@@ -51,12 +52,25 @@ disconnect/reconnect and workspace continuity. Retain the selected candidate's
 affected lifecycle/recovery scenarios. Record the actual result of every row;
 a scan result or one platform cannot stand in for another row.
 
-[C3-G5](../../../specifications/firmware/ports/esp32-c3-4mb.md#c3-g5--real-app-hil-on-both-platforms-frozen)
-requires Stop through the real UI against both a tight loop and print flood.
-Its C3-G2 oracle is exactly one matching `RSP{OK}` before `RUN_STATE(idle)` in
-less than 500 ms from complete STOP submission, a usable connection, and a
-subsequent bounded run. UI responsiveness alone cannot establish that wire
-latency. There is no new arbitrary repetition count added by this app increment.
+The [C3 contract](../../../specifications/firmware/ports/esp32-c3-4mb.md#c3-g5--real-app-hil-on-both-platforms-frozen)
+and inventory require tight-loop and print-flood Stop through the real UI on
+both platforms. The full C3-G5 firmware qualification also requires the C3-G2
+wire oracle: exactly one matching `RSP{OK}` before `RUN_STATE(idle)` in less
+than 500 ms from complete STOP submission, a usable connection and a subsequent
+bounded run. UI observations alone cannot prove that latency or a complete
+C3-G5 pass.
+
+The contract's dated status clarification scopes those frozen qualification
+gates to a fresh automated-qualified C3/candidate claim. Under the inventory's
+app-only scope, this storage/layout increment does not automatically require a
+new firmware qualification or fresh wire-latency capture. Impact review found
+`app/lib/ble/` and `app/lib/pble/` unchanged between `8dde8d6` and the repaired
+runtime baseline; the Run controller's Stop implementation is also unchanged.
+Keep fresh UI workload results, existing firmware provenance and any timing
+claim distinct. No artifact-bound v0.6.1 timing receipt was established by this
+preparation; the historical v0.6.0 qualification and incomplete published
+v0.6.1 automated HIL retain their original limits. No new timing pass or arbitrary
+repetition count is inferred.
 
 ## Prepared Android production artifacts
 
@@ -66,8 +80,8 @@ manager and never written into source or logs.
 
 | Artifact | SHA-256 | Bytes |
 |---|---|---:|
-| `PyBLE-0.3.0-build-9-production-release.aab` | `fcf4692dbf7655f53a50a0687eedb81d9cf63bc601721552f622246d5cca0330` | 64,414,627 |
-| `PyBLE-0.3.0-build-9-production-release.apk` | `8656549a8480ae7ebfe9b6023220fa35c9b967fb07ca0a754a0ec24cd63e3e13` | 66,439,954 |
+| `PyBLE-0.3.0-build-9-production-release.aab` | `6fe609a2ebfb925bbffe2662d64a24b4b9bfdb8b5b39ee3fde6077f3cf8fba73` | 64,413,036 |
+| `PyBLE-0.3.0-build-9-production-release.apk` | `71b99f8312c298693e6a8ed1aaa9fc4dc960ac6371504fdfec81152873f67ef8` | 66,439,954 |
 
 | Check | Actual result |
 |---|---|
@@ -78,22 +92,35 @@ manager and never written into source or logs.
 | Native libraries | All 12 packaged shared objects have every ELF LOAD alignment at least 16 KiB, including `libsqlite3.so` and `libdartjni.so` on all three ABIs |
 | APK alignment | `zipalign -c -P 16 -v 4` passes |
 | Permissions | Expected BLE, legacy location, Internet and AndroidX signature permission; no new authored platform permission |
-| Runtime page-size check | Production APK launched on the official API 36 Google APIs 16 KiB arm64 emulator; kernel `PAGE_SIZE=16384`, About `Version 0.3.0 (9)`, bundled native SQLite mapped from the APK, and fresh schema v1 created successfully |
+| Runtime page-size check | Production APK launched on the official API 36 Google APIs 16 KiB arm64 emulator; kernel `PAGE_SIZE=16384`, About `Version 0.3.0 (9)`, bundled native SQLite mapped from the APK, and existing schema v1 reopened successfully; installed APK bytes match the recorded artifact hash |
 
 The 16 KiB runtime observation also force-stopped and relaunched the same
 installed package without data clearing. The normal disconnected screen
-returned; the retained fresh database and WAL reopened with `integrity_check=ok`
+returned without a fatal exception or native-library load error. The database
+created by the earlier `6f5b3ea` production candidate and its WAL reopened with
+`integrity_check=ok`
 and the expected `projects`, `project_files` and `settings` tables. This is a
 native packaging/startup smoke, not a physical BLE row or the full recovery
 acceptance matrix. The SQLite database's own page size is independent of the
-operating-system memory page size.
+operating-system memory page size. The emulator uses Google APIs 16 KiB arm64
+API 36 image revision 7; its fingerprint and private UI captures are recorded
+with the candidate manifest.
 
 The first local invocation incorrectly used `--no-pub` after fresh `pub get`,
 leaving the integration-test plugin in a generated Android registrant. Its
 failed log is retained. Repeating the canonical CI production commands,
 which allow Flutter to regenerate release plugin metadata, built both artifacts
 successfully without a source change.
 
+A later incremental rebuild after the keyboard repair regenerated AOT inputs
+but reused stale Gradle merged/stripped native libraries. Comparing packaged
+`libapp.so` against current build inputs exposed the mismatch; those artifacts
+were rejected and retained under `rejected-stale-gradle-e54a78a/`. Running
+`flutter clean` and both canonical production commands rebuilt the current
+artifacts above. Their packaged AOT libraries match current stripped outputs
+on all three ABIs. The earlier `6f5b3ea` artifacts remain historical evidence
+under `artifacts-6f5b3ea/`; they are not the repaired release candidate.
+
 The APK uses the upload certificate, whereas Google Play can deliver its own
 app-signing certificate. Do not uninstall an existing user's Play app or clear
 its data merely to install this locally signed APK. Store upgrade acceptance
@@ -103,8 +130,8 @@ must use the actual delivered package.
 
 | Field / check | Actual result |
 |---|---|
-| IPA | `PyBLE-0.3.0-build-9-app-store.ipa`, 23,782,489 bytes |
-| SHA-256 | `73ad7cda10c402a7f25316efc5e30f9c80bbd030e23c2bfc32313fd79c41c2ab` |
+| IPA | `PyBLE-0.3.0-build-9-app-store.ipa`, 23,784,757 bytes |
+| SHA-256 | `14146b8951e4cd3298d27eb20e2036c80bbcd1b05bba42c98bf1abbd53b5eba6` |
 | Identity | `dev.pyble.pyble`, `0.3.0 (9)`, normal `lib/main.dart` |
 | Build / deployment floor | Xcode 27.2 / iOS SDK 27.2; app and compiled deployment floor at least iOS 15.0 |
 | Export | App Store Connect distribution export; automatic signing with build-number management disabled; export destination only, no upload |
 
@@ -13,7 +13,7 @@ contract and rebuilt artifacts, not a renamed file.
 ## Google Play release notes
 
 ```text
-PyBLE can now keep one current Python draft locally and offer Restore or Discard after an app restart. Local recovery status is shown separately from saving to a board. Recovered text requires confirmation of the current destination before board Save, Run or Upload. Blocks workspaces and multi-file projects are not included in local draft recovery. A compatible MicroPython board with the PyBLE agent is still required for board workflows.
+PyBLE can keep one current Python draft locally and offer Restore or Discard after restart. Local recovery status is separate from board saving. Recovered text needs current-destination confirmation before board Save, Run or Upload. Landscape editing stays usable above the keyboard. Blocks workspaces and multi-file projects are not included in draft recovery. Board workflows require a compatible MicroPython board running the PyBLE agent.
 ```
 
 ## TestFlight — What to Test