You are onboarding onto a repository you have never seen. Your job is to map it, not to change it.

Repository: [REPOSITORY PATH OR URL]
What I plan to work on next: [THE AREA OR TASK I CARE ABOUT, OR "NOT DECIDED YET"]

## Rules

- Read-only. Do not create, edit, move or delete any file. Do not install dependencies, run migrations, commit or push.
- You may run commands that only read: listing files, searching, printing git history. Ask before running anything else, including the test suite.
- Report only what you saw in a file, and give the path for every claim. If you inferred something, label it "inferred".
- If you cannot open the repository, say so and ask me to paste the file tree, the README and the manifest files. Do not describe a codebase you have not read.

## Read in this order

1. README, CONTRIBUTING, and any agent instruction files (CLAUDE.md, AGENTS.md, editor rules).
2. Manifests and build files: package.json, pyproject.toml, pom.xml, go.mod, Makefile, Dockerfile, CI workflows.
3. The entry points: where the process starts, and where routes, commands or jobs are registered.
4. One complete feature, followed end to end from the entry point to the data store and back.
5. The tests: where they live, how they are run, what they cover.
6. The last 20 commits: what changes often, and how commits are written.

## Output

Write one Markdown report with these sections, in this order:

1. **What the system does**: three to five sentences on who uses it and for what.
2. **Run and test**: the exact commands to install, run, test, lint and build, each with the file that declares it. Mark any you did not find.
3. **Module map**: a table of the main directories or modules, with one line each on what it owns.
4. **How a request flows**: the feature you traced, as numbered steps with file paths.
5. **Conventions to follow**: naming, folder layout, error handling, test style and commit style, each with one example file.
6. **Risky areas**: code with no tests, very large files, shared state, authentication, migrations, anything a small change could break.
7. **Open questions**: what the code could not tell you, phrased as questions for me.

If I named an area or task above, end with the five files I should read first for it, and why.

Stop after the report. Do not propose a refactor and do not start the task.
