ci: standby fetches full history; runbook — writer wording throughout, master-ref pinning incompatibility

- serial-linux-selfhosted checks out fetch-depth 0: depth 2 misses
  github.event.before on multi-commit or force pushes, failing the
  archive verifier on a valid tree. Full fetch is cheap against the
  VM's local mirror.
- Runbook (both languages): every remaining admin phrasing (problem
  statement, switch heading, alternatives, consequences) now says
  writer; and the 'composes with this mechanism' claim about a
  master-ref-pinned runner group is replaced with the truth observed
  live on 2026-07-27 — master-ref pinning blocks PR failover, and the
  shipped posture is repository-scoped all-workflow group access.
Static gate green locally: 32 passed, 0 failed.
This commit is contained in:
Chinesezjc
2026-07-27 16:13:30 +08:00
committed by Ubuntu
parent 4b7f28026a
commit ce3b13bb08
4 changed files with 17 additions and 16 deletions

View File

@@ -427,12 +427,13 @@ jobs:
name: serial / linux (self-hosted standby)
runs-on: [self-hosted, linux, x64, vm-backup]
steps:
# fetch-depth 2 + DSH_ARCHIVE_BASE_REF below: same frozen-archive
# comparison as serial-linux — without the prior commit the archive
# verifier defaults to HEAD and compares the new manifest with itself.
# Full history + DSH_ARCHIVE_BASE_REF below: same frozen-archive
# comparison as serial-linux. Depth 2 would miss github.event.before
# on multi-commit or force pushes; full fetch is cheap here because
# checkout resolves against the VM's local mirror.
- uses: actions/checkout@v6
with:
fetch-depth: 2
fetch-depth: 0
- uses: actions/setup-node@v6
with: