ci: run the affordable gate set on push and publish at the tag

Assisted-by: DeepSeek V4.1 Flash

CONTRIBUTING.md

@@ -117,12 +117,14 @@ Workflows live in `.gitea/workflows/` and run on the project's own runners:
 
 | Workflow | Trigger | What it does |
 |---|---|---|
-| Test | push or pull request to `development` | build, format check, vet, modernisation, the test suite with the coverage floor, the CLI and debugger tests outside the profile, then the oracle-parity rerun against `go tool asm` |
-| Release | a `v*` tag | the same gates as Test minus the oracle-parity step, then the matrix build, the version smoke test and the release itself; the race detector runs locally in `just gates` before the tag is cut |
+| Test | push or pull request to `development` | the format check, `go vet`, and the short layer of the test suite with the coverage profile and the 80 % floor, inside the two-minute budget |
+| Suite | dispatched by hand | the complete gate set minus race: the build, both static gates, the full suite and the coverage floor |
+| FreeBSD build | dispatched by hand | the three FreeBSD compile gates for amd64, arm64 and riscv64 |
+| Release | a `v*` tag | the matrix build, the version smoke test and the release with its assets; no gate runs at the tag |
 
-The local equivalent is `just gates`, which is the same set plus the race detector. The
-race detector also has its own workflow, dispatched by hand; it never runs on a push or a
-tag, where it would double the time and the memory a shared runner cannot spare.
+The local equivalent is `just gates`, which is the same set plus the race detector. Race
+never runs in CI, on a push or a tag: it would double the time and the memory a shared
+runner cannot spare, so the local `just gates` runs it before the tag is cut.
 
 ## Reporting bugs