@@ -0,0 +1,63 @@
+<!-- SPDX-License-Identifier: MIT -->
+
+# PyBLE platform source consolidation — 2026-09-11
+
+## Scope
+
+The maintainer requested local commits, recoverable worktree/branch cleanup,
+and a pushed pull request targeting `main`.
+
+The integration combines:
+
+- Primary platform work through `66f1916`: reviewed Lenovo tutorial captures,
+  firmware features and diagram, site-wide v0.6.1 guidance, and the App build-8
+  offline privacy policy and publication handoff.
+- Current `main` through `2ce0e8c`, including patched website dependencies.
+- Exact published firmware source `c8f549eeabe6d2b8c2766eab022517944bb09c8c`,
+  its measured baseline, specifications, host tooling and tests, and the
+  previously reviewed App connection-lifecycle fixes.
+
+After integration, the complete firmware and firmware-test trees, firmware
+specification directory and protocol match `c8f549e` exactly. The website tree
+initially matched the deployed primary source exactly. Subsequent pre-PR
+formatting changes are whitespace-only; the frozen protocol bytes are retained.
+
+The public protocol copy's relative `../../AGENTS.md` link lacked its target.
+`tools/web/public/AGENTS.md` now supplies the exact contributor-guideline bytes
+from `c8f549e`, SHA-256
+`2462fdb3823bdec527de4da8323fc44570ca95e68f453ac3c469e5c4494072db`.
+Both source snapshots are excluded from automatic formatting to preserve their
+provenance. Existing publication/link tests caught the missing target and pass
+with it present.
+
+## Local verification
+
+- Flutter analysis: no issues.
+- Flutter non-golden suite: 894 tests passed.
+- Complete website check: formatting, lint, type checking, zero-vulnerability
+  dependency audit, license checks, 342 tests in 23 files, compatibility check,
+  and both static and Sites builds passed.
+- Publication suite: 41 tests passed; all repository-local Markdown targets
+  exist.
+- Clean-room, SPDX, import-boundary, localization, patch-policy and PR-range
+  DCO checks passed. SPDX ran against a tracked-source export so ignored
+  qualification workspaces were not recursively scanned as product source.
+
+The exact firmware source already has its retained full host/build evidence,
+described in the [engineering chronology](firmware-v0.6.1-five-board-engineering-2026-09-06.md).
+This Git integration does not claim new board qualification. No hardware was
+operated, firmware rebuilt, store artifact uploaded or website redeployed.
+The [owner-confirmed publication record](firmware-v0.6.1-publication-2026-09-11.md)
+and its distinction from incomplete automated HIL remain unchanged.
+
+## Cleanup boundary
+
+Auxiliary worktree directories, including dirty edits and ignored backups, are
+archived intact outside the active repository. Git metadata, a verified bundle,
+original branch/HEAD mappings and restoration instructions accompany them.
+Private qualification experiments are preserved, not silently merged into the
+production branch. The primary generated MicroPython board inputs are untouched.
+
+The two remote documentation branch names may be removed after their complete
+history is reachable from the pushed integration branch. Opening this PR does
+not itself merge or bypass any checks on `main`.
@@ -8,3 +8,6 @@ coverage/
 dist/
 public/brand/
 package-lock.json
