@chorus-aidlc/chorus 0.14.0 → 0.14.1

package/.next/standalone/public/kiro-plugin/bin/on-post-verify-task.sh

@@ -0,0 +1,119 @@
+#!/usr/bin/env bash
+# on-post-verify-task.sh — Kiro `postToolUse` hook matched to
+# @chorus/chorus_admin_verify_task.
+#
+# Kiro contract: postToolUse delivers {tool_name, tool_input,
+# tool_response, ...} on STDIN; on exit 0 the hook's STDOUT is added to
+# the agent's context as PLAIN TEXT (no additionalContext JSON envelope).
+#
+# Behavior (design D5 — code-review gateway): when the just-verified task
+# is the LAST task of an idea-rooted proposal, emit a nudge to spawn the
+# read-only `chorus-code-reviewer` subagent for the idea's AGGREGATE code
+# change (the whole feature across all its tasks). Ported from the
+# code-review branch of CC's on-post-verify-task.sh; the CC OpenSpec-archive
+# and completion-report branches are out of scope for this hook per D5.
+#
+# Silent exit 0 (no nudge) when: no parseable taskUuid, the task has no
+# proposal (Quick Task), the proposal is not idea-rooted, tasks remain
+# non-terminal, or Chorus is unreachable.
+#
+# Bash 3.2 compatible (CLAUDE.md pitfall #10). All JSON is parsed with
+# `printf '%s' "$VAR" | jq ...` (echo corrupts multi-line JSON on \n).
+
+set -euo pipefail
+
+# Config toggle — default enabled (Kiro analog of CC's ENABLECODEREVIEWER).
+if [ "${CHORUS_ENABLE_CODE_REVIEWER:-true}" != "true" ]; then
+  exit 0
+fi
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+API="${SCRIPT_DIR}/chorus-api.sh"
+
+# jq is required to resolve the proposal/task graph; without it we cannot
+# safely decide "last task of the idea", so degrade to a silent no-op.
+if ! command -v jq >/dev/null 2>&1; then
+  exit 0
+fi
+
+# Read the event JSON from STDIN.
+EVENT=""
+if [ ! -t 0 ]; then
+  EVENT=$(cat)
+fi
+if [ -z "$EVENT" ]; then
+  exit 0
+fi
+
+# Extract taskUuid from tool_input; no UUID -> silent exit 0 (no broken nudge).
+TASK_UUID=$(printf '%s' "$EVENT" | jq -r '.tool_input.taskUuid // empty' 2>/dev/null) || true
+if [ -z "$TASK_UUID" ]; then
+  exit 0
+fi
+
+# Resolve the verified task -> proposalUuid + project.uuid. If the lookup
+# fails or there is no proposal (Quick Task), the gateway can't fire.
+TASK_JSON=$("$API" mcp-tool chorus_get_task "$(printf '{"taskUuid":"%s"}' "$TASK_UUID")" 2>/dev/null) || exit 0
+if [ -z "$TASK_JSON" ]; then
+  exit 0
+fi
+
+PROPOSAL_UUID=$(printf '%s' "$TASK_JSON" | jq -r '.proposalUuid // empty' 2>/dev/null) || true
+PROJECT_UUID=$(printf '%s' "$TASK_JSON" | jq -r '.project.uuid // empty' 2>/dev/null) || true
+if [ -z "$PROPOSAL_UUID" ] || [ -z "$PROJECT_UUID" ]; then
+  exit 0
+fi
+
+# Fetch the proposal — need inputType (idea-rooted only) + the idea UUID.
+PROPOSAL_JSON=$("$API" mcp-tool chorus_get_proposal "$(printf '{"proposalUuid":"%s"}' "$PROPOSAL_UUID")" 2>/dev/null) || exit 0
+if [ -z "$PROPOSAL_JSON" ]; then
+  exit 0
+fi
+
+INPUT_TYPE=$(printf '%s' "$PROPOSAL_JSON" | jq -r '.inputType // empty' 2>/dev/null) || true
+if [ "$INPUT_TYPE" != "idea" ]; then
+  exit 0
+fi
+
+IDEA_UUID=$(printf '%s' "$PROPOSAL_JSON" | jq -r '(.inputUuids // [])[0] // empty' 2>/dev/null) || true
+if [ -z "$IDEA_UUID" ]; then
+  exit 0
+fi
+
+# All tasks of this proposal must be terminal (done/closed). pageSize=200
+# with a total>returned guard so a wide proposal can't fool the gate by
+# fitting only terminal tasks on page 1.
+TASKS_JSON=$("$API" mcp-tool chorus_list_tasks "$(printf '{"projectUuid":"%s","proposalUuids":["%s"],"pageSize":200}' "$PROJECT_UUID" "$PROPOSAL_UUID")" 2>/dev/null) || exit 0
+if [ -z "$TASKS_JSON" ]; then
+  exit 0
+fi
+
+TASKS_TOTAL=$(printf '%s' "$TASKS_JSON" | jq -r '.total // 0' 2>/dev/null) || exit 0
+TASKS_RETURNED=$(printf '%s' "$TASKS_JSON" | jq -r '(.tasks // []) | length' 2>/dev/null) || exit 0
+if [ -n "$TASKS_TOTAL" ] && [ -n "$TASKS_RETURNED" ] && [ "$TASKS_TOTAL" -gt "$TASKS_RETURNED" ]; then
+  exit 0
+fi
+# Defensive: a zero-task proposal can't be "complete" in a meaningful way.
+if [ -z "$TASKS_RETURNED" ] || [ "$TASKS_RETURNED" -eq 0 ]; then
+  exit 0
+fi
+
+NON_TERMINAL_COUNT=$(printf '%s' "$TASKS_JSON" | jq -r '[(.tasks // [])[] | select(.status != "done" and .status != "closed")] | length' 2>/dev/null) || exit 0
+if [ "$NON_TERMINAL_COUNT" != "0" ]; then
+  exit 0
+fi
+
+# Last task of an idea-rooted proposal verified -> emit the gateway nudge.
+printf '%s\n' "[Chorus Plugin — Code-Review Gateway]
+All tasks of idea-rooted proposal ${PROPOSAL_UUID} are now verified. This is the final ship-time gateway for idea ${IDEA_UUID}.
+
+ACTION REQUESTED: spawn the read-only \`chorus-code-reviewer\` subagent for this idea — an independent review of the idea's AGGREGATE code change (the whole feature across all its tasks), not a single task. It is auto-selected by its description; you can also invoke it as /chorus-code-reviewer.
+
+1. Spawn the code-reviewer synchronously, passing ideaUuid=\"${IDEA_UUID}\" and the review round number (read prior code-review VERDICT comments on the idea to determine it). It reviews cross-task integration, architecture/convention consistency, security, regression/performance, feature-level test coverage, and overall soundness, then posts ONE VERDICT comment on the idea.
+2. Read its VERDICT on the idea (chorus_get_comments targetType=\"idea\").
+3. VERDICT: PASS / PASS WITH NOTES — the feature may ship.
+4. VERDICT: FAIL — create new fix tasks on this approved proposal (chorus_create_tasks) targeting the BLOCKERs; do NOT reopen old tasks. When the fix tasks are done, re-run the code-reviewer (next round).
+
+Run this code-review gateway BEFORE writing any idea-completion report — the report must not be written while a FAIL verdict is outstanding."
+
+exit 0

package/.next/standalone/public/kiro-plugin/bin/on-stop.sh

@@ -0,0 +1,45 @@
+#!/usr/bin/env bash
+# on-stop.sh — Kiro `stop` hook for the `chorus` main agent.
+#
+# Kiro contract (kiro.dev/docs/cli/hooks): the stop event delivers
+# {hook_event_name, cwd, session_id, assistant_response} on STDIN. Kiro
+# parses the hook's STDOUT as JSON ONLY to look for
+# {"decision":"block","reason":"..."} — which would PREVENT the turn from
+# stopping. Any other output (or none) lets the turn stop normally.
+#
+# This hook is a best-effort session heartbeat/checkout: it NEVER emits a
+# block decision and NEVER fails the turn, even if Chorus is unreachable.
+# It prints nothing to STDOUT so the turn always stops cleanly.
+#
+# Bash 3.2 compatible (CLAUDE.md pitfall #10).
+
+# Deliberately NOT `set -e`: a stop hook must never turn a Chorus outage
+# into a failed turn. Every Chorus call below is guarded with `|| true`.
+set -uo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+API="${SCRIPT_DIR}/chorus-api.sh"
+
+# Drain STDIN if present (assistant_response etc. — not needed here).
+if [ ! -t 0 ]; then
+  cat >/dev/null 2>&1 || true
+fi
+
+# Nothing to do if Chorus isn't configured.
+if [ -z "${CHORUS_URL:-}" ] || [ -z "${CHORUS_API_KEY:-}" ]; then
+  exit 0
+fi
+
+# Best-effort: if a Chorus session was cached (swarm-mode flow), send a
+# final heartbeat and check out of any task it holds. All calls are
+# fire-and-forget; failures are swallowed so the turn always stops.
+MAIN_SESSION=$("$API" state-get "main_session_uuid" 2>/dev/null) || true
+if [ -n "${MAIN_SESSION:-}" ]; then
+  "$API" mcp-tool "chorus_session_heartbeat" \
+    "$(printf '{"sessionUuid":"%s"}' "$MAIN_SESSION")" >/dev/null 2>&1 || true
+  "$API" mcp-tool "chorus_session_checkout_task" \
+    "$(printf '{"sessionUuid":"%s"}' "$MAIN_SESSION")" >/dev/null 2>&1 || true
+fi
+
+# Print nothing (no block decision) -> the turn stops normally.
+exit 0

package/.next/standalone/public/kiro-plugin/bin/test-syntax.sh

@@ -0,0 +1,108 @@
+#!/usr/bin/env bash
+# Test all Kiro-plugin hook scripts for compatibility with the current bash
+# version. Runs each script with a mock Kiro hook event on STDIN and mock
+# env to catch runtime errors (e.g. ${VAR,,} bad substitution on Bash 3.2).
+#
+# Mirrors public/chorus-plugin/bin/test-syntax.sh, adapted to Kiro's hook
+# event JSON shape (kiro.dev/docs/cli/hooks): agentSpawn/stop carry base
+# fields only; postToolUse carries tool_name + tool_input + tool_response.
+#
+# Usage:
+#   /bin/bash public/kiro-plugin/bin/test-syntax.sh   # test with macOS system bash 3.2
+#   bash public/kiro-plugin/bin/test-syntax.sh         # test with default bash
+
+set -euo pipefail
+
+DIR="$(cd "$(dirname "$0")" && pwd)"
+PASS=0
+FAIL=0
+FAILED=""
+
+echo "Using: $BASH ($("$BASH" --version | head -1))"
+echo ""
+
+# Mock env so scripts don't exit early on env guards. Use a bogus URL —
+# scripts will fail on actual API calls but that's fine; we only care about
+# bash syntax/substitution errors before the API call.
+export CHORUS_URL="http://localhost:0"
+export CHORUS_API_KEY="cho_test"
+export CLAUDE_PROJECT_DIR="/tmp/kiro-test-$$"
+mkdir -p "$CLAUDE_PROJECT_DIR"
+
+cleanup() { rm -rf "$CLAUDE_PROJECT_DIR"; }
+trap cleanup EXIT
+
+# First-class syntax parse (`bash -n`) for every *.sh in the dir, including
+# chorus-api.sh which is a library (never executed standalone here).
+echo "--- bash -n parse check (all *.sh) ---"
+for f in "$DIR"/*.sh; do
+  base=$(basename "$f")
+  if "$BASH" -n "$f" 2>/tmp/kiro-parse-err-$$; then
+    printf "  PARSE OK  %s\n" "$base"
+  else
+    printf "  PARSE FAIL  %s\n" "$base"
+    sed 's/^/           /' /tmp/kiro-parse-err-$$
+    FAIL=$((FAIL + 1))
+    FAILED="$FAILED $base(parse)"
+  fi
+  rm -f /tmp/kiro-parse-err-$$
+done
+echo ""
+
+# Run each hook with a mock Kiro event; grep stderr for bash version issues.
+run_test() {
+  local name="$1"
+  local input="$2"
+  local script="$DIR/$name"
+  local err_file="/tmp/kiro-test-err-$$"
+
+  if printf '%s' "$input" | "$BASH" "$script" >"$err_file" 2>&1; then
+    printf "  PASS  %s\n" "$name"
+    PASS=$((PASS + 1))
+  else
+    if grep -qi "bad substitution\|syntax error\|unexpected token" "$err_file"; then
+      printf "  FAIL  %s (bash compatibility error)\n" "$name"
+      sed 's/^/         /' "$err_file"
+      FAIL=$((FAIL + 1))
+      FAILED="$FAILED $name"
+    else
+      # Non-zero exit from an API/curl failure is expected — not a bash issue.
+      printf "  PASS  %s (exited non-zero but no bash error)\n" "$name"
+      PASS=$((PASS + 1))
+    fi
+  fi
+  rm -f "$err_file"
+}
+
+echo "--- runtime smoke tests (mock Kiro events) ---"
+
+# agentSpawn — base fields only.
+run_test "on-agent-spawn.sh" '{"hook_event_name":"agentSpawn","cwd":"/tmp","session_id":"sess-1"}'
+
+# stop — base fields + assistant_response.
+run_test "on-stop.sh"        '{"hook_event_name":"stop","cwd":"/tmp","session_id":"sess-1","assistant_response":"done"}'
+
+# postToolUse — tool_name + tool_input + tool_response (happy path).
+run_test "on-post-submit-proposal.sh"   '{"hook_event_name":"postToolUse","tool_name":"@chorus/chorus_pm_submit_proposal","tool_input":{"proposalUuid":"prop-uuid"},"tool_response":{"success":true,"result":["{\"uuid\":\"prop-uuid\",\"title\":\"Test proposal\"}"]},"title":"Test proposal"}'
+run_test "on-post-submit-for-verify.sh" '{"hook_event_name":"postToolUse","tool_name":"@chorus/chorus_submit_for_verify","tool_input":{"taskUuid":"task-uuid"},"tool_response":{"success":true,"result":["ok"]}}'
+run_test "on-post-verify-task.sh"       '{"hook_event_name":"postToolUse","tool_name":"@chorus/chorus_admin_verify_task","tool_input":{"taskUuid":"task-uuid"},"tool_response":{"success":true,"result":["ok"]}}'
+
+# postToolUse — no parseable UUID (must exit 0 with no broken nudge).
+run_test "on-post-submit-proposal.sh"   '{"hook_event_name":"postToolUse","tool_name":"@chorus/chorus_pm_submit_proposal","tool_input":{}}'
+run_test "on-post-submit-for-verify.sh" '{"hook_event_name":"postToolUse","tool_name":"@chorus/chorus_submit_for_verify","tool_input":{}}'
+run_test "on-post-verify-task.sh"       '{"hook_event_name":"postToolUse","tool_name":"@chorus/chorus_admin_verify_task","tool_input":{}}'
+
+# Empty STDIN edge case (all hooks must survive).
+run_test "on-agent-spawn.sh"            ''
+run_test "on-stop.sh"                   ''
+run_test "on-post-submit-proposal.sh"   ''
+run_test "on-post-submit-for-verify.sh" ''
+run_test "on-post-verify-task.sh"       ''
+
+echo ""
+echo "Results: $PASS passed, $FAIL failed"
+
+if [ "$FAIL" -gt 0 ]; then
+  echo "Failed:$FAILED"
+  exit 1
+fi

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.0"
+  version: "0.14.1"
   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.0"
+  version: "0.14.1"
   category: project-management
   mcp_server: chorus
 ---
@@ -198,6 +198,12 @@ Results can be filtered by project(s) using optional HTTP headers in your MCP co
 
 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.
 
+### References
+
+A **reference** is a first-class external-evidence link (`docs` / `repo` / `issue_pr` / `paper_blog`) attached to an idea / proposal / task via `chorus_add_reference`, or inline at creation via the `references[]` param on `chorus_pm_create_idea` / `chorus_pm_create_proposal` / `chorus_create_tasks`. References read back inline through the `chorus_get_*` tools.
+
+**Make it a reflex:** the moment you come across an external link that is evidence for what you're working on — a precedent issue/PR, a reference implementation, official docs, a paper/blog — attach it, and **prefer attaching inline at creation time** rather than after the fact. See the `idea-chorus` skill (`<BASE_URL>/skill/idea-chorus/SKILL.md`), Step 4.4, for the type-selection criteria and a worked example.
+
 ### Proposals
 
 | Tool | Purpose |

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.0"
+  version: "0.14.1"
   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.0"
+  version: "0.14.1"
   category: project-management
   mcp_server: chorus
 ---

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.0"
+  version: "0.14.1"
   category: project-management
   mcp_server: chorus
 ---
@@ -115,6 +115,37 @@ Before elaborating, understand the full picture:
    chorus_get_comments({ targetType: "idea", targetUuid: "<idea-uuid>" })
    ```
 
