Skip to content

docs: point consumers at saw guard for installing & verifying the gate - #24

Merged
Ndevu12 merged 1 commit into
mainfrom
docs/wire-in-saw-guard
Jul 19, 2026
Merged

docs: point consumers at saw guard for installing & verifying the gate#24
Ndevu12 merged 1 commit into
mainfrom
docs/wire-in-saw-guard

Conversation

@Ndevu12

@Ndevu12 Ndevu12 commented Jul 19, 2026

Copy link
Copy Markdown
Owner

What

saw guard (now shipped in the stayawakebot package) installs and verifies this gate, so this wires it into the docs instead of leaving install/verify entirely manual:

  • README Usage — a note that saw guard setup installs the gate SHA-pinned to the latest Strix release (and opens pin-bump PRs), and saw guard check verifies it's present, SHA-pinned, current, and a required check — across one repo or a whole account/org.
  • HARDENING checklist — a callout that saw guard automates most of the checklist (install / SHA-pin / required-check / freshness), while being honest that CODEOWNERS review and fetch-depth: 0 remain yours to set.
  • CHANGELOG [Unreleased] bullet.

Posture is unchanged (and already correct)

No workflow/permission changes. The least-privilege contents: read default and remediation-as-deliberate-opt-in (scoped write, prefer a push trigger, keep PR runs report-only) already match what saw guard setup emits — so this only connects the shipped tooling, it doesn't re-litigate the posture.

saw guard (shipped in the stayawakebot package) now installs and verifies THIS
gate, so wire it into the docs instead of leaving install/verify entirely manual:

- README Usage: a note that `saw guard setup` installs the gate SHA-pinned to the
  latest release (and opens pin-bump PRs), and `saw guard check` verifies it's
  present, SHA-pinned, current, and a required check — across one repo or an account.
- HARDENING checklist: a callout that saw guard automates most of the checklist
  (install / SHA-pin / required-check / freshness), while being honest that CODEOWNERS
  review and fetch-depth: 0 remain yours to set.

Posture is UNCHANGED and already correct — the least-privilege `contents: read`
default and remediation-as-deliberate-opt-in (scoped write, prefer a push trigger,
keep PR runs report-only) already match what stayAwakeBot's `saw guard setup` emits.
This only connects the shipped tooling; no workflow/permission changes.
@Ndevu12 Ndevu12 self-assigned this Jul 19, 2026
@Ndevu12 Ndevu12 added the enhancement New feature or request label Jul 19, 2026
@Ndevu12
Ndevu12 merged commit b122da5 into main Jul 19, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant