diff --git a/.kaizen/config.yml b/.kaizen/config.yml index 1ba8a88..6c49e2b 100644 --- a/.kaizen/config.yml +++ b/.kaizen/config.yml @@ -13,16 +13,31 @@ run: maxAttemptsPerIssue: 3 latestStartHour: 7 scheduler: - nightly: - enabled: true - time: "01:45" - afternoon: - enabled: true - time: "13:45" - poll: - enabled: false - intervalMinutes: 5 - skipIfRunning: true + jobs: + maintenance: + enabled: true + schedule: + type: daily + time: "01:45" + run: + mode: maintenance + lateStartGuard: true + maintenance-followup: + enabled: true + schedule: + type: daily + time: "13:45" + run: + mode: maintenance + lateStartGuard: false + issue-watch: + enabled: false + schedule: + type: interval + everyMinutes: 5 + run: + mode: watch + skipIfRunning: true commands: setup: null verify: diff --git a/skills/kaizen-bug-router/SKILL.md b/skills/kaizen-bug-router/SKILL.md index 555a7d6..9dc1400 100644 --- a/skills/kaizen-bug-router/SKILL.md +++ b/skills/kaizen-bug-router/SKILL.md @@ -44,9 +44,9 @@ 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. +- In opt-in selection mode, add the repository's configured execution authorization label only 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 `. -- If the issue needs human clarification before automation, prefer `kaizen:needs-human` instead of `kaizen:ready`. +- If the issue needs human clarification before automation, do not add an execution authorization label; state what clarification is needed. ## Issue Body