BINKY-WP-0004-T01: kaizen schedule opt-in + executor ownership decision

- .kaizen/schedule.yml scaffolded via schedule init, validates clean
  (coach + optimization weekly, tdd-workflow disabled)
- DEC-2026-002 prepared: executor worker in a new small repo, per
  ADR-005 boundaries; fallback allows sandbox prototype, no cutover
  before resolution
- Decision rationale recorded in the executor assessment

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

integrations/llm-connect-executor-assessment.md

@@ -97,6 +97,16 @@ Ownership note: items 1–5 span activity-core / kaizen-agentic / secrets-
 engine domains; the follow-up workplan in binky-control should track them
 as dependencies, with the implementation workplans living in those repos.
 
+## Ownership decision (2026-07-17, BINKY-WP-0004-T01)
+
+Recommendation recorded as **DEC-2026-002**: the executor worker lives in a
+**new small repo**, not inside activity-core or kaizen-agentic. ADR-005's
+boundaries exclude LLM invocation from both existing repos and explicitly
+defer "headless Claude Code / cloud agent runner integration" as a future,
+runner-agnostic concern — that future runner is exactly this worker.
+binky-control opted into kaizen scheduling on the same date
+(`.kaizen/schedule.yml`, coach + optimization weekly, tdd-workflow off).
+
 ## Verdict
 
 Feasible and well-aligned: every layer already exists or is an active