@openturtle/cli 0.3.2 → 0.3.4

package/README.md

@@ -12,7 +12,7 @@ OpenTurtle CLI 是一个本地命令行工具。它让你不安装 Desktop，也
 npm install --global @openturtle/cli
 ```
 
-CLI 启动时会在后台检查 npm 新版本，最多每 24 小时检查一次。检查不会阻塞当前命令；发现新版本后会通过 npm 自动完成全局升级。
+CLI 启动时会在后台检查 npm 新版本，最多每 24 小时检查一次。检查不会阻塞当前命令；发现新版本后会通过 npm 自动完成全局升级，并刷新此前通过 `ot install` 安装的 Skill、Rule 和 Steering。
 
 也可以手动检查或立即升级：
 
@@ -27,7 +27,7 @@ ot update
 export OPENTURTLE_DISABLE_AUTO_UPDATE=1
 ```
 
-源码运行、`pnpm link` 等开发安装不会被自动覆盖。自动更新状态记录在 `~/.openturtle/cli/update.json`。
+源码运行、`pnpm link` 等开发安装不会被自动覆盖。自动更新状态记录在 `~/.openturtle/cli/update.json`，Agent 安装记录保存在 `~/.openturtle/cli/installations.json`。
 
 临时使用、不全局安装时：
 
@@ -53,18 +53,14 @@ ot projects list
 ot roster list
 ot context get --project <project-id>
 ot knowledge search "部署"
+ot knowledge local search "部署"
 ot meetings list --project <project-id>
+ot work summary --project <project-id>
 ot worklogs record --summary "完成联调" --type progress
 ot report draft --today
 ```
 
-如果你希望 AI 工具自动帮你记录开发过程，再执行：
-
-```bash
-ot install --target all --with-agent-hooks
-```
-
-hooks 只负责记录，不会阻止提交代码，也不会改变 AI 工具原本的行为。
+`ot install` 只安装 CLI 使用指引。Agent 直接执行 `ot ... --json`，不需要 MCP 或 Hook。
 
 ## 常用场景
 
@@ -83,15 +79,22 @@ ot todos progress <todo-id> --message "完成接口联调，等待验收"
 ### 记录一条工作日志
 
 ```bash
-ot worklogs record --summary "完成 Qoder hook 接入验证" --type progress
+ot worklogs record --summary "完成 Qoder CLI 接入验证" --type progress
 ```
 
-### 搜索知识
+### 聚合搜索知识
 
 ```bash
 ot knowledge search "日报"
 ```
 
+默认同时搜索云端知识和本地全文索引。只搜索本地：
+
+```bash
+ot knowledge search "日报" --local-only
+ot knowledge local search "日报"
+```
+
 ### 上传录音并处理会议
 
 ```bash
@@ -182,7 +185,6 @@ ot auth logout
 | ----------------- | -------------------- |
 | CLI command       | `ot`                 |
 | Package           | `@openturtle/cli`    |
-| MCP server name   | `ot-cli`             |
 | Project state dir | `.openturtle-cli/`   |
 | Global state dir  | `~/.openturtle/cli/` |
 
@@ -191,7 +193,6 @@ ot auth logout
 - CLI 项目状态只写 `.openturtle-cli/`
 - CLI 全局状态只写 `~/.openturtle/cli/`
 - 不要创建或写入项目 `.openturtle/`
-- 不要覆盖 Desktop 的 `openturtle-knowledge`
 - 不要覆盖 Desktop 的 `openturtle-automations`
 - 不要覆盖旧的 `openturtle-todo`
 
@@ -239,7 +240,6 @@ ot init --update-gitignore
 .openturtle-cli/
 ├── config.json
 ├── state.db
-├── hooks/
 ├── drafts/
 └── cache/
 ```
@@ -289,22 +289,15 @@ ot auth status
 
 ### 5. 安装 Agent 接入
 
-默认安装 MCP、rules/skills 和 Git hook，不安装 Agent hooks：
+安装 Agent 的 CLI Skill、Rule 或 Steering：
 
 ```bash
 ot install --target all
 ```
 
-安装 Agent hooks：
-
-```bash
-ot install --target all --with-agent-hooks
-```
-
 只安装某个目标：
 
 ```bash
