fix: cache forester dashboard status

[sergeytimoshin]

What changed

• Refresh the expensive forester status snapshot once every 30 seconds and serve the last successful snapshot from memory.
• Return a fast 503 while the first snapshot initializes and retain stale-good data across transient RPC failures.
• Raise the dashboard proxy/client timeout defaults above the backend timeout.
• Add the missing reproducible dashboard build inputs and remove the nonexistent public/ copy from its Docker image.

Why

The dashboard polled /status every 10 seconds. Each request rebuilt all mainnet status data, downloaded roughly 230 MB of Solana account data, and took 8–10 seconds before returning its first byte. The browser bundle aborted after 8 seconds.

Impact

After initial snapshot generation, /status responds from memory in milliseconds. Dashboard clients no longer multiply full mainnet RPC scans.

Validation

• cargo check -p forester
• cargo test -p forester --lib — 54 passed
• cargo build -p forester --bin forester
• production dashboard Docker build
• isolated mainnet integration: initializing 503 in 5 ms; cached 200 responses in 1.7–2.1 ms

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 70b6bbfc-7be1-40df-9699-c5d164301738

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}