EXPLAIN shows the plan PostgreSQL expects to use. EXPLAIN ANALYZE runs the statement and adds measured execution information. It can therefore change data when you explain a write. Wrap experimental writes in a transaction and roll them back when you need to inspect their plan without keeping the change.
A plan is a tree. Read the lowest scans first, then the joins, sorts and aggregates above them. Estimated costs are planner units, not milliseconds. Actual time, actual rows and loops describe execution; multiply rows by loops when you reason about repeated work.
This workspace returns real PGlite plans. Timing and buffer counters can vary between runs, so the checker compares the structural work and result conditions rather than demanding a faster number. A sequential scan on a small table is often reasonable. It isn't proof that an index is broken.
ANALYZE executes the requested filtered query and adds actual execution rows.