* docs: refresh community docs to match the project's current reality - README: download badges now point to releases/latest (were frozen at v0.2.7); Intel-Mac note (pre-built bundle is Apple Silicon; source works on Intel; pre-built Intel tracked in #279) - SECURITY: supported-versions table 0.2.x -> 0.3.x + 0.2.7 legacy row - docs/install/docker.md: tag mapping matches docker.yml after #338 — :latest is the rolling main preview, :stable (new) pins releases - PR template: removed the abolished two-RC/48h-soak ceremony; documents continuous-to-main - CONTRIBUTING: new sections — what bot review looks like (CodeRabbit + Greptile), conventional-commit + issue-link expectations, the quality gates (cross-platform parity, 21-locale i18n + CJK allowlist, alembic, engine back-compat, local-first, loopback security posture), and a contribution-licensing grant that keeps the AGPL + commercial dual-license viable - SUPPORT.md: new — channels, before-you-file checklist, expectations - docs/install/macos.md: Intel caveat aligned with reality Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs: codify the docs-sync hard rule — behavior changes update their docs in the same PR Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * chore(agents): rtk rules for Antigravity — token-compressed tool output Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: mergetest <test@local> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Summary
Changes
Type
- 🐛 Bug fix
- ✨ New feature
- ♻️ Refactor
- 📝 Documentation
- 🧪 Tests
- 🔧 CI / Build
- 🚀 Release prep
Testing
Checklist
- I've tested this locally
- I've updated relevant documentation (if applicable)
- No local machine paths, logs, or personal env details in this PR
- Version files are in sync (if version bump):
pyproject.toml,package.json,tauri.conf.json,Cargo.toml - If this PR changes runtime behavior, the regression fixture at
tests/fixtures/omnivoice_data/still loads green on thesmoke-matrixCI job (macOS + Windows + Linux)
Release cadence
OmniVoice ships continuous-to-main — no release candidates, no soak windows.
Every merged PR is immediately part of the rolling preview (main, Docker
:latest, the desktop Preview channel). Versioned releases are tagged from
main when it's ready; main then bumps to the next patch automatically.
Users who want stability pin a release tag / Docker :stable / the desktop
Stable channel.