hardware: retire dashboard uart and assign oled pins

docs/ARCHITECTURE.md

@@ -193,3 +193,20 @@ Recovery target:
 
 - A setup/status button on the Cargo ESP enclosure can show AP credentials on the OLED.
 - A long hold can restore factory AP credentials or enter recovery mode.
+
+
+## Current communications and GPIO decision
+
+Active dashboard communication is WiFi/HTTP using `/api/v1`.
+
+The old Pico/dashboard UART path is retired from active hardware use. USB Serial remains available for development, debug, and manual configuration from a computer.
+
+Current Cargo ESP32 GPIO plan:
+
+- GPIO 16: Relay 1 trigger output
+- GPIO 17: Relay 2 trigger output
+- GPIO 4: DS18B20 OneWire temperature bus
+- GPIO 34: Ignition sense input
+- GPIO 21: SSD1306 OLED I2C SDA
+- GPIO 22: SSD1306 OLED I2C SCL
+- GPIO 25: OLED setup/status button

docs/CHATGPT_HANDOFF.md

@@ -129,3 +129,20 @@ Update this document when any of these change:
 - Hardware assumptions, wiring, power, relay, CAN, or dashboard target.
 - Validation commands, dependencies, or current test status.
 - Important decisions that a future assistant should not rediscover from scratch.
+
+
+## Current communications and GPIO decision
+
+Active dashboard communication is WiFi/HTTP using `/api/v1`.
+
+The old Pico/dashboard UART path is retired from active hardware use. USB Serial remains available for development, debug, and manual configuration from a computer.
+
+Current Cargo ESP32 GPIO plan:
+
+- GPIO 16: Relay 1 trigger output
+- GPIO 17: Relay 2 trigger output
+- GPIO 4: DS18B20 OneWire temperature bus
+- GPIO 34: Ignition sense input
+- GPIO 21: SSD1306 OLED I2C SDA
+- GPIO 22: SSD1306 OLED I2C SCL
+- GPIO 25: OLED setup/status button

docs/HARDWARE.md

@@ -141,3 +141,20 @@ Purpose:
   - active alarms
 
 Firmware support is optional and disabled by default with OLED_ENABLED set to 0. Enable only after the OLED libraries are installed and the display is wired.
+
+
+## Current communications and GPIO decision
+
+Active dashboard communication is WiFi/HTTP using `/api/v1`.
+
+The old Pico/dashboard UART path is retired from active hardware use. USB Serial remains available for development, debug, and manual configuration from a computer.
+
+Current Cargo ESP32 GPIO plan:
+
+- GPIO 16: Relay 1 trigger output
+- GPIO 17: Relay 2 trigger output
+- GPIO 4: DS18B20 OneWire temperature bus
+- GPIO 34: Ignition sense input
+- GPIO 21: SSD1306 OLED I2C SDA
+- GPIO 22: SSD1306 OLED I2C SCL
+- GPIO 25: OLED setup/status button

docs/UART_PROTOCOL.md

@@ -274,3 +274,20 @@ Alternative:
 `status_response.config.temperature_sensors[]` and `status_response.temps[]` include `weather: false`.
 
 `config_temp` may include `weather: true` to mark one configured sensor as the outside/weather sensor. Clients should treat this as optional and default missing values to `false`.
+
+
+## Current communications and GPIO decision
+
+Active dashboard communication is WiFi/HTTP using `/api/v1`.
+
+The old Pico/dashboard UART path is retired from active hardware use. USB Serial remains available for development, debug, and manual configuration from a computer.
+
+Current Cargo ESP32 GPIO plan:
+
+- GPIO 16: Relay 1 trigger output
+- GPIO 17: Relay 2 trigger output
+- GPIO 4: DS18B20 OneWire temperature bus
+- GPIO 34: Ignition sense input
+- GPIO 21: SSD1306 OLED I2C SDA
+- GPIO 22: SSD1306 OLED I2C SCL
+- GPIO 25: OLED setup/status button

docs/dashboard-esp32s3.md

@@ -154,3 +154,20 @@ Later:
 ## Out of Scope
 
 No Pico dashboard is planned. Existing Pico/UART material is legacy unless explicitly revived for diagnostics or alternate hardware.
+
+
+## Current communications and GPIO decision
+
+Active dashboard communication is WiFi/HTTP using `/api/v1`.
+
+The old Pico/dashboard UART path is retired from active hardware use. USB Serial remains available for development, debug, and manual configuration from a computer.
+
+Current Cargo ESP32 GPIO plan:
+
+- GPIO 16: Relay 1 trigger output
+- GPIO 17: Relay 2 trigger output
+- GPIO 4: DS18B20 OneWire temperature bus
+- GPIO 34: Ignition sense input
+- GPIO 21: SSD1306 OLED I2C SDA
+- GPIO 22: SSD1306 OLED I2C SCL
+- GPIO 25: OLED setup/status button

docs/project-state.md

@@ -185,3 +185,20 @@ Dashboard Client:
 There is no planned Pico dashboard path. Existing Pico/UART files are legacy artifacts unless explicitly revived later.
 
 UART JSON remains optional for diagnostics or alternate clients. New dashboard work should target the Waveshare ESP32-S3 display and the HTTP API.
+
+
+## Current communications and GPIO decision
+
+Active dashboard communication is WiFi/HTTP using `/api/v1`.
+
+The old Pico/dashboard UART path is retired from active hardware use. USB Serial remains available for development, debug, and manual configuration from a computer.
+
+Current Cargo ESP32 GPIO plan:
+
+- GPIO 16: Relay 1 trigger output
+- GPIO 17: Relay 2 trigger output
+- GPIO 4: DS18B20 OneWire temperature bus
+- GPIO 34: Ignition sense input
+- GPIO 21: SSD1306 OLED I2C SDA
+- GPIO 22: SSD1306 OLED I2C SCL
+- GPIO 25: OLED setup/status button

docs/roadmap.md

@@ -128,3 +128,20 @@ Future OLED goals:
 - Long press shows AP credentials.
 - Extended hold enters recovery/reset mode.
 - Add first-boot setup screen once AP password generation is finalized.
+
+
+## Current communications and GPIO decision
+
+Active dashboard communication is WiFi/HTTP using `/api/v1`.
+
+The old Pico/dashboard UART path is retired from active hardware use. USB Serial remains available for development, debug, and manual configuration from a computer.
+
+Current Cargo ESP32 GPIO plan:
+
+- GPIO 16: Relay 1 trigger output
+- GPIO 17: Relay 2 trigger output
+- GPIO 4: DS18B20 OneWire temperature bus
+- GPIO 34: Ignition sense input
+- GPIO 21: SSD1306 OLED I2C SDA
+- GPIO 22: SSD1306 OLED I2C SCL
+- GPIO 25: OLED setup/status button