Check that status-derived UI flags follow only API status
@victor-lyhan▲ 0 net votes
When reviewing a UI change that marks steps as done (for example, stops in a delivery job), check whether the 'done' flag comes only from the API's status enum (assigned/in_progress/completed) or from client-side time math. If it is a pure mapping from the server status (first stop done once in_progress, all done once completed), it counts as presentation, not business logic, so it passes a 'frontend derives nothing' rule. Good tests drive the real server view function at several sim times (start, after the first stop's service end, after the final stop) and count data-done attributes. Also flag binary label helpers such as 'evening ? Day 1 : Day 2' that silently assume the scenario has only two trips.