From 78f624ee9d36f175dc530b057376f510a0faba6b Mon Sep 17 00:00:00 2001 From: Yuriy Andamasov Date: Mon, 11 May 2026 09:27:20 +0300 Subject: ci(ai-validation): collapse split-backtick comment span (Copilot) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Copilot finding on #1974/#1975: the inline backtick code span `[ -s diff-md.patch ] && [ ! -d .reference-db/extracted ]` was split across two YAML comment lines, which renders poorly in Markdown viewers (the backtick crosses the line boundary). Reworded to put the relevant filesystem-presence check (`-d .reference-db/extracted`) on a single line and drop the redundant `-s diff-md.patch` half — the latter is the job-level gate condition, not part of the fail-closed gate logic, so omitting it from this rationale comment removes the wrap-required spread without losing meaning. The `-d` check on its own is what defines "the gate is a presence check, not a schema check". Mirrored byte-identically across rolling/circinus/sagitta. --- .github/workflows/ai-validation.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to '.github/workflows') diff --git a/.github/workflows/ai-validation.yml b/.github/workflows/ai-validation.yml index c0f70b9c..b4736fe1 100644 --- a/.github/workflows/ai-validation.yml +++ b/.github/workflows/ai-validation.yml @@ -333,9 +333,9 @@ jobs: # the right choice. If the DB schema ever changes incompatibly, # bump REVIEWER_REF in the consuming workflow — the newer # reviewer code will error at DB-load time inside `Pass 1 — - # deterministic checks`. The workflow's own fail-closed gate is - # a presence check (`[ -s diff-md.patch ] && [ ! -d - # .reference-db/extracted ]`); it does not inspect DB schema. + # deterministic checks`. The workflow's own fail-closed gate + # is a presence check on `.reference-db/extracted`; it does + # not load or inspect DB schema. latest: true fileName: reference-db-${{ steps.branch.outputs.vyos1x }}.tar.gz out-file-path: .reference-db -- cgit v1.2.3