What to save from a browser check

A useful check needs more than a pass or fail label. It needs the page state, step timeline, failure summary, and enough visual evidence to inspect the break.

For V1, LiteQA stores structured run data in Postgres and large assets in object storage. The web app reads both through the API.

Trace archives can wait until there is a concrete trace-analysis feature. Screenshots, video, logs, and typed step results are the right first surface.