Ship rewire: retire self-contained core, consume valar-core v0.2.0

Make the valar-core rewire the canonical Ropener firmware:
- delete firmware/common/ropener-core.yaml and the old per-board wrappers
- Ropener-VAL3000.yml / Ropener-VAL3100.yml now pull valar-core + scheduling
  from Valar-Systems/valar-motion pinned to tag v0.2.0, + ropener-product.yaml
- bump fw_version 2.6.4 -> 2.7.0
- replace the verify workflow with build-release.yml: builds every board and,
  on a tag, attaches factory.bin + ota.bin + ota.bin.md5 with the stable
  Ropener-VAL3000 / Ropener-VAL3100 asset names (the md5 the OTA button needs)

Verified on real hardware against the identical core commit (v0.2.0 = bc869f7):
0 entity regressions, OTA button URL + asset names unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XpCz2RvuxV5uV8bFwCEpkL

Author: claude

.github/workflows/build-release.yml

@@ -0,0 +1,62 @@
+# Build the Ropener firmware for every board and, on a tag, attach the factory
+# + OTA binaries (and the .ota.bin.md5 the on-device "Update Firmware" button
+# needs) to the GitHub release. Field units self-update by asset name, so keep
+# the Ropener-VAL3000 / Ropener-VAL3100 names stable.
+name: Build firmware
+
+on:
+  push:
+    branches: [main, 'rewire/valar-core']   # rewire/* verifies the branch pre-merge; remove after merge
+    tags: ['v*']
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - config: firmware/VAL3000/Ropener-VAL3000.yml
+            asset: Ropener-VAL3000
+          - config: firmware/VAL3100/Ropener-VAL3100.yml
+            asset: Ropener-VAL3100
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+      - name: Install ESPHome
+        run: pip install esphome
+
+      # On a tag build, stamp the release version (strip a leading "v") so the
+      # on-device "Firmware Version" matches the release the unit is running.
+      - name: Compile ${{ matrix.asset }}
+        run: |
+          if [ "${{ github.ref_type }}" = "tag" ]; then
+            V="${{ github.ref_name }}"; V="${V#v}"
+            esphome -s fw_version "$V" compile "${{ matrix.config }}"
+          else
+            esphome compile "${{ matrix.config }}"
+          fi
+
+      - name: Collect binaries + md5
+        run: |
+          mkdir -p dist
+          F=$(find . -path "*/.pioenvs/*/firmware.factory.bin" | head -1)
+          O=$(find . -path "*/.pioenvs/*/firmware.ota.bin" | head -1)
+          cp "$F" "dist/${{ matrix.asset }}.factory.bin"
+          cp "$O" "dist/${{ matrix.asset }}.ota.bin"
+          md5sum "dist/${{ matrix.asset }}.ota.bin" | cut -d' ' -f1 > "dist/${{ matrix.asset }}.ota.bin.md5"
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: ${{ matrix.asset }}
+          path: dist/*
+
+      - name: Attach to release
+        if: startsWith(github.ref, 'refs/tags/')
+        uses: softprops/action-gh-release@v2
+        with:
+          files: dist/*

.github/workflows/verify-rewire.yml

@@ -16,3 +16,4 @@ docs/dist/
 # Python bytecode cache
 __pycache__/
 *.pyc
+secrets.yaml

.gitignore

@@ -1,9 +1,8 @@
 # =============================================================================
-# Ropener — VAL3000 (ESP32-C3)  [REWIRED: consumes valar-core remotely]
+# Ropener — VAL3000 (ESP32-C3)
 # =============================================================================
-# Board wrapper: sets this board's chip, GPIO map, and OTA identity, then pulls
-# in the shared valar-core + scheduling from the valar-motion repo as remote
-# packages and layers the Ropener product on top. This board has no status LED.
+# Board wrapper: pulls valar-core + scheduling from Valar-Systems/valar-motion
+# as remote packages and layers the Ropener product on top. No status LED.
 # =============================================================================
 substitutions:
   device_name: "ropener"
@@ -13,8 +12,7 @@ substitutions:
   log_uart: "USB_SERIAL_JTAG"
   ota_repo: "Valar-Systems/Ropener"
   ota_asset: "Ropener-VAL3000"
-  fw_version: "2.6.4"
-  # GPIO map (ESP32-C3)
+  fw_version: "2.7.0"
   pin_uart_tx: "6"
   pin_uart_rx: "5"
   pin_enn: "8"
@@ -32,12 +30,12 @@ esphome:
 packages:
   valar_core:
     url: https://github.com/Valar-Systems/valar-motion
-    ref: bc869f79de63a1b2fa39234f81bdd500bef94669
+    ref: v0.2.0
     files: [common/valar-core.yaml]
     refresh: 1d
   scheduling:
     url: https://github.com/Valar-Systems/valar-motion
-    ref: bc869f79de63a1b2fa39234f81bdd500bef94669
+    ref: v0.2.0
     files: [common/scheduling.yaml]
     refresh: 1d
   product: !include ../common/ropener-product.yaml

firmware/VAL3000/Ropener-VAL3000-2.6.4.yml

@@ -1,8 +1,8 @@
 # =============================================================================
-# Ropener — VAL3100 (ESP32-C6)  [REWIRED: consumes valar-core remotely]
+# Ropener — VAL3100 (ESP32-C6)
 # =============================================================================
 # Board wrapper: sets this board's chip, GPIO map, and OTA identity, then pulls
-# in the shared valar-core + scheduling from the valar-motion repo as remote
+# in the shared valar-core + scheduling from Valar-Systems/valar-motion as remote
 # packages and layers the Ropener product on top. No board firmware is copied.
 # =============================================================================
 substitutions:
@@ -11,12 +11,9 @@ substitutions:
   board_id: "VAL3100 (ESP32-C6)"
   esp_board: "esp32-c6-devkitc-1"
   log_uart: "USB_SERIAL_JTAG"
-  # OTA target: keep pointing at the Ropener repo's own releases so field units
-  # self-update from exactly where they always have (asset name unchanged).
-  ota_repo: "Valar-Systems/Ropener"
+  ota_repo: "Valar-Systems/Ropener"     # field units self-update from Ropener's own releases
   ota_asset: "Ropener-VAL3100"
-  fw_version: "2.6.4"
-  # GPIO map (ESP32-C6)
+  fw_version: "2.7.0"
   pin_uart_tx: "0"
   pin_uart_rx: "1"
   pin_enn: "5"
@@ -34,17 +31,16 @@ esphome:
 packages:
   valar_core:
     url: https://github.com/Valar-Systems/valar-motion
-    ref: bc869f79de63a1b2fa39234f81bdd500bef94669
+    ref: v0.2.0
     files: [common/valar-core.yaml]
     refresh: 1d
   scheduling:
     url: https://github.com/Valar-Systems/valar-motion
-    ref: bc869f79de63a1b2fa39234f81bdd500bef94669
+    ref: v0.2.0
     files: [common/scheduling.yaml]
     refresh: 1d
   product: !include ../common/ropener-product.yaml
 
-# Status LED (VAL3100 / ESP32-C6 onboard LED on GPIO23)
 light:
   - platform: status_led
     name: "Status LED"