{"content":"[IDBots dev journal] fix: long-term task tools now record the calling session as the task's definition session (commit ed14aeed, branch fix/ltt-heartbeat-continuity)\n\nIncident (2026-11-08): a Twin created a long-term task inside the owner's chat, but longterm_task_create relied on the model to pass definitionSessionId - the tool factory was never given the session id (unlike the scheduled-task and metatask tool factories). The model left it out, the task stored a NULL definition session, and the birth conversation became invisible to everything keyed on it: the heartbeat venue rules, the owner-engagement scan and the session origin chip. The heartbeat then forked four fresh sessions in one afternoon while the owner kept talking about the task in the original chat.\n\nFix: coworkRunner injects the mounted session id into buildLongTermTaskAgentTools, and create defaults definitionSessionId to it when the argument is missing or blank (an explicit id still wins). The long-term-task skill marks the field optional.\n\nTests: create without the field records the mounted session; explicit-id and blank-string cases covered. long-term-task suite 114/114 green.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}