Skip to content

Deploy hardening: block Claude from prod deploys#2

Open
johnpippett wants to merge 1 commit intomasterfrom
deploy-hardening
Open

Deploy hardening: block Claude from prod deploys#2
johnpippett wants to merge 1 commit intomasterfrom
deploy-hardening

Conversation

@johnpippett
Copy link
Copy Markdown
Owner

Summary

Mirrors LLMScout's 2026-04-20 deploy hardening, scoped to iscooked.

  • .claude/settings.json — PreToolUse hooks block wrangler prod deploys + direct pushes to the default branch
  • CLAUDE.md — cardinal rule: Claude never deploys iscooked; Jack runs the publishing runbook (vault 52.02) himself
  • scripts/hooks/pre-push + install.sh — stand-in branch protection

Why no Pages Git-integration migration

iscooked's blog content (site/blog/*) is gitignored. Git-connected Pages would never see new posts and would wipe them on every deploy. Direct Upload stays.

Test plan

  • Claude attempting a prod-branch wrangler deploy → blocked by repo hook
  • Claude attempting a push to the default branch → blocked by repo hook
  • Jack runs the publishing runbook from his own shell → unblocked
  • After merge + ./scripts/hooks/install.sh: direct push to default branch blocked locally

- .claude/settings.json: PreToolUse hooks block wrangler pages deploy
  against prod branches and direct pushes to the default branch
- CLAUDE.md: cardinal rule — Claude never deploys iscooked; Jack runs
  the publishing runbook (52.02) himself
- scripts/hooks/pre-push + install.sh: stand-in branch protection

Mirrors LLMScout 2026-04-20 hardening, scoped to iscooked's
Direct-Upload Pages setup. No Pages migration (blog content is
gitignored; Git integration would break publishing).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant