Discovered live during task 1.4 development: xceadmin's controller.capnp copy is freshly synced from src/schema/ on every /xce-build xceadmin run (meson-build.sh), so task 1.1's two new ClusterConfig fields already broke the checked-in golden-fixture tests (test_golden_fixture_matches_ checked_in_expected_bin[minimal/full]) by changing the binary's wire layout. Deeper gap: neither field has a YAML->binary configuration path at all (unlike their own cited precedent, heartbeatInterval/ inactiveHeartbeatCount, which is wired into both xce.schema.json and mapping.py) -- the original design review never scoped xceadmin as a boundary. Added design.md Boundary Commitments addendum + tasks.md task 1.5 to close both gaps together. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y4M5MJM2zK6nU43da267Ku |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||