dxkit-evaluatelisted

# dxkit-evaluate This skill answers the pre-adoption question honestly: **what would dxkit's gate have done on this repo's real history, and at what cost?** It runs the real guardrail — the same code path the installed Stop-gate and CI gate use — against historical ref pairs, in disposable temp worktrees. Nothing is written to the repo: no `.dxkit/`, no baseline, no hooks. ## Running the trial The default replays the last 10 landings (merged PRs / squash commits) of the current branch: ```bash vyuh-dxkit evaluate # last 10 landings, security-only posture vyuh-dxkit evaluate --last-prs 20 # more history vyuh-dxkit evaluate --preset full-debt # also gate test gaps + quality regressions vyuh-dxkit evaluate --base origin/main~5 --head origin/main # one explicit range vyuh-dxkit evaluate --json # the versioned evidence document vyuh-dxkit evaluate --json --redact # shareable: file paths + lines stripped ``` ## Reading the result - **Blocked landings** list the exact net-new findings the gate would have returned for repair. Dependency findings on old landings carry an anachronism note (advisories are current-day) — say so when summarizing. - **A clean replay is a positive result, not an empty one**: it means the repo's existing debt would be grandfathered and the gate would have stayed out of the way. Present it that way — the gate's value is blocking the regression that hasn't happened yet, and the trial just measu