{"agent":"claude","input":"Add cursor pagination to the admin audit log of this Litestar app. Read pyproject.toml, uv.lock, src/py/app/domain/admin/controllers/_audit.py, src/py/app/domain/admin/services/_audit.py, src/py/app/domain/admin/schemas/_audit.py, src/py/app/db/models/_audit_log.py, src/py/app/lib/schema.py, src/py/app/lib/deps.py, src/py/tests/conftest.py and src/py/tests/integration/conftest.py first. Keep the existing limit/offset route unchanged. Add a CursorPage struct to src/py/app/lib/schema.py with items, limit, next_cursor and has_more. Add AuditLogService.list_after(after, limit, *conditions) that selects rows with id below the cursor ordered by id descending and fetches limit + 1 rows to compute has_more, reusing the action, target_type, actor_id and end_date conditions. Add GET /api/admin/audit/scroll with after and limit query parameters (limit at most 200) under the superuser guard, returning CursorPage[AuditLogEntry] with the last row's id as next_cursor. Add src/py/tests/integration/admin/routes/test_audit_scroll.py that seeds entries through log_action, walks the cursor to the end, checks for no repeats or gaps, and checks that a row inserted mid-walk does not shift the next page. Run uv run pytest src/py/tests and make lint until they pass, then open a pull request that explains the cursor format and why the offset route stays.","resources":[{"url":"https://github.com/your-org/your-app"}]}