-ot install --target git
 ot install --target claude
 ot install --target codex
 ot install --target cursor
@@ -336,92 +329,25 @@ ot uninstall --target kiro
 ot uninstall --target all
 ```
 
-卸载只会删除 `ot-cli` MCP server、`OPENTURTLE-CLI` 托管 hook、CLI 写入的 rule/skill/steering/agent 文件，以及 `.openturtle-cli/` 本地状态目录。它会保留非 OpenTurtle 配置、用户自己的 hook、Desktop/旧版 MCP server，例如 `openturtle-knowledge`、`openturtle-automations`、`openturtle-todo`。
+卸载只会删除 CLI 写入的 rule/skill/steering/managed note，以及 `.openturtle-cli/` 本地状态目录。它会保留用户自己的 Agent 配置。
 
-如果 Git 原来已有 `post-commit` hook，卸载会恢复原 hook，然后删除 OpenTurtle CLI 的备份文件。
+安装时会迁移旧版本：删除旧 `ot-cli` MCP 和 `OPENTURTLE-CLI` 托管 Hook 条目，同时保留用户自己的 MCP server 和 Hook。`ot uninstall --target git` 仅作为旧版 Git Hook 的清理入口保留，已经不能再安装 Git Hook。
 
 ### 6. Target 安装矩阵
 
-| Target | 默认安装                                      | `--with-agent-hooks`                                                          |
-| ------ | --------------------------------------------- | ----------------------------------------------------------------------------- |
-| Git    | `.git/hooks/post-commit`                      | 同默认                                                                        |
-| Claude | `ot-cli` MCP、Skill                           | `UserPromptSubmit`、`PreToolUse`、`PostToolUse`、`Stop`                       |
-| Codex  | `ot-cli` MCP、Skill、`AGENTS.md` managed note | `PreToolUse`、`PostToolUse`、`Stop`                                           |
-| Cursor | project `.mcp.json`、Cursor Rule              | `preToolUse`、`postToolUse`                                                   |
-| Qoder  | MCP、Skill                                    | `UserPromptSubmit`、`PreToolUse`、`PostToolUse`、`PostToolUseFailure`、`Stop` |
-| Kiro   | MCP、Steering                                 | `agentSpawn`、`userPromptSubmit`、`preToolUse`、`postToolUse`、`stop`         |
-
-Qoder 和 Kiro 支持 native hook。CLI 仍保留 `import-history` 和 `watch`，用于补齐旧会话或未启用 hook 的环境。
-
-### 7. Hooks 的作用
-
-hooks 是本地记录入口。它们把开发过程写入 `.openturtle-cli/state.db`，用于工作日志、待办进展证据和日报草稿。
+| Target | 安装内容                        |
+| ------ | ------------------------------- |
+| Claude | Skill                           |
+| Codex  | Skill、`AGENTS.md` managed note |
+| Cursor | Cursor Rule                     |
+| Qoder  | Skill                           |
+| Kiro   | Steering                        |
 
-会记录：
+### 7. CLI 接入模型
 
-- Git commit
-- 用户提交给 Agent 的 prompt
-- Agent tool call 前后
-- Agent tool call 失败
-- Agent session stop
-- history import 记录
+所有 Agent 都直接执行 `ot ... --json`。读取命令直接运行；写命令先加 `--dry-run` 检查请求，再执行正式写入。CLI 本身负责认证、后端访问、稳定 JSON、自动更新，以及升级后刷新已安装的 Agent 指引。
 
-不会做：
-
-- 不阻止 Git commit
-- 不阻止 Agent tool call
-- 不替用户批准危险操作
-- 不上传私有文件内容
-- 不修改 Desktop MCP server
-
-Git hook 会保留已有 hook。原 hook 的退出码会保留，OpenTurtle 采集失败不会改变 commit 结果。
-
-### 8. MCP server
-
-MCP server 名固定为：
-
-```text
-ot-cli
-```
-
-启动：
-
-```bash
-ot mcp serve
-```
-
-tools：
-
-```text
-list_my_todos
-list_goals
-list_workspace_knowledge
-search_workspace_knowledge
-list_knowledge_source_files
-read_knowledge_source_file
-record_worklog
-list_worklogs
-draft_daily_report
-update_todo_progress
-update_todo_status
-```
-
-`list_workspace_knowledge` / `search_workspace_knowledge` 查询可复用知识对象。`list_knowledge_source_files` / `read_knowledge_source_file` 只查看知识背后的来源文件或原文文件，不把来源文件当成第二套知识库。
-
-MCP tools 优先访问 OpenTurtle API。云端不可用时，尽量返回本地缓存或本地草稿信息，并标记 `source: "local_cache"`。
-
-MCP smoke test：
-
-```bash
-printf '%s\n' \
-  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' \
-  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \
-  | ot mcp serve
-```
-
-期望 `serverInfo.name` 是 `ot-cli`。
-
-### 9. 资源命令
+### 8. 资源命令
 
 项目、团队成员和项目上下文：
 
@@ -430,6 +356,9 @@ ot projects list --keyword "OpenTurtle"
 ot projects resolve "OpenTurtle"
 ot projects show <project-id> --members
 ot roster list
+ot roster list --project <project-id>
+ot work summary --project <project-id>
+ot digest get --project <project-id> --window this_week
 ot context get --project <project-id> --query "本周风险" --section risk
 ot context item meeting <meeting-id> --project <project-id>
 ```
