Pagination contract is not standardized across endpoints

Docs/Tasks.md

@@ -1,22 +1,3 @@
-## 25) No canonical snake_case/camelCase serialization policy
-- Where found:
-	- [backend/app/models/server.py](backend/app/models/server.py)
-	- [frontend/src/types/server.ts](frontend/src/types/server.ts)
-- Why this is needed:
-	- Naming convention drift causes brittle frontend-backend contracts.
-- Goal:
-	- Enforce one API field naming policy.
-- What to do:
-	- Configure model aliasing strategy and update frontend contracts.
-- Possible traps and issues:
-	- Partial migration can leave mixed payload formats.
-- Docs changes needed:
-	- Add naming convention section for API fields.
-- Doc references:
-	- [Docs/Backend-Development.md](Docs/Backend-Development.md)
-	- https://docs.pydantic.dev/latest/concepts/alias/
-
----
 
 ## 26) Pagination contract is not standardized across endpoints
 - Where found: