Addresses planner-audit #8. `listSessions()` had no LIMIT — every call to `GET /api/sessions` returned every non-closed session and did a full table scan ordered by last_activity. On a long-running planner host that's both a memory cliff and a query-plan footgun. Now: defaults to 50 rows, clamps to [1, 200], accepts `?limit=` for pagination-light scenarios. `sessions_last_activity_idx` (added in #438) backs the ORDER BY + LIMIT efficiently. |
||
|---|---|---|
| .. | ||
| journal | ||
| mobile | ||
| planner | ||