[luv-201] feat: add Infra Commands category with 7 opt-in policies (cuts 0.0.7)

[NiveditJain]

Summary

• Adds a new Infra Commands policy category with 7 opt-in policies that block infrastructure CLIs and CI/CD pipeline triggers: block-kubectl, block-terraform (terraform/tofu), block-aws-cli, block-gcloud, block-az-cli, block-helm, block-gh-pipeline.
• All seven default to defaultEnabled: false and accept an allowPatterns param that reuses the existing matchesAllowedPattern helper (inherits its shell-operator-injection defenses, verified by the block-sudo allowPattern test suite).
• block-gh-pipeline matches only mutating subcommands (workflow run/enable/disable, run rerun/cancel, pr merge, release create/delete, cache delete, secret set/delete). Read-only gh calls (gh pr view, gh run list, gh api ...) are intentionally allowed because failproofai's own workflow policies depend on them.
• Cuts the 0.0.7 release: bumps package.json from 0.0.7-beta.0 → 0.0.7 and rolls the ## Unreleased changelog section into ## 0.0.7 — 2026-04-27.

Built-in policy count: 32 → 39. All seven new policies live under the exospherehost/ namespace.

Test plan

• Unit tests: bun run test:run — 1043/1043 passing (added 41 tests across 7 new describe blocks)
• Lint: bun run lint — clean (only pre-existing <img> warning in tool-input-output.tsx)
• Typecheck: bunx tsc --noEmit — clean
• E2E: bun run test:e2e — 207/207 passing
• Local smoke test: failproofai p -i -c <custom> registers cleanly with new policies in the registry
• Docker clean-install (oven/bun:latest + npm install -g failproofai-0.0.7.tgz --ignore-scripts): version reports 0.0.7, custom hook validated, opt-in default behavior verified (kubectl invocation passes through when policy is disabled)
• Confirm block-gh-pipeline does NOT block read-only gh pr view, gh pr list, gh run list, gh api ... (covered by 4 explicit positive-allow tests)
• Shell-injection defense: kubectl get pods; rm -rf / with allowPatterns: ["kubectl get *"] is still denied (the existing matchesAllowedPattern operator check handles it; replicated test from block-sudo)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@NiveditJain has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 37 minutes and 17 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5cfa0628-8557-4f2f-a597-f8561be983e6

📥 Commits

Reviewing files that changed from the base of the PR and between fa53f75 and f4bb7cf.

📒 Files selected for processing (5)

• CHANGELOG.md
• __tests__/hooks/builtin-policies.test.ts
• docs/built-in-policies.mdx
• package.json
• src/hooks/builtin-policies.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch luv-201

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}