@@ -463,6 +392,8 @@ ot todos review <todo-id> --body-file review-decision.json --dry-run
 ```bash
 ot knowledge list
 ot knowledge search "日报"
+ot knowledge search "日报" --cloud-only
+ot knowledge search "日报" --local-only
 ot knowledge show <knowledge-id>
 ot knowledge relations <knowledge-id>
 ot knowledge save --body-file knowledge.json --dry-run
@@ -479,9 +410,16 @@ ot knowledge attachment-download <knowledge-id> <attachment-id> --output ./desig
 ot knowledge sources --path docs
 ot knowledge sources --q "WPS"
 ot knowledge source docs/guide.md
+ot knowledge local list
+ot knowledge local search "部署规范"
+ot knowledge local read <asset-id>
+ot knowledge local import ./docs --dry-run
+ot knowledge local create --body-file local-note.json --dry-run
+ot knowledge local update <asset-id> --body-file local-note.json --dry-run
+ot knowledge local remove <asset-id> --dry-run
 ```
 
-知识对象是可复用的结论、规范、经验、决策沉淀和操作手册。来源文件是知识背后的原文、附件或仓库文档。
+`ot knowledge search` 返回 `{ query, cloud, local }` 聚合结果；`--cloud-only` 和 `--local-only` 可限定范围。知识对象是可复用的结论、规范、经验、决策沉淀和操作手册。来源文件是知识背后的原文、附件或仓库文档，本地知识索引可脱离 Desktop 使用。
 
 会议：
 
@@ -508,8 +446,8 @@ ot meetings updates ignore <meeting-id> <update-id> --dry-run
 
 ```bash
 ot worklogs list --today
-ot worklogs record --summary "完成 Qoder hook 接入验证" --type progress
-ot worklogs record --summary "Codex hook trust 需要用户确认" --type blocker
+ot worklogs record --summary "完成 Qoder CLI 接入验证" --type progress
+ot worklogs record --summary "Codex CLI 登录需要用户确认" --type blocker
 ot worklogs create --body-file worklog.json --dry-run
 ```
 
@@ -529,26 +467,7 @@ ot report draft --today
 ot report draft --today --output .openturtle-cli/drafts/today.md
 ```
 
-### 10. 历史导入与监听
-
-一次性导入：
-
-```bash
-ot import-history --target qoder
-ot import-history --target kiro
-ot import-history --target all
-```
-
-查看 watcher 路径：
-
-```bash
-ot watch --target qoder
-ot watch --target kiro
-```
-
-v1 优先使用 native hook。`import-history` 和 `watch` 是兜底能力。
-
-### 11. AI Agent 推荐流程
+### 9. AI Agent 推荐流程
 
 当你需要在一个新工作区启用 CLI：
 
@@ -560,12 +479,6 @@ ot install --target all
 ot --json doctor
 ```
 
