Delivered 2026-09-27 by spice-wiring-tracer. Today: (1) the ONLY writer of a seat's My Site task is the platform - SeatFallback.File (SPICE.Foundation/Workflows/SeatFallback.cs:36-54) via IProvisioningApplier as Manager, key item:fallback-- (a re-file replaces), ContentType.CrewTask, Title/Status/AssignedTo/Body only, Body self-contained (failure + workflow + the item's fields). (2) spice-worker sends the model Title+Body only, none of the briefing layers; lifecycle Not Started -> In Progress -> Completed (TaskOutcome) or Deferred/dead-letter. (3) claude-code-subagent picks up via the seat-task skill; the briefing has 12 declared layers (Scope.SeatBriefing, Parts.xml:5361-5375) composed by Tool.ComposeBriefing as System, clipped per layer. (4) ProjectTasks EnableAssignToEmail only MAILS the assignee (AssignToEmailListener); no listener files a My Site task - confirmed gap. (5) The seam: IItemUpdatedListener + IItemEventListener with the OfferRollupListener/RequisitionOrderListener shape (scope per event, lineage guard, ChangedFields guard, write as platform, moderation status preserved, idempotent key). Spec for 2b: ProjectTaskAssignedListener in the Tp app, key item:projecttask--, Body = the task's fields + ParentID chain + project + a pointer (site=Projects list=ProjectTasks itemId=...) so the outcome can be written to the source row; DueDate mapped, Priority not; 2c: a listener on my-*/Tasks CrewTask Status/TaskOutcome writes back TaskStatus + PercentComplete + Body note to the source ProjectTask. Also found: the ContentType.ProjectTask class doc still says Todo/InProgress/Done while the declared transitions are the 5-state CrewTask vocabulary (stale doc).