fix: changelog

Author: CodeMeAPixel

CHANGELOG.md

@@ -109,73 +109,3 @@ Endpoints:
   - And more...
 - Proper error handling (400/403/404)
 - File metadata (size, language, path)
-
-Endpoints:
-- `GET /api/source` - Read source files with syntax detection
-
-#### Project Structure
-- `internal/services/` - Business logic layer
-- `internal/handlers/` - HTTP request/response handling
-- `internal/routes/` - Route registration and Swagger docs
-- `docs/` - Auto-generated Swagger specification
-- `Makefile` - Build automation and common tasks
-- `go.mod` - Dependency management
-- `README.md` - Project documentation
-- `DEVELOPMENT.md` - Development setup guide
-
-#### DevOps & Tooling
-- Makefile with targets:
-  - `make install` - Install dependencies and tools
-  - `make build` - Build Go binary
-  - `make dev` - Run with hot-reload (air)
-  - `make run` - Run compiled binary
-  - `make test` - Run tests
-  - `make swagger` - Generate Swagger docs
-- GitHub Actions CI/CD pipeline
-- Docker support (Dockerfile included)
-- `.env.example` - Environment configuration template
-
-#### Documentation
-- `README.md` - Quick start and API reference
-- `DEVELOPMENT.md` - Development environment setup
-- `BACKEND_MIGRATION.md` - Migration guide from Next.js
-- `BACKEND_SETUP.md` - Detailed setup instructions
-- `CHANGELOG.md` - This file
-
-### Technical Details
-
-#### Dependencies
-- `github.com/gofiber/fiber/v2` v2.52.0 - Web framework
-- `github.com/swaggo/swag` v1.16.0 - Swagger documentation
-- `github.com/swaggo/files` v1.0.1 - Swagger UI files
-- `github.com/joho/godotenv` v1.5.1 - Environment variables
-
-#### Architecture
-- **Service Pattern**: Business logic encapsulated in services
-- **Handler Pattern**: HTTP concerns handled separately
-- **Middleware**: CORS, logging, error handling
-- **Error Handling**: Consistent error responses with proper status codes
-- **Caching**: In-memory cache with TTL (ready for Redis migration)
-- **API Versioning**: Prepared for future API versioning
-
-### Performance Features
-- In-memory caching with intelligent TTL management
-- Efficient filtering and sorting algorithms
-- Pagination to prevent large response payloads
-- Relevance-based search scoring
-
-### Security Features
-- CORS enabled for development (can be configured)
-- Path validation for file serving
-- Input validation on all endpoints
-- Structured logging for debugging
-- Proper HTTP status codes for security (403, 404, etc.)
-
-### Known Limitations
-- In-memory cache (no persistence across restarts)
-- No authentication/authorization yet
-- Search endpoint uses Next.js backend (to be migrated)
-- No rate limiting
-- Health check is basic (ready to enhance)
-
----