feat: remove state message retrieval and associated SQLite storage

readme.md

@@ -6,11 +6,10 @@ Repository: https://git.piskot.si/SeminarM2/lambdaiot-core
 
 ## Features ✅
 
-- HTTP API with health, greeting, auth, device CRUD, sensor creation, MQTT ping, and stored message retrieval
+- HTTP API with health, greeting, auth, device CRUD, sensor creation, and MQTT ping
 - JWT-based auth middleware with demo login (`admin`/`password`)
-- MQTT client with startup publish and best-effort subscription to persist `state:` topics into SQLite
-- SQLite sidecar (file) for recent MQTT state messages
-- Multi-stage `Dockerfile` (CGO-enabled for sqlite3) and `Makefile` for common tasks
+- MQTT client with startup publish and best-effort subscription
+- Multi-stage `Dockerfile` and `Makefile` for common tasks
 - `test/docker-compose.yml` spins up MySQL, Mosquitto, phpMyAdmin, and the server for local integration
 
 ---
@@ -66,7 +65,6 @@ The compose file seeds the database from `ai-improved.sql` and exposes:
 - Actors (JWT): `GET /actors`, `GET /actors/:id`, `POST /actors`, `PUT /actors/:id`, `DELETE /actors/:id`
 - Sensor readings (JWT): `GET /sensor-readings`, `GET /sensor-readings/:id`, `POST /sensor-readings`, `PUT /sensor-readings/:id`, `DELETE /sensor-readings/:id` (optional `sensor_id` filter and pagination via `limit`, `page`)
 - `GET /mqttping` — publish timestamp to MQTT default topic (JWT)
-- `GET /messages` — last stored MQTT state messages from SQLite (JWT)
 
 ### Environment