[docs] record C1-S1 execution and reconcile delivery forecasts

Record live channel evidence and explicit device/pilot blockers, prepare the residual TestFlight metadata correction, and update strategy, Scrum views, architecture, roadmap and discovery links. Preserve four completed repository tasks and eight blocked tasks. Carry forward the reviewed recovery contract and its larger estimate without claiming runtime persistence, installations, participant results or release admission.

Signed-off-by: Viwat Vchirawongkwin <viwat.v@chula.ac.th>

Author: yyods

CHANGELOG.md

@@ -6,8 +6,9 @@ are released independently from this monorepo.
 ## Unreleased
 
 These app, website, and repository-source changes do not designate a new app
-or firmware release. The qualified firmware release remains v0.6.0, built from
-its annotated tag rather than from the newer branch tip.
+or firmware release. Firmware v0.6.1 is published on the owner's confirmation;
+incomplete automated evidence remains pending. The qualified v0.6.0 release
+remains a separate historical baseline built from its annotated tag.
 
 The current compatible app feature set now targets `0.2.0`; build `5` was
 handed off through Transporter for TestFlight. This candidate identity improves
@@ -81,6 +82,17 @@ and submission packet do not claim Play submission, approval, or rollout.
   Vitest 4.1.12, with patched Sharp, Undici, source-map-js and supporting
   dependencies. Refreshed the reviewed license notices and dependency
   regression assertions while retaining the high/critical audit gate.
+- Added the reviewed Cycle 1 roadmap, milestones, Scrum working agreement,
+  stories and Sprint Backlogs, plus C1-S1 execution evidence and operational
+  pilot/validation procedures. Physical installation and participant work
+  remain blocked; no pilot results or new release are claimed.
+- Specified bounded Drift current-text recovery, local restore/discard,
+  failure handling and document/session guards in ADR-0048 and the App
+  contracts. Implementation remains pending; sizing requires revising the
+  original S2 forecast.
+- Verified live Android open-testing wording and prepared correction of the
+  older public TestFlight description. Store-installed build identities remain
+  unverified and the TestFlight metadata change remains pending.
 - 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

README.md

@@ -311,6 +311,8 @@ publish new firmware or replace the live site.
 - [App contract](docs/specifications/app.md)
 - [Hardware and compatibility](docs/specifications/hardware.md)
 - [Public roadmap](docs/ROADMAP.md)
+- [Cycle 1 delivery plan](docs/developments/2026-q4-reliable-workflow/01_Overview_and_Scrum_Framework.md)
+- [C1-S1 execution and remaining evidence](docs/developments/2026-q4-reliable-workflow/c1-s1/00_Execution_Record.md)
 - [Architecture decisions](docs/decisions/README.md)
 - [Validation evidence index](docs/validation/README.md)
 - [Security policy](SECURITY.md)

docs/README.md

@@ -16,13 +16,22 @@ maintainer guidance beside the source they govern.
 ## Proposed release plans
 
 - [Firmware v0.6.1 and v0.7.0 roadmap](planning/firmware-v0.6.1-v0.7.0-roadmap.md)
-  — v0.6.1 hardening is approved for implementation; the Reliable Projects
-  v0.7.0 scope remains proposed
+  — v0.6.1 is published on owner confirmation; incomplete automated evidence
+  remains pending, and Reliable Projects v0.7.0 remains proposed
+- [Implementation strategy](planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md)
+  — current outcomes, evidence gates and conditional expansion
+- [Cycle 1 Scrum delivery package](developments/2026-q4-reliable-workflow/01_Overview_and_Scrum_Framework.md)
+  — roadmap, milestones, stories and capacity forecasts
+- [C1-S1 execution record](developments/2026-q4-reliable-workflow/c1-s1/00_Execution_Record.md)
+  — channel evidence, pilot kit, recovery contract/sizing and validation recipe;
+  physical installation and participant work remain blocked
 
 ## Detailed specifications
 
 - [`specifications/App/`](specifications/App/) — app requirements, test design,
   and the Signal visual system
+- [Bounded current-text recovery contract](specifications/App/current-draft-recovery.md)
+  — specified in C1-S1; implementation and acceptance evidence remain pending
 - [`specifications/firmware/`](specifications/firmware/) — firmware
   requirements, test design, browser flashing, release integrity, and HIL
   gates
@@ -64,7 +73,11 @@ bundled offline examples required by its own product contracts.
   plan](testing/testflight/0.2.0-build-5.md)
 - [PyBLE 0.1.0 (4) TestFlight description and test
   plan](testing/testflight/0.1.0-build-4.md)
