dxkit-describelisted

# dxkit-describe This skill turns a repo into a **shareable, honest picture**: what dxkit can see about the stack and its HTTP contracts, and — the part that builds trust — how *much* of it dxkit actually resolved versus inferred or could not see. It is zero-write by default. Nothing lands in the repo unless the user explicitly saves the HTML map with `--out`. ## The one command ``` vyuh-dxkit describe [path] # terminal summary (zero-write) vyuh-dxkit describe --json # the versioned repo card (dxkit.repo-card.v1) vyuh-dxkit describe --html # the contract-map HTML to stdout vyuh-dxkit describe --html --out map.html # save the map (explicit opt-in write) ``` Everything is computed from the code (flow spine, seams, models) via the same canonical analyzers the gate uses — no new heuristics, no second confidence scale. ## What it produces - A **repo card**: stack, routes, calls, bindings, and models, each count broken down by epistemic label: - **observed** — dxkit parsed the source itself, - **derived** — from a declared contract (a spec) dxkit trusts but didn't see, - **inferred** — a heuristic binding that carries a confidence and may be wrong, - **unknown** — the fact exists but can't be resolved (a runtime URL, a missing scanner). - The **seams**, which a linter cannot see: - **unresolved calls** — client calls that reach no served route (integration gaps), - **unconsumed routes** — served routes nothing calls (d