Update series 6 blogs: fix 6.3 narrative, resolve duplicate 6.5 numbering

Author: workcontrolgit

blogs/series-6-ai-app-features/6.3-angular-ai-chat-widget.md

@@ -1,8 +1,8 @@
 # Build a Dedicated AI Section in Angular with Submenu Navigation
 
-## How to Refactor a Tabbed Widget into Four Focused Standalone Pages
+## How to Build Four Focused Standalone Pages with Sidebar Sub-Menu Navigation
 
-A single component with tabs works well for two modes. It breaks down at four. This article refactors the TalentManagement Angular app's AI features from a single `ai-chat` route with tabs into a proper **AI submenu** — four dedicated pages, each with a single responsibility, registered as children of an `ai` route group in the sidebar.
+AI features deserve their own section. This article adds a proper **AI submenu** to the TalentManagement Angular app — four dedicated pages, each with a single responsibility, registered as children of an `ai` route group in the sidebar. Each page is a standalone Angular component with its own route, template, and styles.
 
 ![AI Submenu — Four dedicated AI pages in Angular Material sidebar](https://raw.githubusercontent.com/workcontrolgit/AngularNetTutorial/master/docs/images/angular/application-dashboard-anonymous.png)
 
@@ -192,7 +192,7 @@ src/app/routes/ai/
 
 #### AI Assistant Component
 
-This page extracts the "General Chat" tab from the original `ai-chat` page and gives it a dedicated route.
+This page provides general-purpose chat with the LLM at a dedicated route.
 
 **`ai-assistant.component.ts`:**
 
@@ -274,15 +274,15 @@ export class AiAssistantComponent implements OnDestroy {
 
 **Key design decisions:**
 
-* **Extracted from the old `AiChatComponent` General Chat tab** — All the chat logic moved here unchanged. The only difference is the selector name and that it's no longer wrapped in a `MatTabGroup`.
+* **Single responsibility** — This component handles only the general chat flow. HR Insight, NL Search, and Vector Search each live in their own component.
 * **`private destroy$ = new Subject<void>()`** — The `takeUntil` pattern ensures in-flight Ollama requests are cancelled cleanly when the user navigates away.
 * **State is scoped to this component** — Navigating to HR Insight and back does not clear the chat history here.
 
 ---
 
 #### HR Insight Component
 
-Extracts the "HR Insights" tab. Full implementation follows the same pattern as AI Assistant — replace `chat()` with `hrInsight()` and add the suggestion chips.
+Provides data-aware chat grounded in live workforce metrics. Full implementation follows the same pattern as AI Assistant — replace `chat()` with `hrInsight()` and add the suggestion chips.
 
 The `ai-hr-insight.component.ts` structure is identical to AI Assistant, differing only in:
 * Calls `aiService.hrInsight(question)` instead of `aiService.chat(message)`
@@ -435,18 +435,18 @@ public/
 
 ## 📊 Real-World Impact
 
-**Before this article:**
+**Without this structure:**
 
-* ❌ One page with two tabs — grows unmanageable as AI features are added
-* ❌ Single route `/ai-chat` — no URL structure for bookmarking or deep linking
-* ❌ All AI features in one file — a change to HR Insight breaks the General Chat component
+* ❌ A flat sidebar link gives AI one entry point — no room to grow
+* ❌ Mixing AI features in a single component creates tight coupling — a change to HR Insight risks breaking General Chat
+* ❌ No URL structure for bookmarking or deep linking into specific AI tools
 
-**After this article:**
+**With this structure:**
 
 * ✅ Four focused pages — each component is ~80 lines, easy to read and test independently
 * ✅ Clean URL structure — `/ai/assistant`, `/ai/hr-insight`, `/ai/nl-search`, `/ai/vector-search`
 * ✅ Sidebar group — users discover all four AI features naturally via the collapsible sub-menu
-* ✅ Zero breakage — the backward-compat redirect keeps existing bookmarks working
+* ✅ Backward-compat redirect — any old `/ai-chat` bookmarks silently redirect to `/ai/assistant`
 
 ---
 
@@ -481,7 +481,8 @@ The refactoring from tabs to child routes mirrors how any growing feature sectio
 * [Run a Local LLM in Your .NET 10 API with Ollama](6.1-dotnet-ai-foundation.md) — AI Foundation (Series 6.1)
 * [Build an HR AI Assistant That Knows Your Data](6.2-dotnet-ai-hr-assistant.md) — HR AI Assistant (Series 6.2)
 * **This Article** — Build a Dedicated AI Section in Angular with Submenu Navigation (Series 6.3)
-* [Natural Language Employee Search in Angular Material](6.4-angular-ai-nl-search.md) — NL Search (Series 6.4)
+* [Natural Language Employee Search in Angular Material](6.4-angular-ai-nl-search.md) — NL Search Angular (Series 6.4)
+* [Natural Language Employee Search with LLM Query Parsing](6.4.1-dotnet-natural-language-search.md) — NL Search .NET backend (Series 6.4.1)
 * [Semantic Position Search with Vector Embeddings](6.5-angular-ai-vector-search.md) — Vector Search (Series 6.5)
 
 ---

blogs/series-6-ai-app-features/6.4-angular-ai-nl-search.md

@@ -31,10 +31,10 @@ This article is part of the **AngularNetTutorial** series. The full-stack tutori
 * **Article 6.1 complete** — `POST /api/v1/ai/chat` endpoint working
 * **Article 6.2 complete** — `POST /api/v1/ai/hr-insight` endpoint working
 * **Article 6.3 complete** — AI submenu in place, `ai-nl-search` component scaffolded, `AiService` with `nlEmployeeSearch()` method
-* **Article 6.5 (.NET) complete** — `POST /api/v1/ai/nl-employee-search` endpoint working (the backend for this feature)
+* **Article 6.4.1 (.NET) complete** — `POST /api/v1/ai/nl-employee-search` endpoint working (the backend for this feature)
 * **`AiEnabled: true`** in the API's `appsettings.json` for local testing
 
-> **Note:** The .NET endpoint for natural language employee search is documented in Article 6.5. If you are following this article first (to understand the Angular side), you can still build and run the component — it will show an error until the API endpoint exists.
+> **Note:** The .NET endpoint for natural language employee search is documented in Article 6.4.1. If you are following this article first (to understand the Angular side), you can still build and run the component — it will show an error until the API endpoint exists.
 
 ---
 

…es/6.5-dotnet-natural-language-search.md …/6.4.1-dotnet-natural-language-search.mdblogs/series-6-ai-app-features/6.5-dotnet-natural-language-search.md renamed to blogs/series-6-ai-app-features/6.4.1-dotnet-natural-language-search.md blogs/series-6-ai-app-features/6.5-dotnet-natural-language-search.md renamed to blogs/series-6-ai-app-features/6.4.1-dotnet-natural-language-search.md

@@ -747,9 +747,9 @@ Using an LLM as a **query translator** — input: natural language, output: stru
 * [Building Modern Web Applications with Angular, .NET, and OAuth 2.0](https://medium.com/scrum-and-coke/building-modern-web-applications-with-angular-net-and-oauth-2-0-complete-tutorial-series-7ea97ed3fc56) — Main tutorial
 * [Run a Local LLM in Your .NET 10 API with Ollama](6.1-dotnet-ai-foundation.md) — AI Foundation (Series 6.1)
 * [Build an HR AI Assistant That Knows Your Data](6.2-dotnet-ai-hr-assistant.md) — HR AI Assistant (Series 6.2)
-* [Add an AI Chat Widget to Angular with Material Design](6.3-angular-ai-chat-widget.md) — AI Chat Widget (Series 6.3)
-* [AI-Generated Dashboard Insights in Angular Material](6.4-angular-ai-dashboard-insights.md) — Dashboard Insights (Series 6.4)
-* **This Article** — Natural Language Employee Search with LLM Query Parsing (Series 6.5)
+* [Build a Dedicated AI Section in Angular with Submenu Navigation](6.3-angular-ai-chat-widget.md) — AI Submenu (Series 6.3)
+* [Natural Language Employee Search in Angular Material](6.4-angular-ai-nl-search.md) — NL Search Angular (Series 6.4)
+* **This Article** — Natural Language Employee Search with LLM Query Parsing (Series 6.4.1 — .NET backend for 6.4)
 * [Cache Your AI Responses: Save Time and API Costs](6.6-dotnet-ai-response-caching.md) — AI Response Caching (Series 6.6)
 
 ---