The first real run of ci.yml was a startup_failure — no jobs, no log, just
"this run likely failed because of a workflow file issue".
reusable-chrome-extension.yml declares two mutually exclusive jobs: `build`
(contents: read, `if: !inputs.release`) and `release` (contents: write,
`if: inputs.release`). GitHub validates the caller's grant against EVERY job
the reusable declares, before evaluating any `if:` — so passing `release: false`
does not exempt the caller from the release job's requirement, and the
least-privilege `contents: read` in docs/12 §2.1's sample rejects the whole run.
CodeQL succeeded on the same push because its caller happened to grant a
superset of what its single job needs, which is what isolated the cause.
docs/12 §2.1 updated with the same grant and a warning, since its sample is
what this stub was written from.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>