-
-Internal sprint notes and automated-agent orchestration are intentionally kept
-outside the public source repository. Public work is planned through the
-roadmap and GitHub issues.
+- [Current channel and artifact ledger](developments/2026-q4-reliable-workflow/c1-s1/01_Channel_and_Artifact_Ledger.md)
+- [TestFlight metadata correction packet](developments/2026-q4-reliable-workflow/c1-s1/05_TestFlight_Metadata_Correction.md)
+  — prepared replacement for the stale public description; store update pending
+
+Reviewed delivery plans and redacted execution evidence live under
+`developments/`. Raw observations, contact/consent records, device identifiers,
+local worktree state and automated-agent orchestration remain outside Git.
+Planning IDs are not GitHub issue numbers; link actual issues when created.

docs/ROADMAP.md

@@ -31,6 +31,16 @@ v0.7.0 remains non-normative and requires separate maintainer approval.
 
 ## Near term
 
+- Complete the [C1-S1 remaining evidence](developments/2026-q4-reliable-workflow/c1-s1/00_Execution_Record.md):
+  physical store installations, confirmed pilot ownership/setup and five real
+  baseline observations. The channel ledger, pilot kit, recovery design and
+  validation inventory are prepared; this does not complete the Sprint.
+- Implement the [bounded current-text recovery contract](specifications/App/current-draft-recovery.md)
+  after replanning against its 45–72 hour working estimate for engineering,
+  recipe, representative platform checks and follow-up. Current drafts remain
+  volatile; full A-24 and Blocks persistence remain separate scope.
+- 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.
 - Continue the app 0.2.0 beta train; source is currently `0.2.0+8`. The
   [Android publication review](testing/website/android-open-testing-2026-09-25.md)
   records live open-testing availability. The

docs/decisions/0011-connection-gated-shell.md

@@ -28,3 +28,13 @@ The Signal landscape shell renders a fixed three-pane IDE frame — **Files side
 - The change is confined to the shell + providers; the `Connection` seam (D1/D2), the import boundary (no UI package imports `lib/ble`, CON-8), Riverpod (ADR-0007), and every §1A.3 rejection are unchanged.
 
 Unchanged rejection list, seam, and layering as in [ADR-0009](0009-runtime-connection-manager.md)/[ADR-0010](0010-working-loop-in-memory-document.md).
+
+## Follow-up — 25 September 2026
+
+[ADR-0048](0048-bounded-current-text-draft-recovery.md) and the
+[bounded recovery contract](../specifications/App/current-draft-recovery.md)
+specify a narrow successor exception: a local recovery preview/Restore/Discard
+panel must be reachable without a board, permission prompt or network access.
+The normal IDE remains connection-gated; this is not a full offline IDE or an
+authorization to restore board-write authority. Implementation is pending, so
+the current shell behavior above remains the recorded runtime baseline.

docs/developments/2026-q4-reliable-workflow/01_Overview_and_Scrum_Framework.md

@@ -9,14 +9,14 @@
 |---|---|
 | Package | PyBLE 2026 Q4 reliable workflow, Cycle 1 (`C1`) |
 | Prepared | 25 September 2026; Asia/Bangkok |
-| Strategy | [Implementation Plan, revision 1.2](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md) |
+| Strategy | [Implementation Plan, revision 1.3](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md) |
 | Repository baseline | `23ed764b0ef88dce9720c66fbd1c0655268860cf` |
 | Proposed cycle | 28 September–20 December 2026; six two-week Sprints |
-| Status | Proposed delivery package; no Sprint Planning, estimates, named assignments, implementation approval, or new physical results are implied |
+| 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 |
 | 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 file is currently a local document; include it with this package when proposing the documentation for version control.
+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.
 
 ## Navigation and ownership of information
 
@@ -27,11 +27,12 @@ This package derives execution views from the strategy. It does not replace norm
 | [03 — Milestones](03_Milestones.md) | Evidence-based decisions and admission criteria | New evidence or a milestone decision |
 | [04 — Sprint plan](04_Sprint_Plan.md) | Sprint Goal forecasts, calendar, and capacity | Sprint Planning or Sprint Review |
 | [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) | Candidate tasks, local effort allowances, dependencies, and execution status | Developers select/adapt work during a Sprint |
