Implement `app/app.go` equivalent — node graph wiring & lifecycle

[varex83]

Scope

Port charon/app/app.go (~1256 LOC) — the integration anchor that instantiates every duty-pipeline component in the correct order with lifecycle hooks. This is the final assembly step that makes Pluto a runnable node.

Dependencies (must land first)

This issue cannot start until every component below is implemented:

Track A:

• Rewrite core/qbft to async-Rust-friendly API #393 core/qbft async
• core/consensus framework (controller/wrapper/debugger) — see Track A epic for issue number
• Implement core/consensus/qbft #157 core/consensus/qbft, Implement core/consensus/timer #158 timer, Implement core/consensus/instance #48 instance, Implement core/consensus/metrics #62 metrics, Implement core/consensus/mocks #39 mocks
• Implement core/scheduler #176 core/scheduler, Implement core/dutydb #171 core/dutydb, Implement core/fetcher #172 core/fetcher, Implement core/bcast #170 core/bcast

Track B:

• Implement core/validatorapi #180 core/validatorapi, Implement core/tracker #179 core/tracker, Implement core/sigagg #178 core/sigagg, Implement core/aggsigdb #169 core/aggsigdb

Track C:

• Implement app/health #68 app/health, Implement app/sse #183 app/sse, app/monitoringapi
• core/gater, Implement core/priority #177 core/priority, Implement core/infosync #173 core/infosync

Acceptance

• All components instantiated with proper lifecycle ordering (start/stop semantics match Go)
• Channel/event wiring matches the Go graph
• Unit-level integration test boots the graph against beaconmock (Implement testutil/beaconmock #37)
• cargo clippy --workspace --all-targets --all-features -- -D warnings clean

[emlautarom1-agent]

Port audit — app/app.go wiring

• Status: 🔴 not started — integration anchor
• Charon source: app/app.go — 936 non-test Go LOC (Run @ 146, wireCoreWorkflow @ 399-670, delegating to core.Wire)
• Complexity: Complex

⚠️ Dependency list is over-constrained. The current body lists app/health, app/sse, app/monitoringapi, core/priority, core/infosync as "must land first." Per the actual wiring, none of these are on the duty critical path:

• CurrentConsensus() defaults to QBFT v2.0 before priority/infosync ever fire (core/interfaces.go:104-111).
• tracker/tracing/retry are wrappers (core.WithTracking/WithTracing/WithAsyncRetry) — the raw fns work without them.
• monitoring/sse/health are observability; a slot completes without them.

The minimal set for one end-to-end slot = the 10 core.Wire components (core/interfaces.go:337-357): Scheduler → Fetcher → Consensus → DutyDB → ValidatorAPI → ParSigDB ⇄ ParSigEx → SigAgg → AggSigDB → Broadcaster, plus shared infra (eth2api✅, deadliner✅, p2p✅, DutyGater #399).

Recommendation: split this into two issues — (a) minimal runnable (10 core.Wire components + lifecycle starts: StartScheduler, StartP2PConsensus, StartAggSigDB, StartParSigDB) and (b) full parity (add tracker/priority/infosync/monitoring/sse/recaster/vmock).

Trickiest implicit dep to preserve: the two Fetcher back-edges AggSigDB.Await (RANDAO) and DutyDB.AwaitAttestation (interfaces.go:342-343) — omitting them silently deadlocks proposer/aggregator duties.

---

Automated progress audit (2026-06-15). New comment only — no existing issue content was modified.