feat: add knowledge management functionality with CRUD operations and database schema

- Implemented KnowledgeHandler for managing knowledge groups and items, including listing, creating, updating, and deleting operations.
- Added database migration scripts to create necessary tables for knowledge management, including knowledge_groups, knowledge_items, knowledge_parse_tasks, and knowledge_chunks_meta.
- Introduced prompt_rule_knowledge_groups table to associate prompt rules with knowledge groups.

task_plan.md

@@ -4,7 +4,7 @@
 Finish the completed backend verification/implementation chain, then resume the interrupted work by establishing the missing frontend foundation for `admin-web` so it can authenticate against `tenant-api` and render the first dashboard slice.
 
 ## Current Phase
-Phase 10
+Phase 14
 
 ## Phases
 ### Phase 1: Progress Verification
@@ -82,6 +82,18 @@ Phase 10
 - [ ] Update planning files and deliver the completed scope
 - **Status:** pending
 
+### Phase 13: Prompt Centralization
+- [x] Inventory all currently used hard-coded prompts in runtime and seed paths
+- [x] Extract prompt definitions into a dedicated shared location
+- [x] Refactor existing callers to read from the centralized prompt layer
+- **Status:** complete
+
+### Phase 14: Prompt Verification & Delivery
+- [x] Run targeted compile/test verification for the prompt refactor
+- [x] Update planning files with the final prompt inventory and changed files
+- [x] Deliver the extraction result and any remaining gaps
+- **Status:** complete
+
 ## Key Questions
 1. Which of the 9 steps are already implemented versus partially complete?
 2. What is the earliest step whose acceptance criteria are not yet met?
@@ -102,6 +114,7 @@ Phase 10
 | Use the current backend route graph as the implementation boundary for this turn | The user asked for frontend coverage of existing interfaces, so pages without APIs stay non-primary |
 | Reconstruct the screenshot layouts from visual position data, not OCR text alone | The user explicitly asked to follow image design including element placement |
 | Move the quota card into the left sidebar footer and use page-level hero sections | This matches the reference screenshots more closely than the previous generic topbar layout |
+| Centralize prompt text in a dedicated package instead of leaving it inside business logic functions | The user explicitly asked to extract hard-coded prompts for easier future optimization |
 
 ## Errors Encountered
 | Error | Attempt | Resolution |