-只有用户明确要求自动记录 Agent 行为时，才执行：
-
-```bash
-ot install --target all --with-agent-hooks
-```
-
 然后优先使用高层命令：
 
 ```bash
@@ -580,21 +493,19 @@ ot report draft --today
 
 不要直接改 `.openturtle-cli/state.db`，除非用户明确要求底层排查。
 
-### 12. AI Agent 禁止事项
+### 10. AI Agent 禁止事项
 
 - 不要写项目 `.openturtle/`
-- 不要覆盖 `openturtle-knowledge`
 - 不要覆盖 `openturtle-automations`
 - 不要覆盖旧 `openturtle-todo`
 - 不要删除用户已有 Agent 配置
 - 不要把 token 写入代码、README、commit 或日志
-- 不要让 hook 阻塞 Git commit 或 Agent tool call
-- 不要伪造 Codex hook trust state
+- 不要安装或调用旧版 OpenTurtle MCP/Hook
 - 不要在会议 Knowledge 尚未发布时确认项目更新
 - 不要跳过 `meetings updates list` 直接批量确认会议草稿
 - 不要修改 Qoder/Kiro 私有未知格式文件；只写本文列出的配置面
 
-### 13. JSON 输出约定
+### 11. JSON 输出约定
 
 CLI 默认输出 JSON，便于 AI Agent 读取。
 
@@ -624,7 +535,7 @@ CLI 默认输出 JSON，便于 AI Agent 读取。
 
 token 不应该被完整打印，`auth status` 只显示脱敏 token。
 
-### 14. 开发验证
+### 12. 开发验证
 
 在 `frontend` 目录执行：
 
@@ -642,7 +553,9 @@ npm pack --dry-run
 
 期望包内只包含 `dist/`、`README.md` 和 `package.json` 等运行所需文件，不包含 `src/` 或 `test/`。
 
-### 15. npm 自动发布
+### 13. npm 自动发布
+
+完整的校验、Trusted Publisher、人工兜底、npm 二次认证、远端 `master` 对齐和 Skill 刷新检查见 [RELEASE_RUNBOOK.md](./RELEASE_RUNBOOK.md)。
 
 `.github/workflows/cli-npm-release.yml` 会在 `master` 的 CLI 文件发生变化时运行测试和构建，
 然后以仓库版本为最低版本、基于 npm 已发布版本自动递增 patch，发布公开包 `@openturtle/cli`。
@@ -659,28 +572,15 @@ npm pack --dry-run
 创建包并配置 Trusted Publisher 后，后续 `master` 发布只使用短期 OIDC 凭证。发布固定使用
 `https://registry.npmjs.org/`，不受开发机 `npmmirror` 配置影响。
 
-构建后 MCP smoke test：
-
-```bash
-printf '%s\n' \
-  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' \
-  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \
-  | node apps/cli/dist/index.js mcp serve
-```
-
 ## 常见问题
 
 ### 我没有安装 Desktop，可以用吗？
 
 可以。CLI 的目标就是让没有 Desktop 的用户也能使用 OpenTurtle。
 
-### 安装 hook 会不会影响我提交代码？
-
-不会。它只记录信息，记录失败也不会改变提交结果。
-
-### Qoder 和 Kiro 支持 hook 吗？
+### 为什么升级 CLI 后 Skill 也会更新？
 
-支持。Qoder 使用 settings hook；Kiro 使用 hooks/agent 配置。
+`ot install` 会记录安装过的 target、scope 和工作区。手动执行 `ot update` 或启动时自动更新 npm 包后，新版 CLI 会重新写入这些 Skill、Rule 和 Steering，并清理旧的 OpenTurtle MCP/Hook 配置。
 
 ### 为什么不用 `.openturtle/`？
 

package/RELEASE_RUNBOOK.md

