20260911-1916-air-key-hub-sleep-and-key-scaling Apply the open key count, no-sleep receiver and Air-only sleep decisions
- status: completed
- priority: P1
- owner: doc-review/session-20260911-0251
- createdAt: 2026-09-11 19:16
Description
章节标题:“Description”The user answered the three product questions left open by the documentation repair:
- The Key panel key count must not be fixed at 4/8. It should be open-ended and reach 32 keys or more.
- The Air receiver must not sleep — it is the central, bus-powered unit — and it should not be called Gateway but Hub.
- Only Air sleeps, and Air keeps itself reachable through intermittent communication rather than a maintained link.
Investigate the impact of each decision, prepare a reviewable proposal, and resolve the naming collision with the existing P03 YBO Hub before touching any controlled document.
Acceptance: each decision is reflected consistently across the Key and Air/receiver specifications, design appendices, supplier guides, X01/X02, the governing summaries and the open questions; requirement-to-test mapping stays bidirectional; no cross-reference resolves to a missing section or ID; bun run docs:build and git diff --check pass. No unverified engineering claim is added — scaling ceilings that the decisions expose are recorded as open items, not silently resolved.
ActiveForm
章节标题:“ActiveForm”Investigating the open key count, the non-sleeping receiver, its naming, and Air-only intermittent presence.
Dependencies
章节标题:“Dependencies”- blocked by: the Hub naming question — whether the Air radio folds into the existing P03 Hub or stays a separate device under a new name
- blocks: (none)
Notes
章节标题:“Notes”-
Full-tier task. The previous repair task 20260911-0251 is complete; this builds on its numbering and reference work.
-
A separate session is active in this repository and owns the ESP32-H2 evaluation; coordinate before editing Air Switch silicon documents.
-
complete: Classical CAN bus-wide, Air Hub rename and no-sleep, Air on ESP32-H2 with an AAA lithium pack, open Key count, and both platform comparison documents delivered.