@@ -11,8 +11,9 @@ incomplete automated evidence remains pending. The qualified v0.6.0 release
 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 are engineering candidates, with release qualification and channel
-delivery tracked separately. The recorded existing-channel baseline is Android
+installations support scoped engineering acceptance for bounded recovery and
+the declared app-only matrix. Device closeout is complete; final integration and actual channel
+delivery remain separate. 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.
 
 
@@ -104,11 +104,12 @@ This bounded feature covers text up to 1 MiB, including Python explicitly copied
 from Blocks. Blocks workspace graphs, projects/history and exported backups
 remain outside this increment. Uninstalling or clearing app data removes local
 copies. See the [candidate execution record](docs/developments/2026-q4-reliable-workflow/c1-s2/00_Execution_Record.md)
-for passing automated checks and candidate-specific device evidence. Local
-Android and iPad Preview installations are engineering candidates; their
-installation does not establish store availability or release qualification.
+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 signed-artifact preparation, qualification and the channel handoff.
+tracks the engineering-qualified artifacts, completed device closeout and channel handoff;
+`0.3.0 (9)` is not yet established as a store-delivered update.
 
 ### Firmware
 
 
@@ -37,14 +37,14 @@ v0.7.0 remains non-normative and requires separate maintainer approval.
   and launches are verified on connected tablets; fresh enrollment/reinstallation
   was not exercised. The pilot kit, recovery design and validation inventory
   are prepared; this does not complete the Sprint or board qualification.
-- Validate and qualify the implemented [bounded current-text recovery candidate](developments/2026-q4-reliable-workflow/c1-s2/00_Execution_Record.md)
-  against the [contract](specifications/App/current-draft-recovery.md). Merged
-  candidate `0.3.0+9` supplies atomic local checkpoints and offline recovery;
-  full A-24 and Blocks graph persistence remain separate scope. The original
-  45–72 hour estimate remains a forecast, not measured effort.
+- Deliver the engineering-accepted [bounded current-text recovery candidate](developments/2026-q4-reliable-workflow/c1-s2/00_Execution_Record.md).
+  Candidate `0.3.0+9` passes its [contract](specifications/App/current-draft-recovery.md)
+  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.
-- Complete [release qualification and channel delivery](developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md) for merged app `0.3.0+9`,
+- Complete [final integration and channel delivery](developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md) for qualified app `0.3.0+9`,
   retaining the recorded 0.2.0 channel baseline until the new channel is verified. The
   [Android publication review](testing/website/android-open-testing-2026-09-25.md)
   records live open-testing availability. The
 
@@ -69,6 +69,7 @@ and [C1-S1 review and sizing](../developments/2026-q4-reliable-workflow/c1-s1/03
 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)
-separates source implementation from pending integrated/physical acceptance and
-release admission. The remaining A-24 project, settings, console, import and
+records scoped engineering acceptance after integrated/physical checks, with
+exact test conditions and completed device closeout; final integration and
+channel delivery remain separate. The remaining A-24 project, settings, console, import and
 Blocks obligations remain carried.
@@ -6,8 +6,10 @@
 **Status:** Accepted for the bounded implementation; candidate source implemented
 2026-10-31 under the user's next-release request. The contract was specified
 2026-09-25 during C1-S1. PR #40 merged the source and integrated CI passes.
-Required physical acceptance and release admission remain pending; no named
-human sign-off is claimed.
+Scoped recovery acceptance and app-only qualification are recorded for frozen
+runtime `bef67bd` after required automated and physical checks. Device closeout
+is complete; final branch integration and channel delivery remain separate; no
+named human sign-off is claimed.
 
 ## Context
 
 
@@ -9,16 +9,16 @@
 |---|---|
 | Package | PyBLE 2026 Q4 reliable workflow, Cycle 1 (`C1`) |
 | Prepared | 25 September 2026; Asia/Bangkok |