@@ -0,0 +1,193 @@
+# OpenTurtle CLI Release Runbook
+
+This runbook publishes `@openturtle/cli` to the public npm registry and verifies that the installed `ot` command and companion Agent guidance are usable outside the source repository.
+
+## Release Boundaries
+
+- Package: `@openturtle/cli`
+- Binary: `ot`
+- Registry: `https://registry.npmjs.org/`
+- Source: `packages/frontend/apps/cli`
+- Release branch: `master`
+- Workflow: `.github/workflows/cli-npm-release.yml`
+- Authentication: npm Trusted Publisher in CI; npm browser authentication for manual fallback
+
+The package is CLI + Skill/Rule/Steering only. It must not ship the removed OpenTurtle MCP server, Hook commands, Git Hook installer, or history watcher.
+
+## Prerequisites
+
+Run from the repository root unless a command says otherwise.
+
+```bash
+node --version
+pnpm --version
+npm --version
+git status --short
+npm view @openturtle/cli version --registry=https://registry.npmjs.org
+```
+
+Requirements:
+
+- Node.js satisfies `packages/frontend/apps/cli/package.json#engines`.
+- Dependencies are installed from the repository lockfile.
+- CLI changes are isolated from unrelated worktree changes.
+- The intended release commit is present on both GitLab and GitHub `master` before declaring source delivery complete.
+- npm Trusted Publisher points to `aka-danielZhang/openturtle-os` and `cli-npm-release.yml`.
+
+Never stage unrelated Desktop, backend, mobile, generated local state, or `.openturtle-cli/` files with a CLI release.
+
+## Required Validation
+
+```bash
+cd packages/frontend
+pnpm install --frozen-lockfile
+pnpm --filter @openturtle/cli test
+pnpm --filter @openturtle/cli build
+
+cd apps/cli
+npm pack --dry-run --json --registry=https://registry.npmjs.org
+```
+
+The tarball must contain `dist/index.js`, runtime modules, `README.md`, and `package.json`. It must not contain any of these removed runtime files:
+
+```text
+dist/mcp/server.js
+dist/commands/hook.js
+dist/installers/git.js
+dist/watchers/importers.js
+```
+
+The build script deletes `dist` before TypeScript compilation so removed source files cannot survive as stale package artifacts.
+
+## Normal Release: GitHub Actions
+
+The normal path is a push to GitHub `master` that changes the CLI package or root lockfile.
+
+1. Merge the validated CLI commit into `master` without including unrelated files.
+2. Push `master` to GitLab and GitHub.
+3. Confirm `.github/workflows/cli-npm-release.yml` starts on GitHub.
+4. Wait for test, build, version resolution, package inspection, and publish steps to complete.
+5. Verify the published package from npm, not only the workflow status.
+
+The workflow treats the repository package version as a floor. If npm already has that version or a newer one, `nextReleaseVersion()` increments the published patch version. The workflow does not require `NPM_TOKEN` or `NODE_AUTH_TOKEN`.
+
+Verification:
+
+```bash
+npm view @openturtle/cli version dist.tarball dist.shasum --json \
+  --registry=https://registry.npmjs.org
+```
+
+Do not declare completion while the workflow is queued, running, or blocked by GitHub billing. Use the manual fallback when CI cannot start and the release is required immediately.
+
+## Manual Fallback
+
+Use this only when Trusted Publisher CI is unavailable or when an explicitly requested release must happen before the `master` merge.
+
+1. Confirm npm login and the currently published version:
+
+```bash
+npm whoami --registry=https://registry.npmjs.org
+npm view @openturtle/cli version --registry=https://registry.npmjs.org
+```
+
+2. Set `packages/frontend/apps/cli/package.json` to an unused stable version.
+3. Run the required validation above.
+4. Publish from the package directory:
+
+```bash
+cd packages/frontend/apps/cli
+npm publish --access public --registry=https://registry.npmjs.org
+```
+
+5. Complete npm's browser authentication when prompted. A successful terminal result contains:
+
+```text
++ @openturtle/cli@<version>
+```
+
+6. Verify the exact published version and tarball metadata:
+
+```bash
+npm view @openturtle/cli@<version> version dist.tarball dist.shasum --json \
+  --registry=https://registry.npmjs.org
+```
+
+After a manual publish, still merge and push the exact source to both `master` branches. A later CI run may publish the next patch because the workflow always chooses an unused version.
+
+## Installed Package Smoke Test
+
+Test the public package from a temporary directory, not only from the repository:
+
+```bash
+release_tmp="$(mktemp -d)"
+cd "$release_tmp"
+pnpm dlx @openturtle/cli@<version> --help
+pnpm dlx @openturtle/cli@<version> --json doctor
+```
+
+For a global-install smoke test:
+
+```bash
+npm install --global @openturtle/cli@<version> \
+  --registry=https://registry.npmjs.org
+command -v ot
+ot --version
+ot --json doctor
+```
+
+`doctor` may report missing authentication, but it must return stable JSON rather than crash.
+
+## Skill Refresh Verification
+
+`ot install` records Agent installations in `~/.openturtle/cli/installations.json`. Both `ot update` and the startup auto-update worker reinstall the recorded Skill, Rule, or Steering after npm updates.
+
+Verify at least one installed target:
+
+```bash
+ot install --target codex --scope user
+ot update --check
+```
+
+After an actual version update, confirm the installed Skill contains the new direct CLI guidance:
+
+```bash
+rg -n "ot --json doctor|ot \.\.\. --json" ~/.codex/skills/openturtle-cli/SKILL.md
+```
+
+Installation and refresh must also remove only the legacy OpenTurtle-managed `ot-cli` MCP and `OPENTURTLE-CLI` Hook entries. User-owned MCP servers, Hooks, rules, and settings must remain intact.
+
+## Source Delivery Verification
+
+Before closing the release, compare the intended commit with both remotes:
+
+```bash
+git ls-remote --heads gitlab master
+git ls-remote --heads origin master
+git log -1 --oneline master
+```
+
+If the remotes differ, inspect ancestry and merge rather than force-pushing:
+
+```bash
+git merge-base --is-ancestor <gitlab-master> <release-commit>
+git merge-base --is-ancestor <github-master> <release-commit>
+```
+
+Report all of the following:
+
+- Published npm version and tarball shasum
+- Test/build/package inspection result
+- GitLab `master` commit
+- GitHub `master` commit
+- Workflow result or the reason manual fallback was used
+- Installed `ot --version` and Skill refresh result
+
+## Failure Recovery
+
+- `npm publish` reports an existing version: choose a new stable version; never reuse or overwrite an npm version.
+- Browser authentication expires: rerun `npm publish` and complete the newly generated npm authentication URL.
+- CI cannot start because of billing: use the manual fallback, then still merge the source to `master`.
+- Package contains removed files: ensure the build cleans `dist`, rebuild, and repeat `npm pack --dry-run --json`.
+- Skill is stale after update: inspect `~/.openturtle/cli/installations.json`, rerun `ot install --target <agent> --scope <scope>`, then verify the installed Skill/Rule/Steering.
+- One remote `master` is ahead: fetch both remotes, inspect commits, merge in a clean worktree, and push without force.

