docs(xce-harness-component): list harness in structure.md
Add harness to structure.md's top-level src/ directory tree (after controller/) and extend the flat-root Exceptions bullet to cover it alongside controller. Verified against the real src/harness/ layout (14 flat .c files, no nested src/, own include/ and testsuite/). This completes Major Task 3 (Integration) -- all downstream skills and steering docs now correctly describe the harness component. Task 3.7 of xce-harness-component. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RLSNJhNoULvVcUhXEFafQC
This commit is contained in:
parent
6318183b67
commit
64e4ccb308
2 changed files with 4 additions and 2 deletions
|
|
@ -10,6 +10,7 @@ src/
|
|||
│ ├── raft/ C — reusable Raft consensus module (raft.c/raft.h)
|
||||
│ └── testsuite/ C — libxce unit tests (test_*.c)
|
||||
├── controller/ C — cluster controller daemon
|
||||
├── harness/ C — xce_test wire-protocol test/verification CLI + WAL/snapshot inspection utilities
|
||||
├── worker/ C — per-node job execution daemon (xcecd)
|
||||
├── scheduler/ C — job scheduling engine (plugin architecture)
|
||||
├── autoscaler/ C — autoscaling engine (provider plugins)
|
||||
|
|
@ -35,7 +36,7 @@ src/<component>/
|
|||
```
|
||||
|
||||
**Exceptions**:
|
||||
- `controller/` keeps its `.c` files flat in the component root (not in a nested `src/`), and does have its own `testsuite/`.
|
||||
- `controller/` and `harness/` both keep their `.c` files flat in the component root (not in a nested `src/`), and each has its own `testsuite/`.
|
||||
- `worker/` has no `testsuite/` — no `test_*.c` files exist anywhere in the component.
|
||||
- `autoscaler/` does not follow this pattern at all: it has no CLAUDE.md, and its daemon code lives two levels deeper in `src/autoscaler/scaler/` (flat `.c` files plus its own `include/` and `testsuite/`), alongside `src/autoscaler/providers/`.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue