adapting-to-a-projectlisted

# Adapting to a project No skill in this pack names a command. Disciplines are general; the commands that implement them are not, and a skill that hardcodes one goes stale the moment the project moves — silently, because nothing checks prose. So every project-varying value lives in one file at the repository root, `.ledger.yml`, and every other skill reads it. This skill owns the adapter file and nothing else: it records what a project's commands are, never which of them a given change needs. Your job is to write that file for this repository, and to have run everything you put in it. ## The one rule **A value you did not run is not a value.** The only admissible evidence that a command is this project's coverage lane is having executed it and seen it behave like one. A wrong entry is worse than a missing entry: a missing entry makes a skill stop and ask, while a wrong entry makes it run something and believe the result. Record only what you observed. Where you cannot execute something — a CI-only lane, a command needing credentials you must not use — leave the value `null` and add it to `unverified` with the reason. Never copy a command from a README, a CI file, or a sibling project without running it. ## Procedure 1. **Read before asking.** Take the project's package or build manifest, its CI workflow definitions, its git hook configuration, and its contributor documentation. Most values are discoverable; an interview that asks what the repository already states was