docs: README + roadmap reflect v6.0.0 release and post-merge state

README:
- Branch table now shows main = v6.0.0 (post-merge state) with v5
  archived on legacy/v5-arduino. Includes a one-liner for users
  pulling onto an old local main.
- Quickstart split into "easiest path" (flash prebuilt binary from the
  v6.0.0 release page) and "build from source" — the previous
  copy still described the PR #1 skeleton ("waiting for Wi-Fi setup
  in PR #2") which is wrong now that 6.0 is live.
- IDF version bumped from v5.3 LTS to v5.5.2 to match what was
  actually used to build 6.0.0.
- Reference wiring + first-boot AP setup added so a fresh user can
  go from clone to running without bouncing through HARDWARE.md.
- "v5 (Arduino) docs" disclaimer rewritten — v5 is frozen, not
  "until v6 takes over". Points at legacy/v5-arduino branch.

V6-ROADMAP.md:
- Top banner: v6.0.0 RELEASED, links to release page.
- New "v6.x roadmap (post-6.0.0)" section at the bottom captures
  encrypted ESP-NOW, signed OTA, persistent sessions, auto-topology
  learning, S3 dual-core pinning, sim-driver replay, and the few
  smaller follow-ups documented in the v6.0 release notes.

Author: Ravi Singh

README.md

@@ -24,34 +24,60 @@
 > [docs/HARDWARE.md](docs/HARDWARE.md) for the full board recommendation
 > table and known issues.
 >
-> | Branch | Purpose |
+> | Branch / tag | Purpose |
 > |---|---|
-> | `main` | v5.1.1 Arduino release — stable |
-> | `v6-idf-rewrite` | v6 development branch (current) |
-> | `legacy/v5-arduino` | frozen archive of the v5.x Arduino line |
-> | tag `v6.0.0` | v6 release |
+> | `main` | v6.0.0 — current canonical firmware (this branch) |
+> | `v6-idf-rewrite` | active dev branch for v6.x work (encrypted ESP-NOW, S3 dual-core, auto-topology) |
+> | `legacy/v5-arduino` | frozen archive of the v5.x Arduino line — reference only |
+> | tag `v6.0.0` | shipped release with prebuilt C3 binaries on the release page |
 > | tag `v5.1.1` | last Arduino-era release |
 
-## v6 quickstart (ESP-IDF, requires `v5.3` LTS)
+If you cloned this repo before v6.0.0 landed and your local `main` still
+reflects the old Arduino tree, run `git fetch && git reset --hard origin/main`
+once after the merge to come up to speed. The Arduino code is preserved on
+`legacy/v5-arduino` and under `legacy/AmbiSense/` if you want to keep
+running v5.
+
+## v6 quickstart (ESP-IDF v5.5.2)
+
+**Easiest path** — flash the pre-built C3 binary from the
+[v6.0.0 release page](https://github.com/Techposts/AmbiSense/releases/tag/v6.0.0):
+
+```sh
+pip install esptool
+python -m esptool --chip esp32c3 -p /dev/ttyUSB0 -b 460800 \
+    --before default_reset --after hard_reset write_flash \
+    --flash_mode dio --flash_size 4MB --flash_freq 80m \
+    0x0     bootloader-c3-v6.0.0.bin \
+    0x8000  partition-table-c3-v6.0.0.bin \
+    0x10000 ambisense-c3-v6.0.0.bin
+```
+
+**Build from source** — you need ESP-IDF v5.5.2 installed (`~/esp/esp-idf-v5.5.2/`):
 
 ```sh
-# One-time
 git clone https://github.com/Techposts/AmbiSense.git
 cd AmbiSense/firmware
-. $IDF_PATH/export.sh
+. ~/esp/esp-idf-v5.5.2/export.sh
 
-# Build & flash for your board
-idf.py set-target esp32c3       # or: esp32, esp32s3, esp32c6
+idf.py set-target esp32c3        # or: esp32, esp32s3, esp32c6
 idf.py build flash monitor
 ```
 
-The skeleton boots, initialises NVS, resolves the board profile, and drives
-the onboard status LED into AP-mode blink (waiting-for-Wi-Fi). Wi-Fi setup
-lands in PR #2.
+After flash the device starts a Wi-Fi AP `AmbiSense-XXXX`. Connect from
+your phone — the captive portal pops at `http://192.168.4.1/`. Enter
+home Wi-Fi creds; the device joins and is reachable as
+`http://ambisense-XXXX.local/`.
 
-VSCode users: install Espressif's ESP-IDF extension to get IntelliSense for
-IDF headers — without it, clangd will report `'esp_err.h' file not found`
-and similar; the code still builds correctly via `idf.py`.
+**Recommended hardware**: ESP32-S3 DevKitC-1 or S3-Zero (dual-core,
+native USB). **Supported**: ESP32-C3 SuperMini for single-strip installs.
+See [docs/HARDWARE.md](docs/HARDWARE.md) for the full table and known
+issues.
+
+VSCode users: install Espressif's ESP-IDF extension to get IntelliSense
+for IDF headers — without it, clangd will report
+`'esp_err.h' file not found` and similar; the code still builds
+correctly via `idf.py`.
 
 ## v6 documentation
 
@@ -72,10 +98,17 @@ Assets/, STL Files/      — design assets, enclosures (unchanged)
 
 ---
 
-## v5 (Arduino) docs
+## v5 (Arduino) docs — reference only
+
+The text below is the original v5.1.1 Arduino README, kept here for
+people running v5 hardware. v5 is **frozen** — no further bug fixes or
+features will be backported. Running v5? Track the
+[`legacy/v5-arduino`](https://github.com/Techposts/AmbiSense/tree/legacy/v5-arduino)
+branch instead of `main`, and the source is at `legacy/AmbiSense/`
+in this tree.
 
-The legacy v5 documentation below applies to `main` until v6 takes over.
-For new development, target the `v6-idf-rewrite` branch.
+For new installs we strongly recommend going to v6.0.0 — see the
+quickstart above.
 
 ---
 

docs/V6-ROADMAP.md

@@ -1,5 +1,13 @@
 # AmbiSense v6 — PR-by-PR roadmap
 
+> **Status (2026-05-05): v6.0.0 RELEASED.** All five planned PRs landed
+> plus a post-PR-5 polish pass (Kalman motion, asymmetric pairing,
+> debounced UI saves, mobile CSS, board MCU-mismatch boot guard). See
+> the [v6.0.0 release page](https://github.com/Techposts/AmbiSense/releases/tag/v6.0.0)
+> for the user-facing summary.
+>
+> v6.x roadmap (post-6.0.0 work) is at the bottom of this file.
+
 Five PRs. Each is independently flashable and validated on real C3
 hardware before the next starts. Releases tagged `v6.0.0-alpha.N` from
 PR #2 onwards; final `v6.0.0` ships with PR #5.
@@ -185,3 +193,43 @@ Move v5 README content fully behind a "v5 legacy" link.
 | `v6.0.0`           | PR #5 merge    | feature complete      |
 
 CI auto-attaches per-board firmware artifacts to tag pushes.
+
+---
+
+## v6.x roadmap (post-6.0.0)
+
+These are tracked but did NOT ship in 6.0.0. See the v6.0.0 release
+notes for the user-facing version of the same list.
+
+### Hardening
+- **Encrypted ESP-NOW** — derive a PMK from a user mesh password,
+  enable per-peer LMK, store in NVS namespace `mesh.pmk`. Targets are
+  defined in `mesh.h` (the `mesh_event_cb_t` plumbing is already in
+  place); the actual `esp_now_set_pmk` call and UI password field are
+  v6.1 work.
+- **Signed OTA** — `esp_secure_boot` + signed `.bin` with rollback. The
+  bootloader rollback path is already armed; signing keys + UI
+  workflow are pending.
+- **Persistent sessions** — auth tokens currently live in RAM, lost on
+  reboot. Move to NVS with explicit revocation list.
+
+### UX / scale
+- **Auto-topology learning** — "walk through your stairs" mode where
+  the device records distance histograms over a 60 s window and
+  proposes segment boundaries automatically.
+- **Dual-core pinning (S3 / classic)** — `xTaskCreatePinnedToCore` for
+  Wi-Fi/HTTP on core 0 and radar+LED+motion on core 1. Lifts the
+  HTTP-saturates-render limitation we currently work around with the
+  client-side debounce.
+- **LED count beyond 300** — verified; lift the documented soft cap to
+  the theoretical 1500-pixel limit per device.
+- **Realistic `sim` radar** — replay captured LD2410 frame logs
+  instead of emitting a slow sine.
+
+### Misc
+- **OTA preserves paired peers** — currently a factory reset wipes the
+  topology blob too; needs a "keep mesh config" toggle.
+- **`esp32s3-zero` profile validation** — pinmap is correct in the
+  profile; needs a hardware bring-up + photo for HARDWARE.md once an
+  S3-Zero arrives on bench.
+- **Factory reset preserves Wi-Fi** option.