repo-asset-stocktakelisted

# repo-asset-stocktake — Non-Code Asset Value Stocktake Audit a project repository's **non-code assets** — configs, CI workflows, runbooks, and other files that tooling or humans consume — and assign each a holistic **Keep / Update / Retire / Merge** verdict. Evaluation is single-context and holistic; there is no runtime script and no numeric score. > **Design note 1 — every asset has a consumer.** A non-code asset is not alive because it exists; it is alive because something *consumes* it — a tool invoked from a build script, a CI runner fired by an event, a human who reaches it through a link. When the consumer vanishes, or the asset stops serving the consumer it was written for, the asset becomes a review candidate. The config / workflow / runbook classes below are three **seed** consumer-classes, not the closed set — add a row whenever you meet a new consumer. > **Design note 2 — two tiers, code then judgment.** Reachability is *structural* (decidable by grep/find) so tier-1 enumerates it as code. Value is *semantic* ("does this still mean anything?") so tier-2 leaves it to holistic LLM judgment. The deterministic scan narrows the gray zone, and the LLM judges only what survives. An asset can be perfectly reachable and still be dead (a workflow that fires but runs a no-op, a runbook that is linked but describes a retired process); tier-1 cannot see that, which is exactly why tier-2 exists. ## Modes (`$ARGUMENTS`) `$ARGUMENTS` is `[full|changed] [REPO_DIR]` — mode fir