dashboards-as-codelisted

# dashboards-as-code — migrate hand-authored dashboards to code, provably lossless A hand-port of a dashboard fleet is silently lossy by default; nobody notices the dropped panel until an on-call engineer opens it mid-incident. This skill drives the migration through a round-trip fidelity gate so an as-code migration CANNOT land unless it is provably lossless. ## The five-part harness - **Golden originals are IMMUTABLE — never hand-edited.** One JSON export per dashboard, extracted from the running platform, is the diff oracle for the whole migration. Fixing a diff by editing the golden is falsifying the oracle. - **The emitter uses a generic panel factory, and its unknown-kind fallback FLAGS — never silently guesses.** Common panel kinds (time-series, stat, gauge, table, logs, pie, bar) map through one factory; rows, template variables, and library-panel references are first-class. A panel kind the factory does not know routes to a default kind WITH the `x_foundry_unverified` flag set — the gate then refuses green on it, so it becomes a human-review item instead of a silent guess. A dashboard too irregular to emit cleanly may be hand-authored — it still goes through the same gate. - **The renderer compiles code → platform JSON**, auto-discovering every compiled dashboard (a dashboard that fails to render is a gate failure, not a skipped file). - **The semantic-signature extractor reduces both sides to parity-bearing fields only** — panels → {kind, quer