yyods · Oct 31, 2026 · Oct 31, 2026 · Oct 31, 2026 · Oct 31, 2026 · Oct 31, 2026
@@ -12,11 +12,14 @@ remains a separate historical baseline built from its annotated tag.
 
 The merged app source now targets `0.3.0+9`. Its local Android and iPad Preview
 installations support scoped engineering acceptance for bounded recovery and
-the declared app-only matrix. Device closeout is 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. The recorded existing-channel baseline is Android
-Play `0.2.0 (8)` and iPad TestFlight `0.2.0 (6)`; the earlier build-5 Transporter
-and build-8 submission handoffs remain historical artifact records.
+the declared app-only matrix. Device closeout is complete. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41)
+merged after all 36 checks on its final head passed. Internal-account TestFlight
+`0.3.0 (9)` offer/Open, production About and bounded device smoke are verified
+([delivery record](docs/developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md#31-october-testflight-delivery-and-published-metadata));
+the exact update transaction was not observed. External build 9 is submitted
+and Waiting for Review; Google Play open-testing build 9 is submitted with
+Changes in review. Review approval and remaining delivery are pending. Lenovo
+still has Play `0.2.0 (8)`; earlier iPad `0.2.0 (6)`, build-5 Transporter and build-8 handoff records remain historical.
 
 ### App source
 
@@ -111,11 +114,11 @@ and build-8 submission handoffs remain historical artifact records.
   failure handling and document/session guards in ADR-0048 and the App
   contracts. The bounded successor is implemented in the 0.3.0 source candidate;
   acceptance and broader persistence obligations follow the C1-S2 record.
-- Verified live Android open-testing wording and prepared correction of the
-  older public TestFlight description. Installed identities are now recorded;
-  Android code/assets match the retained build-8 AAB, while iPad build-6 source
-  mapping and a minimum-OS metadata discrepancy need distribution-owner
-  follow-up. The TestFlight metadata change remains pending.
+- Verified live Android open-testing wording and completed the public
+  TestFlight description correction on 31 October. English (U.S.) app-level
+  copy was saved/reloaded and independently verified in the public response;
+  build-9 What to Test was separately saved and exactly reloaded. Historical
+  iPad build-6 source/minimum-OS questions remain separate from this correction.
 - Prepared Google Play open-testing listing text, reviewer hardware setup,
   tester instructions, data-use assessment, and reproducible store artwork
   with authentic screenshot provenance. Store availability remains a separate

@@ -91,7 +91,7 @@ does not establish its installed build/source identity or mean those earlier
 artifacts contain later connection-lifecycle fixes. Both platforms share the
 same Flutter source and app test gates. The iOS/iPadOS project minimum is 15.
 
-### Next app candidate: local draft recovery
+### Local draft recovery in app 0.3.0
 
 The merged `0.3.0+9` candidate adds one on-device current-text recovery copy.
 After restart, preview and explicitly Restore or Discard the last committed
@@ -108,8 +108,19 @@ for accepted automated and candidate-specific device evidence, including the
 declared five-profile × two-platform app matrix and test conditions. Local
 Android and iPad Preview installations remain separate from store delivery.
 The [release readiness record](docs/developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md)
-tracks the engineering-qualified artifacts, completed device closeout and channel handoff;
-`0.3.0 (9)` is not yet established as a store-delivered update.
+tracks the engineering-qualified artifacts, completed device closeout and channel handoff.
+TestFlight `0.3.0 (9)` is verified for the existing internal account on the
+connected iPad, including production About and a bounded board smoke check
+([delivery record](docs/developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md#31-october-testflight-delivery-and-published-metadata)).
+The exact update transaction was not observed. Build 9 is submitted to the
+existing external group and is **Waiting for Review**; Google Play
+open-testing build 9 is submitted with **Changes in review**
+([submission record](docs/developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md#31-october-google-play-open-testing-submission)).
+Neither review state establishes approval or tester delivery. Lenovo still
+offers and runs Play `0.2.0 (8)`.
+The subsequently requested [Android production promotion](docs/developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md#31-october-android-production-scope-decision)
+is held before submission while the saved child audience and Bluetooth
+implementation are reconciled. The existing open-testing review is unchanged.
 
 ### Firmware
 

@@ -42,11 +42,12 @@ v0.7.0 remains non-normative and requires separate maintainer approval.
   and declared app-only matrix with exact test conditions recorded. Full A-24
   and Blocks graph persistence remain separate scope. The original 45–72 hour
   estimate remains a forecast, not measured effort.
-- Correct the [stale public TestFlight description](developments/2026-q4-reliable-workflow/c1-s1/05_TestFlight_Metadata_Correction.md)
-  through the distribution owner; replacement copy is prepared, not published.
+- Maintain the [corrected public TestFlight description](developments/2026-q4-reliable-workflow/c1-s1/05_TestFlight_Metadata_Correction.md#31-october-published-description-and-closure):
+  English (U.S.) copy was saved/reloaded and independently verified publicly on 31 October.
 - Complete [channel delivery](developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md) for qualified app `0.3.0+9`.
-  [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) tracks final integration; required CI and merge precede publishing.
-  Retain the recorded 0.2.0 channel baseline until the new channel is verified. The
+  [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) merged after all 36 checks on its final head passed.
+  Internal-account TestFlight `0.3.0 (9)` offer/Open, installed identity and bounded smoke are verified ([delivery record](developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md#31-october-testflight-delivery-and-published-metadata)); the update transaction was not observed.
+  External build 9 is submitted and Waiting for Review; Google Play open-testing build 9 is submitted with Changes in review; approval/delivery remain pending. Lenovo still has Play `0.2.0 (8)`; earlier iPad build-6 evidence remains historical. The
   [Android publication review](testing/website/android-open-testing-2026-09-25.md)
   records live open-testing availability. The
   [prepared build-8 handoff](testing/google-play/0.2.0-build-8.md) remains a

@@ -70,6 +70,8 @@ That 25 September inspection was design-only. The 31 October candidate now
 implements the bounded current-text successor; its
 [C1-S2 execution record](../developments/2026-q4-reliable-workflow/c1-s2/00_Execution_Record.md)
 records scoped engineering acceptance after integrated/physical checks, with
-exact test conditions and completed device closeout. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) tracks final
-integration; required CI and merge precede publishing. Channel delivery remains pending. The remaining A-24 project, settings, console, import and
-Blocks obligations remain carried.
+exact test conditions and completed device closeout. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41)
+merged after all 36 final-head checks passed. The [delivery record](../developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md#31-october-testflight-delivery-and-published-metadata)
+verifies internal-account TestFlight `0.3.0 (9)`; external build 9 is submitted
+and Waiting for Review, while Google Play open-testing build 9 is submitted with Changes in review; approval and delivery remain pending. The remaining A-24 project, settings, console, import
+and Blocks obligations remain carried.
@@ -8,8 +8,10 @@
 2026-09-25 during C1-S1. PR #40 merged the source and integrated CI passes.
 Scoped recovery acceptance and app-only qualification are recorded for frozen
 runtime `bef67bd` after required automated and physical checks. Device closeout
-is complete. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) tracks final integration; required CI and merge precede
-publishing. Channel delivery remains pending; no named human sign-off is claimed.
+is complete, and [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) merged after
+all 36 final-head checks passed. The [delivery record](../developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md#31-october-testflight-delivery-and-published-metadata)
+verifies internal-account TestFlight `0.3.0 (9)`; external build 9 is submitted
+and Waiting for Review, while Google Play open-testing build 9 is submitted with Changes in review; approval and delivery remain pending. No named human sign-off is claimed.
 
 ## Context
 

@@ -12,13 +12,13 @@
 | Strategy | [Implementation Plan, revision 1.8](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md) |
 | Repository baseline | `23ed764b0ef88dce9720c66fbd1c0655268860cf` |
 | Proposed cycle | 28 September–20 December 2026; six two-week Sprints |
-| Status | C1-S1: six Done, two Prepared and four Awaiting evidence. The 31 October continuation accepts M-02 and app-only M-04; S2 has ten Done tasks and T11 awaiting participants. Channel delivery and human capacity remain unresolved; no staffed-team ceremony is inferred |
+| Status | C1-S1: six Done, two Prepared and four Awaiting evidence. The 31 October continuation accepts M-02 and app-only M-04; S2 has ten Done tasks and T11 awaiting participants. External TestFlight/Google Play delivery and human capacity remain unresolved; no staffed-team ceremony is inferred |
 | Primary audience | Tablet-owning makers, provisionally; confirm one reachable cohort before observation |
 | Authoritative contracts | [Contributor rules](../../../AGENTS.md), [App specification](../../specifications/App/specs.md), [App TDD](../../specifications/App/TDD.md), [PBLE/1](../../specifications/protocol.md), and applicable firmware/release specifications |
 
 This package derives execution views from the strategy. It does not replace normative specifications, expand hardware claims, create GitHub issues, or authorize store/website publication. The strategy and original package were recorded together in planning baseline `d039db0`. The [C1-S1 execution record](c1-s1/00_Execution_Record.md) owns actual results and blockers.
 
-**31 October acceptance update:** scoped current-text recovery (PYB-006.2 / M-02) and the app-only M-04 candidate pass engineering review at `bef67bd`: 984 ordinary tests, 36 frozen-runtime CI checks, both-platform recovery/keyboard evidence and all ten declared app/profile rows. The [C1-S2 record](c1-s2/00_Execution_Record.md) preserves exact artifacts, firmware baselines, earlier-row impact assessments and the temporary Android qualifier battery-policy condition. Signed packages and the release packet are prepared; original device policy and normal board advertising are restored, and owned fixtures are cleaned. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) tracks final integration; required CI and merge precede publishing. Actual M-05 store delivery remains pending. S1 remains six Done / two Prepared / four Awaiting evidence; S2 has ten engineering tasks Done and participant follow-up unfinished. Original dates/hours remain the baseline; the [continuation plan](04_Sprint_Plan.md#31-october-continuation-order-and-reforecast) records the next work and unresolved human capacity.
+**31 October acceptance update:** scoped current-text recovery (PYB-006.2 / M-02) and the app-only M-04 candidate pass engineering review at `bef67bd`: 984 ordinary tests, 36 frozen-runtime CI checks, both-platform recovery/keyboard evidence and all ten declared app/profile rows. The [C1-S2 record](c1-s2/00_Execution_Record.md) preserves exact artifacts, firmware baselines, earlier-row impact assessments and the temporary Android qualifier battery-policy condition. Signed packages and the release packet are prepared; original device policy and normal board advertising are restored, and owned fixtures are cleaned. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) merged after all 36 checks on its final head passed. Internal-account TestFlight `0.3.0 (9)` offer/Open, production About and bounded device smoke are verified ([delivery record](c1-s2/06_Release_Readiness.md#31-october-testflight-delivery-and-published-metadata)); the update transaction was not observed. PYB-002.1 public-description correction is complete. M-05 remains partial: external build 9 is submitted and Waiting for Review; Google Play open-testing build 9 is submitted with Changes in review; approval and delivery remain pending. S1 remains six Done / two Prepared / four Awaiting evidence; S2 has ten engineering tasks Done and participant follow-up unfinished. Original dates/hours remain the baseline; the [continuation plan](04_Sprint_Plan.md#31-october-continuation-order-and-reforecast) records the next work and unresolved human capacity.
 
 ## Navigation and ownership of information
 

@@ -5,15 +5,15 @@
 
 | Control | Value |
 |---|---|
-| Status | C1-S1 remains partial; bounded recovery and app-only qualification pass 31 October engineering review. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) tracks final integration; required CI and merge precede publishing. M-05 delivery and pilot/capacity inputs remain outstanding |
+| Status | C1-S1 remains partial; bounded recovery and app-only qualification pass 31 October engineering review. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) merged after all 36 checks on its final head passed. External TestFlight/Google Play delivery and pilot/capacity inputs remain outstanding |
 | Planning date | 25 September 2026; dates use Asia/Bangkok |
 | Source | [Implementation strategy revision 1.8](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md), particularly §§1, 6–9, 12, 14, and 19 |
 | Inspected baseline | `main` at `23ed764b0ef88dce9720c66fbd1c0655268860cf` |
 | First cycle | C1: 28 September–20 December 2026; later horizons conditional through September 2028 |
 | Planning authority | Product Owner orders the Product Backlog; Developers forecast feasible work during Sprint Planning; names and capacity remain unassigned |
 | Related documents | [Framework](01_Overview_and_Scrum_Framework.md), [milestones](03_Milestones.md), [Sprint Plan](04_Sprint_Plan.md), [stories](05_Product_Backlog_and_Stories.md), [Sprint Backlogs](06_Sprint_Backlogs.md) |
 
-**31 October acceptance update:** scoped current-text recovery (PYB-006.2 / M-02) and the app-only M-04 candidate pass engineering review at `bef67bd`: 984 ordinary tests, 36 frozen-runtime CI checks, both-platform recovery/keyboard evidence and all ten declared app/profile rows. The [C1-S2 record](c1-s2/00_Execution_Record.md) preserves exact artifacts, firmware baselines, earlier-row impact assessments and the temporary Android qualifier battery-policy condition. Signed packages and the release packet are prepared; original device policy and normal board advertising are restored, and owned fixtures are cleaned. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) tracks final integration; required CI and merge precede publishing. Actual M-05 store delivery remains pending. S1 remains six Done / two Prepared / four Awaiting evidence; S2 has ten engineering tasks Done and participant follow-up unfinished. Original dates/hours remain the baseline; the [continuation plan](04_Sprint_Plan.md#31-october-continuation-order-and-reforecast) records the next work and unresolved human capacity.
+**31 October acceptance update:** scoped current-text recovery (PYB-006.2 / M-02) and the app-only M-04 candidate pass engineering review at `bef67bd`: 984 ordinary tests, 36 frozen-runtime CI checks, both-platform recovery/keyboard evidence and all ten declared app/profile rows. The [C1-S2 record](c1-s2/00_Execution_Record.md) preserves exact artifacts, firmware baselines, earlier-row impact assessments and the temporary Android qualifier battery-policy condition. Signed packages and the release packet are prepared; original device policy and normal board advertising are restored, and owned fixtures are cleaned. [PR #41](https://github.com/PyBLE-dev/PyBLE/pull/41) merged after all 36 checks on its final head passed. Internal-account TestFlight `0.3.0 (9)` offer/Open, production About and bounded device smoke are verified ([delivery record](c1-s2/06_Release_Readiness.md#31-october-testflight-delivery-and-published-metadata)); the update transaction was not observed. PYB-002.1 public-description correction is complete. M-05 remains partial: external build 9 is submitted and Waiting for Review; Google Play open-testing build 9 is submitted with Changes in review; approval and delivery remain pending. S1 remains six Done / two Prepared / four Awaiting evidence; S2 has ten engineering tasks Done and participant follow-up unfinished. Original dates/hours remain the baseline; the [continuation plan](04_Sprint_Plan.md#31-october-continuation-order-and-reforecast) records the next work and unresolved human capacity.
 
 ## Product Goal and decision principle