# docs: explain legacy thread migration · pingdotgg/t3code

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

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

Visibility: public

Requested revision: b991834aeff5102be46694d5af81cf6749da898c

Requested commit: b991834aeff5102be46694d5af81cf6749da898c

Commit: b991834aeff5102be46694d5af81cf6749da898c

Tree: 672c97e43e5c712bfdc94a232562ff4b9ef5485a

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

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

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