ci: flip 5 job-level continue-on-error masks to false (#2113) #2126
Reference in New Issue
Block a user
Delete Branch "fix/continue-on-error-triage-2113"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Partial fix for #2113 / mc#1982: flip four proven-stable Gitea workflow job-level
continue-on-errormasks fromtruetofalseso failures become real CI signals instead of masked green statuses.Purpose
This is a CI-hardening-only change. It does not touch workspace-server application code, migrations, database schema, runtime behavior, API handlers, Canvas code, or staging deployment logic. The change narrows prior RFC internal#219 Phase 3 masking after the affected checks had enough clean history to graduate to hard-fail.
Workflow files affected
.gitea/workflows/check-migration-collisions.yml.gitea/workflows/lint-bp-context-emit-match.yml.gitea/workflows/lint-curl-status-capture.yml.gitea/workflows/lint-required-context-exists-in-bp.ymlblock-internal-pathswas intentionally not flipped because pre-flip evidence showed masked failures on main; leaving that mask in place avoids converting a known-red workflow into an immediate unrelated blocker.Safety justification
The affected workflows are lint/audit gates. Flipping their job-level
continue-on-errortofalseonly changes whether a failing lint/audit job blocks CI. It does not alter product runtime code, tenant data paths, auth, billing, schema, or deployment behavior. The current PR head has green required CI onCI / all-required (pull_request).SOP checklist
Comprehensive testing performed
CI-config-only change; no app code touched. Relevant PR-head CI is green:
CI / all-required (pull_request): success on head23bdc47b60ee4a3e2bc4c32d202aa4f9343e8907at/molecule-ai/molecule-core/actions/runs/186906/jobs/251649Lint pre-flip continue-on-error / Verify continue-on-error flips have run-log proof (pull_request): success at/molecule-ai/molecule-core/actions/runs/186914/jobs/251662lint-required-context-exists-in-bp / lint-required-context-exists-in-bp (pull_request): success at/molecule-ai/molecule-core/actions/runs/186915/jobs/251663Lint workflow YAML (Gitea-1.22.6-hostile shapes): success at/molecule-ai/molecule-core/actions/runs/186919/jobs/251667lint-continue-on-error-tracking / lint-continue-on-error-tracking (pull_request): success at/molecule-ai/molecule-core/actions/runs/186911/jobs/251658/sop-ack comprehensive-testing CI-config-only change; no app code touched. PR-head CI all-required success at
/molecule-ai/molecule-core/actions/runs/186906/jobs/251649; relevant lint/pre-flip checks also green on head23bdc47b60ee4a3e2bc4c32d202aa4f9343e8907.Local-postgres E2E run
N/A: CI-config-only workflow change; no database code, migrations, handlers, or application runtime code touched.
/sop-ack local-postgres-e2e N/A: no DB code, migrations, handlers, or application runtime code touched.
Staging-smoke verified or pending
N/A: no application runtime or deployment behavior changes. This PR only changes whether selected lint/audit CI jobs hard-fail.
/sop-ack staging-smoke N/A: no application runtime or deployment behavior changed; lint/audit CI hardening only.
Root-cause not symptom
Root cause: #2113 / mc#1982 identified stale job-level
continue-on-error: truemasks that made CI/audit failures non-blocking after the Gitea migration Phase 3 period. This PR removes four masks whose clean history made them safe to graduate./sop-ack root-cause #2113 / mc#1982 root cause is stale continue-on-error masks hiding lint/audit failures after Phase 3; this flips four proven-stable masks to hard-fail.
Five-Axis review walked
CR2 five-axis review posted as formal COMMENT review
8280: code-OK / gate-failing at review time, with no correctness, robustness, security, performance, or readability blocker in the workflow change itself./sop-ack five-axis-review CR2 formal COMMENT review 8280 completed; workflow diff code-OK, gate-failing at review time.
No backwards-compat shim / dead code added
ACK: CI hardening only. No product/runtime surface, compatibility shim, API behavior, or dead code added.
/sop-ack no-backwards-compat CI hardening only; no product/runtime/API surface and no compatibility shim or dead code added.
Memory/saved-feedback consulted
ACK: prior CI-mask history from #2113 / mc#1982 and the pre-flip continue-on-error gate rationale were consulted; no additional app/runtime feedback applies because this PR is workflow-only.
/sop-ack memory-consulted #2113 / mc#1982 CI-mask history and pre-flip gate rationale consulted; no app/runtime memory applies.
N/A declarations
/sop-n/a qa-review CI-config-only change; no QA product surface, no app code, no runtime behavior.
/sop-n/a security-review CI-config-only change; no auth, billing, data placement, secrets, or runtime security surface.
Gate notes
QA review N/A and security review N/A are appropriate for this PR because it is CI-config-only and has no QA product surface or security-sensitive runtime/data/auth change. CTO explicitly authorized CR2 to fill this ceremony directly for #2126.
cfaea13a8eto23bdc47b60Code review verdict: COMMENT (code-OK, gate-failing)
5-axis review: the CI continue-on-error mask flip is code-OK from this review pass. The intent is appropriate: previously masked job failures should become real blockers. I did not find correctness, robustness, security, performance, or readability issues in the workflow change itself.
SOP-gate snapshot: combined CI is currently failure on head
23bdc47b60. This PR should remain held by the SOP/CI gate until the failing required checks are green and the required SOP acknowledgement is present.Posting note: formal PR review POST was rejected by Gitea because the current token lacks write:repository; posted as PR comment with write:issue so the audit trail is present.
Formal review object test (code-reviewer): CR2 5-axis review — diff flips 4 job-level continue-on-error true->false (CI hardening). No correctness/security/perf/readability issue in the diff itself. Note: SOP gate not yet green (qa/security approvals + sop-ack + PR body pending).
Code review verdict: COMMENT (code-OK, gate-failing)
5-axis review: the CI continue-on-error mask flip is code-OK from this review pass. The intent is appropriate: previously masked job failures should become real blockers. I did not find correctness, robustness, security, performance, or readability issues in the workflow change itself.
SOP-gate snapshot: combined CI is currently failure on head
23bdc47b60. This PR should remain held by the SOP/CI gate until the failing required checks are green and the required SOP acknowledgement is present.Posting note: formal PR review POST was rejected by Gitea because the current token lacks write:repository; posted as PR comment with write:issue so the audit trail is present.
CR2 #2126 ceremony directives (partial: PR body edit is blocked for molecule-code-reviewer; see separate PM blocker report).
/sop-ack comprehensive-testing CI-config-only change; no app code touched. PR-head CI all-required success at /molecule-ai/molecule-core/actions/runs/186906/jobs/251649; relevant lint/pre-flip checks also green on head
23bdc47b60./sop-ack local-postgres-e2e N/A: no DB code, migrations, handlers, or application runtime code touched.
/sop-ack staging-smoke N/A: no application runtime or deployment behavior changed; lint/audit CI hardening only.
/sop-ack root-cause #2113 / mc#1982 root cause is stale continue-on-error masks hiding lint/audit failures after Phase 3; this flips four proven-stable masks to hard-fail.
/sop-ack five-axis-review CR2 formal COMMENT review 8280 completed; workflow diff code-OK, gate-failing at review time.
/sop-ack no-backwards-compat CI hardening only; no product/runtime/API surface and no compatibility shim or dead code added.
/sop-ack memory-consulted #2113 / mc#1982 CI-mask history and pre-flip gate rationale consulted; no app/runtime memory applies.
/sop-n/a qa-review CI-config-only change; no QA product surface, no app code, no runtime behavior.
/sop-n/a security-review CI-config-only change; no auth, billing, data placement, secrets, or runtime security surface.
core-security official-approve. Reviewed: diff is CI-config only — 4 .gitea workflow files flip job-level continue-on-error true->false (RFC#219 Phase-4, 22 days green since 2026-05-11, past the 7-clean-run threshold). No application code, no auth/security surface, no data path touched. Removing the masks makes previously-hidden lint/migration/scheduled failures hard signals (the #2113 intent). CI/all-required + Go + integration + e2e + gate-check-v3 all green on 23bdc47b; SOP ceremony N/A declarations are honest for a CI-config change. No security objection. APPROVE.
core-qa official-approve. CI-config-only hardening (continue-on-error true->false on 4 workflows); all required CI green on head
23bdc47b(CI/all-required, Platform Go, Handlers Postgres Integration, E2E Chat/Canvas/API, lints, gate-check-v3, sop-tier-check, sop-checklist/all-items-acked pull_request_target). App-testing gates legitimately N/A (no app code). Quality bar met. APPROVE./security-recheck
/qa-recheck
/security-recheck
/qa-recheck
/security-recheck
/qa-recheck