# Agent instructions

## Bazel is the project interface

All project execution must happen through Bazel. Use existing `bazel build`,
`bazel test`, and `bazel run` targets instead of invoking compiled binaries,
language runtimes, package managers, generated scripts, or multiple services
manually.

When a workflow needs several processes or commands, add a Bazel target that
owns their startup, runfiles, supervision, shutdown, and exit status. The user
should need one `bazel run` command.

For hg-web development, run the complete local stack with:

```bash
bazel run //hg-web:dev
```

Add or update the smallest relevant Bazel target whenever code cannot be built,
tested, run, bundled, or orchestrated through Bazel.