@@ -9,10 +9,10 @@
 |---|---|
 | Package | PyBLE 2026 Q4 reliable workflow, Cycle 1 (`C1`) |
 | Prepared | 25 September 2026; Asia/Bangkok |
-| Strategy | [Implementation Plan, revision 1.3](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md) |
+| Strategy | [Implementation Plan, revision 1.4](../../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 execution initiated on 25 September; repository deliverables prepared and physical/pilot work blocked. Later Sprints require replanning against new sizing; no staffed-team ceremony is inferred |
+| 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 |
 | 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 |
 
@@ -32,7 +32,7 @@ This package derives execution views from the strategy. It does not replace norm
 
 ```mermaid
 flowchart LR
-    Strategy["Strategy revision 1.3"] --> Goal["One Product Goal"]
+    Strategy["Strategy revision 1.4"] --> Goal["One Product Goal"]
     Goal --> Roadmap["Outcome roadmap and milestones"]
     Roadmap --> Product["Ordered Product Backlog"]
     Product --> Planning["Sprint Planning"]
@@ -58,7 +58,7 @@ flowchart LR
 | Baseline fact | Consequence |
 |---|---|
 | Android open-testing copy correction is complete in PR #33 | Do not replan that correction; identify any new discrepancy separately |
-| App source is `0.2.0+8`; Play publicly identifies `0.2.0`; iPad remains external TestFlight beta | Source version does not prove the installed store binary or its source commit |
+| 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 |
 | Editor draft is volatile under [ADR-0010](../../decisions/0010-working-loop-in-memory-document.md) | Close an accepted subset of A-24; do not claim full project persistence or Blocks recovery |
@@ -107,7 +107,7 @@ Readiness is a local refinement aid. It does not replace Sprint Planning or add
 | Claims have evidence | Exact artifacts, pass/fail/not-run states, limitations and pending release work recorded truthfully |
 | Documentation/discovery scope is complete | Usable reviewed record/guide or agreed findings, source/link checks, and explicit unmet targets; no invented physical results |
 
-This is the proposed package-wide minimum; accepted normative requirements remain binding. Apply it to the selected item rather than treating a source merge as a finished feature. A documentation or discovery item can be Done with a negative finding, while a required physical-installation task cannot be Done if no installation happened. A usable Sprint 1 documentation increment should help an operator or user perform the current workflow; an internal plan alone is not evidence of improved app behavior.
+This is the proposed package-wide minimum; accepted normative requirements remain binding. Apply it to the selected item rather than treating a source merge as a finished feature. A documentation or discovery item can be Done with a negative finding, while a required channel-installation verification task needs observed installation identity, origin and launch; verifying an existing installation does not imply a fresh install. A usable Sprint 1 documentation increment should help an operator or user perform the current workflow; an internal plan alone is not evidence of improved app behavior.
 
 | State distinction | Meaning |
 |---|---|
@@ -128,7 +128,7 @@ Unfinished items return to the Product Backlog for reordering and replanning. Do
 | `C1-S1` … `C1-S6` | This cycle's Sprints; distinct from historical App TDD Sprint labels |
 | `C1-S1-T01`, etc. | Task identities with recorded early C1-S1 outcomes; later task rows remain forecasts, not new public contracts |
 | `M-01`, etc.; `SG0` … `SG6` | Delivery milestones versus strategy gates; neither replaces CI G0/G1 or C3 firmware gates |
-| Item/task status | Proposed → Selected at Planning → In progress → Review → Done; Blocked records a reason/owner; later forecasts remain Proposed |
+| Item/task status | Proposed → Selected at Planning → In progress → Review → Done. Prepared means a reviewed partial deliverable; Awaiting evidence identifies an unperformed observation/session. Both remain unfinished. Blocked names a concrete impediment/owner; later forecasts remain Proposed |
 | Private versus public records | Contact/consent, device identifiers and raw logs remain private/ignored; publish only reviewed aggregate findings and redacted evidence |
 
 When facts or priority change, update the canonical file above and its dependent tables together. Preserve old evidence and dated decisions. New opcode/capability values, hardware support, Ready awards, and publication need their normal specification and authorization paths; none is inferred from this package.
@@ -137,9 +137,9 @@ When facts or priority change, update the canonical file above and its dependent
 
 | Source | Use and precedence |
 |---|---|
-| [Strategy revision 1.3](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md) | Scope, targets, six-Sprint capacity, three outcomes, Ready program and conditional horizons |
+| [Strategy revision 1.4](../../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 |
-| [Android publication review](../../testing/website/android-open-testing-2026-09-25.md), [v0.6.1 publication record](../../testing/firmware-v0.6.1-publication-2026-09-11.md) | Dated evidence; neither establishes a newly installed binary or missing automated qualification |
+| [Android publication review](../../testing/website/android-open-testing-2026-09-25.md), [v0.6.1 publication record](../../testing/firmware-v0.6.1-publication-2026-09-11.md) | Dated publication evidence, separate from the new [Android](c1-s1/06_Android_Channel_Verification.md) and [iPad](c1-s1/07_iPad_Channel_Verification.md) existing-installation checks; missing automated qualification remains unfinished |
 | [HIL guide](../../../tests/firmware_tests/hil/README.md), [CI workflow](../../../.github/workflows/ci.yml), [CONTRIBUTING](../../../CONTRIBUTING.md) | Reuse existing tools and gates; actual CI requirements govern merges |
@@ -5,13 +5,13 @@
 
 | Field | Rule |
 |---|---|
-| Status | C1-S1 execution initiated 25 September: four repository tasks Done, eight device/pilot tasks Blocked. C1-S2–C1-S6 retain original Proposed allowances and require replanning before selection |
+| Status | C1-S1 device retry 25 September: six tasks Done, two Prepared and four Awaiting evidence. Both current channel installations verified; participant-dependent work remains unfinished. C1-S2–C1-S6 retain original Proposed allowances and require replanning before selection |
 | Product/Sprint Goals | [Framework](01_Overview_and_Scrum_Framework.md) and [Sprint plan](04_Sprint_Plan.md) |
 | Acceptance authority | [Product backlog and stories](05_Product_Backlog_and_Stories.md); task completion never overrides a parent story's acceptance criteria |
 | Selection | Developers confirm scope, ownership, estimates and task plan at each Sprint Planning |
 | Hours | Initial task allowances totaling the source plan's 136 hours; not story points or validated effort estimates |
 | Dependencies | Same-Sprint `Txx` references refer to that Sprint's task. Cross-Sprint dependencies name their full item/task ID |
-| Evidence | Record artifact identity and actual results; unavailable access/recruitment leaves the affected task Blocked, not Done |
+| Evidence | Record artifact identity and actual results; use Prepared for reviewed partial work, Awaiting evidence for unperformed sessions/observations, and Blocked for a concrete impediment with an owner; unfinished work is never Done |
 | Privacy | Keep private consent/contact/device records outside Git; link only reviewed public aggregates and redacted evidence |
 
 Actual task evidence and blocker owners are maintained in the [C1-S1 execution record](c1-s1/00_Execution_Record.md). The original future task tables below are retained as the baseline; the new 45–72h recovery estimate and matrix cost model invalidate their assumed fit. Use the [reforecast requirements](04_Sprint_Plan.md#c1-s1-findings-and-required-reforecast) before selection. Prepared TestFlight correction copy records residual PYB-002.1; its external application is not an extra committed task.
@@ -33,19 +33,21 @@ Record optional follow-up consent and the prospective day-7–14 window at each
 | Task ID | Parent child item | Proposed task and expected output | Dependency | Contribution role | h | Status |
 |---|---|---|---|---|---:|---|
 | C1-S1-T01 | PYB-001.1 | Assemble the dated channel/install/provenance/qualification ledger from existing records; assign unresolved fields | Current source/publication records | Release | 1 | Done |
-| C1-S1-T02 | PYB-001.2 | Verify eligible Android enrollment/install and record build/version, restrictions and available source mapping | T01; Play/device access | Release + QA | 2 | Blocked |
-| C1-S1-T03 | PYB-001.2 | Verify current TestFlight installation and record its actual build and provenance limitations | T01; TestFlight/device access | Release + QA | 2 | Blocked |
-| C1-S1-T04 | PYB-003.1 | Review harmless hardware/pilot boundaries, consent/retention rules, and manual support template | Recorded pilot setup; named pilot owner | Pilot + QA | 2 | Blocked |
-| C1-S1-T05 | PYB-004.1 | Confirm primary cohort and Tasks A/B/C, assistance/timeout rules, previous workflow and prospective follow-up | T04; recorded app/setup | Pilot | 2 | Blocked |
-| C1-S1-T06 | PYB-004.2 / PYB-011.2 | Observe the first baseline batch; record every eligible start, assistance, consent/window and any due follow-up | T05; consenting participants | Pilot | 2 | Blocked |
-| C1-S1-T07 | PYB-004.2 / PYB-011.2 | Observe the next baseline batch under the same task/build rules; record windows and collect due follow-up | T05; consenting participants | Pilot | 2 | Blocked |
-| C1-S1-T08 | PYB-004.2 / PYB-011.2 | Complete planned observation/follow-up slots toward five baseline starts; retain failures, missing responses and recruitment gaps | T05; participant access | Pilot | 2 | Blocked |
-| C1-S1-T09 | PYB-004.2 | Summarize baseline outcomes and actual observation cost; identify an observed obstacle without inventing one | T06–T08 actual records | Pilot + Product Owner | 1 | Blocked |
+| C1-S1-T02 | PYB-001.2 | Verify eligible Android enrollment/current installation and record build/version, restrictions and available source mapping | T01; Play/device access | Release + QA | 2 | Done |
+| C1-S1-T03 | PYB-001.2 | Verify current TestFlight installation and record its actual build and provenance limitations | T01; TestFlight/device access | Release + QA | 2 | Done |
+| C1-S1-T04 | PYB-003.1 | Review harmless hardware/pilot boundaries, consent/retention rules, and manual support template | Recorded pilot setup; named pilot owner | Pilot + QA | 2 | Prepared — awaiting pilot setup |
+| C1-S1-T05 | PYB-004.1 | Confirm primary cohort and Tasks A/B/C, assistance/timeout rules, previous workflow and prospective follow-up | T04; recorded app/setup | Pilot | 2 | Prepared — awaiting pilot setup |
+| C1-S1-T06 | PYB-004.2 / PYB-011.2 | Observe the first baseline batch; record every eligible start, assistance, consent/window and any due follow-up | T05; consenting participants | Pilot | 2 | Awaiting participant sessions |
+| C1-S1-T07 | PYB-004.2 / PYB-011.2 | Observe the next baseline batch under the same task/build rules; record windows and collect due follow-up | T05; consenting participants | Pilot | 2 | Awaiting participant sessions |
+| C1-S1-T08 | PYB-004.2 / PYB-011.2 | Complete planned observation/follow-up slots toward five baseline starts; retain failures, missing responses and recruitment gaps | T05; participant access | Pilot | 2 | Awaiting participant sessions |
+| C1-S1-T09 | PYB-004.2 | Summarize baseline outcomes and actual observation cost; identify an observed obstacle without inventing one | T06–T08 actual records | Pilot + Product Owner | 1 | Awaiting observation records |
 | C1-S1-T10 | PYB-006.1 | Draft the bounded Drift recovery contract: write boundary, restore/discard, board association, failure handling and carried Blocks/A-24 scope | ADR-0010 and App contracts; no recruitment dependency | App | 3 | Done |
 | C1-S1-T11 | PYB-006.1 | Review acceptance scenarios and size the safe increment including required tests; record approval or unresolved design questions | T10; review path | App + reviewer | 1 | Done |
 | C1-S1-T12 | PYB-009.1 | Inventory existing suites, hardware/operators, applicable gates and matrix cost; draft the next operator recipe | T01 and current tools/specs | QA + firmware | 2 | Done |
 | **C1-S1 total** | | | | | **22** | |
 
+T02/T03 verified existing Play `0.2.0 (8)` and TestFlight `0.2.0 (6)` installations, origin and launch using the ledger checklist; no fresh enrollment, reinstall or upgrade was performed. Platform reports retain provenance and minimum-OS limitations. T04/T05 have completed source QA but still need the named pilot owner, cohort and tested reference setup.
+
 Five baseline starts is a target, not the implied result of reserving six hours. If access or session duration prevents it, report the actual sample and replan. A completed findings record does not mark an unperformed installation or observation task Done. Missing store source mapping remains an owned limitation under the applicable gate.
 
 ## C1-S2 — deliver a bounded safe recovery increment
@@ -208,10 +210,13 @@ flowchart LR
     S --> W["In progress"]
     W --> R["Review evidence and acceptance"]
     R --> D["Done task; assess parent separately"]
+    R --> A["Prepared or awaiting evidence; unfinished"]
+    A --> W
     W --> B["Blocked with reason and owner"]
     B --> W
     R --> W
     B --> U["Unfinished at Sprint end"]
+    A --> U
     W --> U
     U --> PB["Product Backlog: reorder and replan"]
     PB --> S