+### Step 4.4: Attach External References
+
+**Make attaching external references a reflex, not an afterthought.** While gathering context you will often surface external links that are *evidence* for this Idea — a precedent issue or PR, a reference implementation, official documentation, a paper or blog post. The moment you see one, attach it as a reference artifact. References are read back inline by `chorus_get_idea` / `chorus_get_proposal` / `chorus_get_task`, so they carry the "why" forward to whoever picks up the proposal or task next.
+
+**Prefer attaching at creation time** via the inline `references[]` param on `chorus_pm_create_idea` (and later `chorus_pm_create_proposal` / `chorus_create_tasks`) rather than a post-hoc `chorus_add_reference`. Attaching at create means the evidence is present from the first read; use `chorus_add_reference` only when the link surfaces after the entity already exists.
+
+**Pick the `type` that fits the link:**
+
+| `type` | Use for |
+|--------|---------|
+| `docs` | Official documentation — framework / API / library reference |
+| `repo` | A reference implementation or source repository |
+| `issue_pr` | An issue or pull-request thread — precedent, prior art, the delivering PR |
+| `paper_blog` | A paper or blog post — background or design rationale |
+
+**Example** — a new localization Idea, attaching the precedent PR and the framework docs inline at creation:
+
+```
+chorus_pm_create_idea({
+  projectUuid: "<project-uuid>",
+  title: "Add Portuguese (pt) locale",
+  content: "...",
+  references: [
+    { type: "issue_pr", url: "https://github.com/org/repo/pull/411",
+      title: "PR #411 — prior locale work (precedent to mirror)" },
+    { type: "docs", url: "https://next-intl.dev/docs/routing",
+      title: "next-intl routing docs (locale registration)" }
+  ]
+})
+```
+
 ### Step 4.5: Brainstorm Mode (Optional Prelude)
 
 If the Idea is fuzzy and you'd struggle to enumerate concrete multi-choice questions, offer the user a brainstorm prelude before structured elaboration. Use your IDE's interactive prompt mechanism if available, or present options as text — the same convention used elsewhere in this skill. Two choices: `"Already clear, run structured elaboration"` and `"Brainstorm first to explore directions"`.

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

