7 Commits

Include renames

Author	SHA1	Message	Date
NeilClack	a33a586485	Bake the channel manifest's closure instead of a pinned app version ... Production builds failed CI's baseline preflight because flake.nix pinned the app to tag 1.8 (channel.appVersion = "1.8") while the published manifest had moved on to 1.9; dev was likewise pinned to a stale commit. Stop pinning the app anywhere. flake.nix now fetches the channel's published manifest at eval time (builtins.fetchurl) and bakes its storePath verbatim, so every image carries exactly the closure RadiantWave published to Attic and never compiles the app from source. - flake.nix: drop the radiantwave/radiantwave-dev inputs, appInput, appVersion, channelVersion and baselineOutPaths; add channelAtticUrl, channelManifestDir and publishedApp; builders consume the published path. - configuration.nix: wrap the published store path in a symlinkJoin so it can live in environment.systemPackages; add --impure to autoUpgrade flags and set tarball-ttl = 0 so eval reads the current manifest. - radiantwave-updater.nix: baselinePackage (package) -> baselinePath (str), seeded from the exact manifest path. - CI (build.yml, build-rpi.yml): replace the version-equality preflight with a fail-fast check that the announced closure is in the channel's Attic; set tarball-ttl = 0. - build-rpi.sh: pass --impure. - AGENTS.md: document the manifest-driven baseline.	2026-10-07 10:26:17 -05:00
NeilClack	7aa88ee174	Update radiantwave-updater script to auto-restart tty1	2026-10-05 21:50:15 -05:00
NeilClack	05bb98b107	Enable live app updater on production variants ... All variants now follow the same update procedure as the dev flakes; prod variants pull the RadiantWave binary, Attic repo, and manifest from the radiantwave channel instead of radiantwave-dev.	2026-08-28 16:37:13 -05:00
NeilClack	ca89c234ab	Fix updater timer not re-arming after first run ... RemainAfterExit=true kept the oneshot 'active' forever, which broke the timer's OnUnitActiveSec re-arming: the timer fired once (NEXT emptied, Trigger n/a) and never polled again. Remove it so the service returns to dead and the 2-min cadence keeps firing.	2026-08-28 15:59:23 -05:00
NeilClack	9a8a258228	GC-root the fetched radiantwave closure ... nix-store -r was fetching the closure without --add-root, so the swapped-in app pointer wasn't a GC root and the running closure could be collected. Pin it with --add-root .current-root, and root the already-current closure on the no-op path too.	2026-08-28 15:30:20 -05:00
NeilClack	7d8cc56ba0	Fetch updater closures from cache.nixos.org as well as Attic ... nix copy --from <attic> only pulls from that single store, so nixpkgs deps (e.g. sqlite) that Attic skips and leaves on cache.nixos.org were missing -> 'path is not valid'. Realize the closure through the machine's substituters so the app comes from the dev Attic and its upstream deps resolve from cache.nixos.org, without building from source.	2026-08-28 15:25:04 -05:00
NeilClack	d661162676	Add live RadiantWave updater (dev variants) ... Add a radiantwave-updater NixOS module that polls a manifest on the fileserver and swaps the app pointer /var/lib/radiantwave/current to new closures fetched from the dev Attic cache. Closures are fetched with 'nix copy --from', never built from source; the swap is atomic via mv -T. Enable it on the -dev variants only for now: the login shell launches from /var/lib/radiantwave/current/bin/radiantwave when enabled, and from the immutable system path otherwise, so prod behavior is unchanged. The pointer is seeded on first boot to the baseline copy already baked into the closure (no duplication).	2026-08-27 20:58:07 -05:00