Get the session log

The settled record of a migration: what was planned, which files went in, who approved what, how many rows were written, and whether existing rows were replaced.

Intended to be fetched once and stored, so you can explain a migration to your own customer later. It does not include the conversation transcript — that is /thread — and it does not include individual row values.

Available once nothing is in flight, including for migrations that failed: a run can write rows and then fail, which is exactly when this matters. While a run is active the endpoint returns 409.

Pass ?format=md for the same record as a readable Markdown report.

A migration can be imported again later, so the log always covers every run to date — a re-fetch is a superset of an earlier one. Use generated_at to tell snapshots apart.