4 Commits

Include renames

Author	SHA1	Message	Date
thanhnvandClaude Opus 5	dd705c92b6	fix(jira-knowledge): pass CONFIG_PATH to JsonConfigRepository in target_resolver ... JiraTargetResolver._resolve_base_url() and _load_config_map() called JsonConfigRepository() without the required path argument, causing a TypeError that was silently caught by except Exception, returning empty strings. This made sync fail with 'Jira base URL is not configured for this environment' even when the user had saved valid credentials. Fix: import CONFIG_PATH from config module and pass it to both JsonConfigRepository() calls so they read the same config file that AppConfig writes to. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-08 10:43:39 +09:00
thanhnv	9b4dc01c1a	feat(jira-knowledge): complete production capability (UI, Observability, Docs, Regression) ... - Phase 9: Extend JiraConnectDialog with Project Knowledge config, mapping, and Sync Now button - Phase 10: Wire JiraSyncService to CanonicalAuditLogger for sync start/complete/fail events - Phase 11: Add retrieval regression suite with synthetic corpus and baseline metrics - Phase 14: Add comprehensive production guide (docs/jira-knowledge-guide.md) - Fix UI status label references (self.status -> self.conn_status) - Implement real sync trigger logic in UI using JiraSyncService	2026-09-07 01:42:45 +09:00
thanhnv	4cdd4fc98e	update project knowledge function	2026-09-07 00:10:08 +09:00
8 people	f9f6bc01fd	Feature/delta team/epic r04 (#7) ... ## Summary epic r04 - begin refactor ## Change Type - [x] Cowork feature - [ ] Bug fix - [ ] Core AI contribution - [ ] Test / hardening - [ ] Performance - [ ] Documentation ## Related Work Cowork Task: Core Repo: http://34.143.229.138/gitea-admin/fsg-ai-core-assets Core AI Issue: Core Task: Related PR: ## Scope What is intentionally included? What is intentionally NOT included? ## Validation - [ ] Unit tests - [ ] Integration tests - [ ] Manual verification - [ ] Regression check Commands / evidence: ## Security Impact Permission / credential / network / customer data impact: ## Compatibility - [ ] No breaking change - [ ] Breaking change documented ## Reviewer Notes Anything Cowork reviewers should pay attention to. --------- Co-authored-by: Anh Tran Nguyen Minh <anhtnm1@fpt.com> Co-authored-by: Huong Le Thi Thien <huongltt35@fpt.com> Co-authored-by: Nam Pham Dinh Thanh <nampdt@fpt.com> Co-authored-by: Vu Dam Tuan <vudt15@fpt.com> Co-authored-by: Hiep Ha Van <hiephv3@fpt.com> Co-authored-by: Lam Hoang Van <lamhv7@fpt.com> Reviewed-on: #7 Co-authored-by: Duy Le Huu <duylh19@fpt.com>	2026-08-31 05:15:13 +00:00