Contributing

PRs welcome. The scope is narrow and the workflow is opinionated, both by design.

The canonical document is CONTRIBUTING.md in the repo. Read it before you open a PR. The highlights:

• One long-lived branch: main. Feature branches open PRs directly against it. There is no development branch — we tried it, it lost.
• [skip-release] sigil. Docs-only and in-flight feature PRs must include [skip-release] in the PR title. Without it, the release workflow will try to auto-tag and fail. The exact form matters — square brackets, hyphen, lowercase.
• Code of Conduct. All contributions are governed by the Contributor Covenant 2.1. The short version: be decent, and if you can’t be decent, be elsewhere.

If you’re about to touch networking, credentials, tool policy, or the prompt-injection defences, also read SECURITY.md first and flag the trade-offs in your PR description.