11 rules that run. 10 registered and honestly not built.

• reach.status_not_200/ responds 200
• reach.redirect_chain_changedfinal URL + redirect chain unchanged vs. the previous run

• header.missinga declared security/policy header is present
• header.value_changeda present header's value is unchanged vs. the previous run

• brand.backlink_missingthe footer links back to agentjames.vercel.app
• brand.favicon_missingthe chip-mark favicon is reachable

• link.brokena crawled link resolves without a 4xx/5xx (or a GET retry confirms it genuinely 404/410s)
• link.offsite_redirecta same-origin link still resolves on its declared origin
• link.unverifiablea HEAD request that looked bot-blocked (403/406/429/999) stays inconclusive after one GET retry — not asserted broken

• weight.budget_exceeded/ transfer bytes stay within its declared budget

needs a sibling's own published schema + a deployed artifact to fetch against (SPEC §14 Q6 gates snapgauge's own liveness probe on this too)

• artifact.unreachablea sibling's published artifact fetches
• artifact.schema_invalida fetched artifact parses against its own published schema
• artifact.stalea fetched artifact is within its declared cadence

needs a scoped GitHub token (SPEC §14 Q3: fine-grained PAT vs GitHub App, undecided)

• repo.schedule_disableda sibling's scheduled workflow is still `active` (D4's 60-day rule)
• repo.schedule_overduea sibling's last scheduled run succeeded within cadence+slack
• repo.default_branch_reda sibling's default-branch CI is green

needs `npm i <pkg>@latest` + a smoke command in a clean temp dir — a real install step, not yet wired (SPEC §2)

• pkg.install_failed`npm i <pkg>@latest` + its smoke command succeed in a clean temp dir
• pkg.version_tag_mismatchthe published version matches the repo's release tag
• pkg.unexpected_publishno publish landed outside a tagged release
• pkg.deprecatedthe package is not marked deprecated on the registry

• watch.chain_gapthe audit sequence is contiguous across runs