End-to-end Robot Framework test suite + Docker Compose stack for the whole safeAPIRBC2oo2 system: the 6-container RBC (roles A/B/C × WEST/EAST) plus the Train/IL/CTC simulators (TrainRBCSim, ILRBCSim, CTCRBCSim), 11 containers total.

This is the project that stands the whole system up to test it — it owns docker-compose.yml (moved here from safeAPIRBC2oo2GP) and the Robot Framework suite (moved from that project's old tests/robot/).

Start here

doc/BUILD_GUIDE.md — source checkout to a verified install package (or Docker image), end to end: the dependency chain, plain-host build, Docker build. Read this first.
doc/design/DESIGN.md — the (proposed, not yet implemented) structured JSON sendMessage/getMessage test-assertion protocol intended to replace today's log-scraping assertions; read before adding new test assertions.
doc/design/SIM_INTERFACES.md, doc/design/TEST_CASE_TEMPLATE.md.

Layout

robot/ — the Robot Framework suites: containers/ (whole-stack liveness/health), rbc_scenario/ (train connects → IL grants → IL extends a Movement Authority), fault_injection/ (network-partition and container-reboot recovery per role/site).
etc/scripts/ — start_docker.sh/start_containers.sh/stop_containers.sh/run_robot_tests.sh drive the stack from the CLI; build.sh is the single front door for building every C project (build.sh all/platform <targets>/package/release/clean/distclean).
src/web_runner/ — a local, dev-only web server + live visualization page for the rbc_scenario suite (run by hand against a local test env — never hosted, since it executes real build/start/ stop/run subprocesses).

Running

etc/scripts/runDockerTests.sh          # containers/ + rbc_scenario/ against the full 11-container stack
etc/scripts/runDockerTests.sh --full   # + fault_injection/ (several minutes)
etc/scripts/runLocalTests.sh           # rbc_scenario/ only, plain local processes, no Docker

See doc/BUILD_GUIDE.md for what has to be built first.