loop-setup

# Session 0 — set up the loop You are setting up a working method in **someone else's project**. Touch nothing until they have seen what you propose to write. Never invent a fact about their stack: check it. ## 1 · Read the project Detect, don't ask, what you can find yourself: `ls`, `git remote -v`, `git branch --show-current`, `cat .gitignore`, and whichever of these exist — `package.json` scripts, `Makefile`, `pyproject.toml`, `Cargo.toml`, `go.mod`, `docker-compose.yml`, CI config, test config, migrations directory. Report in three lines what this project is and how it is built. ## 2 · Check the connections — live, not by asking The method depends on being able to *observe* things. Find out what is actually available in this session, right now, and print a table of PASS / FAIL / ABSENT: | Need | How to check | |---|---| | Version control | `git status` works, and whether a remote exists | | Build / tests | run the project's build or test command once | | Browser | is a browser-driving tool available (in-app browser, Chrome extension, Playwright/Puppeteer in devDependencies)? If yes, open one page and confirm it renders | | Database | is there a DB MCP server, a CLI (`psql`, `mysql`, `sqlite3`), or an ORM with a dev database? If yes, run one harmless read query | | Payments sandbox | if the project charges money: is a test-mode key present in the environment (never print its value) | | Deploy | how does this project publish, and is that command something the owner ru...