Dyno Run Debug

This skill turns failing dynobox run output into a root-cause diagnosis and a verified fix proposal. Assume dynobox is the public CLI invoked with npx dynobox, unless the user says they are debugging the Dynobox repo itself (then: pnpm build && node packages/cli/dist/bin.js ...).

Two hard rules:

1. Never apply a fix unprompted. Diagnose, present ranked fix options with concrete diffs, and wait for the user to pick one.
2. Every changed or reconstructed dyno file must be verified with npx dynobox validate <file> before you present it as done or rerun any harness against it. For JS/TS dynos (.mjs, .js, .ts, .mts), also run node --check <file> first — skip node --check for YAML dynos; it only parses JavaScript and will fail even when dynobox validate would pass.

Workflow