status-ui: deterministic bind + RPC_URLS multi-node polling; harden make lint

[BioMark3r]

Motivation

• Make the status UI bind and RPC targets deterministic so it doesn't accidentally collide with existing services and so the dashboard shows one card per RPC endpoint instead of collapsing when peer counts are >0.
• Make make lint and CI linting resilient and actionable when developer machines/containers are missing go.sum entries, while still enforcing strict checks in CI.

Description

• Updated apps/status-ui/server.js to prefer STATUS_UI_PORT over PORT and STATUS_UI_HOST over HOST, log the bind host/port and RPC count, and introduced RPC_TIMEOUT_MS for per-RPC request timeouts.
• Replaced the old single-endpoint CLI polling with JSON-RPC fanout: support RPC_URLS (comma-separated) with fallback to RPC_URL, defaulting to the 4-node devnet http://127.0.0.1:8545..:8548; each RPC is polled in parallel (eth_blockNumber, net_peerCount, optional eth_chainId), errors/timeouts are captured per-node, and returned node objects use reachable, ethBlockNumber, netPeerCount, and chainId.
• Updated UI template apps/status-ui/public/index.html to render one card per configured RPC and to display reachable/unreachable, RPC label, eth_blockNumber, net_peerCount, chainId, and last error.
• Changed Makefile: added STATUS_UI_HOST, STATUS_UI_PORT, RPC_URLS, and CI_LINT_STRICT defaults; status-ui target now passes STATUS_UI_HOST/STATUS_UI_PORT/RPC_URLS explicitly and writes a proper PID; stop-ui/status logic preserved with best-effort kill+SIGKILL.
• Hardened lint target in Makefile to detect the common go vet failures caused by missing go.sum entries: it prints guidance and only fails when CI_LINT_STRICT=1.
• CI/workflow and scripts updated: CI_LINT_STRICT=1 is set for GitHub Actions and scripts/ci/run.sh runs lint early; scripts/tests/integration.sh updated to use the new status-ui port/env names.
• README updated to document new env vars and defaults (STATUS_UI_HOST, STATUS_UI_PORT, RPC_URLS, RPC_TIMEOUT_MS) and example overrides.

Testing

• Ran make lint (local mode, CI_LINT_STRICT=0): produced the expected go vet warnings about missing go.sum entries and exited successfully with a clear guidance message. (succeeded, warning printed)
• Ran CI_LINT_STRICT=1 make lint: go vet failures due to missing go.sum caused lint to fail as designed. (failed as expected in strict mode)
• Ran make test-unit: failed in this environment due to missing go.sum dependency checksum issues reported by Go toolchain (observed and reported). (failed due to environment dependency checksums)
• Verified make status-ui / make status-ui-status / make stop-ui lifecycle: server started (logged bind and rpc count), PID file behavior and stop path tested; calling /api/status against a manual server run reported configuredRpcs=4 and returned 4 node entries (one per RPC). (status-ui behavior verified)
• Attempted headless UI capture via Playwright but the local browser connection returned ERR_EMPTY_RESPONSE in this environment, and npm may fail under restrictive registry/proxy policies, so some make status-ui runs can fail to install packages here (network/registry policy related). (environment-dependent)

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b94ae41cff

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep health checks dependent on block progress

summarize now marks the system healthy as soon as any RPC endpoint is reachable, which means /healthz can return 200 even when the chain is stalled (RPC responds but eth_blockNumber is not advancing). In that outage mode, monitoring and CI gates that rely on /healthz will get false positives; the prior behavior required evidence of sealing before reporting healthy.

Useful? React with 👍 / 👎.