fleet/fleetd
3
0
Fork 0
Code Issues 106 Pull Requests 3 Actions Packages Projects Releases 1 Wiki Activity

fleetd #775: pane-placement guard trigger keys on lead existence #776

Closed
agent wants to merge 2 commits from worker/775-pane-placement-guard-lost-its-trigger-998e6e-1 into main
pull from: worker/775-pane-placement-guard-lost-its-trigger-998e6e-1
merge into: fleet:main
Conversation 1 Commits 2 Files Changed 2
+74 -17

2 Commits

Author SHA1 Message Date
Dai Ha f50a150a4d fleetd #775: say which remedy applies to a lead vs a collaborator
CI / shell-tests (pull_request) Failing after 11s
Details
CI / contract (pull_request) Successful in 56s
Details
CI / build (pull_request) Failing after 1m58s
Details 
The ticket's correction comment pointed out the refusal message still
implied removing a lead's tab helps, when only placement: tab does.
Restate the message so the lead and collaborator remedies are not
conflated, and keep the variable name the correction specified.
 2026-10-05 14:13:32 +02:00
Dai Ha 043b3290c4 fleetd #775: pane-placement guard trigger keys on lead existence, not tab:
CI / shell-tests (pull_request) Failing after 9s
Details
CI / contract (pull_request) Successful in 57s
Details
CI / build (pull_request) Failing after 2m2s
Details 
The guard's lead half now fires whenever fleet.leaders has any entry,
since a lead's tab is always labelled by the fixed LEAD_TAB_LABEL
constant regardless of its own deprecated tab: field. The refusal
message no longer advises removing a lead's tab:, which cannot
satisfy the guard any more.
 2026-10-05 14:09:19 +02:00