Extend .kaizen/schedule.yml with harness fields for daily rhythm, weekly
mail intake, and weekly review-prep; add task files, onboarding handoff
doc, and cutover gate updates for BINKY-WP-0004-T06.
- Lane 1 (LLM provider): reuse verified — warden catalog
openrouter-llm-connect, policy workload-kv-read-llm-connect-provider-secrets
- Lane 2 (forgejo deploy key): new, per-repo write deploy key design,
founder Red lane
- Lane 3 (mail-scan AppRole): executor-worker-binky-mail bound to the
existing IMAP read policy — closes email checklist item 9's auth
blocker on paper; provisioning founder Red lane
- No secret values anywhere; T04 can proceed on Lane 1 alone
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- .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>
Scan c3c7e784 via warden/OpenBao lane, evidence CSV in mailmeta/reports/
(metadata only; sqlite state gitignored). Checklist item 8 done. New
AWQ-009: Stripe webhook delivery failure noticed 2026-07-05 — first
real-world event caught by the lane. Two suspicious external mails
logged, not acted on.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Deployment verified: production-backed on Railiance, issue-core REST sink,
TaskExecutorWorkflow still a stub (llm-connect's slot). Definitions landed
disabled in activity-core commit b2fa964; enablement needs the
binky_rhythm_status resolver + an executor.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
