TheUnboundDeveloper/AM-Reaper v3.4.5-beta-BQ16_PRO

Reaper v3.4.5-beta — BQ16_PRO

on GitHub

v3.4.5 — a factory Reaper router joins AiMesh as a node, mode changes stay in Reaper

Everything in v3.4.4 is included.

• AiMesh: a factory-fresh Reaper router could not be added as a node (field: a ZenWiFi BQ16 under a
  GT-BE98 main router with MLO on stopped at "Unable to add" near 24%; the same unit on stock firmware
  joined). Reaper ships the WPS setting off, and the rule that turns WPS on for a radio kept the AiMesh
  join inside that setting, so the box came up with WPS disabled on the band the join uses. On a box that
  has never been set up, while it joins a mesh, that band now gets WPS for the join only; the WPS setting
  itself is never changed, and the reboot that ends the join closes the window. Logged as
  aimesh: wlN: WPS on for the AiMesh join of this factory box. Host test test_aimesh_wps_enrollee.py.
• Operation mode: Access Point, Media Bridge and the return to Router stay in Reaper. They used to
  leave the shell for ASUS's setup wizard. A Reaper step page writes the same settings the wizard writes
  (checked against the wizard's own source), picks the Media Bridge parent from the Site Survey scan and
  restarts the router. The MLO page's "Get started" opens the Wireless console. Repeater and AiMesh Node
  still use the stock wizard. 85 new strings in all 25 languages. Host test test_mode_setup.py.
• QoS page: two colours only. Every chip on the engine cards is green (something the engine does) or
  amber (something it lacks or costs); Hardware QoS's "Upload only" and "No classes" are amber.
• Build gate: a release marker quoted a dictionary token, which the web install turns into a number,
  so it could never match; markers now pin token-free text.

Images & checksums (BQ16_PRO)

Two flashable images: + AI Advisor (default) and Standard (noMCP, all AI components compiled out entirely). Flash the *_nand_squashfs.pkgtb via Administration > Firmware Upgrade.

This is a beta release. Its filename carries _BETA and the router reports the same string on the dashboard and the About page, so you can always tell which channel a flashed image came from. Stable releases carry no marker.

Verify a download against the attached SHA256SUMS-BQ16_PRO-Reaper_v3.4.5.txt.

Corresponding source & reproducibility

The BQ16_PRO image for v3.4.5-beta is built from this repository at tag v3.4.5-beta-BQ16_PRO: the pinned Asuswrt-Merlin base (3006.102.8-beta2, a7ebfa133a) plus the complete patch series. The tag freezes the exact source that produced it.

• Patches: patches/
• Provenance record: provenance/manifest.json
• How to verify: docs/REPRODUCIBILITY.md and docs/SOURCE-AVAILABILITY.md

The auto-attached Source code (zip/tar.gz) asset below is this repository at tag v3.4.5-beta-BQ16_PRO (patches + docs).