Repository navigation
1.7.0
cfKanban 1.7.0
简体中文
相对正式版 1.6.0，本版汇总数据库读取、负责人选择和 Agent 项目范围与更新体验的改善，业务源码沿用已验收的 1.7.0-rc.3，仅收敛正式版本与发行说明。
- 减少不必要的数据库读取：改善成员、邀请及协作列表的分页和摘要查询，减少代表性场景中的重复读取，保留实时权限、完整历史和精确统计。
- 直接分配当前项目的人员：在看板卡片选择、更换或清除有资格的负责人，候选按 Principal ID 归一，分页不会重复列出同一人；保存时仍复核资格与版本。
- 紧凑且稳定的人员菜单：看板与事项详情共用菜单，圆形姓名首字符和勾选标记便于识别，支持键盘和手机触屏；加载、重试和分页收在菜单内，避免撑开卡片、引起布局跳动。
- 项目范围跟随工作树：Agent 从仓库子目录或 linked worktree 使用时，识别对应工作树根目录并复用项目关联；接受建议后才保存，保留既有关联。
- 技能更新承接准确目标：文字更新优先采用用户明确指定或当前会话明确承接的准确发行，否则发现最新正式版；分别核对安装副本与长期稳定更新来源。
English
Compared with stable 1.6.0, this release brings together improvements to database reads, assignee selection, and Agent project scope and update behavior, retaining the validated 1.7.0-rc.3 application source with only stable-version and release-note changes.
- Fewer unnecessary database reads: Improved member, invitation, and collaboration list pagination and summary queries reduce repeated reads in representative cases while preserving live permissions, complete history, and exact statistics.
- Assign eligible people in the current project: Select, change, or clear an assignee from a board card. Candidates are deduplicated by Principal ID across pages, and saving still checks eligibility and version.
- Compact, steady people menus: Boards and issue details share a menu with circular name initials and selection checkmarks, supporting keyboard and mobile touch interaction. Loading, retries, and pagination stay inside the menu to avoid expanding cards and shifting the layout.
- Project scope follows the worktree: Agents used from repository subdirectories or linked worktrees detect the corresponding worktree root and reuse project associations. Associations are saved only after acceptance, preserving existing targets.
- Skill updates retain an exact target: Text update requests prioritize a release explicitly selected by the user or clearly continued from the current conversation; otherwise they discover the latest stable release. The installed copy and long-term stable update source are checked separately.
升级与已知限制 / Upgrade and known limitations
从正式版 1.6.0 升级需先执行 0018_read_query_indexes.sql，将 schema 17 → 18，再部署 Worker；从 1.7.0-rc.3 升级没有新增 migration，schema 保持 18。API 保持 0.1.0，仍须核对真实迁移记录与 schema；Worker 回滚不会回退 D1。新增的 11 个索引有构建成本和持续写入放大，读取成本的本地隔离证据不能证明线上大规模计费降幅，稀疏匹配、空页和精确计数仍可能随历史或匹配规模增长。读取与索引成本记录
圆形人员标记使用姓名首字符，暂无头像上传。历史负责人失去资格时保留引用，不会自动替换。实例升级与 Skill 更新独立执行；准确历史版或 RC 的 release discover 请求需显式传入 selectionMode: exact_version 和准确 version，刷新固定 tag 不会自动取得最新正式版，当前聊天加载新版仍须单独核对。
Upgrading from stable 1.6.0 requires applying 0018_read_query_indexes.sql before deploying the Worker, moving schema 17 → 18. Upgrading from 1.7.0-rc.3 adds no migration and keeps schema at 18. The API remains 0.1.0. Verify the actual migration ledger and schema; Worker rollback does not roll back D1. The 11 new indexes carry construction costs and ongoing write amplification. Isolated local read-cost evidence does not establish lower live billing at large scale, and sparse matches, empty pages, and exact counts can still grow with history or matching data. Read and index cost evidence
Circular people badges use name initials; avatar uploads are unavailable. Historical assignee references remain when eligibility is lost, with no automatic replacement. Instance upgrades and Skill updates are independent. release discover requests for exact historical releases or RCs must pass selectionMode: exact_version and an exact version. Refreshing a fixed tag does not obtain the latest stable release, and loading the new version in the current chat requires separate verification.