@@ -52,6 +52,8 @@ bundled offline examples required by its own product contracts.
 
 ## Testing and release handoff
 
+- [PyBLE 0.2.0 (5) TestFlight description and test
+  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)
 
 
@@ -0,0 +1,190 @@
+# PyBLE 0.2.0 (5) TestFlight test description
+
+This document contains the English (`en-US`) TestFlight copy and test plan for
+PyBLE app version `0.2.0`, build `5`. It is written for external beta testers
+updating from TestFlight build `0.1.0 (4)`.
+
+- App bundle ID: `dev.pyble.pyble`
+- App source: `8f8dd32010fac9b2b636f57f9044fd040565e0dd`
+- PBLE/1 baseline: `PBLE/1`
+- Qualified board-agent release: `0.6.0`
+- TestFlight channel: public external beta
+- Minimum iOS/iPadOS encoded by this historical build: `13.0`
+- Transporter advisory observed during upload: `90068` (Apple's announced
+  Spring 2027 minimum becomes iOS/iPadOS 15)
+
+## Transporter artifact handoff
+
+- Prepared: `2026-08-27`
+- IPA filename: `PyBLE-0.2.0-build-5-8f8dd32.ipa`
+- IPA size: `22,409,046` bytes
+- IPA SHA-256:
+  `e2e44019aafd6b75f1d281a7cf4fb49d3ef7f326a4d604f2900ad249af70f2af`
+- Signing: Apple Distribution / App Store provisioning for
+  `dev.pyble.pyble`
+- Matching archive and dSYMs: retained outside Git with the local handoff
+  artifact
+
+The IPA has passed the repository's strict local App Store payload validator,
+including code-signature, nested-code, and Xcode software-information checks.
+That validator did not evaluate Apple's later-announced Spring 2027 deployment
+floor. The retained IPA and archive therefore remain exact iOS/iPadOS 13
+artifacts and MUST NOT be relabelled or re-exported as iOS/iPadOS 15. Future
+source raises the project floor through a clean rebuild; this record claims no
+corrected build-6 upload. This preparation record also does not claim that App
+Store Connect accepted or processed build 5.
+
+Apple treats the Beta App Description as app-level information and What to Test
+as build-specific information. Paste only the text inside the corresponding
+plain-text blocks into App Store Connect. Keep tester or reviewer credentials
+out of both fields; PyBLE does not require an account or test credentials.
+
+## Beta App Description
+
+```text
+PyBLE is a free, open-source, tablet-first MicroPython IDE. It connects an iPad to a compatible board running the PyBLE agent over Bluetooth Low Energy, so you can edit, save, run, and stop MicroPython programs, view live console output, manage board files, and build programs with offline Blocks—without Wi-Fi onboarding or an account.
+
+Build 5 starts the PyBLE 0.2.0 beta. The GitHub importer now opens with the editable official PyBLE examples repository, offers an easy public-branch chooser while retaining advanced tag or commit entry, and guides protected root targets into a child folder. Files now supports reviewed deletion of multiple visible regular files and keeps its actions on one responsive toolbar row. GitHub import remains the app's only Internet-dependent workflow; imported code is never opened or run automatically.
+```
+
+## What to Test
+
+```text
+Build 5 adds five focus areas to TestFlight build 4:
+
+1. Open About and confirm version 0.2.0 (5). Connect to a board running qualified PyBLE firmware v0.6.0 and confirm the Board ID and agent version remain correct through Run, Stop, disconnect, and reconnect.
+
+2. In Files, open “Import examples from GitHub.” Confirm Public repository URL starts with https://github.com/PyBLE-dev/examples and remains editable. Confirm the branch-only chooser loads, marks the default branch, and lets you search or select another available branch. Browse main and confirm a full pinned commit SHA appears. Advanced mode must still allow a branch, tag, or commit.
+
+3. At the board root, browse to examples/capabilities/buses/i2c_scan and select pyble_i2c_scan.py. Review must stop before writing and guide you to a child folder such as /examples. Close Import, create and enter that folder, reopen Import, repeat the selection, and confirm the exact child-folder destination before importing. The imported file must not open or run automatically.
+
+4. In one disposable child folder, prepare two or more regular files. Enter selection with Select files or a long press, toggle individual files, and try Select all shown. Folders and board-protected entries must not be selectable. Choose Delete selected and confirm the dialog lists the exact folder and filenames. Cancel once and verify nothing is removed; repeat, confirm deletion, and verify the Files list and deleted count are accurate.
+
+5. Rotate between portrait and landscape. In a compact Files pane, Select files and GitHub import should remain directly visible on one row while Refresh, New file, New folder, and Upload appear under More file actions. A roomy pane should show all six actions on one row. Please also test 2× text size and, if available, keyboard navigation.
+
+With a selection or delete confirmation open, disconnect and reconnect once. Stale selection and the old board listing must disappear without deleting anything.
+
+Please recheck scanning, Save, Run, Stop, console output, ordinary single-file operations, and offline Blocks for regressions. Report the iPad model, iPadOS version, exact firmware profile, Board ID, agent version, pinned GitHub commit when relevant, steps taken, and expected versus actual behavior.
+```
+
+## Tester setup
+
+1. Back up the board before provisioning. Installing PyBLE firmware erases its
+   existing flash workspace.
+2. Install qualified firmware v0.6.0 from
+   [pyble.dev/flash](https://pyble.dev/flash), choosing only the exact profile
+   that matches the board and memory topology:
+   - `esp32-4mb`
+   - `esp32-s3-n16r8`
+   - `waveshare-esp32-s3-lcd-147b`
+   - `esp32-c3-4mb`
+   - `rpi-pico2-w`
+3. Provision an ESP profile from a supported desktop Chromium browser. For
+   Pico 2 W, use the verified UF2 download and copy it in BOOTSEL mode. iPadOS
+   cannot perform either wired provisioning workflow.
+4. Power the board, keep it nearby, and allow Bluetooth access when PyBLE asks.
+   Stock MicroPython without a conforming PyBLE agent will not appear as a
+   compatible PBLE/1 board.
+5. Internet access is needed only for the optional GitHub-import scenarios. A
+   GitHub account or token is neither needed nor accepted.
+6. Use only disposable test files for deletion scenarios. Multi-file deletion
+   is permanent and is not a transaction or a reversible trash operation.
+
+## Focused test matrix
+
+| Area | Exercise | Expected result |
+| --- | --- | --- |
+| Build identity | Open About before connecting and after reconnecting | The app consistently reports `0.2.0 (5)`; firmware continues to report agent `0.6.0` independently. |
+| Official examples | Open GitHub import from Files | The repository starts as editable `https://github.com/PyBLE-dev/examples`; opening ordinary Files does not make a GitHub request. |
+| Branch discovery | Load, search, refresh, and select public branches; then try Advanced | Branch mode shows branches only, marks the reported default, and never presents a partial catalog as complete. Advanced still accepts an explicit branch, tag, or commit. |
+| Immutable browse | Browse a selected branch and change the repository or ref | A full pinned commit SHA is visible. Changing repository or ref clears the earlier navigation and selection before a new snapshot is browsed. |
+| Root guidance | At the board root, select `pyble_i2c_scan.py`; repeat inside `/examples` | Review is blocked at the protected top-level destination with path-specific child-folder guidance. The same basename is accepted inside an ordinary child folder. |
+| GitHub import | Review and import the I2C scan example into `/examples` | Review shows the exact source and board destination. Existing files require separate overwrite consent. Imported code is not opened or run automatically. |
+| File selection | Select individual files, long-press, Select all shown, Cancel, Escape/Back, and reconnect | Only eligible direct regular files in the current folder are selected. Selection clears on cancellation, navigation, folder/session replacement, or disconnect. |
+| Multi-delete | Cancel one exact confirmation, then confirm deletion of disposable files | Cancel removes nothing. Confirmed deletion is sequential and fail-fast; the result and refreshed listing report what actually happened without claiming rollback. |
+| Protected entries | Inspect folders, board-control files, and transfer scratch entries | Folders use their separate one-at-a-time flow. Protected or scratch paths are visibly locked and cannot enter bulk selection. |
+| Files toolbar | Exercise narrow/roomy panes, portrait/landscape, and 2× text | Actions remain on one row. Select and GitHub import stay direct in compact mode; the other four actions move into one labelled overflow menu. |
+| Core regression | Scan, connect, Save, Run, Stop, view console output, manage one file, and use offline Blocks | BLE-first workflows remain responsive; no account or network connection is required outside user-started GitHub import. |
+
+## Expected boundaries and known limitations
+
+- Public GitHub requests are unauthenticated and rate-limited. If GitHub reports
+  a limit, follow the app's retry/reset guidance instead of repeatedly retrying.
+- Branch mode lists branches only. Tags and commit SHAs remain available through
+  Advanced. Discovery is deliberately bounded and fails closed instead of
+  presenting an incomplete list as all available branches.
+- GitHub import accepts selected ordinary lowercase `.py` files from one shown
+  remote folder and writes them into the current connected board folder. It
+  does not recreate remote directories, keep a durable local project or
+  provenance record, open imported code, or run it.
+- Importing at the board root is not entirely forbidden. Protected top-level
+  lowercase `pyble*`/`pble*`, exact `boot.py`/`_boot.py`, and `.pbltmp` paths
+  are refused. An ordinary `pyble_*` basename remains eligible inside a normal
+  child folder such as `/examples`.
+- Multi-delete applies only to eligible direct regular files visibly shown in
+  one current folder. It excludes folders, descendants, board-control paths,
+  transfer scratch paths, and omitted or truncated entries.
+- Deletion is permanent, sequential, fail-fast, and non-atomic. If a later
+  deletion or the connection fails, earlier successful deletions may remain;
+  the result identifies succeeded, current/failed, and unattempted files.
+- Editing, BLE, Files, Blocks, and Run remain offline and account-free. Public
+  GitHub requests begin only after the tester opens the importer.
+- App `0.2.0 (5)` does not change PBLE/1 or the independently qualified firmware
+  `0.6.0` baseline. It is a beta candidate, not a production `1.0.0` release.
+- The uploaded `0.2.0 (5)` artifact supports iOS/iPadOS `13.0` or later. The
+  source-level `15.0` floor applies only to later builds produced after this
+  retained artifact; no build 6 is prepared or uploaded by that source change.
+
+## Feedback checklist
+
+For actionable TestFlight feedback, include:
+
+- iPad model and exact iPadOS version;
+- PyBLE app version and build from About;
+- exact firmware profile used;
+- Board ID and PyBLE agent version shown by the app;
+- current board folder and selected filenames for Files issues;
+- repository URL, chosen ref, and pinned commit SHA for GitHub-import issues;
+- whether GitHub displayed a request-limit or retry time;
+- whether the issue followed first connect, reconnect, or a board switch;
+- numbered reproduction steps and expected versus actual behavior;
+- whether portrait/landscape, 2× text, VoiceOver, or an external keyboard was
+  involved; and
+- a screenshot, screen recording, or TestFlight crash report when it contains
+  no private code, repository credentials, or other secrets.
+
+## App Store Connect handoff
+
+- Paste **Beta App Description** under TestFlight **Additional → Test
+  Information** for the English localization.
+- Paste **What to Test** into the English build localization for `0.2.0 (5)`.
+- Set the maintained feedback email separately; Apple requires it for external
+  testing.
+- Complete the separate **Beta App Review Information** with the maintained
+  reviewer's first name, last name, email address, and phone number. Mark a
+  demo account as not required because PyBLE has no sign-in. Put any physical
+  board access or setup guidance needed by the reviewer in the review-only
+  notes.
+- Confirm the live field counters before saving. Apple's public TestFlight
+  documentation does not publish maximum lengths for these two fields, so this
+  document does not assert an unofficial limit.
+- Put private review-only directions in TestFlight App Review Information,
+  never in tester-visible copy.
+
+Apple references:
+
+- [Provide test information](https://developer.apple.com/help/app-store-connect/test-a-beta-version/provide-test-information/)
+- [Include notes for testers](https://developer.apple.com/documentation/xcode/including-notes-for-testers-with-a-beta-release-of-your-app)
+- [Beta App Localization attributes](https://developer.apple.com/documentation/appstoreconnectapi/betaapplocalization/attributes-data.dictionary)
+- [Beta Build Localizations](https://developer.apple.com/documentation/appstoreconnectapi/beta-build-localizations)
+- [Beta App Review Detail](https://developer.apple.com/documentation/appstoreconnectapi/beta-app-review-detail)
+
+Project references:
+
+- [Changelog](../../../CHANGELOG.md)
+- [Current app capabilities](../../../app/README.md)
+- [Detailed app requirements](../../specifications/App/specs.md)
+- [GitHub import trust boundary](../../decisions/0040-sha-pinned-connected-github-import.md)
+- [Official examples and branch discovery](../../decisions/0042-prefill-official-examples-and-discover-branches.md)
+- [Visible-file multi-delete](../../decisions/0043-session-bound-visible-file-multi-delete.md)
+- [App 0.2.0 beta identity](../../decisions/0044-start-app-v020-beta-train-at-build-5.md)