@chorus-aidlc/chorus 0.14.1 → 0.14.2

package/.next/standalone/public/kiro-plugin/.kiro/skills/chorus-yolo/SKILL.md

@@ -4,7 +4,7 @@ description: Full-auto AI-DLC pipeline — from prompt to done. Automates the en
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---
@@ -508,7 +508,7 @@ After all waves complete, output a markdown summary:
 
 ### Phase 5b: Idea Completion Report (mandatory)
 
-A successful `/chorus-yolo` run always finishes the Idea — call `chorus_create_report` once with `proposalUuid` set to the last verified proposal. The tool's description carries the section template; follow it. Surface the returned `documentUuid` in the Phase 5 summary. Skipping is a protocol violation.
+A successful `/chorus-yolo` run always finishes the Idea — call `chorus_create_report` once with `proposalUuid` set to the last verified proposal. The `content` parameter's description carries the section template; follow it. Surface the returned `documentUuid` in the Phase 5 summary. Skipping is a protocol violation.
 
 > **Order:** the completion report is written only **after** the Phase 4.5 code-review gateway returns PASS / PASS WITH NOTES. Never write it while a code-review FAIL is outstanding — the report is a ship-time summary, and the gateway is what clears the feature to ship.
 

package/.next/standalone/public/kiro-plugin/.kiro/steering/chorus.md

@@ -143,7 +143,7 @@ Main agent: no session needed — call tools without `sessionUuid`. See `/chorus
 
 ### Reports
 
-A **report** is a short idea-completion summary persisted as a `type="report"` Document at end-of-Idea, authored via `chorus_create_report` (gated on `document:write`). The tool's description carries the section template — read it there. `/chorus-yolo` writes one mandatorily; `/chorus-develop` offers it advisorily on last-task verify.
+A **report** is a short idea-completion summary persisted as a `type="report"` Document at end-of-Idea, authored via `chorus_create_report` (gated on `document:write`). The `content` parameter's description carries the section template — read it there. `/chorus-yolo` writes one mandatorily; `/chorus-develop` offers it advisorily on last-task verify.
 
 ### References
 
@@ -320,6 +320,19 @@ The plugin ships three read-only reviewer subagents (`chorus-code-reviewer`, `ch
 
 Reviewers post a VERDICT comment with one of three outcomes: **PASS** (no issues), **PASS WITH NOTES** (minor non-blocking notes), or **FAIL** (BLOCKERs found). Results are advisory — they do not block approval, verification, or ship; the code-review gateway in particular is behavioral (it does not change the Idea's stored status). On a code-review FAIL, fix it via the `/chorus-quick-dev` workflow: `chorus_create_tasks` with `proposalUuid` set to the current approved proposal so the fix tasks attach to it, then execute → verify and re-run the gateway.
 
+### 6. Enable OpenSpec Mode (Optional)
+
+Opt-in spec-driven path: `/chorus-proposal`, `/chorus-develop`, `/chorus-yolo` write `proposal.md` / `design.md` / spec deltas on disk and mirror them into Chorus drafts. Fully optional — free-form authoring works without it. The stage skills re-check the three activation signals inline (the Kiro spawn hook shows no OpenSpec banner): `CHORUS_OPENSPEC_MODE` ≠ `off`, an `openspec/` directory at the project root, and the `openspec` CLI on `PATH`.
+
+**When the user wants it on**, actually **enable it for them** — run whichever steps are missing, don't just describe them:
+
+```bash
+npm i -g @fission-ai/openspec       # 1. install the CLI if it's not on PATH (global, pure Node)
+openspec init --tools kiro          # 2. scaffold openspec/ + wire up Kiro's native integration
+```
+
+`openspec init` is interactive if you omit `--tools`; pass `--tools kiro` to run it unattended. Chorus's detection only needs the `openspec/` directory, but wiring up Kiro also gives OpenSpec its own integration. There's no SessionStart banner on Kiro — the stage skills re-check the three signals inline, so once the directory and CLI are both present they fold in `/chorus-openspec-aware` automatically (no re-launch needed). To turn it off, set `CHORUS_OPENSPEC_MODE=off`.
+
 ---
 
 ## Execution Rules

package/.next/standalone/public/kiro-plugin/bin/chorus-api.sh

@@ -240,7 +240,7 @@ cmd_mcp_tool() {
     # Step 1: Initialize MCP session
     local init_payload
     init_payload=$(cat <<JSONEOF
-{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"chorus-hook","version":"0.1.1"}}}
+{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"chorus-hook","version":"0.14.2"}}}
 JSONEOF
 )
 

