Make rbuilder depend on beacon to avoid failures

[canercidam]

No description provided.

[claude]

Claude finished @canercidam's task in 1m 38s —— View job

---

Review: PR #369 — Make rbuilder depend on beacon to avoid failures

• Analyze the diff and changed files
• Review component dependency patterns in the codebase
• Post review feedback

---

LGTM. The change is correct and consistent.

The rbuilder config template (playground/utils/rbuilder-config.toml.tmpl:10) hardcodes cl_node_url = "http://beacon:3500", meaning rbuilder requires a healthy beacon node at startup. Without this dependency, rbuilder could start before beacon is ready and fail on connection attempts.

The fix is applied consistently across all three locations where rbuilder's dependencies are defined:

• playground/components.go — Go component definition
• custom-recipes/rbuilder/bin/playground.yaml — binary custom recipe
• custom-recipes/rbuilder/container/playground.yaml — container custom recipe

This follows the same pattern used by other components (e.g., MevBoostRelay at components.go:640 and Contender at components.go:914 both depend on beacon being healthy).

No issues found.