[green] refresh README and roadmap for published v0.6.1

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

Author: yyods

README.md

@@ -8,14 +8,17 @@ MicroPython IDE.
 [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.22064467.svg)](https://doi.org/10.5281/zenodo.22064467)
 [![Platforms](https://img.shields.io/badge/app-iPadOS%20%7C%20Android-2D5BFF.svg)](#app)
 [![Protocol](https://img.shields.io/badge/protocol-PBLE%2F1-0E7490.svg)](docs/specifications/protocol.md)
-[![Firmware](https://img.shields.io/badge/firmware-v0.6.0%20qualified-15803D.svg)](https://pyble.dev/flash)
+[![Firmware](https://img.shields.io/badge/firmware-v0.6.1%20published-15803D.svg)](https://pyble.dev/flash)
 
 PyBLE lets you edit, transfer, run, and stop MicroPython programs on a
 compatible microcontroller board over Bluetooth Low Energy. Its normal
 workflow needs no USB serial connection, Wi-Fi onboarding, cloud account, or
 telemetry.
 
-- Qualified firmware v0.6.0: [installer and download](https://pyble.dev/flash)
+- Published firmware v0.6.1: [installer and download](https://pyble.dev/flash)
+- Tutorials: [learn PyBLE](https://pyble.dev/learn)
+- Firmware features and functional block diagram: [architecture reference](https://pyble.dev/features)
+- Official example collection: [PyBLE-dev/examples](https://github.com/PyBLE-dev/examples)
 - iPad external beta:
   [join with TestFlight](https://testflight.apple.com/join/yU4e8s6d)
 - Android invited testing: [see the app page](https://pyble.dev/app)
@@ -45,16 +48,20 @@ The Flutter app currently provides:
 - a Python-highlighted MicroPython editor with always-visible, one-based line
   numbers, an adjustable 10–24 point code font, save, run, stop, soft reboot,
   and live console;
-- wireless file browsing and transfer with integrity checks;
+- wireless file browsing and transfer with integrity checks, reviewed
+  multi-file deletion, and a compact Files action menu;
 - an optional public GitHub example browser that resolves a repository/ref to
   an immutable commit, previews exact `.py` source-to-board paths, and imports
   selected files into the connected Files folder only after explicit review;
+  the official repository URL is prefilled and editable, with a branch chooser
+  and an optional manual tag/commit input;
 - an offline Blockly workspace with GPIO and standard MicroPython NeoPixel
   blocks, including explicit numeric GPIOs and bounded named `machine.Pin`
   identities;
 - editable beginner examples;
 - exact Blockly sidecar reopening and a bounded Python-to-blocks importer;
-- an adaptive tablet interface for portrait and landscape use; and
+- an adaptive tablet interface for portrait and landscape use;
+- an offline privacy policy accessible from About; and
 - core editing, BLE, Files, Blocks, and Run operation without an account,
   analytics, or cloud dependency. GitHub is the sole optional network surface;
   its public, unauthenticated requests start only when the user opens the
@@ -67,47 +74,64 @@ fetches and validates the complete batch, shows the exact destination paths,
 and asks separately before overwriting existing files. Import never creates a
 remote folder hierarchy, opens an editor document, or runs downloaded code.
 
-The iPad build is available through public TestFlight. An invited Android
-internal test is available through Google Play; this is not a public Play
-release. Both platforms share the same Flutter source and app test gates.
+The current App source version is `0.2.0+8`; App and firmware versions are
+independent. iPad testing uses TestFlight, and Android distribution follows
+the testing access shown on the [App page](https://pyble.dev/app). The
+[Google Play build-8 handoff](docs/testing/google-play/0.2.0-build-8.md)
+records prepared artifacts and their exact source; preparation does not
+establish a live store release 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.
 
 ### Firmware
 
 The board-side agent is built with upstream MicroPython and exposes PBLE/1 as a
 BLE GATT peripheral. It supports:
 
-- capability and device-information negotiation;
-- run, stop, console, and soft-reboot control;
-- filesystem operations with CRC validation and atomic uploads;
-- resumable transfer behavior and bounded transport recovery;
-- optional `main.py` auto-run protection;
-- board naming and identify support; and
+- capability and device-information negotiation with session-scoped HELLO;
+- run, stop, console, and soft-reboot control, with fresh globals per file RUN
+  and stdin isolated to its owning run;
+- LFS2 workspaces across all five profiles, CRC-checked resumable uploads,
+  atomic publication, storage-reserve checks, and serialized file mutations;
+- bounded fragment reassembly and transport/session recovery;
+- optional `main.py` auto-run protection and checked configuration persistence;
+- board naming and identify support;
+- an exact-board ST7789 display and boot splash on Waveshare's B-version; and
 - upstream MicroPython’s standard `neopixel` module.
 
-The installer offers the qualified public v0.6.0 release across all five exact
-release profiles. All five exact-byte HIL rows passed. The four ESP profiles
-use Web Serial from a supported desktop Chromium browser; Pico 2 W uses a
-browser-verified UF2 download followed by a manual BOOTSEL copy.
-
-| Profile                       | Exact hardware constraint                                               | Provisioning                       | Public status    |
-| ----------------------------- | ----------------------------------------------------------------------- | ---------------------------------- | ---------------- |
-| `esp32-4mb`                   | Classic ESP32; exactly 4 MiB external flash; no PSRAM required          | ESP Web Serial                     | Qualified v0.6.0 |
-| `esp32-s3-n16r8`              | Lean ESP32-S3; exactly 16 MiB flash and 8 MiB Octal PSRAM               | ESP Web Serial                     | Qualified v0.6.0 |
-| `waveshare-esp32-s3-lcd-147b` | Exact ESP32-S3-LCD-1.47B B-version; 16 MiB flash and 8 MiB Octal PSRAM  | ESP Web Serial                     | Qualified v0.6.0 |
-| `esp32-c3-4mb`                | ESP32-C3 revision v0.3 or newer; exactly 4 MiB flash; no PSRAM required | ESP Web Serial                     | Qualified v0.6.0 |
-| `rpi-pico2-w`                 | Raspberry Pi Pico 2 W; RP2350 with CYW43439                             | Verified UF2 + manual BOOTSEL copy | Qualified v0.6.0 |
+The installer offers the owner-confirmed public v0.6.1 release across all five
+exact release profiles. The owner confirmed completed qualification and
+authorized publication on 2026-09-11. Existing automated qualification records
+remain incomplete and are preserved unchanged; owner confirmation does not
+mark missing automated measurements passed. The four ESP profiles use Web Serial
+from a supported desktop Chromium browser; Pico 2 W uses a browser-verified UF2
+download followed by a manual BOOTSEL copy.
+
+| Profile | Exact hardware constraint | Provisioning | Public status |
+| --- | --- | --- | --- |
+| `esp32-4mb` | Classic ESP32; exactly 4 MiB external flash; no PSRAM required | ESP Web Serial | Owner-confirmed v0.6.1 |
+| `esp32-s3-n16r8` | Lean ESP32-S3; exactly 16 MiB flash and 8 MiB Octal PSRAM | ESP Web Serial | Owner-confirmed v0.6.1 |
+| `waveshare-esp32-s3-lcd-147b` | Exact ESP32-S3-LCD-1.47B B-version; 16 MiB flash and 8 MiB Octal PSRAM | ESP Web Serial | Owner-confirmed v0.6.1 |
+| `esp32-c3-4mb` | ESP32-C3 revision v0.3 or newer; exactly 4 MiB flash; no PSRAM required | ESP Web Serial | Owner-confirmed v0.6.1 |
+| `rpi-pico2-w` | Raspberry Pi Pico 2 W; RP2350 with CYW43439 | Verified UF2 + manual BOOTSEL copy | Owner-confirmed v0.6.1 |
 
 The immutable
-[release descriptor](https://pyble.dev/firmware/v0.6.0/release.json), with
+[release descriptor](https://pyble.dev/firmware/v0.6.1/release.json), with
 SHA-256
-`c2940281a14feddb55c48de15ac18087e9317d1b7130e514fab5a209b046a1e6`,
-binds the five artifacts and passed HIL status to source commit
-`0c7230d6708797c241160ba71fbd37e6b22f180a` and the annotated
-[`firmware-v0.6.0` source tag](https://github.com/PyBLE-dev/PyBLE/tree/firmware-v0.6.0).
-See the [release notes](https://pyble.dev/firmware/v0.6.0/RELEASE_NOTES.md),
-[artifact checksums](https://pyble.dev/firmware/v0.6.0/SHA256SUMS), and
-[recovery guide](https://pyble.dev/firmware/v0.6.0/RECOVERY.md) before
-installing.
+`71f6aca6df07e31a1f54c7f70a48d82c7fe26b1c8ca0626a8ffc57c804fbb1bd`,
+binds the five artifacts to exact source
+[`c8f549eeabe6d2b8c2766eab022517944bb09c8c`](https://github.com/PyBLE-dev/PyBLE/tree/c8f549eeabe6d2b8c2766eab022517944bb09c8c).
+See the [owner confirmation](https://pyble.dev/firmware-v0.6.1-owner-confirmation.md),
+[release notes](https://pyble.dev/firmware/v0.6.1/RELEASE_NOTES.md),
+[artifact checksums](https://pyble.dev/firmware/v0.6.1/SHA256SUMS), and
+[recovery guide](https://pyble.dev/firmware/v0.6.1/RECOVERY.md) before installing.
+
+Back up before moving from older workspace formats. v0.6.1 refuses nonblank or
+uncertain media that it cannot mount safely; it does not silently reformat an
+old workspace. That refusal requires USB recovery rather than a BLE session.
+The prior [qualified v0.6.0 release](https://pyble.dev/firmware/v0.6.0/RELEASE_NOTES.md)
+and its [source tag](https://github.com/PyBLE-dev/PyBLE/tree/firmware-v0.6.0)
+remain historical references, not the current installer selection.
 
 These maintained release profiles are not an app-side chip or board allowlist.
 A future board is compatible when it has a maintained PyBLE agent port, BLE
@@ -129,8 +153,9 @@ This repository is intentionally a monorepo:
 - [`app/`](app/) — the Flutter tablet application;
 - [`firmware/`](firmware/) — the portable agent, board overlays, and release
   tooling;
-- [`examples/`](examples/) — clean-room, board-neutral MicroPython examples,
-  including the public GitHub-import fixtures;
+- [`examples/`](examples/) — small source/conformance examples and GitHub-import
+  fixtures; the separately maintained [official example collection](https://github.com/PyBLE-dev/examples)
+  contains the user-facing examples for all five profiles;
 - [`docs/specifications/protocol.md`](docs/specifications/protocol.md) — the
   open PBLE/1 wire contract;
 - [`tests/`](tests/) — host, conformance, release, and HIL test runners;
@@ -147,23 +172,32 @@ shared conformance corpus, documentation, and CI atomically.
    [TestFlight](https://testflight.apple.com/join/yU4e8s6d), or build the
    Flutter app locally.
 2. Open [pyble.dev/flash](https://pyble.dev/flash) in a supported desktop
-   Chromium browser. Confirm that the qualified v0.6.0 release is selected,
+   Chromium browser. Confirm that the published v0.6.1 release is selected,
    then choose only the exact profile matching the board and memory topology.
 3. Before provisioning, back up the board and accept every safety
    acknowledgement. Flashing erases the board and its existing workspace.
 4. For the four ESP profiles, connect the board and install with Web Serial.
    For Pico 2 W, download the verified UF2 and copy it manually to the BOOTSEL
    mass-storage volume. iPadOS cannot perform either wired provisioning step.
 5. Open PyBLE, scan for the provisioned board, and connect over BLE.
-6. To try the optional public example importer, open the destination folder in
-   **Files**, choose **Import examples from GitHub**, enter
-   `https://github.com/PyBLE-dev/PyBLE` with ref `main`, then browse to
-   `examples/github-import`.
-7. Select `hello.py` or `count.py`, review the displayed commit SHA and exact
-   board target, and confirm any overwrite separately. Import does not open or
-   run the file; open it from Files and choose Run only when you are ready.
-
-See [support and troubleshooting](https://pyble.dev/support) for browser,
+6. In **Files**, create or open a writable subfolder such as `/examples` within
+   the board's advertised filesystem root. Do not assume `/` is writable on
+   every board; read the destination warning before importing there.
+7. Choose **Import examples from GitHub**. The prefilled URL
+   `https://github.com/PyBLE-dev/examples` is editable. Let the branch chooser
+   load, select `main` (or another available branch), and browse to
+   `examples/portable/basics/hello_console`. If GitHub reports its public
+   request limit, wait for the displayed retry time rather than repeatedly
+   reloading. Advanced users can enter a tag or commit manually.
+8. Select `pyble_hello_console.py`, review the displayed immutable commit SHA
+   and exact board destination, and confirm any overwrite separately. The
+   official URL does not bypass source review or imply validation of every
+   example. Import does not open or run the file; open it from Files and
+   choose Run only when you are ready.
+
+Follow the [guided tutorials](https://pyble.dev/learn), including real Lenovo
+workflow screenshots, for the complete learning path. See
+[support and troubleshooting](https://pyble.dev/support) for browser,
 Bluetooth, network, and recovery requirements. A GitHub account or token is not
 needed for the optional import; every other workflow remains available without
 it.
@@ -194,6 +228,7 @@ Firmware host tests:
 
 ```sh
 tests/firmware_tests/run_tests.sh
+python3 -m unittest discover -s tests/firmware_tests/host -p 'test_*.py' -v
 ```
 
 Firmware build preparation and target builds:
@@ -205,19 +240,20 @@ firmware/scripts/build.sh esp32-s3
 firmware/scripts/build.sh waveshare-esp32-s3-lcd-147b
 firmware/scripts/build.sh esp32-c3
 firmware/scripts/install_arm_toolchain.sh
+firmware/scripts/install_picotool.sh
 firmware/scripts/build_rp2.sh rpi-pico2-w
 ```
 
-These are the five target builds in the qualified v0.6.0 release. The four ESP
+These are the five target builds in the published v0.6.1 release. The four ESP
 targets produce Web Serial artifacts; `rpi-pico2-w` produces the UF2 used by
 the verified-download and BOOTSEL flow.
 
 The commands above build the current checkout. To start from the exact source
-used for the public v0.6.0 artifacts, detach at the annotated release tag and
+used for the public v0.6.1 artifacts, detach at the exact source commit and
 restore its pinned submodules:
 
 ```sh
-git switch --detach firmware-v0.6.0
+git switch --detach c8f549eeabe6d2b8c2766eab022517944bb09c8c
 git submodule update --init --recursive
 ```
 
@@ -237,17 +273,26 @@ static export with no Node.js website process.
 The complete build requires the pinned toolchains documented in the relevant
 component README and specifications.
 
-Firmware binaries are external release artifacts, not committed source. The
-production website receives a qualified bundle and validates its descriptor
-and hashes before enabling installation. A source-only website build remains
-fail-closed unless an explicit validated release input is supplied.
+Firmware binaries are external release artifacts, not committed source.
+The public v0.6.1 installation uses its exact owner-confirmed release descriptor
+and artifact hashes; the standard automated qualification gate remains
+unchanged. A source-only website build remains fail-closed unless an explicit
+validated release input is supplied. See the
+[publication record](docs/testing/firmware-v0.6.1-publication-2026-09-11.md)
+and [website deployment record](docs/testing/website/site-v061-consistency-2026-09-11.md)
+for the release-specific deployment path; building this checkout does not
+publish new firmware or replace the live site.
 
 ## Documentation
 
 - [Documentation index](docs/README.md)
 - [Changelog](CHANGELOG.md)
-- [Qualified firmware v0.6.0 source](https://github.com/PyBLE-dev/PyBLE/tree/firmware-v0.6.0)
-- [Qualified firmware v0.6.0 release notes](https://pyble.dev/firmware/v0.6.0/RELEASE_NOTES.md)
+- [Tutorials with reviewed App screenshots](https://pyble.dev/learn)
+- [Firmware features and functional block diagram](https://pyble.dev/features)
+- [Official examples repository](https://github.com/PyBLE-dev/examples)
+- [Published firmware v0.6.1 source](https://github.com/PyBLE-dev/PyBLE/tree/c8f549eeabe6d2b8c2766eab022517944bb09c8c)
+- [Firmware v0.6.1 release notes](https://pyble.dev/firmware/v0.6.1/RELEASE_NOTES.md)
+- [Firmware v0.6.1 publication record](docs/testing/firmware-v0.6.1-publication-2026-09-11.md)
 - [Product specification](docs/specifications/product.md)
 - [Architecture](docs/specifications/architecture.md)
 - [PBLE/1 protocol](docs/specifications/protocol.md)
@@ -264,7 +309,7 @@ fail-closed unless an explicit validated release input is supplied.
 If you use PyBLE in research, teaching, or another published work, use the
 metadata in [CITATION.cff](CITATION.cff). The app and firmware are versioned
 independently, so cite the exact archived project snapshot or component
-release you used; qualified firmware v0.6.0 is not the app version.
+release you used; published firmware v0.6.1 is not the app version.
 
 The first whole-project citation snapshot is
 [`source-2026.08.23`](https://github.com/PyBLE-dev/PyBLE/releases/tag/source-2026.08.23).

docs/ROADMAP.md

@@ -5,27 +5,34 @@ promising dates; accepted work is tracked through GitHub issues and milestones.
 
 The detailed [firmware v0.6.1 and v0.7.0 proposal](planning/firmware-v0.6.1-v0.7.0-roadmap.md)
 records the post-v0.6.0 contract-hardening and Reliable Projects candidates.
-The v0.6.1 hardening scope is approved for specification-first implementation;
+The v0.6.1 hardening implementation has been published on owner confirmation;
 v0.7.0 remains non-normative and requires separate maintainer approval.
 
 ## Available now
 
 - iPad external beta through TestFlight
 - PBLE/1 editing, run/stop, console, and file workflows over BLE
 - Offline Blockly with beginner GPIO and NeoPixel examples
-- The current qualified firmware v0.6.0 covers five exact profiles: four ESP
-  Web Serial installers and the verified Pico 2 W UF2/manual-BOOTSEL path. All
-  five exact-byte hardware, recovery, PBLE/1, iPadOS, and Android rows passed
-  for that immutable release.
+- The published firmware v0.6.1 covers five exact profiles: four ESP
+  Web Serial installers and the verified Pico 2 W UF2/manual-BOOTSEL path.
+  Publication follows the owner's qualification confirmation, recorded in the
+  [owner confirmation](https://pyble.dev/firmware-v0.6.1-owner-confirmation.md).
+  Incomplete automated evidence is preserved unchanged; the qualified v0.6.0
+  release remains a separate historical baseline.
+- Guided [tutorials](https://pyble.dev/learn) with reviewed Lenovo captures,
+  the [firmware functional reference](https://pyble.dev/features), and the
+  separate [official example collection](https://github.com/PyBLE-dev/examples)
 - MIT-licensed app, agent firmware, protocol, website, tests, and release tools
 
 ## Near term
 
-- Qualify the app 0.2.0 beta train, starting at globally monotonic build 5,
-  across the retained iPad/Android and five-profile hardware test scope
-- Complete source-selected firmware v0.6.1 contract hardening, deterministic
-  builds, and fresh resource, recovery, and physical qualification across the
-  same atomic five-profile scope before publication
+- Continue the app 0.2.0 beta train; source is currently `0.2.0+8`. The
+  [prepared build-8 handoff](testing/google-play/0.2.0-build-8.md) is not proof
+  of store publication or validation of subsequent source changes.
+- Reconcile the original automated qualification tracker
+  [#24](https://github.com/PyBLE-dev/PyBLE/issues/24) with the recorded
+  owner-confirmed v0.6.1 publication without inventing missing measurements.
+- Review the proposed v0.7.0 Reliable Projects scope before implementation.
 - Expand user-facing setup, recovery, and board-specific wiring guidance
 - Open and document the Android beta distribution path
 - Convert remaining pre-public planning references into focused GitHub issues