docs: CHANGELOG + REPORT for the CI workflow (no version bump)

CHANGELOG.md

@@ -1,3 +1,32 @@
+## CI — the gate entry point runs on every push (2026-08-02, R-168) — NO VERSION BUMP
+
+**No version bump, no build, no deploy** — this adds a workflow file only. Stated explicitly so the
+omission reads as a decision rather than a miss.
+
+**`.gitea/workflows/gates.yml` (new).** Triggers on `push`, `runs-on: felhom-gates`, obtains the
+source with a shallow `git fetch` of the **exact pushed SHA** from the in-cluster Gitea Service, and
+runs this repo's entry point with `--fast` — nothing else. **No `uses:` step anywhere**: JavaScript
+actions need a node runtime the host-mode runner does not have, and probe P3 measured a plain
+`git fetch` as sufficient. No `|| true`; the entry point's exit code IS the job's result.
+
+**It REPORTS, it cannot REFUSE**, and the workflow header says so: this repo pushes straight to
+`main` with no pull request, so there is no merge for a status check to stand at. The refusing half
+is `.githooks/pre-push`, which is per-clone and `--no-verify`-able; this half notices when that was
+skipped. Making CI blocking needs branch protection plus a PR workflow → felhom.eu `OPEN-ITEMS.md`
+R-169, an operator decision.
+
+**A failed run emails the operator** via Resend and prints the provider's accepted id, because probe
+P5 measured that Gitea itself sends nothing at all on a failed run. Demonstrated end to end on a real
+red run (`RESEND-ACCEPTED id=…`), not assumed. Full detail:
+`felhom.eu/documentation/audits/SPIKE-ci-runner-2026-08-02.md`.
+
+**CI reproduces the workspace's SIBLING LAYOUT on purpose.** This repo's entry point invokes the
+shared `reuse_refs_check.py` that lives in the `felhom.eu` clone next door and is deliberately never
+copied here, and this repo's `REUSE.md` cites `hub/internal/store/dr_recipe.go`, which lives in the hub. The workflow
+therefore clones `felhom.eu` as a sibling; without it the gate fails **closed** with
+`gate is MISSING` — correctly, but for the wrong reason. Verified that CI and the local hook then
+agree exactly: 90 cited paths, 88 exact / 1 suffix / 1 cross-repo, 0 failures.
+
 ## Gate enforcement — this repo gets a place to put a gate (2026-08-02) — NO VERSION BUMP
 
 **Deliberately no version bump, and no build or deploy.** Nothing compiled changed: this touches