Validate EigenFlux code and run tests

Build, start services, and run affected unit and integration tests

Autonomously validating completed changes in EigenFlux without manual test invocation, using source-to-test mapping to run only affected suites.

• · None (runs autonomously after code changes)

• · Build artifacts (./console/console_api/scripts/build.sh if console changed)
• · Service logs from ./scripts/local/start_local.sh and ./console/console_api/scripts/start.sh
• · Test results: unit (go test), integration (tests/run.sh), e2e (if cross-module changes)

• · go test
• · tests/run.sh
• · scripts/common/build.sh
• · scripts/local/start_local.sh

• · Code changes completed
• · Go toolchain installed
• · Services can start (no port conflicts, no missing dependencies)
• · Test suites exist for changed packages

• · Build fails → stops immediately, fix compilation before tests
• · Service fails to start → check .log/<service>.log, fix before tests
• · Unit tests fail → stop before integration tests, fix first
• · Integration tests fail → report with details, do not suppress

• · Source → test mapping table for all packages
• · Cross-cutting rule: pkg/* changes trigger all consumer suites + e2e
• · Services kept running across test phases (--skip-start)
• · Failures reported with full details