@@ -5,61 +5,105 @@ are released independently from this monorepo.
 
 ## Unreleased
 
-- Admitted the characterized Waveshare single-page largest-block transient
-  with a fixed `98304` heap floor in a second-replacement qualification era
-  (ADR-0039), with byte-identity-conditioned carry-forward of already-passed
-  physical evidence; no firmware bytes changed.
-- Established `PyBLE-dev/PyBLE` as the canonical public monorepo.
-- Added public contributor, security, architecture, protocol, and validation
-  documentation.
+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.
 
-### App and website source
+### App source
 
 - Added fail-closed Android upload signing and signed App Bundle CI contracts,
-  plus the invited Google Play internal-test link and QR alongside TestFlight
-  on `pyble.dev`.
-- Added an independent `/privacy` policy and stable `/app` landing page.
+  while retaining invited Google Play testing as distinct from a public Play
+  release.
 - Extended every Blocks GPIO surface to accept explicit bounded MicroPython
   pin names such as `LED` while preserving numeric GPIOs, offline operation,
   and the app's board-neutral architecture.
+- Hardened the Android WebView integration path so a named-pin edit made after
+  preview is re-read from the live field before generated-code assertions.
+
+### Website and repository source
+
+- Established `PyBLE-dev/PyBLE` as the canonical public monorepo and added
+  contributor, security, architecture, protocol, and validation documentation.
+- Added an independent `/privacy` policy and stable `/app` landing page, with
+  invited Android testing and public TestFlight presented as distinct channels.
 - Patched the remediable website PostCSS/Nanoid dependency chain and bounded
   the remaining build-only `image-size` advisory behind a static-deploy and
   no-metadata-image-route contract until an upstream fix exists.
