[OisinKyne]

Why

• dv-pod 0.23 broke the backup instructions. Since chart 0.23 the Charon container sees an empty validator_keys/. The backup commands in two guides copy from -c dv-pod, so they silently produce a backup with no key shares.
• The skills pages predate v1.11.0 of the Obol skills plugin, and the docs never mention the MCP server it bundles.

Changes

dv-pod 0.23

• obol-stack/run-a-dv.md and create-a-dv-with-a-group.mdx: back up from -c validator-client and check that validator_keys/ lists keystores. Prysm or VC-less setups go to the chart's short-lived-pod recipe, and charts before 0.23 keep -c dv-pod.
• update-a-dv.mdx: an "Upgrading from a chart older than 0.23.0" warning covering:
  • backups from the validator client container;
  • charon exit sign / charon edit from a backup copy;
  • the non-root security context and memory limits;
  • the check for a pod that kept the old spec.
• Chart pins go 0.22.x → 0.23.0, and dv-pod upgrades use --reset-then-reuse-values so new chart defaults apply.

Agent skills

• agent-skills/README.md: a "The bundled Obol MCP server" section covering what it does, that it needs uv, and which skills use it.
• agent-skills/skills.md:
  • obol-monitoring: per-peer triage that catches offline peers, failures per node, largest clusters by stake, nicknames, and a perf-check prompt.
  • distributed-validators: MCP-first, cluster names, and who runs a peer.
  • dvpod: the 0.23 backup note.

Notes

• Merge after skills v1.11.0 is released, which means the marketplace ref has moved. Until then, plugin users get v1.6.0, which has neither the MCP server nor the new triage.
• I didn't run yarn build locally; the test deploy checks links.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud