This Pull Request implements the complete **Retrieval module (Read Path)** for the Knowledge-Map RAG (KM-RAG) architecture within the NexusReader platform. It resolves all requirements for vector-based semantic search, Neo4j graph context expansion, structured grounding with Google Gemini, API/Wasm integration, and an interactive front-end global Q&A panel.
Resolves#48
### 🚀 Key Implementations
1. **Grounded DTOs & Schema Definition**
- Added `GroundedResponseDto` and `CitationDto` for strict JSON Schema matching with Gemini.
2. **Core Service & Read Path Logic**
- Implemented the robust **5-step pipeline** in `KnowledgeService.AskQuestionAsync`:
1. *Embedding*: Query vectorization using `IEmbeddingGenerator`.
2. *Semantic Search*: Multi-tenant vector search with Qdrant, supporting scoping to a specific book or global search.
3. *Graph Expansion*: Fetching connected concepts and parent relationships using Neo4j Cypher.
4. *Citation Hydration*: Cross-referencing results with PostgreSQL to fetch book titles and accurate chapter citations.
5. *Grounded Generation*: Strict structured generation via `IChatClient` (Gemini) preventing hallucinations and using citations.
3. **CQRS & Endpoints**
- Added `AskLibraryQuestionQuery` and its handler.
- Mapped `/api/knowledge/ask` and `/api/knowledge/search` endpoints inside `Program.cs`.
- Updated `WasmKnowledgeService` to support proxying retrieval requests.
4. **Premium Blazor UI Panel**
- Implemented `/intelligence` (Global AI Q&A) with a curated HSL palette, dark theme, smooth micro-animations, loading shimmers, and side-by-side citation cards.
- Registered the panel within the `MainHubLayout` sidebar.
5. **Test Coverage**
- Wrote comprehensive xUnit tests in `QueryTests.cs` using Moq and FluentAssertions to assert that handlers correctly validate input and interact with services.
### 🧪 Verification
- Verified compilation and build gate successfully (`dotnet build`: 0 errors).
- All 7 tests passed perfectly (`dotnet test`).
---------
Co-authored-by: Marek Jasiński <jasins.marek@gmail.com>
Reviewed-on: #49
Reviewed-by: Marek Jaisński <jasins.marek@gmail.com>
Co-authored-by: Antigravity <antigravity@google.com>
Co-committed-by: Antigravity <antigravity@google.com>
This PR finalizes the implementation of issue #35 by establishing a formal foreign key relationship between `KnowledgeUnit` and `Ebook`.
Closes#35
### Changes:
- **Domain**: Refactored `KnowledgeUnit` to use `Guid EbookId` and added navigation property.
- **Data**: Updated `AppDbContext` fluent configuration and generated a new migration.
- **Service**: Updated `IKnowledgeService` and its implementations to propagate `ebookId`.
- **API**: Updated Web API endpoints to support linking extracted knowledge to specific ebooks.
### Verification:
- [x] Solution builds successfully (`dotnet build`).
- [x] Schema changes verified in migration file.
- [x] Cascading delete behavior confirmed.
---------
Co-authored-by: Marek Jasiński <jasins.marek@gmail.com>
Reviewed-on: #43
Co-authored-by: Antigravity <antigravity@google.com>
Co-committed-by: Antigravity <antigravity@google.com>
Antigravity
mjasin