nick/overland-controller
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: prepare api contract for lilygo transition

Browse Source
This commit is contained in:
nick
2026-06-09 15:05:29 -06:00
parent 90c4490a3d
commit f2966518da
6 changed files with 131 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CHATGPT_HANDOFF.md
+12
View File
@@ -185,3 +185,15 @@ Before making dashboard firmware changes, inspect the current API tests and this
Before suggesting a release/tag prior to Cargo ESP hardware migration, check `docs/pre-lilygo-baseline-checklist.md`.
Do not suggest migrating active Cargo ESP firmware to LilyGO hardware until the user explicitly decides to buy/use that board.
## LilyGO Transition Guardrail
The user has ordered a LILYGO T-Relay-S3 6-way board, but it will not arrive for a couple weeks.
Until the user confirms hardware is available and bench tested:
- Keep the existing 2-channel relay board as the active test target.
- Do not remove 2-channel support.
- Do not assume LilyGO firmware is active.
- Prepare API/config/docs for output-count-agnostic operation.
- Treat LilyGO migration as a future hardware-profile change.