-| Strategy | [Implementation Plan, revision 1.7](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md) |
+| 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 device retry on 25 September: six tasks Done, two Prepared and four Awaiting evidence; both current channel installations verified, pilot work unfinished. Later Sprints require replanning against new sizing; 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. Channel 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 continuation update:** the `0.3.0+9` recovery baseline merged in [PR #40](https://github.com/PyBLE-dev/PyBLE/pull/40). Physical qualification exposed three keyboard defects; their repairs at `bef67bd` pass 984 ordinary tests and all 36 PR #41 checks. iPad recovery, final keyboard regressions and all five iPad app-only board rows pass with declared source/firmware scope. Earlier Android recovery and board rows pass, but a later final-candidate Blocks startup observation remains under investigation. Signed packages and a channel packet are prepared; admission and actual store delivery remain separate. The [C1-S2 record](c1-s2/00_Execution_Record.md) binds the evidence. S1 remains six Done / two Prepared / four Awaiting evidence. Original dates/hours remain the baseline; the [continuation plan](04_Sprint_Plan.md#31-october-continuation-order-and-reforecast) records unresolved capacity inputs.
+**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. Final branch integration and actual M-05 store delivery remain separate. 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
 
@@ -31,11 +31,11 @@ This package derives execution views from the strategy. It does not replace norm
 | [05 — Product backlog and stories](05_Product_Backlog_and_Stories.md) | Ordered work, parent/child identities, acceptance criteria, and source traceability | Refinement or changed user evidence |
 | [06 — Sprint backlogs](06_Sprint_Backlogs.md) | Task allowances, dependencies, C1-S1 execution status and later forecasts requiring replanning | Developers select/adapt work during a Sprint |
 | [C1-S1 — Execution and evidence](c1-s1/00_Execution_Record.md) | Actual channel checks, pilot kit, recovery design/sizing and validation inventory | New evidence, source review or a resolved blocker |
-| [C1-S2 — Implementation and evidence](c1-s2/00_Execution_Record.md) | Bounded recovery candidate, actual test states, remaining physical/release work and scoped operator recipe | Source integration, actual platform runs or admission decision |
+| [C1-S2 — Implementation and evidence](c1-s2/00_Execution_Record.md) | Accepted bounded recovery and app-only qualification, retained evidence/limits, release continuation and scoped operator recipe | Source integration, actual platform runs or admission decision |
 
 ```mermaid
 flowchart LR
-    Strategy["Strategy revision 1.7"] --> Goal["One Product Goal"]
+    Strategy["Strategy revision 1.8"] --> Goal["One Product Goal"]
     Goal --> Roadmap["Outcome roadmap and milestones"]
     Roadmap --> Product["Ordered Product Backlog"]
     Product --> Planning["Sprint Planning"]
@@ -64,7 +64,7 @@ flowchart LR
 | App source is `0.2.0+8`; physical retry verifies Play `0.2.0 (8)` and TestFlight `0.2.0 (6)` | Android payloads map to the historical build-8 bundle; iPad source mapping remains unknown. Neither channel check proves BLE or older-OS compatibility |
 | Firmware v0.6.1 is published on owner confirmation across five exact profiles | Pending automated results stay pending; no automatic PyBLE Ready badge |
 | Issue #24 is closed/superseded | Do not resurrect its old release umbrella as a dependency |
-| S1 baseline draft was volatile; [ADR-0048](../../decisions/0048-bounded-current-text-draft-recovery.md) now has a bounded candidate implementation | Complete applicable recovery acceptance; full project persistence and Blocks graph recovery remain carried |
+| S1 baseline draft was volatile; [ADR-0048](../../decisions/0048-bounded-current-text-draft-recovery.md) now has an accepted bounded recovery increment | M-02 acceptance is recorded on 31 October; full project persistence and Blocks graph recovery remain carried |
 | Lifecycle protections, tutorials, imports, and test tools already exist | Reuse them; refine only observed gaps and the documented persistence gap |
 
 ## Applying Scrum to PyBLE
@@ -140,7 +140,7 @@ When facts or priority change, update the canonical file above and its dependent
 
 | Source | Use and precedence |
 |---|---|
-| [Strategy revision 1.7](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md) | Scope, targets, six-Sprint capacity, three outcomes, Ready program and conditional horizons |
+| [Strategy revision 1.8](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md) | Scope, targets, six-Sprint capacity, three outcomes, Ready program and conditional horizons |
 | [Public roadmap](../../ROADMAP.md), [README](../../../README.md) | Current capability and distribution baseline |
 | [App specification](../../specifications/App/specs.md), [App TDD](../../specifications/App/TDD.md), [ADR-0010](../../decisions/0010-working-loop-in-memory-document.md) | Persistence contract and recorded implementation deviation; consult frozen working-loop scope |
 | [Firmware roadmap](../../planning/firmware-v0.6.1-v0.7.0-roadmap.md), [PBLE/1](../../specifications/protocol.md) | v0.7 proposals versus frozen wire behavior; old v0.6.1 publication/#24 wording is historical |
 
@@ -5,15 +5,15 @@
 
 | Control | Value |
 |---|---|
-| Status | C1-S1 has six tasks Done, two Prepared awaiting pilot setup and four Awaiting evidence; existing channel installations verified. Future direction remains conditional and forecasts need revision after sizing |
+| Status | C1-S1 remains partial; bounded recovery and app-only qualification pass 31 October engineering review. Next release work is final integration and M-05 delivery; pilot/capacity inputs remain outstanding |
 | Planning date | 25 September 2026; dates use Asia/Bangkok |
-| Source | [Implementation strategy revision 1.7](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md), particularly §§1, 6–9, 12, 14, and 19 |
+| 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 continuation update:** the `0.3.0+9` recovery baseline merged in [PR #40](https://github.com/PyBLE-dev/PyBLE/pull/40). Physical qualification exposed three keyboard defects; their repairs at `bef67bd` pass 984 ordinary tests and all 36 PR #41 checks. iPad recovery, final keyboard regressions and all five iPad app-only board rows pass with declared source/firmware scope. Earlier Android recovery and board rows pass, but a later final-candidate Blocks startup observation remains under investigation. Signed packages and a channel packet are prepared; admission and actual store delivery remain separate. The [C1-S2 record](c1-s2/00_Execution_Record.md) binds the evidence. S1 remains six Done / two Prepared / four Awaiting evidence. Original dates/hours remain the baseline; the [continuation plan](04_Sprint_Plan.md#31-october-continuation-order-and-reforecast) records unresolved capacity inputs.
+**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. Final branch integration and actual M-05 store delivery remain separate. 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
 
@@ -49,7 +49,7 @@ team capacity or a completed formal Sprint.
 | Existing workflow | PBLE/1 editing, files, run/stop, console, Blocks, tutorials, and reviewed import already exist | Reuse implementation and tests; improve measured failures rather than rebuild the workflow |
 | Firmware v0.6.1 | Owner-confirmed publication for five exact profiles; incomplete automated evidence remains visible | New qualification and compatibility claims require their own applicable evidence |
 | Historical issue #24 | Closed as superseded; incomplete checklist was not declared passed | Do not recreate closure as a new dependency or treat historical closure as qualification |
-| Durable drafts | Bounded current-text recovery now has candidate source under ADR-0048; required acceptance remains unfinished | Complete integrated/physical evidence for PYB-006.2; retain broader A-24/Blocks scope |
+| Durable drafts | Bounded current-text recovery under ADR-0048 passes scoped engineering acceptance on 31 October | Deliver the qualified candidate through the selected channels; retain broader A-24/Blocks scope |
 | Adoption and Ready | No measured cohort results or awarded PyBLE Ready badge established by the strategy | Treat outcome targets and badge eligibility as proposals requiring evidence |
 
 The [Android publication review](../../testing/website/android-open-testing-2026-09-25.md)
@@ -61,7 +61,8 @@ That proposal still informs conditional Reliable Projects scope and compatibilit
 
 The windows are sequencing forecasts measured from the proposed cycle start.
 Overlapping windows permit options; they do not create simultaneous commitments
-for one maintainer. All rows in this table have status **Proposed**.
+for one maintainer. The horizons remain proposals; the dated acceptance above records completed
+bounded work inside H1 without declaring that whole horizon complete.
 
 | Horizon / indicative window | Outcome and user value | Planning items / milestone | Admission and dependency | Evidence for continuation |
 |---|---|---|---|---|