+| [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 |
 
 ```mermaid
 flowchart LR
-    Strategy["Strategy revision 1.2"] --> Goal["One Product Goal"]
+    Strategy["Strategy revision 1.3"] --> Goal["One Product Goal"]
     Goal --> Roadmap["Outcome roadmap and milestones"]
     Roadmap --> Product["Ordered Product Backlog"]
     Product --> Planning["Sprint Planning"]
@@ -122,10 +123,10 @@ Unfinished items return to the Product Backlog for reordering and replanning. Do
 | Convention | Rule |
 |---|---|
 | `PYB-001` … `PYB-032` | Existing strategy planning parents; not GitHub issue numbers |
-| `PYB-006.1`, `PYB-006.2`, etc. | Derived child items in this package; acceptance is maintained in file 05 |
+| `PYB-006.1`, `PYB-006.2`, etc. | Derived child items in this package; acceptance is maintained in file 05; new residual `PYB-002.1` records the TestFlight metadata discrepancy |
 | `A-24` | Existing broader persistence story; a bounded child does not complete all of it |
 | `C1-S1` … `C1-S6` | This cycle's Sprints; distinct from historical App TDD Sprint labels |
-| `C1-S1-T01`, etc. | Proposed task rows; not new public contracts |
+| `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 |
 | Private versus public records | Contact/consent, device identifiers and raw logs remain private/ignored; publish only reviewed aggregate findings and redacted evidence |
@@ -136,7 +137,7 @@ When facts or priority change, update the canonical file above and its dependent
 
 | Source | Use and precedence |
 |---|---|
-| [Strategy revision 1.2](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md) | Scope, targets, six-Sprint capacity, three outcomes, Ready program and conditional horizons |
+| [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 |
 | [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 |

docs/developments/2026-q4-reliable-workflow/02_Product_Roadmap.md

@@ -5,9 +5,9 @@
 
 | Control | Value |
 |---|---|
-| Status | Proposed; product direction and forecasts, not approved feature or release commitments |
+| Status | C1-S1 repository work recorded; physical/pilot tasks blocked. Future direction remains conditional and forecasts need revision after sizing |
 | Planning date | 25 September 2026; dates use Asia/Bangkok |
-| Source | [Implementation strategy revision 1.2](../../planning/PyBLE_Implementation_Plan_and_Strategy_v1.0.md), particularly §§1, 6–9, 12, 14, and 19 |
+| Source | [Implementation strategy revision 1.3](../../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 |
@@ -33,11 +33,11 @@ continues to communicate direction without promising release dates.
 ## Completed baseline and remaining uncertainty
 
 These records are inputs to planning, not new achievements of this development
-cycle. Future work below remains **Proposed** until explicitly selected.
+cycle. The [C1-S1 record](c1-s1/00_Execution_Record.md) distinguishes completed design/evidence preparation from blocked installations and observations. Future work remains **Proposed** until explicitly selected.
 
 | Baseline item | Recorded state at the planning date | Consequence for this roadmap |
 |---|---|---|
-| Android distribution and public copy | Google Play 0.2.0 open testing; README/site correction completed in PR #33 | Preserve accurate copy; PYB-002 covers only newly found discrepancies |
+| Android distribution and public copy | Google Play 0.2.0 open testing; direct live-site checks on 25 September confirm the PR #33 correction | Preserve accurate copy; newly found TestFlight description discrepancy is PYB-002.1 |
 | App source and installed identity | Source `0.2.0+8`; source version alone does not identify an installed Play/TestFlight binary | PYB-001 records actual installed versions/builds and source mapping or explicit unknowns |
 | iPad distribution | External TestFlight beta is the recorded channel | Verify the selected installation path and artifact evidence; do not infer production App Store availability |
 | 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 |
@@ -78,9 +78,11 @@ for one maintainer. All rows in this table have status **Proposed**.
 | C1-S5; 23 Nov–6 Dec | Freeze candidate, complete applicable evidence, and assess mature follow-ups | M-04 / SG1; M-06 inputs | Release only when relevant evidence passes; qualified maintenance may also ship earlier |
 | C1-S6; 7–20 Dec | Verify actual channel/install state and choose one subsequent investment | M-05; M-06 / SG3 | Record pass, iterate, blocked, or inconclusive outcomes; make a dated next-stage decision |
 
+**Sizing update:** recovery now has a 45–72 hour working estimate including supporting tasks. Its 60-hour S2–S4 allocation option would displace original matrix/activation work. The table above is the original sequencing baseline, not a validated selection; replan before using its delivery dates. The full matrix has its own [costed inventory](c1-s1/04_Validation_Inventory_and_Operator_Recipe.md).
+
 The [Sprint Plan](04_Sprint_Plan.md) owns detailed dates and capacity. The first
-Sprint Backlog is a candidate for Sprint Planning; later allocations are
-forecasts. A milestone review neither replaces a Sprint Review nor supplies
+Sprint Backlog now records early C1-S1 execution and its remaining blockers;
+later allocations are forecasts requiring replanning. A milestone review neither replaces a Sprint Review nor supplies
 missing Definition of Done evidence.
 
 ```mermaid