152 Commits

Author	SHA1	Message	Date
chiguyong	d7ca6e8065	fix(review): W1 ServerConfig from_dict wiring, W3 internal kwargs filter, N3 status docstring ... Code review fixes for Wave 1: - W1: ServerConfig.from_dict now wires prompt_cache/streaming/verification sections from YAML to constructor (previously these params existed but were never read) - W3: Tool._validate_input filters _-prefixed kwargs (e.g. _skip_dangerous_check) before jsonschema.validate, preventing additionalProperties:false schemas from rejecting internal control parameters - N3: ReActResult.status docstring now lists "empty_fallback" and "verify_failed" Added test test_internal_kwargs_underscore_prefixed_skipped_by_validation for W3.	2026-06-29 21:58:40 +08:00
chiguyong	cd211c6cd9	feat(U4): G1 verify 失败回灌 ReAct ... - ReActEngine 新增 max_reinjections 构造参数(默认 1,=0 等价原行为) - execute()/execute_stream() verify 块从循环后移到循环内 final-answer 检测点: - verify 通过 → 正常 break - verify 失败 + reinjections < max + step < max_steps → errors 作为 user 消息回灌 conversation, continue 让 LLM 自纠正 - verify 失败 + 达到 max_reinjections 或 max_steps → 记录 verify log 到 trajectory, trace_outcome="verify_failed", break - execute_stream 的 final_answer 事件在 verify 通过后才 yield,避免客户端过早收到完成信号 - ReActResult.status 现在传递 trace_outcome(原默认 "success") - ServerConfig.verification 配置项(max_reinjections) - test_verify_reinjection.py 10 测试:characterization(max=0)+ 新行为(R1/R2/R3/R14)	2026-06-29 21:35:08 +08:00
chiguyong	0f3f0a7550	feat(U3): G8 delta_flush_interval 调速 ... - ReActEngine 新增 flush_interval_ms 构造参数(默认 0 = 逐 chunk yield 向后兼容) - execute_stream chunk 循环用 time.monotonic 节流,累积 _flush_buffer 批量 yield - flush_interval_ms=0 条件短路为 True 逐 chunk yield 保当前行为 - 流结束 mid-interval 最终 flush 剩余 buffer 不丢字符 - ServerConfig.streaming 配置项(flush_interval_ms) - test_delta_flush.py 覆盖 R11/R12/R14	2026-06-29 20:49:52 +08:00
chiguyong	c4aaef05aa	feat(U2): G2 prompt cache 双块结构 ... - ReActEngine 新增 _build_system_message(stable+volatile) 双块构造 - Anthropic provider 返回 content blocks,stable 块带 cache_control - 非 Anthropic provider 返回字符串拼接,依赖 stable 前缀命中自动前缀缓存 - execute_stream/execute 记忆注入从 system_prompt 末尾移到 volatile 层 - LLMGateway.get_provider_name_for_model 暴露 provider 检测能力 - anthropic.py _convert_messages 支持 list-type system content 透传 - ServerConfig.prompt_cache 配置项(默认 enable=True) - ReActEngine.prompt_cache_enable 构造参数(默认 True 保当前行为) - test_prompt_cache_layers.py 覆盖 R4-R7/R13	2026-06-29 20:47:23 +08:00
chiguyong	2747bb4e64	chore(prior): malformed tool call handling, auth whitelist, dev scripts, wave1 plan	2026-06-29 20:25:03 +08:00
chiguyong	a6e1bf5884	feat(bitable): 多维表格文件层 + 默认字段 + 表内字段操作 + ce-code-review 修复 (Stage 1) ... 实现多维表格 UI 完整性 Stage 1（U1-U6），补齐飞书/twenty 对齐缺失的文件层、 默认字段与表内字段操作能力，并修复 ce-code-review 走查发现的 P0/P1 级问题。 后端（U1-U2）: - 新增 BitableFile 实体（models/db/repository/service/routes），三级层级：文件→数据表→字段/记录 - Schema V2 迁移：bitable_files 表 + tables.file_id 列，幂等（IF NOT EXISTS），保留 V1 孤儿表 - 新建数据表自动创建 5 个默认字段（标题/状态/日期/创建人/创建时间） - agent-owned 字段在 create_record 时自动填充（按 type+owner 匹配，传 actor_user_id） - 7 个文件 REST 端点 + IDOR ownership 检查（404-before-403，internal token 旁路） 前端（U3-U5）: - 文件列表页（FileCard 网格 + 新建/重命名/删除）+ 文件详情页（侧栏表格列表 + vxe-table 网格） - Vue Router 嵌套路由 /bitable → /bitable/:fileId → /bitable/:fileId/:tableId - 列头菜单（编辑/隐藏/删除字段）+ 末尾 + 列新增字段 - select/multiselect 字段自定义单元格编辑器 + Tag 展示 - Pinia store 扩展 file 状态与动作，深链直访回退 getFile，fileId 切换 watch 测试（U6）: - 文件 CRUD（12 例）+ 默认字段（10 例）单元测试 - 3 个 E2E spec（视图加载、文件流、字段操作），后端不可用时优雅跳过 ce-code-review 修复（P0/P1）: - P0 路由冲突：GET /files/{file_id} 遮蔽下载端点 → 下载改 /uploads/{filename} - P0 IDOR：update/delete field/record/view 五端点补 ownership 检查 - P1 is_initialized property 缺失致二次初始化崩溃 - P1 直接 URL 导航失效（files 数组为空）→ selectFile 回退 getFile - P1 fileId 切换不重载 → 增加 watch - P1 轮询丢弃最终公式值（wasCalculating 守卫）+ 复用视图 filters - P1 测试断言 200→201；test_db 无 URL 用例解除 postgres 标记得以执行 - P2 _check_table_ownership 403→404；输入长度校验；upload field-table 一致性校验 - P2 multiselect 浅比较 → 深比较；E2E bitable-view 补 waitForServer 守卫 验证：ruff check 通过；pytest 91 passed/116 skipped；vue-tsc --noEmit 通过。	2026-06-29 04:07:45 +08:00
chiguyong	5c15238a5a	fix(calendar): 修复 agent 创建日历事件后 UI 不刷新 + 文档化三根因三部曲 ... 代码修复 (ce-debug): - CalendarService.create_event 注入 notify_callback，成功后广播 calendar_event_created WS 消息 - app.py 调整 _calendar_ws_sender 闭包定义顺序，注入 CalendarService（与 ReminderScheduler 共享） - tauri-auth.ts keychain fallback 修复（localStorage 始终作为备份） - 新增 2 个广播回归测试 文档 (ce-compound + ce-compound-refresh): - 新增 docs/solutions/ui-bugs/calendar-agent-create-no-refresh.md（第三根因：WS 广播缺失） - 更新 calendar-capability-and-ui-fixes.md：刷新 test count + 加 Related Issues 前向引用 - 更新 jwt-secret-dev-mode-user-id-mismatch.md：扩展 e2e bullet + 加第三个根因引用 - CONCEPTS.md 新增 Service Broadcast Callback 条目 (Real-Time Fan-Out 节) 测试: - 新增 E2E 测试套件 (admin/auth-persistence/bitable/calendar/conversation/documents/evolution/settings/skills) - 新增 tests/e2e/test_api_coverage.py - CI: .gitea/.github workflows/test.yml	2026-06-29 02:20:33 +08:00
chiguyong	d27681a93c	fix(portal-auth): 修复 dev mode JWT 验证误激活 + README 文档同步 ... ## Portal 401 根因修复 问题：AGENTKIT_JWT_SECRET 未设置时，jwt_utils 生成 ephemeral 非空 secret， 该 secret 被传给 AuthMiddleware 后 _is_dev_mode() 返回 False（not "" = False）， 导致无 JWT/API key 的请求被拒为 401（17 个 portal 测试失败）。 修复：分离 explicit_jwt_secret 与 jwt_secret — - explicit_jwt_secret = get_jwt_secret() # None when env unset - jwt_secret = explicit_jwt_secret or get_or_create_jwt_secret() # for signing - AuthMiddleware(jwt_secret=explicit_jwt_secret or "") # only explicit activates JWT verify ephemeral secret 仅供 token 签名 routes，不激活 middleware 的 JWT 验证。 生产环境（AGENTKIT_JWT_SECRET 已设置）行为不变。 验证： - _is_dev_mode(): False → True - GET /api/v1/portal/conversations: 401 → 200 - 27 个 portal 测试全部通过（之前 17 失败） - 232 个测试通过 (portal + auth + calendar)，0 失败 ## README 文档同步 代码中 CostAwareRouter / RegexRules / HeuristicClassifier / SemanticRouter / LLMClassifier 类已完全删除，仅 RequestPreprocessor 存在。README.md 6 处过时引用同步： - 第 4 节"意图路由"改为引用 RequestPreprocessor（详见第 7 节） - 第 7 节重写为"请求预处理（RequestPreprocessor）"，按 AGENTS.md 架构描述 - 第 8 节"语义路由"删除（合并入第 7 节历史说明） - 架构图 CostAwareRouter → RequestPreprocessor，22→28 路由模块 - 模块详解 chat/skill_routing + chat/semantic_router 合并为 chat/request_preprocessor - 模块详解 router/intent 描述更新为"未接入 chat 流程" - 目录注释 CostAwareRouter → RequestPreprocessor - 章节重新编号 1-16 连续（原 1-17 跳过 9）	2026-06-28 15:26:42 +08:00
chiguyong	c9ce15fa4b	fix(code-review): 修复走查发现的 13 High + Medium 安全/可靠性问题 ... 代码修复（8 High + 9 Medium）： - portal.py — C1 IDOR 文档 / C2 类型修复 / C3 WS 连接上限 16 / C4 ws_user_id 早初始化 / M silent swallow 日志化 - auth/middleware.py — C5 WS sid 补齐 - calendar_tool.py — C6 偏移量 ±43200 双向校验 + reminder_channels 类型/白名单校验 - sqlite_conversation_store.py — C7 DELETE 事务回滚 - chat.ts (Pinia) — C8 deleteConversation 清理 pending 缓存 - app.py — M except: pass → logger.debug(exc_info=True) - Scene6Error.vue — M onUnmounted 清理 setTimeout - DocumentsTab.vue — M Invalid Date 守卫 - ChatSidebar/RightPanel/TopNav.vue — M aria-label 无障碍标签 - SystemMonitorPanel.vue — M v-else 兜底 + active 边框色 + tablist 键盘导航 - CalendarDrawer.vue — M overflow-y: auto - CalendarGrid.vue — M ResizeObserver 反馈循环防护 - SkillsTab.vue — M onMounted 始终 fetchSkills 文档修复（5 High + 6 Medium）： - portal-platform-security-reliability-fixes.md — D2 测试路径 / D3 Root Cause+Impact 章节 / D4 severity: mixed / 标题中文化 / 12 处绝对路径转相对 / P2 #12 数字口径 - AGENTS.md — D5 路由表 22→28 / 专家模板 5→15 / LiteLLM U15 迁移 / 配置查找 fallback - README.md — 8 处端口 8000→8001 新增测试： - tests/unit/calendar/test_calendar_tool.py — ponytail 自检断言 验证： - ruff check (5 文件) — All checks passed - vue-tsc --noEmit — exit 0 - git stash baseline 验证 — portal 17 个 401 失败为预存在问题 已知限制（预存在）： - 17 个 portal 测试 401 失败 — 需另起 ce-debug 调查 - README.md 7 处 CostAwareRouter 引用过时 — 文档同步另起任务	2026-06-28 15:06:41 +08:00
chiguyong	43e9025c6d	fix(calendar): 日历能力缺失修复 + UI 布局优化 + 会话404处理 ... P0: calendar_tool reminder_rules 未传入 create_event，提醒功能完全失效。P1: chat.ts deleteConversation 未清理 pending + 404 递归保护。P2: app.py 系统提示重复段落 + gui_mode F821 + SystemMonitorPanel flex 布局。P3: portal send_json 快照 + WS connected 清除 is_local + 移除死代码。验证: ruff+pytest 98passed+typecheck 通过。	2026-06-28 14:24:58 +08:00
chiguyong	31c65e01b8	fix(security): P0 安全加固 + 多实例部署一致性 (U1-U4 + U5c) ... U1: LLM gateway KB 缓存 fail-closed — 异常时默认禁用缓存防止 KB 数据泄漏 U2: MCP 危险工具黑名单过滤 — 6+1 端点覆盖，防止绕过 chat confirmation U3: SecretsStore Redis 迁移 — 多 worker 共享凭证，内存降级保留开发模式 U4: channels webhook Redis 状态 — ZSET 滑动窗口限流 + nonce dedup + backpressure U5c: ce-code-review 修复批次: - P0: 统一 MCP 黑名单与 publisher.py 一致 (terminal_execute -> terminal, +file_read) - P1: ZSET 限流 member 加 uuid 后缀避免同时间戳碰撞 - P1: SecretsStore redis 参数 Any -> aioredis.Redis | None (AGENTS.md 合规) - P1: Redis client 添加 socket_timeout 防止单点故障请求挂死 测试: 171 scoped tests pass, ruff clean	2026-06-26 04:05:33 +08:00
chiguyong	53faa60472	fix(review): ce-code-review P1+P2 修复 — 安全/可靠性/性能 ... P1 安全与可靠性（4 项）： - wecom: verify_signature 增加时间戳新鲜度校验（5 分钟窗口防重放） - cache: should_cache 在 per_user_namespace 开启时拒绝 user_id=None 匿名请求，避免跨用户缓存泄漏（安全要求 a/e） - channels: webhook receive_message 异常兜底，防止 500 触发平台重试风暴 - app: shutdown 调用 close_all_adapters + await _pending_webhook_tasks， 防止 httpx 连接泄漏和丢失 IM 回复 P2 效率与可维护性（5 项）： - feishu: _TOKEN_CACHE_TTL 300 → 6900（2h 减 5min 余量，避免 24x 过频刷新） - channels: _pending_webhook_tasks 有界化（2x 并发上限时 429 拒绝） - gateway: quota 检查每 period 单次 get_usage，复用 summary 检查 token+cost - cache_key: generate_cache_key 合并为单次 SHA-256（消除 8-10 次冗余哈希） - config: ProviderConfig.get_api_key 移除未用的 secrets_store 参数 P3 去重（1 项）： - channels: _process_inbound_message DIRECT_CHAT 路径提取 _direct_chat 辅助函数 测试： - test_wecom: 时间戳改用 int(time.time())，新增 test_expired_timestamp_rejected - test_cache: should_cache 测试覆盖匿名拒绝 + namespace_off 兼容 - test_config_migration: get_api_key 测试适配新签名 - channels/config_migration/quota_enforcement 测试全部通过	2026-06-26 01:40:31 +08:00
chiguyong	1ccaf56b9a	refactor: ce-simplify-code 审查修复 — 去重 + 效率 + 死代码清理 ... 3 个审查代理（复用/质量/效率）发现 15 个问题，全部修复： 效率与安全（6 项）： - MCPClient 缓存 MultiServerMCPClient 单例 + aclose()，修复连接/子进程泄漏 - _rate_limits 清理空 IP 条目，修复 X-Forwarded-For 欺骗下内存泄漏 - _seen_nonces 改用 OrderedDict，O(1) 摊销过期清理 - webhook 后台任务加 Semaphore(20) + 任务引用追踪，限制无界并发 - _build_adapter 用 asyncio.gather 并行解密 secrets - 适配器实例缓存（_adapter_cache），token TTL 缓存跨请求命中 去重（4 项）： - header_get 提取到 channels/base.py，4 个适配器统一 import - _get_client/close() 移入 MessageAdapter 基类，子类继承 - URLVerificationChallenge 统一到 base.py，feishu/slack/wecom 共用 - Transport ABC 添加 endpoint_url 属性，from_transport 不再访问私有字段 死代码与类型安全（5 项）： - detect_cache_hit 死方法替换为 record_cache_result 公开 API - execution_mode.value == "direct_chat" 改用枚举比较 - 删除 yielded_any 死变量、重复 from fastapi import Request、 多余 getattr 防御 453 tests passed, ruff clean（预存 F841 非本次引入）	2026-06-25 23:54:14 +08:00
chiguyong	069dbc22b1	feat(llm): U15 — LiteLLM unified provider + api_key encrypted secrets migration	2026-06-25 21:41:15 +08:00
chiguyong	13c516a54f	feat(mcp): U14 — Skill/Team MCP publish with admin auth + dangerous-tool opt-in	2026-06-25 21:10:06 +08:00
chiguyong	16c33be295	feat(mcp): U13 — refactor MCPServer to route factory + mount at /api/v1/mcp with auth	2026-06-25 20:58:41 +08:00
chiguyong	8998f94c42	feat(channels): U12 — DingTalk/WeCom/Slack adapters + multi-channel webhook dispatch	2026-06-25 20:45:43 +08:00
chiguyong	4b58e8f661	feat(channels): U11 — Feishu IM adapter end-to-end (webhook + signature + AES-CBC decrypt + chat integration)	2026-06-25 20:24:21 +08:00
chiguyong	5572387c01	feat(channels): U10 — message adapter ABC + AES-256-GCM secrets store + channel CRUD routes	2026-06-25 20:13:37 +08:00
chiguyong	864bb95a30	feat(server): wire rag_platform components to app.state lifespan ... Initialize in lifespan() (after bitable, before yield): - KBStore + ensure_tables() → app.state.kb_store (if database_url available) - RetrievalEngine + vector_store → app.state.retrieval_engine (if database_url available) - HitProcessor → app.state.hit_processor (with llm_gateway) - TaskManager → app.state.task_manager (degraded mode, InMemoryTaskStore) - KBSettingsStore → app.state.kb_settings_store (singleton) Each component wrapped in try/except — failures logged but don't block startup. Follows same pattern as episodic memory initialization.	2026-06-25 20:02:01 +08:00
chiguyong	1f691ca178	feat(frontend): U9 — KB management extension with segment preview, status display, settings ... New: SegmentPreview.vue, KBSettings.vue Extended: DocumentUpload.vue (status badges, retry, preview), SearchTest.vue (3 modes), SourceConfig.vue (ACL), KnowledgeBaseView.vue (settings + task history tabs) API+Store: kb.ts new types/methods, knowledge.ts new state/actions typecheck: passed	2026-06-25 13:14:58 +08:00
chiguyong	d026a91f43	feat(rag_platform): U6 — hit processing mode + KB settings ... Add hit_processing.py: HitProcessor with model_opt (LLM-generated) and direct (concatenated chunks) modes, with in-process cache Add settings.py: KBSettings/KBSettingsUpdate models, KBSettingsStore with async CRUD Add KB settings endpoints to kb_management.py: GET/PUT /kb-management/kbs/{kb_id}/settings with owner-only modification Tests: 43 new tests (25 hit_processing + 18 settings), 293 total passing	2026-06-25 12:44:47 +08:00
chiguyong	3f9588e673	feat(rag_platform): U3+U7 — rewrite upload endpoint with sanitization + pipeline ... Rewrite upload_document() to use rag_platform sanitize + DocumentProcessor: - File type whitelist validation (8 allowed types, reject .exe/.sh) - File size limit (50MB) + zip bomb detection for ZIP-based formats - DocumentProcessor.parse() (with content sanitization) + segment() - Return chunks preview, status="segmenting" (pending vectorization) Add POST /kb-management/documents/preview endpoint: - Pre-upload preview with adjustable chunk_size/chunk_overlap - Same security validation as upload, no document record created Add POST /kb-management/documents/{id}/vectorize placeholder: - Returns 503 — full async vectorization deferred to U8 (TaskIQ) Test: update test_upload_document assertion (status "indexed" → "segmenting")	2026-06-25 12:06:16 +08:00
chiguyong	bbbf9cd40a	feat(bitable): add bitable companion service with full P0-P2 fixes ... Bitable is a multi-dimensional table companion service that runs alongside the main AgentKit server. It provides structured data storage with formula fields, views, and ingestion pipelines. Major components: - Domain models (Pydantic v2): Table, Field, Record, View, RecalcTask - SQLAlchemy 2 async ORM with independent bitable PostgreSQL schema - Formula engine: AST parser, DAG, Kahn topological sort, safe eval - RecalcWorker: atomic task claiming (FOR UPDATE SKIP LOCKED), topo-order processing, stale-threshold reaper for crash recovery - REST API (/api/v1/bitable): tables, fields, records, views, files - BitableTool: agent-facing tool with batch chunking (500/batch) - CLI: agentkit bitable subcommands (create, list, import-excel, etc.) - Frontend: Vue 3 + vxe-table grid with field management, views, filters - Ingestion: Excel (openpyxl), database reflection, API collector Security fixes (ce-code-review P0 + ce-debug P1): - SQL injection prevention (field_id validation, parameterized queries) - IDOR protection (_check_table_ownership on all table-level endpoints) - SSRF prevention (URL scheme + private IP validation in parse_excel_url) - OOM prevention (streaming file upload, batch delete, batch insert) - Atomic recalc task claiming (FOR UPDATE SKIP LOCKED) - Formula engine cache invalidation on field changes - Composite cursor pagination for non-id sort orders - Batch upsert (eliminates N+1 queries) - Sync I/O offloaded to thread pool in async contexts - Internal token auth (X-Internal-Token, hmac.compare_digest) - PK unique index enforcement Test coverage: 88 unit tests (95 skipped without Docker)	2026-06-25 01:09:59 +08:00
chiguyong	dfd188b1a4	feat(orchestrator): add pipeline checkpoint and crash recovery (U7) ... Add PipelineCheckpoint for stage-level crash recovery with Redis-first + memory fallback. TeamOrchestrator saves checkpoints after each phase finalizes and supports resume(plan_id) to continue from the last completed phase. New POST /api/v1/tasks/{id}/resume endpoint recreates the team from saved plan and calls resume.	2026-06-24 21:04:18 +08:00
chiguyong	ef84e3fd53	feat(experts): add SharedWorkspace state offloading for long-horizon runs ... U4: ExpertTeam accepts redis_client, passes to SharedWorkspace. After phase completion, full result is written to workspace and in-memory phase.result is replaced with a 500-char summary + _ref_key. Dependency output reading resolves offloaded content from workspace on demand, with graceful fallback to summary on read failure. Tests: 8 scenarios (offload creation, short content, dependency resolution, workspace failure fallback, non-offloaded passthrough, redis_client wiring, memory dict fallback, pipeline integration) — all pass.	2026-06-24 20:32:10 +08:00
chiguyong	a312e584ae	Merge branch 'feat/expert-team-pm-collaboration' — PM 协同模式 + 代码审查全量修复 ... # Conflicts: # src/agentkit/server/frontend/components.d.ts	2026-06-24 18:57:37 +08:00
chiguyong	574db8458f	fix(experts): PM 协同代码审查全量修复 ... P0: 跨阶段契约状态同步 — _notify_collaborators 更新接收方契约状态为 received P0: 4 个 PM 事件加入 _VALID_TEAM_EVENT_TYPES 白名单 P1: 验收 fail-open 改标注降级原因 P1: 返工失败抛 RuntimeError 而非返回 dict P1: 验收 prompt injection 防护 — 专家输出用 XML 标签包裹 P1: 契约字段校验 _EXPERT_NAME_RE P1: bool("false") 修复 — 显式比较避免字符串真值陷阱 P1: _parse_risk_flags(None) 防御 P2: _notify_collaborators 移到验收通过后 P2: SharedWorkspace 写入移到验收通过后 P2: 验收贪婪正则修复 P2: 风险标记数量上限 MAX_RISK_FLAGS=10 P2: 返工 feedback 截断 P2: 前端会话隔离 — 切换会话时清除/恢复 collaborationState P2: 前端契约状态更新 — collaboration_notice 时标记 delivered P2: CLI 死代码标注 + 异常改 debug 日志 P2: 模块级 _RISK_FLAG_RE 预编译	2026-06-24 18:56:27 +08:00
chiguyong	34a4164430	feat(frontend): U5 前端协作关系图 + 验收/风险卡片 ... - types.ts 新增 ICollaborationContract/ICollaborationNotice/IReviewResult/IRiskFlag 等接口 - chat.ts 新增 collaborationState ref，处理 4 种协同事件 (collaboration_contract_defined/collaboration_notice/review_result/risk_flagged) 并在 plan_update 中提取 contracts，team_formed/dissolved 清理状态 - CollaborationGraphCard.vue SVG 协作关系图： 圆形布局节点（专家首字），实线=契约，虚线动画=数据流向 节点颜色编码验收状态（绿=通过，红=返工/失败），橙色!标记风险 - ReviewResultCard.vue 验收结果卡片（passed/failed + feedback） - RiskFlagCard.vue 风险标记卡片（专家 + 风险描述） - useMessageRenderer.ts 新增 3 个视图类型和渲染规格 - index.ts 导出 3 个新组件 - 遵循 U5 辩论可视化 BoardState 模式 - typecheck 通过	2026-06-24 14:42:00 +08:00
chiguyong	59e47c5871	test(calendar): 8 Playwright e2e tests + config fixes (JWT secret, rate limit) ... E2E tests (calendar.spec.ts): - E1: panel loads, shows empty state - E2: create event via UI, verify in panel - E3: switch between calendar/card/list views - E4: edit event title via UI - E5: delete event via API, verify removal from UI - E6: create event with tag via UI (keyboard.type for Ant Select) - E7: recurring event displays multiple occurrences - E8: invitation manager button accessible Config fixes (playwright.config.ts): - Set AGENTKIT_JWT_SECRET so AuthMiddleware can verify login tokens (without it, get_jwt_secret() returns None → 401 on all API calls) - Call create_app(rate_limit=10000) explicitly instead of uvicorn factory=True — factory mode lets server_config.rate_limit (60, from agentkit.yaml) override the env var, causing 429 rate limiting - Use .venv/bin/python instead of system python3 (missing deps) All 8 tests pass (47s).	2026-06-24 13:17:53 +08:00
chiguyong	49b483b933	feat(frontend): U5 前端辩论可视化 ... 前端展示辩论过程，专家交锋有独立气泡样式，裁决结果清晰可见。 类型 (api/types.ts): - WsServerMessage 新增 5 个辩论事件：debate_started / expert_argument / debate_round_summary / debate_resolved / team_intervention_ack - IChatMessage.message_type 新增 4 个辩论消息类型 - IChatMessage 新增 7 个可选辩论字段（topic/round/decision 等） - 新增 4 个数据接口 Chat Store (stores/chat.ts): - 新增 debateState ref（topic/participants/round/status） - WS switch 新增 5 个 case，复用 appendMessage/appendStep 模式 - 辩论结束 1s 后清空 debateState（与 board_concluded 一致） 渲染器 (useMessageRenderer.ts): - MessageViewType + resolveMessageType 新增 4 个辩论视图类型 - useMessageRenderer 新增 4 个 render spec 新组件 (messages/): - DebateBannerCard.vue — 辩论开始横幅（主题 + 参与专家 + 开场白） - DebateArgumentCard.vue — 专家论点卡片（专家色边框 + 轮次标签） - DebateSummaryCard.vue — 主持人轮次小结 - DebateConclusionCard.vue — 裁决卡片（按 decision 着色） 输入框 (ChatInput.vue): - 团队模式下显示「辩论」按钮，点击弹出 prompt 输入主题 - 发送 /debate <topic> 命令（U4 WS 干预通道处理） npm run typecheck 通过。	2026-06-24 12:37:37 +08:00
chiguyong	c831e925b6	feat(experts): U4 用户干预通道 + 手动辩论触发 ... 建立 @team 执行期间的用户干预通道，支持 /stop、/debate <topic>、 普通文本追加上下文。 ExpertTeam (src/agentkit/experts/team.py): - 新增 _interventions: asyncio.Queue (maxsize=64) 干预队列 - add_user_intervention(msg): 广播 + 入队 - consume_user_interventions(): 排空并返回待处理干预 - broadcast_user_message 现在同时入队干预队列 TeamOrchestrator (src/agentkit/experts/orchestrator.py): - 新增 _user_context: list[str] 累积普通文本干预 - 新增 _process_interventions(lead, plan) 在每层执行前调用： * /stop → 终止执行，广播 plan_update(stopped_by_user) * /debate <topic> → 动态插入 DEBATE phase（受 MAX_DEBATES 限制） * 普通文本 → 累积到 _user_context - _synthesize_results 将 _user_context 追加到 synthesis prompt WS 路由 (src/agentkit/server/routes/chat.py): - 模块级 _active_teams dict 跟踪每个 session 的活跃团队 - _execute_team_collab 执行前注册、finally 注销 - WS 消息循环：若 session 有活跃团队，message 路由为干预而非新任务 - 新增 team_intervention_ack 确认消息 测试：tests/unit/experts/test_team_intervention.py（20 测试）， 覆盖队列基础、/stop、/debate、普通文本、混合消息、synthesis 影响。 同步更新 test_orchestrator_debate.py 的干预通道兼容性测试 （U4 已实现 consume_user_interventions）。 全部 418 experts 测试 + 325 server 测试通过。	2026-06-24 12:17:09 +08:00
chiguyong	d4bc79e409	test(calendar): wire calendar router into app.py + test plan ... - Register calendar router in create_app() so /api/v1/calendar/* is reachable - Initialize CalendarService + ReminderScheduler in lifespan - Register CalendarTool into tool registry for ReAct integration - Lazy-import ICSProvider in routes to break circular import - Add test plan document (5 layers: unit/integration/e2e)	2026-06-24 11:51:31 +08:00
chiguyong	3fdee65979	fix(calendar): code review fixes - 23 issues (2 critical, 15 major, 6 minor)	2026-06-24 11:29:23 +08:00
chiguyong	394d734d42	feat(calendar): U12 reminder config and external sync settings UI	2026-06-24 05:02:29 +08:00
chiguyong	3131769aed	feat(calendar): U11 event editor, invitation manager and batch operations	2026-06-24 05:02:12 +08:00
chiguyong	8350b02d75	feat(calendar): U10 frontend calendar views with 3 view modes and drawer	2026-06-23 23:50:28 +08:00
chiguyong	40bc27822f	feat(calendar): U9 frontend store, API client and types ... CalendarApiClient with 20 methods covering all backend endpoints (listEvents, createEvent, importIcs, searchUsers, syncNow, etc.). useCalendarStore Pinia store with events/eventTypes/tags state, view mode switching, and handleWsEvent dispatch for 4 calendar WS message types. WsServerMessage union extended with calendar variants. - src/agentkit/server/frontend/src/api/calendar.ts — API client + types - src/agentkit/server/frontend/src/stores/calendar.ts — Pinia store - src/agentkit/server/frontend/src/api/types.ts — WS message types	2026-06-23 22:52:40 +08:00
chiguyong	ffb184acc7	feat(calendar): U8 iCal/ICS import and export ... ICSProvider parses .ics files (icalendar library) and creates local CalendarEvents, skipping duplicate UIDs. Export builds an iCalendar from events in a date range, deduplicating recurring event occurrences back to a single VEVENT with RRULE. REST endpoints: POST /import-ics (multipart upload), GET /export-ics (download). - src/agentkit/calendar/sync/__init__.py — sync subpackage init - src/agentkit/calendar/sync/ics_provider.py — ICSProvider (import/export) - src/agentkit/calendar/db.py — added get_event_by_external_id() for dedup - src/agentkit/server/routes/calendar.py — import-ics and export-ics endpoints - pyproject.toml — added icalendar>=5.0 dependency - tests/unit/calendar/test_ics_provider.py — 8 tests	2026-06-23 22:20:07 +08:00
chiguyong	d36e45bbe7	feat(calendar): U2 backend service & REST API ... Add CalendarService business logic layer and 14 REST endpoints: - service.py: event CRUD with RRULE expansion, event types, tags, invitations, non-admin user search (G5/A3), type-level default reminder rule cloning - routes/calendar.py: JWT-authenticated endpoints for events, types, tags, invitations, user search — with ownership checks - 17 new tests (12 service + 5 routes), 33 total calendar tests passing	2026-06-23 21:43:39 +08:00
chiguyong	3d108dd08e	fix(skills): P3 frontend polish for skill/agent category split ... - skills.ts: make category/agent_type/execution_mode/task_mode optional in ISkillInfo and ISkillDetail for backward compat during rollout - SkillCard.vue: remove dead size="small" on a-tag, add title attr for a11y, add isEngine computed, CSS fallback cleanup, category fallback in class binding - SkillsView.vue: fix a-empty condition to use grouped counts so orphan skills (category mismatch) don't render a blank page - SkillsTab.vue: add type tag (引擎/技能) and category-based icon (thunderbolt for engine, appstore for business), remove size="small", add engine icon color variant	2026-06-23 19:41:54 +08:00
chiguyong	a672dddc9a	feat(skills): distinguish agent templates from business skills in UI ... The skills tab mixed generic execution-engine templates (react/direct/ rewoo/...) with business-domain skills (monitor/geo_optimizer/...) with no visual or data distinction. Adds a derived `category` field to the SkillInfo/SkillDetail API models and groups the frontend display. Backend: - SkillInfo/SkillDetail: add category (Literal), agent_type, execution_mode, task_mode fields - _skill_to_info: derive category from explicit _ENGINE_TEMPLATE_NAMES set (not name suffix — trend_agent/deai_agent are business skills despite the _agent suffix) - Simplify repetitive hasattr pattern with getattr Frontend: - ISkillInfo/ISkillDetail: add category + mode fields - skills store: agentTemplates/businessSkills computed getters (businessSkills is defensive: anything not explicitly engine template) - SkillsView: group into 执行引擎 / 业务技能 sections with counts - SkillCard: type badge (引擎/技能), category-based icon, mode display, dark-mode-aware accent color Tests: - test_category_derived_from_name_suffix: verifies field exposure - test_category_no_orphans: invariant — every skill has a valid category - test_trend_agent_classified_as_business_skill: regression guard for the _agent suffix misclassification bug Code review (ce-code-review): 2 P1 + 5 P2 findings applied.	2026-06-23 15:55:59 +08:00
chiguyong	47f3bfecfc	feat(documents): add document processing capability (U1-U9) ... Implements end-to-end document generation, template filling, and reading: - DocumentService: unified business layer for create/query/download - Renderers: Word (Markdown->docx), Excel (Markdown/JSON->xlsx), PDF (Markdown->pdf with CJK font), Template (Jinja2 sandbox .docx fill) - DocumentLoader: read PDF/Word/Excel/Markdown/HTML/text -> Document - DocumentTool: Agent tool with action=create|read - REST API: /api/v1/documents (create, upload-template, list, download) - Frontend: DocumentPanel, DocumentCard, documents Pinia store, chat store tool_result detection - Security: path traversal guard (Path.resolve + relative_to), SSTI guard (SandboxedEnvironment), API key auth, 50MB upload limit - Bug fixes: template path traversal (400 not 500), TemplateRenderer lazy-load (no external registration dependency) - Tests: 168 tests (unit + security + E2E F1/F2/F3 + bug hunt) - Docs: README section 17, requirements + plan + test-plan docs Requirements R1-R28 verified, F1-F3 user flows pass.	2026-06-23 15:05:01 +08:00
chiguyong	bc424574c7	fix: Tauri reload, multi-conv blocking, skill install, UI polish ... 1) Tauri reload login: main.ts beginStartup before mount + router guard await waitForStartup 2) Multi-conversation blocking: per-conversation Map/Set tracking 3) Skill install: npx --yes + SKILL.md support + path traversal validation 4) Markdown table rendering + 80ms streaming debounce 5) Agent execution UI: structured IStreamingStep 6) auth.py _ensure_db idempotent Code review fixes: renderTimer cleanup, counter accumulation, memory leak, WS reconnect stale steps	2026-06-23 11:03:46 +08:00
chiguyong	4f261523c2	fix(review): U3 atomic file writes for YAML + .env + skill config ... All config file writes now use the write-temp + fsync + os.replace pattern (KTD-4) so a crash mid-write leaves the original file intact. - Add src/agentkit/server/utils/atomic_write.py with write_text_atomic - settings.py: _write_yaml_config and _write_env_var use atomic write - skill_service.py: import_skill uses atomic write - skill_service.py: update_skill_config uses atomic write + fcntl.flock around the read-modify-write cycle to serialize concurrent updates - Add 11 unit tests covering happy path, crash safety, concurrency, errors	2026-06-22 17:03:27 +08:00
chiguyong	698a8fafba	fix(review): U7 refresh token hash verification on whoami ... The whoami route accepted rotated/old refresh tokens for cold-start because it only checked session revocation status, not the token hash. Now when token_type == "refresh", the route computes hash_token(token) and compares it with the session's stored refresh_token_hash using hmac.compare_digest (constant-time). Mismatch returns 401. - Add SessionService.get_stored_refresh_hash(session_id) helper - Add hash verification in whoami route (R9) - Add TestWhoamiTokenHash with 5 integration tests	2026-06-22 16:55:20 +08:00
chiguyong	206b82740c	fix(review): U5 DB migration — always run init_auth_db + busy_timeout	2026-06-22 16:40:30 +08:00
chiguyong	45b6752e0d	fix(review): U4 WebSocket quota enforcement + gateway-layer hardening	2026-06-22 16:37:23 +08:00
chiguyong	278d76b381	fix(review): U6 frontend field alignment + CLI top-users field fix	2026-06-22 16:28:44 +08:00
chiguyong	00c8386939	fix(review): U1 Redis quota enforcement — key construction + fail-closed + degradation recovery + async	2026-06-22 16:22:33 +08:00