CONTRIBUTING.md

Rama main · réplica de lectura del repositorio original.

# Contributing

TinyRouter values a small, legible core over a large feature matrix.

Before opening a change:

1. Explain the failure mode or user need it addresses.
2. Keep provider-specific behavior inside its adapter.
3. Never log prompts, completions, provider keys, or inbound bearer tokens.
4. Add tests for request translation, response normalization, and streaming when applicable.
5. Run `bun run check`, `bun run lint`, `bun run knip`, and `bun test`.

New dependencies should remove more complexity than they introduce. Features requiring persistent infrastructure should normally live outside the core process.

## Releasing

`package.json` holds the version; `--version` and `GET /` read it from there, so never hardcode it elsewhere.

```bash
bun run release 0.2.0
git push origin main --follow-tags
```

Pushing the tag runs the release workflow, which re-runs the suite, gates on the live smoke checks against real providers, and publishes executables only if everything passes. Bump the minor for changes to the configuration schema, the routing contract, or an endpoint's shape; bump the patch for fixes.