docs(worker-rejoin-resync): add task 1.5, xceadmin config-build wiring
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
This commit is contained in:
parent
25347648be
commit
9fbbd12b36
2 changed files with 9 additions and 0 deletions
|
|
@ -28,6 +28,14 @@
|
|||
- _Boundary: wire codec_
|
||||
- _Depends: 1.1_
|
||||
|
||||
- [ ] 1.5 (P) Wire the new config fields into xceadmin's config-build pipeline
|
||||
- Add the two new cluster-config fields (the recently-finished reporting window, the reconciliation timeout) to xceadmin's YAML validation schema and its YAML-to-binary field mapping, following the existing `heartbeatInterval`/`inactiveHeartbeatCount` pattern exactly, so an operator can actually set them through `xceadmin config build` — added to the wire schema by task 1.1, but with no configuration path into it until this task
|
||||
- Regenerate the checked-in golden config-build fixtures to match the wire schema's current field set (task 1.1 grew it; the fixtures predate that and no longer match a fresh build)
|
||||
- Observable completion: a YAML config supplying values for both new fields produces a binary that decodes back to those exact values, and the existing golden-fixture regression tests pass again
|
||||
- _Requirements: 3.7, 5.3_
|
||||
- _Boundary: xceadmin config-build_
|
||||
- _Depends: 1.1_
|
||||
|
||||
- [ ] 2. Core: controller job-table reconciliation outcomes
|
||||
- [ ] 2.1 Return an unrecognized job to pending state, releasing its resource allocation
|
||||
- When a worker reports a queried job as unrecognized, transition that job back to pending using the existing state-transition guard so a terminal or already-more-final job is never overwritten
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue