[Epic] Track C — Orchestration + CLI

Track C — Orchestration + CLI

Parent: #394

This epic covers everything that wires Pluto together — lifecycle, monitoring, the node graph, and the user-facing CLI commands beyond DKG. Two integration anchors (#402, #403) depend on Track A + Track B landing first; they're the final assembly step.

Scope

App utilities

• #68 app/health
• #41 app/forkjoin
• #71 app/stacksnipe
• #46 app/protonil
• #47 app/tracer
• #183 app/sse
• #400 app/monitoringapi
• #401 app/vmock

Core coordination

• #399 core/gater
• #177 core/priority
• #173 core/infosync

Integration anchors (final assembly)

• #402 app/app.go wiring — node graph instantiation & lifecycle
• #403 cmd/run — the pluto run binary entry point 🎯 Phase 4 gate

CLI surface

• #181 cmd/combine
• #410 cmd/addvalidators
• #411 cmd/manifest_tools
• #412 cmd/debug_tools

Sequencing

1. App utilities (most are small) — front-load in Phase 0/1
2. #400 monitoringapi + #183 sse — observability surface
3. #399 gater + #177 priority + #173 infosync — peer coordination
4. #402 app/app.go wiring — needs every Track A + B module to be ready
5. #403 cmd/run — needs #402 complete
6. CLI commands (#410, #181, #411, #412) — parallelizable any time

Acceptance

• All sub-issues closed
• pluto run boots, joins peers, completes one slot in a 4-node compose
• Monitoring endpoint exposes scheduler/duty/inclusion metrics
• All CLI commands ported with --help parity vs charon

Start with the parent epic #394 and the listed sub-issues, following the stated sequencing from app utilities through #402 app/app.go and #403 cmd/run. Review the integration anchors and CLI entries first. Done means all sub-issues are closed, pluto run completes one slot in a four-node compose, monitoring exposes the listed metrics, and CLI help matches charon.