20260928-0836-key-wireless-service-and-mcu Add a wireless configuration and update path to Key and re-select its MCU

• status: completed
• priority: P1
• owner: claude/session-20260922-0815
• createdAt: 2026-09-28 08:36

Description

On 2026-09-28 the owner, while comparing ESP32-H2 and ESP32-C6 for Key, stated that Key needs wireless for configuration and firmware update ("需要无线去配置和升级"). The Key spec R0.2 says the opposite in three places: the brief and §1 position Key as independent of wireless, §6 adds no wireless pairing requirement, and §7 puts Key on the non-wireless compliance row. The recommended MCU (STM32G0B1CE) has no radio.

Deliverable after approval: Key spec, design appendix, guide, brief and index updated for a service-only wireless path; a Key evaluation page with the MCU options and the static-current budget; line spec, compliance matrix, product plan and open questions aligned.

Acceptance criteria:

1. Control stays wired: no load command can originate from the wireless interface, and the spec says so as a requirement with a test.
2. The wireless path has authenticated pairing, a time-limited service window opened by a physical action, and signed configuration and firmware.
3. The selected MCU option states its static current against KEY-05 and its CAN capability against X01, with datasheet sources.
4. Requirement IDs that exist today are unchanged; new ones are added, not renumbered.
5. bun run docs:lint && bun run docs:build && git diff --check passes.

ActiveForm

Adding the wireless service path to Key and re-selecting its MCU

Dependencies

• blocked by: owner decision on the option (plan 20260928-0836)
• blocks: (none)

Notes

• Full tier: about ten files across bizplan/product/switch/ and bizplan/governance/.

• Plan: 20260928-0836-key-wireless-service-and-mcu.

• complete: Key spec R0.3, design R0.3, guide R0.4, evaluation and governance pages updated; lint 229 pages 0 findings, build and git diff --check pass.