package/dist/commands/collaboration.js

@@ -29,17 +29,73 @@ export function createCollaborationCommands(client = new ApiClient()) {
                 candidates: exact ? [] : items,
             };
         },
-        async listRoster(teamId) {
+        async listRoster(teamId, projectId) {
             const team = teamId ? { id: teamId } : await client.get('/api/teams/me');
             const resolvedTeamId = String(team.id || teamId || '');
             if (!resolvedTeamId)
                 throw new Error('Current team response did not include an id');
-            const [members, profile, rosterProfile] = await Promise.all([
+            const [members, profile, rosterProfile, projectMembers] = await Promise.all([
                 client.get(`/api/teams/${encodeURIComponent(resolvedTeamId)}/members`, { page_size: 100 }),
                 client.get('/api/me/profile').catch(() => null),
                 client.get('/api/me/roster-profile').catch(() => null),
+                projectId
+                    ? client.get(`/api/projects/${encodeURIComponent(projectId)}/members`).catch(() => null)
+                    : Promise.resolve(null),
             ]);
-            return { team, profile, roster_profile: rosterProfile, members };
+            return { team, profile, roster_profile: rosterProfile, project_id: projectId || null, members, project_members: projectMembers };
+        },
+        async getWorkSummary(options) {
+            const limit = Number(options.limit) || 20;
+            const goalId = String(options.goal || '');
+            const projectId = String(options.project || '');
+            const todos = goalId
+                ? client.get(`/api/goals/${encodeURIComponent(goalId)}/todos`, {
+                    status: options.status,
+                    page: 1,
+                    page_size: limit,
+                })
+                : client.get('/api/todos', {
+                    scope: 'assigned',
+                    project_id: projectId || undefined,
+                    status: options.status,
+                    page: 1,
+                    page_size: limit,
+                });
+            const [digest, todoPage, notifications] = await Promise.all([
+                client.get('/api/goals/daily-digest/me'),
+                todos,
+                options.notifications === false
+                    ? Promise.resolve(null)
+                    : client.get('/api/notifications', { is_read: false, page: 1, page_size: limit }),
+            ]);
+            return {
+                project_id: projectId || null,
+                goal_id: goalId || null,
+                digest,
+                todos: todoPage,
+                notifications,
+            };
+        },
+        getProjectDigest: (projectId, window) => client.get('/api/digest', { project_id: projectId, window }),
+        async runOrgSyncSynthesis(options, dryRun = false) {
+            const scope = String(options.scope || 'active-project');
+            const projectId = String(options.project || '');
+            if (scope !== 'all' && !projectId)
+                throw new Error('--project is required unless --scope all is used');
+            const body = listQuery({
+                project_id: scope === 'all' ? undefined : projectId,
+                limit: options.limit,
+                updated_after: options.updatedAfter,
+            });
+            if (dryRun)
+                return dryRunRequest('POST', '/api/orgsync-synthesis/run', body);
+            const result = await client.post('/api/orgsync-synthesis/run', body);
+            return {
+                scope: scope === 'all' ? 'all' : 'active_project',
+                project_id: scope === 'all' ? null : projectId,
+                updated_after: options.updatedAfter || null,
+                result,
+            };
         },
         resolveContext: (body) => client.post('/api/project-context/resolve', body),
         getContextItem: (sourceType, sourceId, options) => client.get(`/api/project-context/items/${encodeURIComponent(sourceType)}/${encodeURIComponent(sourceId)}`, listQuery(options)),
@@ -127,7 +183,35 @@ export function registerCollaborationCommands(program, groups, callbacks) {
         .description('Current team roster')
         .command('list')
         .option('--team <id>')
-        .action(action(async (options) => print(await commands.listRoster(options.team))));
+        .option('--project <id>', 'include project roles and membership')
+        .action(action(async (options) => print(await commands.listRoster(options.team, options.project))));
+    program
+        .command('work')
+        .description('Current user action summary')
+        .command('summary')
+        .option('--project <id>')
+        .option('--goal <id>')
+        .option('--status <status>')
+        .option('--limit <number>', 'maximum todos and notifications', Number)
+        .option('--no-notifications')
+        .action(action(async (options) => print(await commands.getWorkSummary(options))));
+    program
+        .command('digest')
+        .description('Project execution digest')
+        .command('get')
+        .option('--project <id>')
+        .option('--window <window>', 'today|yesterday|this_week|last_week|this_month', 'today')
+        .action(action(async (options) => print(await commands.getProjectDigest(options.project, options.window))));
+    program
+        .command('orgsync')
+        .description('Generate reviewable organization knowledge candidates')
+        .command('synthesize')
+        .option('--scope <scope>', 'active-project|all', 'active-project')
+        .option('--project <id>')
+        .option('--limit <number>', 'maximum recent sessions', Number, 20)
+        .option('--updated-after <iso-time>')
+        .option('--dry-run')
+        .action(action(async (options) => print(await commands.runOrgSyncSynthesis(options, Boolean(options.dryRun)))));
     const context = program.command('context').description('Viewer-scoped project context');
     context
         .command('get')