Reassigning a task only rewrites a column on `tasks`, so nothing records
who moved it or when. Add an append-only event table alongside the other
task-child tables: one row per change, carrying the actor (user or agent)
and the ids the slot moved between.
`type` is a plain text column typed through `.$type<>()`, so onboarding a
new event kind — status, priority, … — is a type-only change rather than
a migration. `visibility` mirrors the parent task the same way
`task_topics` / `task_comments` do, so ownership filters without joining
back to `tasks`, and the public → private demotion cascade covers it too.
Claude-Session: https://claude.ai/code/session_015wKZMihFpqsChKSb5YR23P
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Rdmclin2