package/.next/standalone/public/skill/brainstorm-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Optional divergent-then-convergent dialogue for fuzzy ideas. Invoke
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/skill/chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Chorus AI Agent collaboration platform — overview, common tools,
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---
@@ -196,7 +196,7 @@ Results can be filtered by project(s) using optional HTTP headers in your MCP co
 
 ### Reports
 
-A **report** is a short idea-completion summary persisted as a `type="report"` Document at end-of-Idea, authored via `chorus_create_report` (gated on `document:write`). The tool's description carries the section template — read it there. The `yolo` skill writes one mandatorily; the `develop` skill offers it advisorily on last-task verify.
+A **report** is a short idea-completion summary persisted as a `type="report"` Document at end-of-Idea, authored via `chorus_create_report` (gated on `document:write`). The `content` parameter's description carries the three-section template (`## Summary` / `## Decisions` / `## Follow-ups`) — read it there. The `yolo` skill writes one mandatorily; the `develop` skill offers it advisorily on last-task verify.
 
 ### References
 

package/.next/standalone/public/skill/code-reviewer-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Read-only adversarial Chorus code-review gateway — independently
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/skill/develop-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Chorus Development workflow — claim tasks, report work, self-chec
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---
@@ -203,7 +203,7 @@ Once Admin verifies (status: `done`), move to the next available task (back to S
 
 ### Step 11: Idea Completion Report (advisory)
 
-If the task you just self-verified was the LAST one of its Idea (every Task across every approved Proposal is now `done`/`closed`) and you have `document:write`, prompt the user and call `chorus_create_report` on accept. The tool description carries the section template. Skip on decline.
+If the task you just self-verified was the LAST one of its Idea (every Task across every approved Proposal is now `done`/`closed`) and you have `document:write`, prompt the user and call `chorus_create_report` on accept. The `content` parameter's description carries the section template. Skip on decline.
 
 ---
 

package/.next/standalone/public/skill/idea-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Chorus Idea workflow — claim ideas, run elaboration rounds, and p
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/skill/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chorus-skill",
-  "version": "0.14.1",
+  "version": "0.14.2",
   "description": "Chorus AI Agent collaboration platform skill. Supports PM, Developer, and Admin roles via MCP tools for the Idea-Proposal-Task workflow.",
   "author": "chorus",
   "license": "AGPL-3.0",

package/.next/standalone/public/skill/proposal-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Chorus Proposal workflow — create proposals with document and tas
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/skill/proposal-reviewer-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Read-only adversarial Chorus proposal reviewer — audits PRD/task
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/skill/quick-dev-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Quick Task workflow — skip Idea→Proposal, create tasks directly
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/skill/review-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Chorus Review workflow — approve/reject proposals, verify tasks,
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/skill/task-reviewer-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Read-only adversarial Chorus task reviewer — independently verifi
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/skill/yolo-chorus/SKILL.md

@@ -4,7 +4,7 @@ description: Full-auto AI-DLC pipeline — drive a single prompt from Idea throu
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.14.1"
+  version: "0.14.2"
   category: project-management
   mcp_server: chorus
 ---
@@ -514,14 +514,14 @@ When all waves complete, output a markdown summary:
 
 ### Phase 5b: Idea Completion Report (mandatory)
 
-A successful yolo run always finishes the Idea. Call `chorus_create_report` **exactly once**, with `proposalUuid` set to the **last verified proposal**. The tool's own description carries the section template — follow it. Surface the returned `documentUuid` in the Phase 5 summary table. Skipping this is a protocol violation.
+A successful yolo run always finishes the Idea. Call `chorus_create_report` **exactly once**, with `proposalUuid` set to the **last verified proposal**. The `content` parameter's description carries the three-section template (`## Summary` / `## Decisions` / `## Follow-ups`) — follow it. Surface the returned `documentUuid` in the Phase 5 summary table. Skipping this is a protocol violation.
 
 > **Order:** write the completion report only **after** the Phase 4.5 code-review gateway returns PASS / PASS WITH NOTES. Never write it while a code-review FAIL is outstanding — the report is a ship-time summary, and the gateway is what clears the feature to ship.
 
 ```
 result = chorus_create_report({
   proposalUuid: "<last-verified-proposal-uuid>",
-  // ... follow the tool description's section template ...
+  // ... follow the content parameter's section template ...
 })
 # Surface result.documentUuid in the Phase 5 summary.
 ```

package/README.ja.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="docs/images/chorus-slug.png" alt="Chorus" width="240" />
+  <img src="packages/landing/public/images/chorus-slug.png" alt="Chorus" width="240" />
 </p>
 
 <p align="center"><strong>AI と人間の協働のための Agent Harness</strong></p>
@@ -180,7 +180,7 @@ CHORUS_DAEMON_CWDS="~/work/repo-a:~/work/repo-b" chorus daemon   # または環
 
 ### リモートエージェントのウェイク — ディレクトリにディスパッチし、実行を見守る
 
-![Remote Agent Wake](docs/images/agent-daemon-wake.gif)
+![Remote Agent Wake](packages/landing/public/images/agent-daemon-wake.gif)
 
 着想をリモートエージェントの特定のディレクトリに割り当て、会話を開くと、ローカルの Claude Code が作業を引き受けてリアルタイムで実行する様子を見られます — ターミナルも手動の resume も不要です。
 
@@ -192,7 +192,7 @@ Chorus はプロジェクト全体を自動でマインドマップに整理し
 
 ### 提案 — AI エージェントがリアルタイムで計画を生成
 
-![Proposal Presence](docs/images/proposal-presence.gif)
+![Proposal Presence](packages/landing/public/images/proposal-presence.gif)
 
 PM エージェントが要件を分析し、PRD と課題 DAG を含む提案を生成する様子を見られます — エージェントの活動を示すリアルタイムのプレゼンスインジケーター付きです。
 
@@ -204,37 +204,37 @@ PM エージェントが要件を分析し、PRD と課題 DAG を含む提案
 
 ### カンバン — リアルタイムな課題フロー
 
-![Kanban Presence](docs/images/kanban-presence.gif)
+![Kanban Presence](packages/landing/public/images/kanban-presence.gif)
 
 カンバンボードはエージェントの作業に合わせて自動更新され、課題カードが To Do → In Progress → To Verify の間をリアルタイムで移動します。エージェントのプレゼンスインジケーターが、どのリソースが作業中かをハイライトします。
 
 ### カンバンと課題 DAG
 
-![Kanban & Task DAG](docs/images/kanan-dag.png)
+![Kanban & Task DAG](packages/landing/public/images/kanban-dag.png)
 
 課題のステータスを追跡するカンバンボードと、実行順序や並行経路を示す依存関係 DAG を並べて表示します。
 
 ### 着想と要件詳細化
 
-![Idea & Elaboration](docs/images/idea-elaborate.png)
+![Idea & Elaboration](packages/landing/public/images/idea-elaborate.png)
 
 PM エージェントは、提案を作成する前に、構造化された Q&A ラウンドを通じて要件を明確にします。パネルには、着想の詳細と、回答・カテゴリタグ付きの完了した詳細化ラウンドが並んで表示されます。
 
 ### 提案のレビュー
 
-![Proposal Review](docs/images/proposal.png)
+![Proposal Review](packages/landing/public/images/proposal.png)
 
 PM エージェントが生成した提案には、文書ドラフトと課題 DAG のドラフトが含まれます。管理者はこのパネルでレビューし、承認または却下します。
 
 ### 受け入れ基準 — 二経路の検証
 
-![Acceptance Criteria](docs/images/task-ac.png)
+![Acceptance Criteria](packages/landing/public/images/task-ac.png)
 
 開発エージェントのセルフチェックと管理者のレビューが、各受け入れ基準を独立して検証し、項目ごとに構造化された合格／不合格の根拠を残します。
 
 ### ユニバーサル検索 — Cmd+K コマンドパレット
 
-![Universal Search](docs/images/universal-search.png)
+![Universal Search](packages/landing/public/images/universal-search.png)
 
 6 種類すべてのエンティティ（課題・着想・提案・文書・プロジェクト・プロジェクトグループ）を横断して検索する Cmd+K コマンドパレットです。スコープの絞り込み（Global / Group / Project）、エンティティ種別ごとのフィルタタブ、キーボードナビゲーションに対応します。Web UI と AI エージェント（`chorus_search` MCP ツール経由）は、同じ検索バックエンドを共有します。
 
@@ -402,7 +402,7 @@ PGlite はポート 5433 で組み込み PostgreSQL を実行します。デー
 
 API キーは Web UI の **Settings → Agents → Create API Key** から作成します。キーは `cho_` で始まり、一度しか表示されません。
 
-![Create API Key](docs/images/create-key.png)
+![Create API Key](packages/landing/public/images/create-key.png)
 
 ---
 

package/README.ko.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="docs/images/chorus-slug.png" alt="Chorus" width="240" />
+  <img src="packages/landing/public/images/chorus-slug.png" alt="Chorus" width="240" />
 </p>
 
 <p align="center"><strong>AI-인간 협업을 위한 Agent Harness</strong></p>
@@ -180,7 +180,7 @@ CHORUS_DAEMON_CWDS="~/work/repo-a:~/work/repo-b" chorus daemon   # 또는 환경
 
 ### 원격 에이전트 웨이크 — 디렉터리로 디스패치하고 실행을 지켜보기
 
-![Remote Agent Wake](docs/images/agent-daemon-wake.gif)
+![Remote Agent Wake](packages/landing/public/images/agent-daemon-wake.gif)
 
 아이디어를 원격 에이전트의 특정 디렉터리에 배정한 다음 대화를 열면, 로컬 Claude Code가 작업을 이어받아 실시간으로 실행하는 모습을 볼 수 있습니다 — 터미널도, 수동 재개도 필요 없습니다.
 
@@ -192,7 +192,7 @@ Chorus는 프로젝트 전체를 마인드맵으로 자동 정리합니다 —
 
 ### 제안 — AI 에이전트가 실시간으로 계획을 생성
 
-![Proposal Presence](docs/images/proposal-presence.gif)
+![Proposal Presence](packages/landing/public/images/proposal-presence.gif)
 
 PM 에이전트가 요구사항을 분석하고 PRD와 작업 DAG를 포함한 제안을 생성하는 모습을 볼 수 있습니다 — 에이전트 활동을 보여주는 실시간 프레즌스 인디케이터와 함께 말이죠.
 
@@ -204,37 +204,37 @@ PM 에이전트가 요구사항을 분석하고 PRD와 작업 DAG를 포함한
 
 ### 칸반 — 실시간 작업 흐름
 
-![Kanban Presence](docs/images/kanban-presence.gif)
+![Kanban Presence](packages/landing/public/images/kanban-presence.gif)
 
 칸반 보드는 에이전트의 작업에 맞춰 자동으로 업데이트되며, 작업 카드가 To Do → In Progress → To Verify 사이를 실시간으로 이동합니다. 에이전트 프레즌스 인디케이터가 어떤 리소스가 작업 중인지 하이라이트합니다.
 
 ### 칸반 & 작업 DAG
 
-![Kanban & Task DAG](docs/images/kanan-dag.png)
+![Kanban & Task DAG](packages/landing/public/images/kanban-dag.png)
 
 작업 상태를 추적하는 칸반 보드와, 실행 순서 및 병렬 경로를 보여주는 의존성 DAG를 나란히 표시합니다.
 
 ### 아이디어 & 요구사항 구체화
 
-![Idea & Elaboration](docs/images/idea-elaborate.png)
+![Idea & Elaboration](packages/landing/public/images/idea-elaborate.png)
 
 PM 에이전트는 제안을 만들기 전에 구조화된 Q&A 라운드를 통해 요구사항을 명확히 합니다. 패널에는 아이디어 상세 정보와 함께, 답변 및 카테고리 태그가 달린 완료된 구체화 라운드가 나란히 표시됩니다.
 
 ### 제안 검토
 
-![Proposal Review](docs/images/proposal.png)
+![Proposal Review](packages/landing/public/images/proposal.png)
 
 PM 에이전트가 생성한 제안에는 문서 초안과 작업 DAG 초안이 담깁니다. 관리자는 이 패널에서 검토하여 승인하거나 거부합니다.
 
 ### 수락 기준 — 이중 경로 검증
 
-![Acceptance Criteria](docs/images/task-ac.png)
+![Acceptance Criteria](packages/landing/public/images/task-ac.png)
 
 개발자 에이전트의 자체 점검과 관리자의 검토가 각 수락 기준을 독립적으로 검증하며, 모든 항목마다 구조화된 통과/실패 증빙을 남깁니다.
 
 ### 유니버설 검색 — Cmd+K 커맨드 팔레트
 
-![Universal Search](docs/images/universal-search.png)
+![Universal Search](packages/landing/public/images/universal-search.png)
 
 6가지 엔티티 유형(작업·아이디어·제안·문서·프로젝트·프로젝트 그룹)을 아우르는 검색을 위한 Cmd+K 커맨드 팔레트입니다. 범위 필터링(Global / Group / Project), 엔티티 유형별 필터 탭, 키보드 내비게이션을 지원합니다. Web UI와 AI 에이전트(`chorus_search` MCP 도구를 통해)는 동일한 검색 백엔드를 공유합니다.
 
@@ -402,7 +402,7 @@ PGlite는 포트 5433에서 내장 PostgreSQL을 실행합니다. 데이터는 `
 
 API 키는 Web UI의 **Settings → Agents → Create API Key**에서 만듭니다. 키는 `cho_`로 시작하며 한 번만 표시됩니다.
 
-![Create API Key](docs/images/create-key.png)
+![Create API Key](packages/landing/public/images/create-key.png)
 
 ---
 

package/README.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="docs/images/chorus-slug.png" alt="Chorus" width="240" />
+  <img src="packages/landing/public/images/chorus-slug.png" alt="Chorus" width="240" />
 </p>
 
 <p align="center"><strong>The Agent Harness for AI-Human Collaboration</strong></p>
@@ -180,7 +180,7 @@ On startup the daemon banner prints the **exact `daemon.json` path it read** (an
 
 ### Remote Agent Wake — Dispatch to a Directory, Watch It Run
 
-![Remote Agent Wake](docs/images/agent-daemon-wake.gif)
+![Remote Agent Wake](packages/landing/public/images/agent-daemon-wake.gif)
 
 Assign an idea to a specific directory on a remote agent, then open the conversation and watch the local Claude Code pick up the work and run in real time — no terminal, no manual resume.
 
@@ -192,7 +192,7 @@ Chorus auto-organizes the entire project into a mind-map — Ideas, Proposals, D
 
 ### Proposal — AI Agent Generates Plans in Real Time
 
-![Proposal Presence](docs/images/proposal-presence.gif)
+![Proposal Presence](packages/landing/public/images/proposal-presence.gif)
 
 Watch a PM Agent analyze requirements and generate a proposal with PRD and task DAG — with real-time presence indicators showing agent activity.
 
@@ -204,37 +204,37 @@ The left panel is a pixel workspace where pixel characters represent each Agent'
 
 ### Kanban — Real-time Task Flow
 
-![Kanban Presence](docs/images/kanban-presence.gif)
+![Kanban Presence](packages/landing/public/images/kanban-presence.gif)
 
 The Kanban board updates automatically as Agents work, with task cards flowing between To Do → In Progress → To Verify in real time. Agent presence indicators highlight which resources are being worked on.
 
 ### Kanban & Task DAG
 
-![Kanban & Task DAG](docs/images/kanan-dag.png)
+![Kanban & Task DAG](packages/landing/public/images/kanban-dag.png)
 
 Kanban board for task status tracking alongside a dependency DAG showing execution order and parallel paths.
 
 ### Idea & Requirements Elaboration
 
-![Idea & Elaboration](docs/images/idea-elaborate.png)
+![Idea & Elaboration](packages/landing/public/images/idea-elaborate.png)
 
 PM Agents clarify requirements through structured Q&A rounds before creating Proposals. The panel shows idea details alongside completed elaboration rounds with answers and category tags.
 
 ### Proposal Review
 
-![Proposal Review](docs/images/proposal.png)
+![Proposal Review](packages/landing/public/images/proposal.png)
 
 Proposals generated by the PM Agent contain document drafts and task DAG drafts. Admins review and approve or reject on this panel.
 
 ### Acceptance Criteria — Dual-Path Verification
 
-![Acceptance Criteria](docs/images/task-ac.png)
+![Acceptance Criteria](packages/landing/public/images/task-ac.png)
 
 Dev Agent self-checks and Admin reviews each acceptance criterion independently, with structured pass/fail evidence for every item.
 
 ### Universal Search — Cmd+K Command Palette
 
-![Universal Search](docs/images/universal-search.png)
+![Universal Search](packages/landing/public/images/universal-search.png)
 
 A Cmd+K command palette for searching across all 6 entity types (Tasks, Ideas, Proposals, Documents, Projects, Project Groups). Supports scope filtering (Global / Group / Project), filter tabs per entity type, and keyboard navigation. Both the Web UI and AI agents (via `chorus_search` MCP tool) share the same search backend.
 
@@ -402,7 +402,7 @@ If you'd rather read the full docs:
 
 Create API Keys in the Web UI under **Settings → Agents → Create API Key**. Keys start with `cho_` and are shown only once.
 
-![Create API Key](docs/images/create-key.png)
+![Create API Key](packages/landing/public/images/create-key.png)
 
 ---
 

package/README.zh.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="docs/images/chorus-slug.png" alt="Chorus" width="240" />
+  <img src="packages/landing/public/images/chorus-slug.png" alt="Chorus" width="240" />
 </p>
 
 <p align="center"><strong>面向 AI 与人类协作的 Agent Harness</strong></p>
@@ -171,7 +171,7 @@ daemon 启动时的横幅会打印它**实际读取的 `daemon.json` 路径**（
 
 ### 远程唤醒 Agent——派活到指定目录，实时看它跑
 
-![远程唤醒 Agent](docs/images/agent-daemon-wake.gif)
+![远程唤醒 Agent](packages/landing/public/images/agent-daemon-wake.gif)
 
 把一条想法派给远程 Agent 的某个目录，打开对话窗口，就能实时看到本地的 Claude Code 接活、开跑，全程不用碰终端，也不用手动 resume。
 
@@ -183,7 +183,7 @@ Chorus 自动把整个项目整理成一张思维导图——想法、提案、
 
 ### Proposal——AI Agent 实时生成计划
 
-![Proposal Presence](docs/images/proposal-presence.gif)
+![Proposal Presence](packages/landing/public/images/proposal-presence.gif)
 
 PM Agent 分析需求并实时生成包含 PRD 和任务 DAG 的提案，Presence 指示器实时显示 Agent 活动状态。
 
@@ -195,37 +195,37 @@ PM Agent 分析需求并实时生成包含 PRD 和任务 DAG 的提案，Presenc
 
 ### Kanban——任务状态实时流转
 
-![Kanban Presence](docs/images/kanban-presence.gif)
+![Kanban Presence](packages/landing/public/images/kanban-presence.gif)
 
 Kanban 看板随 Agent 工作进度自动更新，任务卡片在 To Do → In Progress → To Verify 之间实时流转。Presence 指示器高亮显示正在被操作的资源。
 
 ### 看板 & 任务 DAG
 
-![Kanban & Task DAG](docs/images/kanan-dag.png)
+![Kanban & Task DAG](packages/landing/public/images/kanban-dag.png)
 
 看板追踪任务状态，DAG 展示依赖关系和并行路径，一目了然。
 
 ### Idea & 需求细化
 
-![Idea & Elaboration](docs/images/idea-elaborate.png)
+![Idea & Elaboration](packages/landing/public/images/idea-elaborate.png)
 
 PM Agent 在创建 Proposal 前，通过结构化问答轮次澄清需求。面板展示 Idea 详情及已完成的细化轮次。
 
 ### 提案审阅
 
-![Proposal Review](docs/images/proposal.png)
+![Proposal Review](packages/landing/public/images/proposal.png)
 
 PM Agent 生成的 Proposal 包含文档草稿和任务 DAG 草稿，Admin 在此面板审阅并决定批准或驳回。
 
 ### 验收标准——双路验证
 
-![Acceptance Criteria](docs/images/task-ac.png)
+![Acceptance Criteria](packages/landing/public/images/task-ac.png)
 
 Dev Agent 自检 + Admin 独立审核，每条验收标准都有结构化的通过/失败证据。
 
 ### Universal Search——Cmd+K 全局搜索
 
-![Universal Search](docs/images/universal-search.png)
+![Universal Search](packages/landing/public/images/universal-search.png)
 
 Cmd+K 命令面板，支持跨 6 种实体类型搜索。支持范围筛选（全局/项目组/单项目）、按类型切换 Tab、键盘导航。Web UI 和 AI Agent（通过 `chorus_search` MCP 工具）共享同一搜索后端。
 
@@ -393,7 +393,7 @@ PGlite 在端口 5433 运行嵌入式 PostgreSQL。数据存储在 `.pglite/`，
 
 在 Web UI 的 **Settings → Agents → Create API Key** 创建 API Key。Key 以 `cho_` 开头，仅在创建时显示一次。
 
-![Create API Key](docs/images/create-key.png)
+![Create API Key](packages/landing/public/images/create-key.png)
 
 ---
 

package/cli/lineage.mjs

@@ -146,6 +146,26 @@ export class LineageResolver {
         `[Chorus] lineage: non-string directIdeaUuid for ${entityType}:${entityUuid}`
       );
     }
+    // A non-null ROOT idea with a null/absent DIRECT idea is a lineage gap: the wake will
+    // anchor the execution on the entity (task/proposal), never on the idea conversation,
+    // so its run shows no running indicator / Interrupt on the idea chat — permanently, for
+    // this class of wake. The overwhelmingly likely cause is a Chorus server that predates
+    // the `directIdeaUuid` field on the /root-idea endpoint. Surface it as a visible WARN
+    // rather than folding it into the generic success `info` below (where it is
+    // indistinguishable from the legitimate "no idea ancestor" outcome, root=direct=null).
+    // Diagnostic ONLY — we do NOT substitute the root for the missing direct idea: for a
+    // DERIVED child idea root ≠ direct, so falling back to root would light the PARENT
+    // conversation and leave the child (which owns the woken session) idle. The correct fix
+    // is server-side; this warn points the operator straight at it.
+    if (root !== null && direct === null) {
+      this.logger.warn(
+        `[Chorus] lineage: ${entityType}:${entityUuid} resolved a root idea (${root}) but NO ` +
+          `directIdeaUuid — this wake will anchor on the entity, not the idea conversation, ` +
+          `so its run will not show a running indicator / Interrupt on the idea chat. Most ` +
+          `likely the Chorus server predates the directIdeaUuid field on /root-idea; upgrade ` +
+          `the server to restore child-wake → idea-conversation matching.`
+      );
+    }
     this.logger.info(
       `[Chorus] lineage: ${entityType}:${entityUuid} → root ${root ?? "none"}, direct ${direct ?? "none"}` +
         (typeof data.resolvedVia === "string" ? ` (${data.resolvedVia})` : "")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chorus-aidlc/chorus",
-  "version": "0.14.1",
+  "version": "0.14.2",
   "description": "The Agent Harness for AI-Human Collaboration — session lifecycle, task state, sub-agent orchestration, observability, and failure recovery",
   "homepage": "https://github.com/Chorus-AIDLC/Chorus",
   "repository": {

package/prisma/migrations/20260718062756_add_project_visit/migration.sql

@@ -0,0 +1,29 @@
+-- CreateTable
+CREATE TABLE "ProjectVisit" (
+    "id" SERIAL NOT NULL,
+    "uuid" TEXT NOT NULL,
+    "companyUuid" TEXT NOT NULL,
+    "userUuid" TEXT NOT NULL,
+    "projectUuid" TEXT NOT NULL,
+    "lastVisitedAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "pinnedAt" TIMESTAMP(3),
+    "createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
+    "updatedAt" TIMESTAMP(3) NOT NULL,
+
+    CONSTRAINT "ProjectVisit_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateIndex
+CREATE UNIQUE INDEX "ProjectVisit_uuid_key" ON "ProjectVisit"("uuid");
+
+-- CreateIndex
+CREATE INDEX "ProjectVisit_companyUuid_idx" ON "ProjectVisit"("companyUuid");
+
+-- CreateIndex
+CREATE INDEX "ProjectVisit_userUuid_pinnedAt_idx" ON "ProjectVisit"("userUuid", "pinnedAt");
+
+-- CreateIndex
+CREATE INDEX "ProjectVisit_userUuid_lastVisitedAt_idx" ON "ProjectVisit"("userUuid", "lastVisitedAt");
+
+-- CreateIndex
+CREATE UNIQUE INDEX "ProjectVisit_userUuid_projectUuid_key" ON "ProjectVisit"("userUuid", "projectUuid");

package/prisma/schema.prisma

@@ -730,6 +730,28 @@ model NotificationPreference {
   @@index([companyUuid])
 }
 
+// Per-user project quick-access state: recency + pin. One row per (user, project).
+// User-only surface (agents never render the sidebar), so keyed on userUuid rather
+// than the polymorphic ownerType/ownerUuid pair NotificationPreference uses.
+// Mirrors the NotificationPreference convention: scalar companyUuid only, no
+// `company Company @relation` field (relationMode = "prisma", app-level scoping).
+model ProjectVisit {
+  id            Int       @id @default(autoincrement())
+  uuid          String    @unique @default(uuid())
+  companyUuid   String
+  userUuid      String
+  projectUuid   String
+  lastVisitedAt DateTime  @default(now()) // updated on every project-page entry
+  pinnedAt      DateTime? // non-null = pinned; ordering key for the pinned list
+  createdAt     DateTime  @default(now())
+  updatedAt     DateTime  @updatedAt
+
+  @@unique([userUuid, projectUuid])
+  @@index([companyUuid])
+  @@index([userUuid, pinnedAt])
+  @@index([userUuid, lastVisitedAt])
+}
+
 // Mention (tracks @mentions in comments, tasks, ideas)
 model Mention {
   id            Int      @id @default(autoincrement())