Read Committed is PostgreSQL's default isolation level. Each statement takes a new snapshot of committed data. Two SELECT statements in the same transaction can therefore observe different committed values. A transaction always sees its own previous writes.
Repeatable Read uses a stable transaction snapshot established by its first relevant statement. PostgreSQL also prevents phantom reads at this level, but it can still allow a serialization anomaly. Serializable detects unsafe interactions and can abort a transaction that the application must retry in full. Read Uncommitted behaves as Read Committed in PostgreSQL.
PGlite has one connection. The labeled session workspace below uses a deterministic model of these rules for numeric account rows; it doesn't create two live PostgreSQL sessions. The traces expose reads, commits and waits. Use that model to reason about a schedule, and treat production concurrency tests as a separate integration task.
Read Committed takes a new snapshot for the second SELECT after B commits.