[buzzcrow]

What changed

CI readiness failures were caused by services being treated as ready before their dependency probes were live, and transient KV quorum errors were classified too narrowly. The monitor now preserves live processes across bounded readiness failures, retries only the allocation path for transient quorum errors, and reports readiness transitions explicitly.

The node launcher now supports multiple host-network containers on one physical host. CROWDB_PORT_OFFSET shifts monitor, SSH, Web, Access, KV, DiskDB, DiskIO, ChunkDB and Chunk-KV listeners; accepted node policies and Group 0 endpoint publication use the shifted KV ports. The host launcher validates the shifted listener set before creating a container.

SSH admission in the physical-node validation uses Ed25519 keys after initial provisioning and restarts without a password file.

Validation

• pixi run cargo fmt --all -- --check
• Full crowdb-protocol tests
• Focused crowdb-monitor readiness, policy and management tests
• crowdb-console-shared library tests
• Clippy for crowdb-protocol, crowdb-monitor, crowdb-console-shared and crowdb-web
• Host launcher unit tests and shell/Python syntax checks
• Two physical hosts: one logical node per host, key-only admission and restart
• Three host-network containers on one physical host with offsets 0/200/400, three-voter Group 0 bootstrap, dynamic KV ports 10000/10100, 10200/10300, 10400/10500, and key-only restart