repo-reconlisted

# Repo Recon Map before you touch. Most agent failures in unfamiliar code are not bad logic, they are wrong assumptions: editing the wrong file, reimplementing a helper that already exists, or writing code in a style the project rejects. Fifteen minutes of recon is cheaper than one wrong-direction diff. ## The recon pass Work through these in order. Write findings into a scratch note (`NOTES.md` or similar) as you go, because context gets long and rediscovering the test command three times is waste. ### 1. Read the map Look at the repo root first: README, the package manifest (package.json, pyproject.toml, go.mod, Cargo.toml, etc.), build config, CI config, and the lockfile. From these alone you learn the language, framework, package manager, supported runtimes, and usually the entry points. Skim the top-level directory layout to see how the project thinks about itself (by feature? by layer? monorepo?). ### 2. Learn the commands Find out how to install, build, test, and lint. The truth usually lives in manifest scripts, a Makefile, a justfile, or the CI workflow files, in that order of convenience. Then run the test suite once before changing anything. This gives you a baseline: if it is green now and red after your change, the problem is yours. If it is already red, record that, so nobody blames your diff for pre-existing failures. ### 3. Trace one flow end to end Pick one existing feature that resembles the task at hand and follow it from entry point (route, CLI co