# Repository instructions

## Purpose

<!-- Describe what this repository does and who it serves. Keep this factual and brief. -->

## Repository map

<!-- List only paths that exist at the reviewed revision. -->

- `[path]` — [what belongs here]
- `[path]` — [what belongs here]

## Working agreements

- Read the nearest applicable instruction file before editing.
- Keep changes limited to the requested scope.
- Preserve unrelated work and existing behavior.
- Reuse established project patterns before adding new abstractions.
- Do not add dependencies, change public interfaces, or modify deployment settings without explicit approval.
- Never add credentials, private URLs, customer data, or other sensitive information to the repository.

## Setup

<!-- Copy exact, evidenced setup commands from committed project documentation. Delete this section if none are established. -->

```text
[verified setup command]
```

## Verification

<!-- Copy exact, evidenced checks from committed scripts or project documentation. Do not invent commands. -->

```text
[verified test, lint, typecheck, or build command]
```

## Change boundaries

- Ask before destructive, irreversible, production, credentialed, or paid actions.
- Do not broaden a task into unrelated cleanup.
- Report missing evidence instead of guessing paths, commands, ownership, or release procedures.

## Completion

- Summarize the files changed and the behavior affected.
- Report the exact verification performed and its result.
- Call out anything not tested, any unresolved risk, and any follow-up that still needs an owner.