Markdown audit — 1.17.1.5 USA Cascade
Audited on 2026-09-05 against firmware source 26303793, the resolved build
configuration, and the qualified 1.17.1.5 staging manifests. The scope was all
71 tracked Markdown files present at the start, including root documents,
docs, examples, tools, tests, variants, and vendored library documentation.
Generated/ignored build directories and external repositories were outside that scope.
Corrections
- Added role-specific feature switches, exact Companion/infrastructure MQTT and logging controls, board exceptions, SNMP, and the USB web console.
- Added an exact-name variant map; every one of its 1,325 covered entries resolves to a staged firmware file. The 36 excluded entries are identified rather than linked to substitute hardware.
- Corrected universal 254-neighbor claims, Full Companion MQTT filename/CLI assumptions, TLora Full WebConfig availability, and partition/NVS guidance.
- Documented the power-saving guards present at audit time; current instructions
now use the shared
get powersaving/set powersaving on|offcommand set. Corrected the RS232 baud range and SNMP environment list. - Linked OTAFIX 2.4.6 and its board/storage requirements from operator guides; aligned the two manual USA OTA quickstarts with 910.525 MHz.
- Marked old provider catalogs and dated hardware results as historical;
documented the legacy tag workflow that also matches
repeater-room-*. - Fixed the vendored MQTT documentation link and documentation-site links that incorrectly treated repository source files as generated site pages.
Verification and limits
All original Markdown files were scanned for relative links, section anchors, source-path references, version/default claims, and role/OTA terminology. Flagged operator instructions were checked against CommonCLI, its observer extension, Companion command handlers, board configuration, and release manifests. Brace-expanded source references and SDK-relative paths were retained as such. Historical measurements, changelogs, upstream findings, contribution/security policies, and licenses were not rewritten as new validation results.
The documentation site passed a strict MkDocs Material build. Relative repository links and section anchors were checked separately, including documents outside the MkDocs source directory. Console and current bootloader links were checked on their primary sites. This was not a crawl of every third-party URL or a new hardware/firmware qualification; no claim is made that every board was physically tested or every protocol statement independently re-proved.
Original file coverage
“Retained” means no correction was identified by this documentation audit; it does not certify all historical statements as current hardware behavior.