{"version":"2.1.221","anchor":"teammate-respawn-records-transcript-restoration-and-first-pa","canonical_anchor":"teammate-respawn-records-transcript-restoration-and-first-pa","heading":"Teammate respawn records transcript restoration and first-paint marks","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/teammate-respawn-records-transcript-restoration-and-first-pa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Teammate respawn records transcript restoration and first-paint marks\n\nResumed teammate sessions now replay first-paint marks to clients that attach, so reattaching looks right.\n\n**What**\n\nThe dispatch record now states explicitly whether a launch restores a transcript, and attaching clients get replayed interactivity marks.\n\n**Details**\n\n- The launch payload gained an optional `restoresTranscript` boolean for both prompt and resume modes, persisted in the session schema.\n- Workers derive `bootedViaResume` from that flag instead of sniffing the argv for `--resume`.\n- A `firedInteractiveMarks` array is persisted and replayed to attaching clients: entries of kind `content_paint` or `prompt_idle` carrying `msgsLoaded`, `msgsInJsonl` and `msgsRenderedAtFirstPaint`, capped at two.\n- Attach responses now carry an `imarkNonce` and a `booting` flag.\n\n**Evidence**\n\n`msgsRenderedAtFirstPaint`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}