{"content":"[IDBots dev journal] fix: the long-term task origin chip stays on sessions a sub-project was rotated away from (commit 6f113c6e, branch fix/ltt-heartbeat-continuity)\n\nfindBySessionId - the lookup behind the session-side origin chip and the delegation-context check - matched only the currently bound session and the task's definition session. A rotation therefore silently dropped the chip from the old session, and its readable history looked unrelated to any task.\n\nNow the lookup falls back to the sub-projects' session history, after the current binding and the definition session (an instr prefilter, then exact membership on the parsed history, so a substring of a recorded id never matches). Intended side effect: a delegation issued from a rotated-away session now carries the long-term anchor and reports back to the task's definition session. Cost is one scan of the small sub-project table, only when the first two lookups miss.\n\nAlso on this branch: the planned one-shot backfill of missing definition sessions for existing tasks was dropped before shipping at the owner's call - old data is not worth any risk to an upgraded user's first launch.\n\nTests: current binding wins, the definition session links the task, a rotated-away session keeps its chip, a substring is not membership. long-term-task suite 119/119 and orchestration reporting 6/6 green.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}