fix(fleet): restore ConditionPathExists dropped by my own red-check

Self-inflicted and worth recording rather than quietly amending. To prove the new tests were red without the fix I ran `git checkout origin/next -- <fleet.ts> <[email protected]>`. That writes the *index*, not just the working tree. Copying my versions back afterwards restored the working tree only, so the unit file sat staged-as-origin/next and modified-in-tree, and the next commit (67f5014c) committed the index — silently removing the ConditionPathExists line that 463745e3 had added. Nothing caught it. The spec reads the file from the working tree, so it stayed 10/10 green against a HEAD that no longer had the guard. Found by reading `git status` after the push, not by any gate. Verified by content, not by assumption: origin/next 0 occurrences 463745e3 1 67f5014c 0 <- the regression this commit 1 Refs #1237
2026-08-15 23:35:54 -05:00
parent 67f5014cc0
commit 6f5b4c3dc1
1 changed files with 8 additions and 0 deletions
@@ -4,6 +4,14 @@ Documentation=https://git.mosaicstack.dev/mosaicstack/stack
 Requires=mosaic-tmux-holder.service
 After=mosaic-tmux-holder.service
 PartOf=mosaic-tmux-holder.service
+# Do not attempt a seat before its generated env exists. `install` enables this
+# unit (WantedBy=default.target) but on a roster-v2 fleet the reconciler owns the
+# generated env, so between `install` and the first `apply`/`regen --write` there
+# is a boot window where ExecStart would run against an absent env file and the
+# launcher would fail the unit. A skipped unit is the honest state for "enabled
+# but not yet configured"; systemd re-evaluates the condition on every start, so
+# the seat comes up on the next start once the reconciler has written env.
+ConditionPathExists=%h/.config/mosaic/fleet/agents/%i.env.generated

 [Service]
 Type=oneshot