Sync Kaizen dogfood contracts

.github/ISSUE_TEMPLATE/kaizen.yml

@@ -1,5 +1,5 @@
 name: "Kaizen improvement"
-description: Request a fix or improvement for the nightly maintenance agent
+description: Request a fix or improvement for the Kaizen Agents organization
 labels: ["kaizen"]
 body:
   - type: textarea

skills/kaizen-bug-router/SKILL.md

@@ -12,8 +12,10 @@ When a Kaizen Agents bug is reported, investigate where the bug originates befor
 ## Repository Routing
 
 - `kaizen-agents-org/builder-agent`: builder execution, build request/result contracts, Codex/Claude backend invocation, self-review, implementation output, builder artifacts, or generated change quality before verifier review.
-- `kaizen-agents-org/verifier`: verifier execution, verdict schemas, approval/rejection logic, verification prompts, risk evaluation, or verifier result artifacts.
+- `kaizen-agents-org/verifier`: verifier execution, verdict schemas, MVP verdict statuses (`open_pr`, `open_pr_with_warning`, `block_pr`, `needs_context`), `must_fix`/`should_fix` semantics, approval/rejection logic, verification prompts, risk evaluation, or verifier result artifacts.
 - `kaizen-agents-org/kaizen-loop`: issue selection, labels, scheduling, registry/config loading, orchestration, retry loops, workspace/git handling, GitHub issue/PR operations, reflection policy, protected path handling, comments, or cross-agent handoff.
+- `kaizen-agents-org/coderabbit`: CodeRabbit configuration, review policy, automated review rules, or review feedback behavior owned by the shared CodeRabbit setup.
+- `kaizen-agents-org/renovate-config`: Renovate presets, dependency update policy, package rule behavior, or shared dependency automation configuration.
 - `kaizen-agents-org/.github`: org-level shared docs, issue templates, reusable skills, PR/issue linking guidance, or org configuration.
 
 Use `kaizen-loop` as the fallback when symptoms span multiple projects or the available evidence does not isolate a clearer owner.
@@ -33,10 +35,18 @@ Use `kaizen-loop` as the fallback when symptoms span multiple projects or the av
 
    ```sh
    gh label list --repo kaizen-agents-org/<repo> --limit 200
-   gh issue create --repo kaizen-agents-org/<repo> --title "<title>" --body-file <body-file> --label kaizen
+   gh issue create --repo kaizen-agents-org/<repo> --title "<title>" --body-file <body-file>
    ```
 
-Only pass `--label` values that exist. Prefer `kaizen` so the issue can enter the Issue-to-PR MVP; also add `bug` if that label exists. If no useful labels exist, create the issue without labels rather than blocking.
+Only pass `--label` values that exist. Prefer `bug` for ordinary bug reports and add the base `kaizen` label by default when it exists. Treat `kaizen` as a visibility/routing label, not execution authorization. If no useful labels exist, create the issue without labels rather than blocking.
+
+Issue creation and execution authorization are separate:
+
+- Add `kaizen` by default when the label exists, but do not add `kaizen:ready` or any other execution-selection label by default.
+- Add the execution authorization label only when the user asks to queue, approve, run, execute, or put the issue on the Kaizen Loop.
+- In opt-in selection mode, prefer `kaizen:ready` as the execution authorization label when it exists.
+- If the user asks for immediate execution, file the issue, add the execution authorization label when available, then report the explicit command that should run next, such as `kaizen fix <issue>`.
+- If the issue needs human clarification before automation, prefer `kaizen:needs-human` instead of `kaizen:ready`.
 
 ## Issue Body