vyos-documentation.git/.github/workflows, branch sagitta

ci: bump AI-validation reviewer pin to reviewer-v1.1.0

2026-11-01T18:23:03+00:00

reviewer-v1.1.0 carries the Opus 5.5 batch fixes, the pass-1 resolver rework, and MyST extraction from a CommonMark token stream (lists, blockquotes and HTML comments handled correctly). Without this bump the per-PR review keeps running the v1.0.4 pass-1 code. 🤖 Generated by [robots](https://vyos.io) (cherry picked from commit 3cc456c8f852c055efa67596e3bd42678b9a403d)

ci: pin claude-code-action to v1.0.266 for Opus 5.5 support

2026-11-01T15:23:58+00:00

v1.0.119 installs Claude Code 2.1.138, which predates claude-opus-5-5 (added in Claude Code 2.1.280). v1.0.266 installs 2.1.316. The inputs this workflow passes are unchanged between the two releases. 🤖 Generated by [robots](https://vyos.io) (cherry picked from commit 396ef7a20a23b5aa03c954a86b04e0c35c3864e2)

ci: bump AI-validation reviewer model to claude-opus-5-5

2026-11-01T15:23:57+00:00

Move the Pass 2 review in ai-validation.yml from claude-opus-4-7 to claude-opus-5-5, matching the reference copy in VyOS-Networks/vyos-docs-opus-reviewer. 🤖 Generated by [robots](https://vyos.io) (cherry picked from commit 800e08db46f615ae7759fd9d0e7fe097f98f5885)

ci: T9208: bump AI-validation reviewer pin to v1.0.4 for scutum branch map (#2203)

2026-08-14T15:05:55+00:00

🤖 Generated by [robots](https://vyos.io)

ci: bump REVIEWER_REF to reviewer-v1.0.3 (rolling branch-map fix) (#2182) (#2184)

2026-08-03T18:29:40+00:00

The reviewer-v1.0.2 tag ships a branches.json that maps docs branch 'rolling' to vyos-1x branch 'current'. The vyos-networks/vyos-1x mirror renamed 'current' to 'rolling', so the 'Checkout vyos-1x at mapped branch' step fails on every rolling-based PR (first observed run 30565684480, PR #2177). reviewer-v1.0.3 carries the corrected mapping (rolling -> rolling) plus CI/docs-only changes; no reviewer Python source changes between the two tags. 🤖 Generated by [robots](https://vyos.io) (cherry picked from commit 3263d8760117ab85bdfc6e13bbaf2d45db3c10a8) Co-authored-by: Yuriy Andamasov

ci: track Context7 variant by branch (sagitta companion) (#2129)

2026-07-02T17:31:35+00:00

Companion to vyos-documentation#2127 (rolling). That PR switched the Context7 1.5/1.4 variants to branch-backed and moved context7-refresh to a push trigger, but a push-triggered workflow only fires from the copy present on the pushed branch. Land the same two workflow changes on sagitta so pushes here self-refresh the branch variant: - context7-refresh.yml: workflow_run chain → push trigger on rolling/circinus/sagitta; refresh payload uses branch:"sagitta". - Delete update-version-tags.yml (obsolete — no more git-tag indirection; branch variant tracks HEAD natively). No context7.json on this branch — Context7 reads config only from the default branch (rolling). Workflow-only change. 🤖 Generated by [robots](https://vyos.io)

T8960: ai-validation — mint vyos-bot token via get-token@production

2026-06-03T00:57:24+00:00

Swap the cross-repo-checkout token from the dedicated vyos-docs-reviewer App (VYOS_APP_ID/_PRIVATE_KEY) to the shared vyos-bot App via the fleet get-token composite, scoped contents:read. Skip-check now gates on APP_CLIENT_ID + APP_PRIVATE_KEY + ANTHROPIC_API_KEY (org-level vyos-bot creds); reword the stale token comment. PR-comment posting still uses the default GITHUB_TOKEN. Byte-identical to the paired reference copy in VyOS-Networks/vyos-docs-opus-reviewer (scripts/ai-validation.yml). 🤖 Generated by [robots](https://vyos.io) (cherry picked from commit 459109f13adf026d012c4e803f4a86a8f84e6ce3)

ci(ai-validation): allow Pass 2 review on external-contributor PRs

2026-05-29T09:21:01+00:00

The upstream `anthropics/claude-code-action` performs a write-permission check on `github.actor` before our skip logic runs. On `pull_request_target` the actor is the PR author; external contributors resolve to `read` and the action exits 1 with `Actor does not have write permissions to the repository`. Net effect: AI validation has been failing on every external-contributor PR (LiudmylaNad, teslazonda, scottlaird in the last 4 weeks) while succeeding on maintainer PRs. Failure reproduced on run 26541079685 (PR #2061). Fix: set `allowed_non_write_users: '*'` on the Pass 2 step. The action bypasses the actor check when this input is set and `github_token` is provided (already the case). The action also auto-scrubs Anthropic / cloud / GHA secrets from subprocess envs when this input is set. Safe in THIS workflow because the existing defense-in-depth bounds what Pass 2 can do with untrusted PR content: - `allowedTools` restricted to inline-comment + read-only surfaces - `github_token` is the PR-scoped default (not the broader VYOS_APP_ID) - prompt marks PR content as untrusted via `` - workspace-wipe removes `CLAUDE.md` / `.claude/` before Pass 2 - prepare bundles MD via `git show HEAD:` (blob, not `cp`) Full rationale inlined as a comment block above the new input. 🤖 Generated by [robots](https://vyos.io) (cherry picked from commit 1fa39bd7ac64898f7a21922bc0f195d115d3cdeb)

Merge pull request #2042 from vyos/mergify/bp/sagitta/pr-2023

2026-05-14T07:23:44+00:00

ci(doc-linter): fix 12 accumulated bugs flagged across PR #2014/#2019/#2020 reviews (backport #2023)

ci(ai-validation): skip prepare on Mergify-authored PRs

2026-05-14T06:45:22+00:00

Lifts the existing Mergify-author short-circuit (today inside validate's `secrets-check` step) to a job-level `if:` on `prepare`, so the whole pipeline skips for backport/queue PRs. Why now: every Mergify backport whose merge ref shares no shallow ancestor with the (advanced) base branch fails the prepare step at git diff "$BASE...HEAD" --name-only ... fatal: FETCH_HEAD...HEAD: no merge base (because base is `git fetch --no-tags --depth=1` and the merge ref is `fetch-depth: 2`). Proximate symptom: run 25842928620 on PR #2042 (sagitta backport of #2023). AI Validation isn't a required check so the queue isn't blocked, but every Mergify backport is left with a red "prepare" check that adds noise to PR review. The validate-level skip in commit 0e8a2956 was correct for the "claude-code-action rejects bot-initiated runs" failure mode but fires too late — prepare has already run and crashed before validate's `if: needs.prepare.outputs.has_md_changes == 'true'` even evaluates. Implementation: single job-level `if:` on prepare. validate's `needs: [prepare]` cascades the skip naturally (skipped needs make the dependent's expression-based `if:` evaluate against empty outputs). The in-step author check in validate stays as defense-in-depth. 🤖 Generated by [robots](https://vyos.io) (cherry picked from commit 7d94d6116be1a4776b7317cb5190a83dd065e571)