@@ -11,7 +11,7 @@
 | Candidate | App `0.3.0+9`; recovery baseline merged at `6f5b3ea`, landscape repair `e54a78a`, native dismissal `01a7ac8`, and guide correction `bef67bd` under PR #41; platform and release reports bind each actual artifact |
 | Scope | PYB-006.2 bounded current-text recovery; supporting PYB-009.1 recipe and applicable PYB-008.1 observations |
 | Contract | [Current-draft recovery](../../../specifications/App/current-draft-recovery.md), [ADR-0048](../../../decisions/0048-bounded-current-text-draft-recovery.md) |
-| Overall state | Scoped PYB-006.2 / M-02 and app-only M-04 pass engineering review at frozen runtime `bef67bd`: 984 ordinary tests, 36 runtime-head CI checks, both-platform recovery/keyboard evidence and all ten declared app/profile rows. Device policy, owned fixtures and normal board advertising are restored; [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) tracks final integration; required CI and merge precede publishing. M-05 channel delivery and S2 participant follow-up remain unfinished |
+| Overall state | Scoped PYB-006.2 / M-02 and app-only M-04 pass engineering review at frozen runtime `bef67bd`: 984 ordinary tests, 36 runtime-head CI checks, both-platform recovery/keyboard evidence and all ten declared app/profile rows. Device policy, owned fixtures and normal board advertising are restored; [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) merged at `247e58a` after all 36 final-head checks passed. M-05 channel delivery and S2 participant follow-up remain unfinished |
 | S1 state | Unchanged: six Done, two Prepared, four Awaiting evidence; M-01/SG0 and pilot work remain unfinished |
 | Capacity/calendar | Original S2 allowance 24h and 12–25 October dates remain historical forecasts. The 45–72h estimate / 60h S2–S4 option is not measured effort or confirmed human capacity |
 | Method | Separate storage, coordinator and UI Git worktrees; root integrates board/session guards, regressions, release records and qualification attempts |
@@ -25,7 +25,7 @@ console output strip compact while the keyboard is open and make navigation
 scrollable. The repaired app tree is `d0f2a464e9886c8451a0cb046123973095f246c6`.
 At that revision, the ordinary suite had 974 passing tests, the focused shell
 suite had 25 passing tests and analysis was clean. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41)
-tracks the repair and its current CI/review state. These new results are separate from the
+merged the repair and subsequent acceptance record. These results are separate from the
 972-test PR #40 baseline below. Physical checks and artifact packaging must use
 or explicitly revalidate the repaired candidate; version `0.3.0 (9)` alone is
 not enough to equate the earlier and repaired binaries.
@@ -54,7 +54,7 @@ scope; no M-02/M-04 acceptance follows from packaging alone.
 |---|---|---|
 | iPad normal workflow | [iPad acceptance continuation](04_iPad_Acceptance.md) | Normal Preview passes offline Unicode Restore/current-board consent at `e54a78a`, generated-text handoff/recovery at `01a7ac8`, and Editor/native Blocks palette Hide→Show/dismissal at `bef67bd`; exact text and usable viewports are retained. All five iPad Q rows pass on their recorded candidates; exact firmware baselines and unchanged-behavior impact assessment remain explicit |
 | Android normal workflow | [Android acceptance continuation](05_Android_Acceptance.md) | Recorded P01–P15 scope and all five Q rows pass with explicit earlier-source/accessibility limits. Final `bef67bd` normal profile `945e9746…` passes Editor/native Blocks keyboard checks and generated-text/offline recovery after actual launcher start under temporary qualifier-only Unrestricted battery policy; original watchdogs and the policy condition remain recorded |