@@ -1,6 +1,6 @@
 {
   "name": "chorus-skill",
-  "version": "0.11.0",
+  "version": "0.14.1",
   "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.0"
+  version: "0.14.1"
   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.0"
+  version: "0.14.1"
   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.0"
+  version: "0.14.1"
   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.0"
+  version: "0.14.1"
   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.0"
+  version: "0.14.1"
   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.0"
+  version: "0.14.1"
   category: project-management
   mcp_server: chorus
 ---

package/README.ja.md

@@ -36,6 +36,8 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 
 ## 最近の更新
 
+**[v0.14.1](https://chorus-ai.dev/blog/chorus-v0.14.1-release/)** — Amazon Kiro CLI が 4 つ目の接続方法になりました（Kiro CLI v2）：ワンコマンドの `install-kiro.sh` プラグインと `--agent kiro` デーモンバックエンド、加えていくつかのデーモン修正。
+
 **[v0.14.0](https://chorus-ai.dev/blog/chorus-v0.14.0-release/)** — アプリ全体のダークモード（ライト / ダーク / システム）。参考資料をあらゆる着想・提案・課題に添付でき、インラインでも MCP 経由でも読み取れます。韓国語と日本語を追加（韓国語はコミュニティによる貢献）。グループ化のための**テーマ**着想、デーモンの「開発を開始」/「Yolo」ボタン、対話式の着想入力、クラッシュからの再開、`chorus daemon install`。
 
 **[v0.13.0](https://chorus-ai.dev/blog/chorus-v0.13.0-release/)** — プロジェクトごとのリソースマインドマップ：新しい Graph ビューが、各プロジェクトの着想・提案・文書・課題を、プロジェクト自身の構造から生成した 1 本の折りたたみ可能なツリーにつなぎます。各カードには現在のステータスが表示され（着想には、着想トラッカーが使う派生パイプラインステータスが表示されます）、タイトル検索はヒットした各ノードまでの経路を自動展開してハイライト／減光し、前後ナビゲーションを備えます。同じズーム／パン対応のキャンバスが、デスクトップとモバイルの両方で描画されます（ピンチ + ダブルタップ）。
@@ -384,7 +386,7 @@ PGlite はポート 5433 で組み込み PostgreSQL を実行します。デー
 
 ### AI エージェントを接続する
 
-最も手早い方法は、アプリ内のセットアップウィザードです：Web UI を開き、**Settings → Setup Guide → Open setup guide** に進み、お使いのクライアント（Claude Code、Codex、OpenCode、OpenClaw、その他のエージェント）向けのステップバイステップの手順に従ってください。ウィザードが API キーを作成し、正確なコマンドを表示して、接続の確認まで案内します。
+最も手早い方法は、アプリ内のセットアップウィザードです：Web UI を開き、**Settings → Setup Guide → Open setup guide** に進み、お使いのクライアント（Claude Code、Codex、Kiro、OpenCode、OpenClaw、その他のエージェント）向けのステップバイステップの手順に従ってください。ウィザードが API キーを作成し、正確なコマンドを表示して、接続の確認まで案内します。
 
 詳細なドキュメントを読みたい場合は：
 
@@ -392,6 +394,7 @@ PGlite はポート 5433 で組み込み PostgreSQL を実行します。デー
 |--------|-------|
 | Claude Code | [CONNECT_CLAUDE_CODE.md](docs/CONNECT_CLAUDE_CODE.md) |
 | Codex CLI | [CONNECT_CODEX.md](docs/CONNECT_CODEX.md) |
+| Kiro CLI | [CONNECT_KIRO.md](docs/CONNECT_KIRO.md) |
 | OpenCode † | [CONNECT_OPENCODE.md](docs/CONNECT_OPENCODE.md) |
 | その他の MCP エージェント（Cursor、Continue、自作など） | [CONNECT_OTHER_AGENTS.md](docs/CONNECT_OTHER_AGENTS.md) |
 

package/README.ko.md

@@ -36,6 +36,8 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 
 ## 최근 업데이트
 
+**[v0.14.1](https://chorus-ai.dev/blog/chorus-v0.14.1-release/)** — Amazon Kiro CLI가 네 번째 연결 방식이 되었습니다(Kiro CLI v2): 명령 한 줄로 설치하는 `install-kiro.sh` 플러그인과 `--agent kiro` 데몬 백엔드, 여기에 몇 가지 데몬 수정.
+
 **[v0.14.0](https://chorus-ai.dev/blog/chorus-v0.14.0-release/)** — 앱 전체 다크 모드(라이트 / 다크 / 시스템). 참고 자료를 어떤 아이디어·제안·작업에도 첨부할 수 있고, 인라인으로도 MCP를 통해서도 읽을 수 있습니다. 한국어와 일본어 추가(한국어는 커뮤니티 기여). 그룹화를 위한 **테마** 아이디어, 그리고 데몬의 개발 시작 / Yolo 버튼, 대화식 아이디어 입력, 크래시 복구, `chorus daemon install`.
 
 **[v0.13.0](https://chorus-ai.dev/blog/chorus-v0.13.0-release/)** — 프로젝트별 리소스 마인드맵: 새로운 Graph 뷰가 각 프로젝트의 아이디어·제안·문서·작업을 프로젝트 자체 구조에서 생성한 하나의 접을 수 있는 트리로 엮습니다. 모든 카드에 현재 상태가 표시되며(아이디어는 아이디어 트래커가 사용하는 파생 파이프라인 상태를 보여줍니다), 제목 검색은 모든 일치 항목까지의 경로를 자동으로 펼쳐 하이라이트/디밍하고 이전/다음 탐색을 제공합니다. 동일한 줌/팬 캔버스가 데스크톱과 모바일 모두에서 렌더링됩니다(핀치 + 더블탭).
@@ -384,7 +386,7 @@ PGlite는 포트 5433에서 내장 PostgreSQL을 실행합니다. 데이터는 `
 
 ### AI 에이전트 연결하기
 
-가장 빠른 방법은 앱 내 설정 마법사입니다: Web UI를 열고 **Settings → Setup Guide → Open setup guide**로 이동한 뒤, 사용하는 클라이언트(Claude Code, Codex, OpenCode, OpenClaw, 또는 그 밖의 에이전트)에 맞는 단계별 안내를 따르세요. 마법사가 API 키를 만들어 주고, 정확한 명령을 보여주며, 연결 확인까지 안내합니다.
+가장 빠른 방법은 앱 내 설정 마법사입니다: Web UI를 열고 **Settings → Setup Guide → Open setup guide**로 이동한 뒤, 사용하는 클라이언트(Claude Code, Codex, Kiro, OpenCode, OpenClaw, 또는 그 밖의 에이전트)에 맞는 단계별 안내를 따르세요. 마법사가 API 키를 만들어 주고, 정확한 명령을 보여주며, 연결 확인까지 안내합니다.
 
 전체 문서를 읽고 싶다면:
 
@@ -392,6 +394,7 @@ PGlite는 포트 5433에서 내장 PostgreSQL을 실행합니다. 데이터는 `
 |--------|-------|
 | Claude Code | [CONNECT_CLAUDE_CODE.md](docs/CONNECT_CLAUDE_CODE.md) |
 | Codex CLI | [CONNECT_CODEX.md](docs/CONNECT_CODEX.md) |
+| Kiro CLI | [CONNECT_KIRO.md](docs/CONNECT_KIRO.md) |
 | OpenCode † | [CONNECT_OPENCODE.md](docs/CONNECT_OPENCODE.md) |
 | 그 밖의 MCP 에이전트(Cursor, Continue, 커스텀 등) | [CONNECT_OTHER_AGENTS.md](docs/CONNECT_OTHER_AGENTS.md) |
 

package/README.md

@@ -36,6 +36,8 @@ The labels under each stage are the **permissions** an actor needs at that stage
 
 ## What's New
 
+**[v0.14.1](https://chorus-ai.dev/blog/chorus-v0.14.1-release/)** — Amazon Kiro CLI is the fourth way to connect (Kiro CLI v2): a one-command `install-kiro.sh` plugin and a `--agent kiro` daemon backend, plus daemon fixes.
+
 **[v0.14.0](https://chorus-ai.dev/blog/chorus-v0.14.0-release/)** — Dark mode across the app (light / dark / system). Reference artifacts: attach docs, repos, issues, and articles to any idea, proposal, or task, readable inline and over MCP. Korean and Japanese locales (Korean contributed by the community). **Theme** ideas for grouping, plus daemon Start Development / Yolo buttons, conversational idea entry, crash-resume, and `chorus daemon install`.
 
 **[v0.13.0](https://chorus-ai.dev/blog/chorus-v0.13.0-release/)** — Per-project resource mind-map: a new Graph view wires each project's Ideas, Proposals, Documents, and Tasks into one collapsible tree, generated from the project's own structure. Every card carries its current status (ideas show the derived pipeline status the idea tracker uses), a title search auto-expands the path to every match with highlight/dim and prev/next navigation, and the same zoom/pan canvas renders on desktop and mobile (pinch + double-tap).
@@ -384,7 +386,7 @@ The interactive installer provisions VPC, Aurora Serverless v2, ElastiCache Serv
 
 ### Connect AI Agents
 
-The fastest path is the in-app setup wizard: open the Web UI, go to **Settings → Setup Guide → Open setup guide**, and follow the step-by-step instructions for your client (Claude Code, Codex, OpenCode, OpenClaw, or other agents). The wizard creates the API key for you, shows the exact commands, and walks through verifying the connection.
+The fastest path is the in-app setup wizard: open the Web UI, go to **Settings → Setup Guide → Open setup guide**, and follow the step-by-step instructions for your client (Claude Code, Codex, Kiro, OpenCode, OpenClaw, or other agents). The wizard creates the API key for you, shows the exact commands, and walks through verifying the connection.
 
 If you'd rather read the full docs:
 
@@ -392,6 +394,7 @@ If you'd rather read the full docs:
 |--------|-------|
 | Claude Code | [CONNECT_CLAUDE_CODE.md](docs/CONNECT_CLAUDE_CODE.md) |
 | Codex CLI | [CONNECT_CODEX.md](docs/CONNECT_CODEX.md) |
+| Kiro CLI | [CONNECT_KIRO.md](docs/CONNECT_KIRO.md) |
 | OpenCode † | [CONNECT_OPENCODE.md](docs/CONNECT_OPENCODE.md) |
 | Other MCP agents (Cursor, Continue, custom, …) | [CONNECT_OTHER_AGENTS.md](docs/CONNECT_OTHER_AGENTS.md) |
 

package/README.zh.md

@@ -27,6 +27,8 @@ Idea ──> Proposal ──> [Document + Task DAG] ──> Execute ──> Veri
 
 ## 最近更新
 
+**[v0.14.1](https://chorus-ai.dev/zh/blog/chorus-v0.14.1-release/)** — Amazon Kiro CLI 成为第四种接入方式（Kiro CLI v2）：一条命令的 `install-kiro.sh` 插件，以及 `--agent kiro` 的 daemon 后端，另有若干 daemon 修复。
+
 **[v0.14.0](https://chorus-ai.dev/zh/blog/chorus-v0.14.0-release/)** — 全应用深色模式（浅色 / 深色 / 跟随系统）。参考资料可挂到任意想法、提案或任务上，行内可读，也能通过 MCP 读写。新增韩语和日语（韩语由社区贡献）。用于归类的**主题**想法，以及 daemon 的「开始开发」/「Yolo」按钮、对话式建想法、崩溃恢复与 `chorus daemon install`。
 
 **[v0.13.0](https://chorus-ai.dev/zh/blog/chorus-v0.13.0-release/)** — 项目资源思维导图：新增 Graph 视图，把每个项目的想法、提案、文档、任务连成一棵可折叠的树，从项目自身结构自动生成。每张卡片都标着当前状态（想法用想法列表那套派生状态），标题搜索会自动展开命中节点的上游并高亮/调暗、配上下切换定位，同一张可缩放可拖动的图在桌面与手机上通用（捏合 + 双击缩放）。
@@ -375,7 +377,7 @@ PGlite 在端口 5433 运行嵌入式 PostgreSQL。数据存储在 `.pglite/`，
 
 ### 连接 AI Agent
 
-最快的方式是用应用内的 setup 向导：打开 Web UI，进入 **Settings → Setup Guide → 打开设置向导**，按照向导给出的分步指引接入自己的客户端（Claude Code、Codex、OpenCode、OpenClaw 或其他 agent）。向导会帮你创建 API Key、展示完整命令，并引导你验证连接。
+最快的方式是用应用内的 setup 向导：打开 Web UI，进入 **Settings → Setup Guide → 打开设置向导**，按照向导给出的分步指引接入自己的客户端（Claude Code、Codex、Kiro、OpenCode、OpenClaw 或其他 agent）。向导会帮你创建 API Key、展示完整命令，并引导你验证连接。
 
 如果偏好文档：
 
@@ -383,6 +385,7 @@ PGlite 在端口 5433 运行嵌入式 PostgreSQL。数据存储在 `.pglite/`，
 |--------|---------|
 | Claude Code | [CONNECT_CLAUDE_CODE.zh.md](docs/CONNECT_CLAUDE_CODE.zh.md) |
 | Codex CLI | [CONNECT_CODEX.zh.md](docs/CONNECT_CODEX.zh.md) |
+| Kiro CLI | [CONNECT_KIRO.md](docs/CONNECT_KIRO.md) |
 | OpenCode † | [CONNECT_OPENCODE.zh.md](docs/CONNECT_OPENCODE.zh.md) |
 | 其他 MCP agent（Cursor / Continue / 自研等） | [CONNECT_OTHER_AGENTS.zh.md](docs/CONNECT_OTHER_AGENTS.zh.md) |
 

package/chorus.mjs

@@ -181,6 +181,10 @@ DAEMON / LOGIN (client mode)
   --sigint-timeout <ms>    Grace window after SIGINT before a forceful kill    (env: CHORUS_DAEMON_SIGINT_TIMEOUT)
                            when an interrupt is received (default: 10000).
                            Also configurable via ~/.chorus/daemon.json sigintTimeoutMs.
+  -y, --yes                Non-interactive 'chorus daemon install': skip all install
+                           prompts (credentials are still resolved, persisted, and
+                           validated; install aborts if none resolve). A non-TTY
+                           install behaves as if --yes were passed.
 
   Credential resolution order: flags > CHORUS_URL/CHORUS_API_KEY env >
   ~/.chorus/daemon.json (from 'chorus login') > Claude Code plugin config.

package/cli/client-args.mjs

@@ -13,10 +13,11 @@
  */
 export const DAEMON_ACTIONS = new Set(["stop", "status", "restart", "logs", "install", "uninstall"]);
 
-/** Known agent backends. Only `claude-code` is implemented; the rest reserve
- * the extension point (see daemon-agent-selection). Exported for the resolver
- * the --agent task wires in; parsing here does not validate the value. */
-export const KNOWN_AGENTS = new Set(["claude-code"]);
+/** Known agent backends, kept in sync with the authoritative list in
+ * daemon-agent.mjs (`claude-code`, `codex`, `kiro` — all implemented). This copy
+ * is informational only: parsing here does not validate the value (the resolver
+ * in daemon-agent.mjs is the single source of truth for validation). */
+export const KNOWN_AGENTS = new Set(["claude-code", "codex", "kiro"]);
 
 /**
  * Parse the client-subcommand flags out of an arg list. Recognizes the
@@ -38,7 +39,7 @@ export const KNOWN_AGENTS = new Set(["claude-code"]);
  * @returns {{
  *   url?: string, apiKey?: string, yolo?: boolean, sigintTimeout?: string,
  *   agent?: string, chorusOnly?: boolean, verbose?: boolean, detach?: boolean,
- *   cwd?: string[], force?: boolean, help?: boolean,
+ *   cwd?: string[], force?: boolean, yes?: boolean, help?: boolean,
  * }}
  */
 export function parseClientFlags(argv) {
@@ -63,6 +64,7 @@ export function parseClientFlags(argv) {
     else if (a === "--verbose") out.verbose = true;
     else if (a === "-d" || a === "--detach") out.detach = true;
     else if (a === "--force") out.force = true;
+    else if (a === "--yes" || a === "-y") out.yes = true;
     else if (a === "--help" || a === "-h") out.help = true;
   }
   return out;
@@ -117,7 +119,7 @@ OPTIONS
   --url <url>              Remote Chorus server URL            (env: CHORUS_URL)
   --api-key <cho_...>      Agent API key                       (env: CHORUS_API_KEY)
   --agent <type>           Local agent backend to wake         (env: CHORUS_AGENT)
-                           (claude-code | codex; default: claude-code)
+                           (claude-code | codex | kiro; default: claude-code)
   --yolo                   Full autonomy for the woken agent   (env: CHORUS_YOLO=1)
                            (--dangerously-skip-permissions: Bash, file writes, any
                            command). This is the DEFAULT permission mode.
@@ -130,6 +132,10 @@ OPTIONS
                            local paths at once. Default: the directory it was launched
                            from. (Also configurable as "cwds":[…] in ~/.chorus/daemon.json.)
   -d, --detach             Run detached in the background (pidfile + logfile)
+  -y, --yes                Non-interactive install: skip all 'chorus daemon
+                           install' prompts (credentials still resolved, persisted,
+                           and validated; install aborts if none resolve). A non-TTY
+                           install behaves as if --yes were passed.
   --verbose                More detailed per-wake logging
   --sigint-timeout <ms>    Grace window after SIGINT before a forceful kill
                            (env: CHORUS_DAEMON_SIGINT_TIMEOUT; default 10000)
@@ -147,8 +153,13 @@ SERVICE (install)
   starts at login, restarts on failure, and 'systemctl --user stop' shuts it
   down gracefully. Do NOT hand-write a Type=forking unit around 'chorus daemon
   -d' — the daemon self-daemonizes, which systemd cannot track and which loops
-  on restart. The install captures the --cwd / --agent / --chorus-only flags you
-  pass. On macOS/Windows install prints a correct template you install manually.
+  on restart. Before writing the unit, install resolves + persists + validates
+  your credentials into ~/.chorus/daemon.json (so the clean boot environment can
+  authenticate) and configures the served working directories there too (prompting
+  interactively for one or more when none are set — pass -y/--yes or run non-TTY to
+  skip prompts). The unit captures --agent / --chorus-only but NOT --cwd (cwds live
+  in daemon.json). On macOS/Windows install prints a correct template you install
+  manually.
 
 EXAMPLES
   chorus daemon                        # Foreground, default yolo (TTY confirms once)