+- Made publication CI fetch the complete source history required by
+  ancestry-routed firmware gates, and made the RP2 runtime-closure fixture
+  hermetic instead of depending on a retained local archive.
+- Made RP2 builds report a missing or mismatched pinned Arm toolchain before
+  evaluating the nested source graph, while preserving fail-closed source
+  validation once the compiler is present.
+- Corrected two C3 ADR links for the public repository layout.
+
+## Website deployment — 2026-08-22
+
+- Activated the validated v0.6.0 release descriptor on `pyble.dev`, so the
+  home, flash, and support surfaces derive their current five-profile status
+  from the selected immutable release instead of hard-coded board copy.
+- Kept the exact-board Waveshare presentation separate from the lean generic
+  S3 profile and retained the real-hardware image on the flash page.
+- Published the firmware release notes, checksums, recovery instructions,
+  license inventory, and exact profile artifacts under `/firmware/v0.6.0/`.
+
+## Firmware 0.6.0 — 2026-08-21
+
+_Firmware release only. The app is versioned independently and remains
+`0.1.0+2` in this source tree._
+
+- Published and deployed the qualified five-profile release at
+  [pyble.dev/flash](https://pyble.dev/flash): `esp32-4mb`,
+  `esp32-s3-n16r8`, `waveshare-esp32-s3-lcd-147b`, `esp32-c3-4mb`, and
+  `rpi-pico2-w`.
+- Completed the exact-byte qualification matrix: all five HIL rows passed,
+  including install and recovery, PBLE/1 workflows, run/stop and console
+  behavior, filesystem reliability, fixed resource and timing limits, and app
+  operation on iPadOS and Android.
+- Provisioned the four ESP profiles through ESP Web Serial. Pico 2 W uses a
+  verified UF2 download followed by a manual BOOTSEL copy; it is not a Web
+  Serial target.
+- Added qualified ESP32-C3 revision v0.3-or-newer support for the exact 4 MiB
+  profile and qualified Raspberry Pi Pico 2 W support through the portable
+  frozen-Python RP2 agent.
+- Kept `esp32-s3-n16r8` lean and board-neutral while giving the exact
+  Waveshare B-version profile its ST7789 runtime and fresh-install splash with
+  persistent disable.
+- Hardened response delivery, VM and run lifecycle, STOP and soft-reboot
+  ordering, filesystem concurrency, and console flow across the ESP and RP2
+  ports.
+- Bound the immutable release to annotated tag `firmware-v0.6.0`, PyBLE source
+  `0c7230d6708797c241160ba71fbd37e6b22f180a`, MicroPython v1.28.0 and
+  ESP-IDF v5.5.1, agent `0.6.0`, protocol `PBLE/1`, and zero upstream patches.
+- Published schema-4 metadata with SHA-256
+  `c2940281a14feddb55c48de15ac18087e9317d1b7130e514fab5a209b046a1e6`
+  and independently hashed artifacts, notices, release notes, and recovery
+  instructions.
+- Admitted the characterized Waveshare single-page largest-block transient
+  with the fixed `98304` heap floor defined by ADR-0039; firmware bytes stayed
+  unchanged while the final qualification policy was corrected.
 
-### Firmware 0.6.0 source integration
-
-- Abandoned the unpublished local `firmware-v0.6.0` candidate at `719b211…`
-  after the C3 stateless-PHY/post-OI receipt and fixed performance-contract
-  amendments. Version 0.6.0 and its atomic five-profile scope are retained for
-  a source-era-routed replacement; all candidate/HIL gates restart before any
-  tag is pushed or release is published.
-- Added the `rpi-pico2-w` portable frozen-Python agent port, its isolated RP2
-  build plane, and pinned Arm GNU toolchain input alongside the four existing
-  ESP build variants.
-- Recorded successful pre-GP2 Pico 2 W BLE/app operation and physical onboard
-  LED actuation as engineering evidence. Pico remains absent from public
-  release metadata and the web installer until its complete GP2 matrix passes.
-- Reserved a new source identity instead of reusing the earlier `0.5.1`
-  Waveshare/ESP candidate version; all publishable artifacts require fresh
-  version-bound build, provenance, resource, recovery, and HIL evidence.
-
-### Firmware 0.5.1 source candidate — 2026-08-03
-
-- Defined the independently selected `waveshare-esp32-s3-lcd-147b`
-  provisioning profile for the exact ESP32-S3-LCD-1.47B B-version board with
-  16 MiB flash and 8 MiB Octal PSRAM.
-- Specified its exact-board-only ST7789 MicroPython runtime, bounded boot
-  companion, app QR, persistent splash opt-out, and dedicated display/HIL
-  qualification contract. An erased exact-board installation defaults the
-  splash on; stored `0` remains an explicit opt-out.
-- Kept `esp32-s3-n16r8` lean and board-neutral: its image contract contains no
-  Waveshare pin map, TFT driver, companion, QR, splash hook, or display-only
-  readiness seam.
-- Expanded the candidate source/build contract to four variants over the three
-  initial ESP32-family targets. No new exact bytes or public profile are
-  qualified by this documentation change; reproducible builds, license audit,
-  and independent final-candidate HIL remain required for all three candidate
-  release profiles, while ESP32-C3 remains deferred.
+## Firmware 0.5.1 — 2026-08-03
+
+- Published the qualified three-profile release for `esp32-4mb`, the lean
+  `esp32-s3-n16r8`, and the separate exact-board
+  `waveshare-esp32-s3-lcd-147b` profile.
+- Made the Waveshare PyBLE splash the fresh-install default while preserving a
+  stored opt-out; kept its ST7789 runtime and board pin map out of the generic
+  S3 image.
+- Bound the release to annotated tag `firmware-v0.5.1`, source
+  `bab472131f0a71c5c4a7efc689eab266189a1896`, MicroPython v1.28.0, and
+  ESP-IDF v5.5.1. ESP32-C3 and Pico 2 W were not included in this release.
+
+## Firmware 0.5.0 — 2026-08-03
+
+- Published the first qualified three-profile bundle, adding the exact
+  Waveshare ESP32-S3-LCD-1.47B B-version profile alongside the two generic ESP
+  profiles.
+- Added its isolated ST7789 MicroPython runtime and opt-in splash without
+  adding board-specific display code to `esp32-s3-n16r8`.
+- Bound the release to annotated tag `firmware-v0.5.0` and source
+  `4ac661e610a00207246bc9e9863d96085e77854f`.
 
 ## Firmware 0.4.2 — 2026-07-31
 
@@ -95,7 +139,7 @@ are released independently from this monorepo.
 
 The pre-publication development history is intentionally archived outside this
 repository. Public development starts from the audited source snapshot.
-Firmware 0.4.1 therefore remains a legacy pre-publication release; its source
+Firmware 0.4.1 therefore remains a legacy pre-publication release: its source
 is present here, but its original commit identifier is not part of the public
-history. The next firmware release will rebuild and requalify from a public
-commit.
+history. Later firmware entries identify the annotated public source tag and
+exact commit used for their immutable artifacts.
@@ -7,13 +7,14 @@ MicroPython IDE.
 [![License: MIT](https://img.shields.io/badge/license-MIT-yellow.svg)](LICENSE)
 [![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)
 
 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.
 
-- Website and browser-installer status: [pyble.dev](https://pyble.dev)
+- Qualified firmware v0.6.0: [installer and download](https://pyble.dev/flash)
 - iPad external beta:
   [join with TestFlight](https://testflight.apple.com/join/yU4e8s6d)
 - Android invited testing: [see the app page](https://pyble.dev/app)
@@ -65,27 +66,36 @@ BLE GATT peripheral. It supports:
 - board naming and identify support; and
 - upstream MicroPython’s standard `neopixel` module.
 
-The public browser installer currently offers the exact v0.4.2 hardware-tested
-beta for both current profiles. Production Chrome erase/install and deliberately
-interrupted-flash recovery passed on real hardware for both exact profiles.
-Complete release qualification continues across the app, PBLE/1, resource, and
-remaining firmware matrices:
-
-| Installer profile | Exact target constraint                                      | Public status                                                |
-| ----------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| `esp32-4mb`       | Classic ESP32, 4 MiB external SPI flash; no PSRAM assumed    | v0.4.2 hardware-tested beta; browser install/recovery passed |
-| `esp32-s3-n16r8`  | ESP32-S3, 16 MiB flash / 8 MiB Octal PSRAM; N16R8-class only | v0.4.2 hardware-tested beta; browser install/recovery passed |
-| `esp32-c3-4mb`    | ESP32-C3, 4 MiB external SPI flash; no PSRAM assumed         | Planned; unavailable; no public image                        |
-
-See the
-[post-release production-browser attestation](docs/validation/browser-flashing/v0.4.2-production.md)
-for the exact hashes, completed checks, and deliberately bounded claim.
-
-These are the initial port targets, not a chip-family allowlist. A future board
-is compatible when it has a maintained PyBLE agent port, BLE GATT
-peripheral support, adequate resources, PBLE/1 conformance, recovery testing,
-and hardware-validation evidence. Stock MicroPython plus generic Bluetooth
-hardware is not sufficient by itself.
+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 immutable
+[release descriptor](https://pyble.dev/firmware/v0.6.0/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.
+
+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
+GATT peripheral support, adequate resources, PBLE/1 conformance, recovery
+testing, and hardware-validation evidence. Stock MicroPython plus generic
+Bluetooth hardware is not sufficient by itself.
 
 ## How it fits together
 
@@ -117,15 +127,14 @@ 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.
-   The exact v0.4.2 hardware-tested beta is active. Browser installation and
-   interrupted-flash recovery passed on both exact profiles; complete release
-   qualification continues. Confirm the active version, your exact profile,
-   and the enabled install action.
-3. Before flashing, back up the board, confirm its exact memory profile, and
-   accept every safety acknowledgement before using the one-time wired
-   installer. Flashing erases the board.
-4. Open PyBLE, scan for the provisioned board, connect, and run an example over
+   Chromium browser. Confirm that the qualified v0.6.0 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, connect, and run an example over
    BLE.
 
 See [support and troubleshooting](https://pyble.dev/support) for browser,
@@ -148,7 +157,9 @@ flutter pub get --enforce-lockfile
 flutter gen-l10n
 dart format --output=none --set-exit-if-changed lib test integration_test
 flutter analyze
-flutter test
+flutter test --exclude-tags golden
+# Run the pixel-golden lane on its pinned macOS host:
+flutter test --tags golden
 ```
 
 Firmware host tests:
@@ -169,9 +180,18 @@ firmware/scripts/install_arm_toolchain.sh
 firmware/scripts/build_rp2.sh rpi-pico2-w
 ```
 
-The Pico 2 W command builds the in-progress `0.6.0` source port. It has
-successful pre-GP2 hardware evidence but no public installer image or support
-claim until the complete GP2 matrix passes.
+These are the five target builds in the qualified v0.6.0 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
+restore its pinned submodules:
+
+```sh
+git switch --detach firmware-v0.6.0
+git submodule update --init --recursive
+```
 
 Website:
 
@@ -184,9 +204,17 @@ npm run check
 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.
+
 ## 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)
 - [Product specification](docs/specifications/product.md)
 - [Architecture](docs/specifications/architecture.md)
 - [PBLE/1 protocol](docs/specifications/protocol.md)
@@ -195,6 +223,7 @@ component README and specifications.
 - [Hardware and compatibility](docs/specifications/hardware.md)
 - [Public roadmap](docs/ROADMAP.md)
 - [Architecture decisions](docs/decisions/README.md)
+- [Validation evidence index](docs/validation/README.md)
 - [Security policy](SECURITY.md)
 
 ## Contributing