-| Production artifacts and channel packet | [Release readiness](06_Release_Readiness.md) | Current `bef67bd` signed Android/iOS artifacts pass packaging and repeated 16 KiB Android startup/storage checks. Earlier artifacts are historical; scoped engineering acceptance is recorded below, with device closeout complete. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) tracks final integration; required CI and merge precede publishing. Actual channel delivery remains pending |
+| Production artifacts and channel packet | [Release readiness](06_Release_Readiness.md) | Current `bef67bd` signed Android/iOS artifacts pass packaging and repeated 16 KiB Android startup/storage checks. Earlier artifacts are historical; scoped engineering acceptance is recorded below, with device closeout complete. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) merged at `247e58a` after all 36 final-head checks passed. Apple accepted the `0.3.0 (9)` upload and started processing; actual channel delivery remains pending |
 | Pilot and capacity | [Pilot kit](../c1-s1/02_Pilot_Protocol_and_Observation_Kit.md) and [continuation order](../04_Sprint_Plan.md#31-october-continuation-order-and-reforecast) | Human owner/cohort/setup/capacity and actual consented sessions remain pending |
 
 The subsequent guide correction is integrated at
@@ -172,7 +172,7 @@ Done; participant follow-up is a separate unfinished task, so the whole Sprint i
 | C1-S2-T07 / PYB-006.2 | Done — applicable automated regression | 984 ordinary tests; 36 frozen-runtime CI checks including pinned goldens/native WebView; later documentation integration tracked separately |
 | C1-S2-T08 / PYB-008.1 | Done — Android observations reviewed | [Android report](05_Android_Acceptance.md): exact sources, final affected checks, OEM qualifier condition and retained failures |
 | C1-S2-T09 / PYB-008.1 | Done — iPad observations reviewed | [iPad report](04_iPad_Acceptance.md): offline/consent/generated text, final palette regression and all five app/profile rows |
-| C1-S2-T10 / PYB-006.2 | Done — scoped review, evidence reconciliation and device closeout | Actual policy restoration, owned-fixture cleanup and restored advertising recorded; final branch CI/review/merge remains an integration step |
+| C1-S2-T10 / PYB-006.2 | Done — scoped review, evidence reconciliation and device closeout | Actual policy restoration, owned-fixture cleanup and restored advertising recorded; PR #41 subsequently merged after all 36 final-head checks passed |
 | C1-S2-T11 / PYB-011.2 | Awaiting participant evidence | No consenting activation dates or mature follow-up records supplied |
 
 ## Required scenario evidence
@@ -210,7 +210,7 @@ source gates; physical observations remain bound to their recorded artifacts.
 | Full app regression and repository gates | At app source `90311f3`: 972 ordinary Flutter tests pass; analysis clean; 204 Dart files formatted; no-leak/SPDX/import/locale/DCO pass; 42 publication tests and Markdown links pass after documentation updates |
 | Android additional harness | Lenovo Android 12 separate-process seed/verify and production-entry offline UI checks pass in an isolated app; [scope/artifacts](02_Platform_Qualification.md) |
 | iPad additional harness | Signed profile build/install/launch succeed. Seed and verify assertion receipts pass across a killed process; closed database hash unchanged. Flutter debug path remains unavailable |
-| Candidate store state | No Google Play/TestFlight submission, approval, new public availability or installed-store verification established by this work |
+| Candidate store state | Apple accepted the `0.3.0 (9)` upload on 31 October at `14:03:25 UTC` and started processing; see the [channel receipt](06_Release_Readiness.md#31-october-app-store-connect-upload-receipt). Processing completion, new TestFlight availability and an installed-channel upgrade remain unverified. No Google Play upload is established |
 | Firmware and Ready | No new firmware publication or complete five-profile qualification; no second-operator reproduction or PyBLE Ready award |
 
 ```mermaid
@@ -256,11 +256,12 @@ human sign-off or a Scrum ceremony.
   ordinary RTS reset, with no firmware/filesystem write; all five boards then
   advertised. That restoration is not counted as an app reconnect pass. The
   platform/release reports retain the private receipts. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41)
-  tracks final integration; required CI and merge precede publishing and remain
+  merged after all 36 final-head checks passed; those integration checks are
   separate from the 36 passing frozen-runtime checks.
-- **Next release stage — M-05:** verify store access and unused build numbers,
-  upload only the admitted artifacts after final integration, then record processing,
-  actual availability and store-delivered upgrade/launch evidence separately.
+- **Next release stage — M-05:** verify Google Play access and the unused build
+  number before uploading its admitted artifact; follow the accepted Apple
+  upload through processing. Record actual channel availability and
+  store-delivered upgrade/launch evidence separately.
   Prepared binaries, local Preview installs and passing engineering tests do not
   establish channel delivery.
 
@@ -293,3 +294,20 @@ Its workspace exactly matched an intentional invalid-media fixture left by an
 earlier qualification run. A fresh backup and the verified valid original
 workspace were preserved; restoring only that region returned `8C9E` to normal
 advertising. No firmware or scan-count logic changed.
+
+### PR #41 final integration receipt
+
+[PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) merged on
+31 October 2026 at `14:01:01 UTC` as
+`247e58adadd52ebe46c6f684a6ee06f36a90a9bf`. All 36 checks on final reviewed head
+`34dd89e40bc69b97a0d1caf198f234eab6cf1e02` passed across the
+[push workflow](https://github.com/PyBLE-dev/PyBLE/actions/runs/41206669043) and
+[PR workflow](https://github.com/PyBLE-dev/PyBLE/actions/runs/41206673197).
+After fetching `main`, both commits resolved to the exact repository tree
+`b32115d210dcd198f0289f0b4486f1bce4a0b108`.
+
+This proves integration of the reviewed source and evidence. The accepted
+production artifacts remain bound to frozen runtime `bef67bd` and app tree
+`60b3a68b693551af5d83076547c502f69838e052`; the later explanatory comment and
+reports do not change their executable behavior. Merge and CI do not establish
+store upload, processing, availability or an installed-channel upgrade.