lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(controller-peers-env-fallback): default the harness masters setting from XCE_CONTROLLER_PEERS (task 3.3)

Browse source 
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-10-03 07:22:28 +00:00
parent 05a7e6dd0c
commit 65ae25a1e6
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
3 changed files with 154 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.kiro/specs/controller-peers-env-fallback/tasks.md
View file

@ -63,7 +63,7 @@
- Done when, after rebuilding the worker, the worker suite passes and every worker case in the regression script passes
- _Requirements: 1.1, 1.2, 1.3, 1.4, 1.5, 1.7, 1.8_
- [ ] 3.3 Default the harness `masters` setting from the environment variable
- [x] 3.3 Default the harness `masters` setting from the environment variable
- Add the harness cases to the regression script first and see them fail, always with `--norc`: a bare `set` shows the env value as the `masters` default; after `set masters ...` the explicit value is shown; on a connecting command, the invalid-value message says explicit `set masters` when one ran, default from the variable when none ran and the variable is set, and an explicit invalid value still blames `set masters` with a valid variable set; `help set` names the variable and the opt-out
- At startup, before rc-file loading and the command loop, set the `masters` default from the variable when it is set, otherwise keep today's built-in default; an explicit `set masters` still wins
- Make the invalid-`masters` message name the source as above (today's wording when neither applies); update the `set` help text