Investigate CI-only filesystem secret-scan failure #235

New issue

Open

opened 2026-07-21 15:04:08 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-21 15:04:08 +00:00

Member

Commit 1437329 closed #234 and passed the complete local suite. Forgejo CI run 355 reports test and lint successful, but secrets job 2 failed after the filesystem scan stage. The agent reproduced the CI command locally with trufflehog filesystem, no verification, no update, fail mode, and JSON output. It exited 0 with zero findings. The mounted Forgejo Actions log endpoint returns 404, matching the documented dead log route, so the agent could not gather the failing step output through the guarded operator surface. Promotion succeeded and release run 357 started. An interactive ops run must inspect the job page or runner log, determine whether the failure came from scanner-version drift, checkout state, or the alert step, and fix the pipeline only from that evidence. The agent made no rerun or follow-up push.

Commit 1437329 closed #234 and passed the complete local suite. Forgejo CI run 355 reports test and lint successful, but secrets job 2 failed after the filesystem scan stage. The agent reproduced the CI command locally with trufflehog filesystem, no verification, no update, fail mode, and JSON output. It exited 0 with zero findings. The mounted Forgejo Actions log endpoint returns 404, matching the documented dead log route, so the agent could not gather the failing step output through the guarded operator surface. Promotion succeeded and release run 357 started. An interactive ops run must inspect the job page or runner log, determine whether the failure came from scanner-version drift, checkout state, or the alert step, and fix the pipeline only from that evidence. The agent made no rerun or follow-up push.

coilyco-ops added the

autonomy

live-collab

label

2026-07-21 15:04:08 +00:00

coilyco-ops added the

priority

label

2026-07-29 03:45:31 +00:00

coilyco-ops added

priority

and removed