another step just a little remaining

server/README.md

@@ -2,14 +2,15 @@
 
 Backend API for the Balinyaar application. It is an **ASP.NET Core (.NET 10)** solution organized around **Clean Architecture**, with:
 
-- **CQRS** via MediatR (source-generated)
+- **CQRS** via `martinothamar/Mediator` (source-generated; not MediatR)
 - **ASP.NET Core Identity** with **JWE** (signed + encrypted JWT) and **OTP** authentication
 - **Dynamic, permission-based authorization**
 - **EF Core** persistence (SQL Server) with the Repository + Unit of Work patterns
 - A modular **gRPC plugin** mounted via Application Parts
 - Observability out of the box: Serilog, OpenTelemetry, Prometheus metrics, health checks
 
-> Looking for an architecture/file map to navigate the code? See [AGENTS.md](AGENTS.md).
+> Looking for an architecture/file map to navigate the code? See [CLAUDE.md](CLAUDE.md) (agent guide)
+> and [CONVENTIONS.md](CONVENTIONS.md) (coding rules).
 
 ## Requirements
 
@@ -85,7 +86,7 @@ The core of the project. Each entity may carry its own behavior. Entities derive
 
 ### Application
 
-Routes requests and defines the **contracts** (interfaces) the system depends on, without knowing their implementations. This is where **CQRS** lives: Commands and Queries are kept separate and dispatched to their handlers by **MediatR**. Cross-cutting concerns (validation, metrics) are applied as MediatR pipeline behaviors.
+Routes requests and defines the **contracts** (interfaces) the system depends on, without knowing their implementations. This is where **CQRS** lives: Commands and Queries are kept separate and dispatched to their handlers by **Mediator** (`martinothamar/Mediator`, source-generated). Cross-cutting concerns (validation, metrics) are applied as Mediator pipeline behaviors.
 
 ### Infrastructure