cc-safety-net

<!-- Keep the workflow below in sync with src/opencode/builtin-commands/templates/cc-safety-net.ts. --> ## Workflow Help the user configure custom blocking rules for CC Safety Net. Use information already provided in the user's prompt. Ask only when the scope, action, rule intent, merge behavior, or target command is unclear. 1. Run `npx -y cc-safety-net rule doc` and treat that output as the complete source of truth for schema, paths, GitHub sources, matching behavior, and validation. 2. Determine the requested scope from the prompt when possible: - User: applies to all projects. - Project: applies only to the current project. - GitHub: edits or creates a shareable rulebook structure in the current repository. 3. Determine whether to add a rule, edit a rule, disable a rule, override a reason, migrate legacy rules, or explain custom rules from the prompt when possible. 4. Inspect existing configs before modifying installed local rules: - Run `npx -y cc-safety-net rule verify` - Run `npx -y cc-safety-net rule list` 5. Inspect relevant project files only when the user asks for rule suggestions or the requested rule depends on project context. Look at manifests, scripts, task runners, CI, infrastructure, database, migration, and deployment files that explain risky commands. 6. Convert the request into valid CC Safety Net JSON using `rule doc`. - For User or Project scope, add or edit the selected local `rule.json` and `<rulebook-name>/rulebook.json`. - F...