+# Byte-for-byte source snapshots; their provenance depends on unchanged bytes.
+public/reference/firmware-v0.6.1/protocol.md
+public/AGENTS.md
@@ -0,0 +1,96 @@
+# AGENTS.md — PyBLE contributor guidelines
+
+These rules apply to humans and automated contributors working in this
+repository.
+
+## Project identity
+
+**PyBLE** (“Python over BLE”) is a free, MIT-licensed, tablet-first
+MicroPython IDE. The Flutter app communicates over Bluetooth Low Energy with a
+compatible board running MicroPython and the portable PyBLE agent.
+
+- App: `app/`
+- Agent firmware: `firmware/`
+- Open wire protocol: PBLE/1, specified in
+  `docs/specifications/protocol.md`
+- Initial validated ports: `esp32`, `esp32-s3`, and `esp32-c3`
+
+Support is capability-defined, not tied to one chip family. A new port needs a
+maintained PBLE/1 agent, BLE GATT peripheral support, sufficient resources, and
+the project’s conformance and hardware-validation gates.
+
+## Open-source and clean-room boundary
+
+1. All PyBLE-authored source is MIT licensed.
+2. Author changes fresh. Do not paste proprietary or unknown-licensed source,
+   protocols, UUIDs, board profiles, examples, or product-specific pedagogy.
+3. Keep PyBLE identifiers independent: `PBLE/1`, `pble_*`, `pyble_*`, the
+   PyBLE UUID base, and the `PyBLE-` advertising prefix.
+4. Run `tools/ci/no_leak.sh` before committing. The gate is the canonical,
+   tested list of prohibited identifiers in shippable source.
+5. Third-party dependencies remain under their own licenses and must be
+   recorded in the relevant dependency and notice files.
+
+The pinned, gitignored compiler/tool trees at `firmware/.esp-idf`,
+`firmware/.arm-gnu`, and `firmware/.picotool` are third-party build inputs,
+not shippable source. Source gates prune those exact roots while continuing to
+scan similarly named authored directories.
+
+## Spec-driven and test-driven development
+
+1. `docs/specifications/` defines public behavior and architecture.
+2. Change the relevant specification before implementation when a contract
+   changes.
+3. Work red → green → refactor:
+   - add a failing test in a `[red]` commit;
+   - implement the minimum passing change in a `[green]` commit;
+   - clean up in a `[refactor]` commit while tests remain green.
+4. No behavior is complete without an automated test. Hardware behavior also
+   needs the documented HIL evidence.
+5. Sign off every commit for DCO compliance: `git commit -s`.
+
+Allowed commit prefixes are `[red]`, `[green]`, `[refactor]`, `[docs]`,
+`[build]`, and `[chore]`.
+
+## Repository layout
+
+Keep the repository root limited to governance files and these directories:
+
+```text
+.github/  app/  docs/  firmware/  protocol/  examples/  tests/  tools/
+```
+
+Root governance files are:
+
+```text
+README.md  LICENSE  CONTRIBUTING.md  CODE_OF_CONDUCT.md  SECURITY.md
+CHANGELOG.md  CITATION.cff  AGENTS.md  CLAUDE.md  .gitignore  .gitmodules
+```
+
+Put specifications and decisions under `docs/`, scripts under `tools/` or
+`firmware/scripts/`, and examples under `examples/`. Keep raw or unreviewed
+screenshots, signing material, builds, assistant state, and local notes out of
+Git. A deliberately reviewed, provenance-recorded image used by the public
+website may live below `tools/web/public/`; its raw capture must remain in an
+ignored workspace.
+
+## Naming
+
+- Product and wordmark: **PyBLE**
+- Domain: `pyble.dev`
+- Protocol: **PBLE/1**
+- Native modules: `pyble_agent`, `pyble_ble`, `pyble_runner`, `pyble_fs`,
+  and related `pyble_*` / `pble_*` files
+- Flutter packages: `lib/ble/`, `lib/pble/`, `lib/editor/`, `lib/console/`,
+  `lib/files/`, `lib/blocks/`, and `lib/localization/`
+
+## Hard boundaries
+
+- Do not edit upstream MicroPython or Blockly in place. Pin upstream as
+  submodules; isolate any unavoidable MicroPython patch under
+  `firmware/patches/` with a written reason.
+- Do not make USB serial or Wi-Fi the primary workflow. PyBLE is BLE-first.
+- Do not introduce paid or closed features.
+- Do not ship compiled `.mpy` examples; use readable `.py` files.
+- Do not commit credentials, signing assets, firmware binaries, IPA files, or
+  generated build directories.
@@ -64,14 +64,14 @@ export default function FlashPage() {
           {ownerConfirmed
             ? " Firmware v0.6.1 is available for all five board profiles following qualification confirmed by the project owner."
             : preview
-            ? ` LOCAL ENGINEERING PREVIEW v${preview.version} — UNQUALIFIED. This is not a public release.`
-            : publicBeta
-              ? " The current v0.4.2 installer is a hardware-tested firmware beta. Production Chrome erase/install and deliberately interrupted-flash recovery passed on both exact profiles. Complete release qualification is still pending; this is not a qualified release."
-              : qualifiedPublic
-                ? ` Qualified v${release.version} firmware is available for all ${exactProfileCountLabel(release.profiles.length)} exact release profiles.`
-                : candidate
-                  ? ` This protected, access-controlled v${release.version} release candidate is staged for hardware qualification. Hardware validation is pending on every included profile; the public install action stays unavailable until it passes.`
-                  : " No firmware release is selected for this build; installation remains unavailable."}
+              ? ` LOCAL ENGINEERING PREVIEW v${preview.version} — UNQUALIFIED. This is not a public release.`
+              : publicBeta
+                ? " The current v0.4.2 installer is a hardware-tested firmware beta. Production Chrome erase/install and deliberately interrupted-flash recovery passed on both exact profiles. Complete release qualification is still pending; this is not a qualified release."
+                : qualifiedPublic
+                  ? ` Qualified v${release.version} firmware is available for all ${exactProfileCountLabel(release.profiles.length)} exact release profiles.`
+                  : candidate
+                    ? ` This protected, access-controlled v${release.version} release candidate is staged for hardware qualification. Hardware validation is pending on every included profile; the public install action stays unavailable until it passes.`
+                    : " No firmware release is selected for this build; installation remains unavailable."}
         </p>
       </PageIntro>
 
 
@@ -160,8 +160,11 @@ function policyFailure(release: FirmwareReleaseDescriptor | null | undefined) {
       body: "No firmware release is selected for this build. Check the current public installer before provisioning.",
     };
   }
-  if (release.deployment !== "public" && release.deployment !== "candidate" &&
-      !isOwnerConfirmedFirmwareRelease(release)) {
+  if (
+    release.deployment !== "public" &&
+    release.deployment !== "candidate" &&
+    !isOwnerConfirmedFirmwareRelease(release)
+  ) {
     if (
       release.deployment !== "public-beta" ||
       !isExactPublicBetaFirmwareRelease(release)
@@ -491,10 +494,10 @@ function FlashStatusForRelease({
             {ownerConfirmed
               ? "Owner-qualified release"
               : candidate
-              ? "Protected release candidate"
-              : publicBeta
-                ? "Hardware-tested firmware beta"
-                : "Qualified release"}
+                ? "Protected release candidate"
+                : publicBeta
+                  ? "Hardware-tested firmware beta"
+                  : "Qualified release"}
           </h2>
         </div>
       </div>
@@ -504,14 +507,20 @@ function FlashStatusForRelease({
         className="flash-status__message"
       >
         {ownerConfirmed ? (
-          <>Firmware v0.6.1 qualification was confirmed by the project owner.
-            {" "}<a href="/firmware-v0.6.1-owner-confirmation.md">Publication record</a>.
-            {" "}Select and verify your exact board profile before installation.</>
-        ) : candidate
-          ? "Protected release candidate: hardware validation is pending."
-          : publicBeta
-            ? "Hardware-tested firmware beta: exact PyBLE v0.4.2 browser installation and interrupted-flash recovery passed on real esp32-4mb and esp32-s3-n16r8 hardware. Complete release qualification is still pending; this is not a qualified release."
-            : "Select and verify the exact module profile before installation."}
+          <>
+            Firmware v0.6.1 qualification was confirmed by the project owner.{" "}
+            <a href="/firmware-v0.6.1-owner-confirmation.md">
+              Publication record
+            </a>
+            . Select and verify your exact board profile before installation.
+          </>
+        ) : candidate ? (
+          "Protected release candidate: hardware validation is pending."
+        ) : publicBeta ? (
+          "Hardware-tested firmware beta: exact PyBLE v0.4.2 browser installation and interrupted-flash recovery passed on real esp32-4mb and esp32-s3-n16r8 hardware. Complete release qualification is still pending; this is not a qualified release."
+        ) : (
+          "Select and verify the exact module profile before installation."
+        )}
       </div>
 
       {heterogeneous ? (
 
@@ -74,7 +74,8 @@ export type HistoricalFirmwareProfileId =
   (typeof historicalFirmwareProfileTable)[number]["id"];
 export type PlannedFirmwareProfileId =
   (typeof plannedFirmwareProfileTable)[number]["id"];
-export type FirmwareDeployment = "public" | "candidate" | "public-beta" | "owner-confirmed";
+export type FirmwareDeployment =
+  "public" | "candidate" | "public-beta" | "owner-confirmed";
 export type FirmwareHilStatus = "pending" | "passed";
 export type FirmwareProvisioningKind =
   "esp-web-serial" | "verified-uf2-bootsel";