903 B
Repository rules
Read agent.md and task_plan.md on resume. Maintain the journal and evidence log for meaningful changes. Never modify the legacy sibling directory. Never copy its credentials or contact its game hosts.
Use cargo fmt --check, cargo clippy --all-targets -- -D warnings, cargo test --all-targets before claiming completion. Test Linux-specific behavior in Orb. Treat byte integrity, TCP half-close, backpressure, freshness and persistence as correctness requirements. Never describe request mirroring as database replication or guarantee zero latency/loss across failed networks.
Separate config, forwarding, control-plane, scoreboard and operator UI modules. Keep data-path synchronization short and never hold a lock across network I/O. Document public HTTP contracts in docs/api.md. Tests must exercise externally observable behavior, not mirror implementation details.