# docs: explain legacy thread migration · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/652fe9c9e102a7f9e1b3c7f6bc19fdc0872b3608)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 652fe9c9e102a7f9e1b3c7f6bc19fdc0872b3608

Requested commit: 652fe9c9e102a7f9e1b3c7f6bc19fdc0872b3608

Commit: 652fe9c9e102a7f9e1b3c7f6bc19fdc0872b3608

Tree: 4b0f214ae9077de88c7b7c3c44c08a4c61d0c1fb

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
docs: explain legacy thread migration

Document which thread metadata and transcript data migrate, which runtime history does not, and how the fresh provider continuation uses the latest 32,000 characters. Add a safe read-only recovery procedure without claiming an export API.

Audit: D02

Written by GPT-5.6 Sol with Codex.

```

## Parents

- [9a2e7ede014df1573a2b5226737ef2725e5c7d2f](https://git.cafe/pingdotgg/t3code/commit/9a2e7ede014df1573a2b5226737ef2725e5c7d2f?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/652fe9c9e102a7f9e1b3c7f6bc19fdc0872b3608?format=markdown)