Meta conformance ledger

Append-only trend of meta-health detector counts, written by /k-meta-watch (stack-RFC-014 phase 6). One row per run. A count that goes UP between runs is an obediencequality regression → `k-meta-watch escalates (open a ticket / fire /k-meta-tune / promote a gate). A count that goes **down** is a meta cleanup landing (e.g. a /k-meta-tune` apply). This is the longitudinal signal that keeps the owner out of the human-smoke-detector role.

Sources (deterministic only — the AI-judgment passes of /k-meta-tune are not trended here): koder-spec-audit meta-friction --json (section-budget + dangling-command-ref + stale-ref). Future deterministic audits (audit-*.yml / koder-spec-audit checks) append more columns as they're wired in.

Schema: date · section-budget · dangling-ref · stale-ref · notes. Append a row; never rewrite history (the trend IS the value). Concurrent-safe by low frequency (nightly) + append-only.