4 Commits

Include renames

Author	SHA1	Message	Date
admin	a03c25aa1f	security-scan gate (shared felhom.eu/scripts/security_scan_gate.py) in the fast set and CI, warn-first, with the accepted-hits file and decoys (R-986)	2026-10-19 21:11:31 +02:00
admin	615940de35	CI workflow: the failure mail links the public run page, by run id (R-1135) ... The alarm step built its link from GITHUB_SERVER_URL, which on this runner is the in-cluster Gitea address, and from the run NUMBER, which Gitea 1.26 reads as a run id first (felhom.eu /actions/runs/1116 opened run id 1116 = run number 613). Now https://gitea.dooplex.hu + GITHUB_RUN_ID, and the link is printed into the job log as ALARM-LINK. Same change in all four repos.	2026-10-18 20:34:59 +02:00
admin	411d7761d9	CI workflow: a manual proof that the failure mail can be sent (R-1129) ... workflow_dispatch with input force_alarm (default false). A dispatch-only step prints the RESEND_API_KEY length (never the key) and, when forced, fails so the alarm step sends its real mail, subject marked FORCED TEST. Push runs are unchanged. No controller release, no code change. Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS	2026-10-17 12:49:43 +02:00
admin	dcc400e175	ci: run the gate entry point on every push (R-168) ... Reports, does not refuse — pushes go 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. CI reproduces the workspace's SIBLING LAYOUT on purpose: this repo's entry point invokes the shared reuse_refs_check that lives in the felhom.eu clone next door and is never copied here, and this repo's REUSE.md cites wgsync/reconciler.go, which lives in the hub. Without the sibling the gate fails closed with 'gate is MISSING' — correctly, but for the wrong reason. No uses: step anywhere; no version bump; nothing built or deployed.	2026-08-02 16:27:25 +02:00