build: FTW holds no driver source

.changeset/ftw-holds-no-driver-source.md

@@ -0,0 +1,5 @@
+---
+"ftw": patch
+---
+
+Driver source is no longer committed here. `drivers/*.lua` is gitignored and fetched from the pinned device-drivers commit with `make drivers`.

.github/workflows/beta.yml

@@ -88,6 +88,12 @@ jobs:
         with:
           ref: ${{ needs.tag.outputs.version }}
 
+      # drivers/ is gitignored and fetched from the commit pinned in
+      # drivers/BUNDLED_SOURCE.json. The image copies it, so it has to exist
+      # in the build context before buildx runs.
+      - name: Fetch the bundled drivers
+        run: make drivers
+
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v3
 

.github/workflows/release-assets.yml

@@ -118,6 +118,12 @@ jobs:
           go-version: '1.26'
           cache-dependency-path: go/go.sum
 
+      # drivers/ is gitignored and fetched from the commit pinned in
+      # drivers/BUNDLED_SOURCE.json. Both the tarballs and the image carry it,
+      # so it has to exist before either is built.
+      - name: Fetch the bundled drivers
+        run: make drivers
+
       - name: Build
         env:
           GOOS: ${{ matrix.goos }}
@@ -236,6 +242,10 @@ jobs:
         with:
           ref: ${{ needs.meta.outputs.tag }}
 
+      # drivers/ is gitignored and fetched from the pin; the image copies it.
+      - name: Fetch the bundled drivers
+        run: make drivers
+
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v3
 

.github/workflows/test.yml

@@ -117,6 +117,11 @@ jobs:
       - name: Vet
         working-directory: go
         run: go vet ./...
+      # drivers/ is gitignored and fetched from the pin, so a checkout alone
+      # leaves it empty. Anything that loads a driver needs this first.
+      - name: Fetch the bundled drivers
+        run: make drivers
+
       - name: Test
         working-directory: go
         run: go test -count=1 ./...
@@ -227,11 +232,16 @@ jobs:
         with:
           go-version: '1.26'
           cache-dependency-path: go/go.sum
+      # drivers/ is gitignored and fetched from the pin, so a checkout alone
+      # leaves it empty. Anything that loads a driver needs this first.
+      - name: Fetch the bundled drivers
+        run: make drivers
+
       # drivers/ is a snapshot of srcfl/device-drivers, not a source. Hand-
       # editing a file here made this a second source of truth and the two
       # drifted: a Sungrow fix landed upstream while the bundled copy kept the
       # bug that took a customer's inverter offline.
-      - name: Bundled drivers match the pinned device-drivers commit
+      - name: No driver source is committed here
         run: bash scripts/sync-bundled-drivers.sh --check
       - name: Validate publication
         working-directory: go
@@ -389,6 +399,11 @@ jobs:
         with:
           go-version: '1.26'
           cache-dependency-path: go/go.sum
+      # drivers/ is gitignored and fetched from the pin, so a checkout alone
+      # leaves it empty. Anything that loads a driver needs this first.
+      - name: Fetch the bundled drivers
+        run: make drivers
+
       - run: make e2e
 
   test:

.gitignore

@@ -79,3 +79,7 @@ deploy/secrets/*
 # Goalbuddy renders local review boards; keep the markdown/state, not the
 # generated static board assets.
 docs/**/.goalbuddy-board/
+
+# Bundled drivers are fetched from srcfl/device-drivers at the commit pinned
+# in drivers/BUNDLED_SOURCE.json, never authored here. Run `make drivers`.
+drivers/*.lua

Makefile

@@ -96,10 +96,10 @@ container-boundary-test:
 optimizer/.venv/.installed: optimizer/pyproject.toml
 	$(MAKE) optimizer-install
 
-e2e:
+e2e: drivers-present
 	cd go && FTW_E2E=1 go test ./test/e2e -v -timeout 180s
 
-driver-repository-validate:
+driver-repository-validate: drivers-present
 	cd go && go run ./cmd/ftw-driver-repository publish -unsigned -drivers ../drivers -output ../dist/driver-repository -base-url https://example.invalid/releases/download/drivers-local -repository https://github.com/srcfl/ftw
 
 DRIVER_BASE ?= origin/master
@@ -187,7 +187,7 @@ build-windows-amd64:
 
 # ---- Release archives ----
 
-release: build-arm64 build-amd64 build-windows-amd64
+release: drivers-present build-arm64 build-amd64 build-windows-amd64
 	@mkdir -p release
 	@# Per-arch staging dirs ship ftw and its compatibility alias.
 	@for arch in arm64 amd64; do \

README.md

@@ -45,19 +45,21 @@ The local catalog is generated from `DRIVER` metadata. The public
 [`srcfl/device-drivers`](https://github.com/srcfl/device-drivers) repo is the
 editable source and FTW's default signed driver channel.
 
-[`drivers/*.lua`](drivers/) is FTW's offline recovery set, and it is a
-**generated snapshot** of that repository at the commit pinned in
-[`drivers/BUNDLED_SOURCE.json`](drivers/BUNDLED_SOURCE.json). It exists because
-startup is deliberately local: a gateway boots and runs without the network, so
-a remote refresh must never block it. Editing a `.lua` file here is not a way to
-change a driver — fix it upstream, move the pin, and run `make drivers`.
-CI fails if the two drift.
-
-A fresh clone gets the files from git today. `make drivers` fetches the same
-bytes from the pin, and CI proves the two agree on every pull request by
-throwing the committed copies away and rebuilding from the pin alone. That is
-the groundwork for dropping them from git entirely, so this repository holds no
-driver source at all.
+**This repository holds no driver source.** `drivers/*.lua` is gitignored and
+fetched from that repository at the commit pinned in
+[`drivers/BUNDLED_SOURCE.json`](drivers/BUNDLED_SOURCE.json):
+
+```bash
+make drivers
+```
+
+The files still ship. FTW's offline recovery set exists because startup is
+deliberately local — a gateway boots and runs without the network, so a remote
+refresh must never block it — so the image, the release tarballs and the tests
+all read `drivers/`. They are simply fetched rather than committed, which is
+why a driver cannot be edited here at all. There is no file to open a pull
+request against; fix it upstream and move the pin. CI fails if one is
+committed.
 
 Moving the pin is a driver release. `make driver-versions-across-pin` compares
 the drivers at the old pin against the drivers at the new one and fails when a

drivers/BUNDLED_SOURCE.json

@@ -17,7 +17,7 @@
     "for coverage. Run scripts/sync-bundled-drivers.sh to update."
   ],
   "repository": "srcfl/device-drivers",
-  "commit": "edb32ffed2f1225da160cc51c0cce8fe8e0adfd9",
+  "commit": "a4d0205d5f4439f0994b2b708a4d69a7a0c20023",
   "source_dir": "drivers/lua",
   "drivers": [
     "ambibox_v2x", "ctek", "ctek_hybrid", "ctek_v2", "deye", "easee_cloud",