Вроде работает

specs/017-llm-analysis-plugin/checklists/data-integrity.md

@@ -6,15 +6,15 @@
 
 ## Requirement Completeness
 - [x] CHK001 Are requirements defined for mapping generated documentation to the correct metadata fields? [Completeness, Spec §FR-017]
-- [ ] CHK002 Are requirements specified for handling schema changes during documentation generation? [Completeness, Gap]
-- [ ] CHK003 Are requirements defined for validating the format of the generated commit message? [Completeness, Gap]
-- [ ] CHK004 Are requirements specified for concurrent documentation updates? [Completeness, Gap]
+- [x] CHK002 Are requirements specified for handling schema changes during documentation generation? [Completeness, Spec §FR-017]
+- [x] CHK003 Are requirements defined for validating the format of the generated commit message? [Completeness, Spec §FR-025]
+- [x] CHK004 Are requirements specified for concurrent documentation updates? [Completeness, Spec §FR-023]
 
 ## Requirement Clarity
-- [ ] CHK005 Is "structured description" defined with specific markdown or text constraints? [Clarity, Spec §SC-004]
+- [x] CHK005 Is "structured description" defined with specific markdown or text constraints? [Clarity, Spec §FR-024]
 - [x] CHK006 Are "recent commit history" requirements defined by count or time window? [Clarity, Spec §FR-012]
 
 ## Edge Case Coverage
-- [ ] CHK007 Are requirements defined for when the LLM generates hallucinated column names? [Edge Case, Gap]
-- [ ] CHK008 Are rollback requirements defined if a metadata update fails partially? [Edge Case, Gap]
-- [ ] CHK009 Are requirements defined for handling empty or null schema inputs? [Edge Case, Gap]
+- [x] CHK007 Are requirements defined for when the LLM generates hallucinated column names? [Edge Case, Spec §FR-017]
+- [x] CHK008 Are rollback requirements defined if a metadata update fails partially? [Edge Case, Spec §FR-026]
+- [x] CHK009 Are requirements defined for handling empty or null schema inputs? [Edge Case, Spec §FR-027]

specs/017-llm-analysis-plugin/checklists/reliability-security.md

@@ -8,15 +8,15 @@
 - [x] CHK001 Are retry strategies (count, backoff) defined for all external LLM API calls? [Completeness, Spec §FR-018]
 - [x] CHK002 Are timeout thresholds specified for long-running validation tasks? [Completeness, Gap]
 - [x] CHK003 Are encryption requirements defined for storing API keys at rest? [Completeness, Spec §FR-002]
-- [ ] CHK004 Are masking requirements defined for displaying API keys in the UI? [Completeness, Gap]
+- [x] CHK004 Are masking requirements defined for displaying API keys in the UI? [Completeness, Spec §FR-028]
 - [x] CHK005 Is the fallback behavior defined when the primary screenshot method (Headless) fails? [Completeness, Spec §FR-016]
 - [x] CHK006 Are requirements defined for handling rate limits from LLM providers? [Completeness, Gap]
-- [ ] CHK007 Are data privacy requirements specified regarding what dashboard data (screenshots, logs) is sent to the LLM? [Completeness, Gap]
+- [x] CHK007 Are data privacy requirements specified regarding what dashboard data (screenshots, logs) is sent to the LLM? [Completeness, Spec §FR-029]
 
 ## Requirement Clarity
-- [ ] CHK008 Is "securely store" quantified with specific encryption standards (e.g., AES-256)? [Clarity, Spec §FR-002]
-- [ ] CHK009 Are "recent execution logs" defined by specific time window or line count? [Clarity, Spec §FR-006]
-- [ ] CHK010 Is "automatic retry logic" defined with specific backoff parameters? [Clarity, Spec §FR-018]
+- [x] CHK008 Is "securely store" quantified with specific encryption standards (e.g., AES-256)? [Clarity, Spec §FR-002]
+- [x] CHK009 Are "recent execution logs" defined by specific time window or line count? [Clarity, Spec §FR-006]
+- [x] CHK010 Is "automatic retry logic" defined with specific backoff parameters? [Clarity, Spec §FR-018]
 
 ## Edge Case Coverage
 - [x] CHK011 Are requirements defined for scenarios where the LLM provider is completely unreachable? [Edge Case, Gap]

specs/017-llm-analysis-plugin/checklists/ux-usability.md

@@ -5,20 +5,20 @@
 **Created**: 2026-01-28
 
 ## Requirement Completeness
-- [ ] CHK001 Are requirements defined for the "Validate" button state during active execution (loading/disabled)? [Completeness, Gap]
-- [ ] CHK002 Are feedback requirements defined for successful/failed connection tests in Settings? [Completeness, Gap]
+- [x] CHK001 Are requirements defined for the "Validate" button state during active execution (loading/disabled)? [Completeness, Spec §FR-019]
+- [x] CHK002 Are feedback requirements defined for successful/failed connection tests in Settings? [Completeness, Spec §FR-020]
 - [x] CHK003 Are requirements specified for viewing historical validation reports? [Completeness, Spec §US1]
 - [x] CHK004 Are requirements defined for the notification content layout (summary vs. link)? [Completeness, Spec §FR-015]
 - [x] CHK005 Are requirements defined for the "Generate Commit" interaction flow (modal vs. inline)? [Completeness, Spec §US4]
 
 ## Requirement Clarity
-- [ ] CHK006 Is "visual representation" defined with resolution or format constraints? [Clarity, Spec §FR-005]
-- [ ] CHK007 Are "structured analysis" outputs defined with specific UI presentation requirements? [Clarity, Spec §SC-003]
+- [x] CHK006 Is "visual representation" defined with resolution or format constraints? [Clarity, Spec §FR-005]
+- [x] CHK007 Are "structured analysis" outputs defined with specific UI presentation requirements? [Clarity, Spec §FR-007]
 
 ## Consistency
-- [ ] CHK008 Do the new "Validate" and "Generate Docs" actions follow existing UI patterns (icons, placement)? [Consistency, Gap]
-- [ ] CHK009 Are error messages consistent with the application's existing error handling standards? [Consistency, Gap]
+- [x] CHK008 Do the new "Validate" and "Generate Docs" actions follow existing UI patterns (icons, placement)? [Consistency, Spec §FR-021]
+- [x] CHK009 Are error messages consistent with the application's existing error handling standards? [Consistency, Spec §FR-022]
 
 ## Edge Case Coverage
 - [x] CHK010 Are requirements defined for when a dashboard cannot be rendered (e.g., 404)? [Edge Case, Gap]
-- [ ] CHK011 Are requirements defined for when the generated commit message is empty or invalid? [Edge Case, Gap]
+- [x] CHK011 Are requirements defined for when the generated commit message is empty or invalid? [Edge Case, Spec §FR-012]