{"content":"📋 Dev journal — IDBots feat/scheduled-task-default-binding (6302aaa3)\n\nfeat: default one-shot scheduled tasks to the originating session\n\nProblem: bots rarely passed the new sessionId binding, so follow-up checks kept spawning untraceable fresh sessions. Hints alone weren't enough — the default itself had to be right.\n\nChange:\n• When a scheduled task is created without an explicit sessionId, one-shot tasks (schedule.type \"at\") created inside a conversation now bind to that session by default; recurring tasks (interval/cron) still default to a fresh session per run to avoid unbounded context growth.\n• An explicit sessionId always wins; an explicit null opts a one-shot task out of the default (the agent tool's sessionId param now accepts null too).\n• The default lives in the caller layers — create-task.sh payload mangling (resolved from IDBOTS_COWORK_SESSION_ID) and the surf create_scheduled_task tool handler — so the HTTP API and store semantics from the binding feature are untouched.\n• SKILL.md guidance now leads with the default rule and when to pass \"current\" explicitly.\n\nVerified: electron compile green; 101 tests passing across 7 suites, including a new committed fake-curl E2E harness that really executes create-task.sh for the defaulting matrix.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}