fix(ci): move workflow to .gitea/workflows — the server is Gitea, not Forgejo

The runner was alive all along (gitea/act_runner, ubuntu-latest label);
no run ever appeared because Gitea only reads .gitea/workflows/ (or
.github/workflows/) and ignores the .forgejo/ path the workflow shipped
under. The legacy repo's .gitea/workflows/check.yml was the clue.
References corrected (workflow header, TESTING.md, agent files); this
push doubles as the first live trigger of the workflow.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

agent/JOURNAL.md

@@ -17,6 +17,21 @@ Template:
 
 ---
 
+## 2026-07-04 — CI fix: wrong workflow dir (correction to iteration #2)
+- **Task:** Bernardo reported no run despite an active runner + shared
+  his compose file: the server is **Gitea** (gitea/act_runner), not
+  Forgejo — I'd shipped the workflow to `.forgejo/workflows/`, which
+  Gitea never reads. The legacy repo's `.gitea/workflows/` path was the
+  clue I under-weighted.
+- **Did:** `git mv` → `.gitea/workflows/check.yml`; corrected the
+  Forgejo references in the workflow header, TESTING.md §1b, BACKLOG
+  item 20 (now: watch the first run; runner was never the problem);
+  MEMORY.md gains the Gitea-not-Forgejo line.
+- **Verified:** the push of this commit is itself the test — the run
+  must appear; monitoring.
+- **Pending:** first green run (item 20); runner-container memory
+  headroom is the watch-out.
+
 ## 2026-07-04 — CI checks-on-push shipped (loop iteration #2)
 - **Task:** BACKLOG NOW#2 — Forgejo Actions workflow.
 - **Did:** `.forgejo/workflows/check.yml` (push to main/v1 + dispatch):