@chorus-aidlc/chorus 0.9.1 → 0.9.3

package/.next/standalone/public/chorus-plugin/skills/brainstorm/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.9.0"
+  version: "0.9.3"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/chorus-plugin/skills/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.9.0"
+  version: "0.9.3"
   category: project-management
   mcp_server: chorus
 ---
@@ -156,7 +156,7 @@ A **report** is a short idea-completion summary persisted as a `type="report"` D
 | Tool | Purpose |
 |------|---------|
 | `chorus_get_proposals` | List project Proposals (filterable by status: pending, approved, rejected) |
-| `chorus_get_proposal` | Get a single Proposal's details, including documentDrafts and taskDrafts |
+| `chorus_get_proposal` | Get a single Proposal, sliced by `section` (default `basic`: metadata + lightweight draft index; `documents`/`tasks`/`full` for the draft bodies) |
 
 ### Tasks
 

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

@@ -4,7 +4,7 @@ description: Chorus Development workflow — claim tasks, report work, manage se
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.9.0"
+  version: "0.9.3"
   category: project-management
   mcp_server: chorus
 ---
@@ -125,8 +125,9 @@ Each task and proposal includes a `commentCount` field — use it to decide whic
 
 4. **Read the originating proposal** for design intent:
    ```
-   chorus_get_proposal({ proposalUuid: "<proposal-uuid>" })
+   chorus_get_proposal({ proposalUuid: "<proposal-uuid>", section: "documents" })
    ```
+   (`chorus_get_proposal` defaults to `section: "basic"` — just metadata + a draft index. Pass `section: "documents"` for the design docs, or `section: "full"` for docs + task drafts.)
 
 5. **Read project documents** (PRD, tech design, ADR):
    ```

package/.next/standalone/public/chorus-plugin/skills/idea/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.9.0"
+  version: "0.9.3"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/chorus-plugin/skills/openspec-aware/SKILL.md

@@ -4,7 +4,7 @@ description: Opt-in OpenSpec-mode authoring for Chorus PM workflows in Claude Co
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.9.0"
+  version: "0.9.3"
   category: project-management
   mcp_server: chorus
 ---

package/.next/standalone/public/chorus-plugin/skills/proposal/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.9.0"
+  version: "0.9.3"
   category: project-management
   mcp_server: chorus
 ---
@@ -121,6 +121,8 @@ chorus_pm_add_document_draft({
 
 Add task drafts one at a time. The response returns the new draft's `draftUuid` — use it directly for `dependsOnDraftUuids` in subsequent drafts.
 
+**`acceptanceCriteriaItems` is required** — every task draft must include at least one item with a non-blank `description`, or the call is rejected. Use the structured `acceptanceCriteriaItems` array (the legacy `acceptanceCriteria` Markdown string does not satisfy the requirement).
+
 ```
 # First task -> response includes { draftUuid, draftTitle }
 chorus_pm_add_task_draft({
@@ -129,7 +131,10 @@ chorus_pm_add_task_draft({
   description: "Detailed description of what to build...",
   priority: "high",
   storyPoints: 3,
-  acceptanceCriteria: "- [ ] Criteria 1\n- [ ] Criteria 2"
+  acceptanceCriteriaItems: [
+    { description: "Criteria 1", required: true },
+    { description: "Criteria 2", required: true }
+  ]
 })
 
 # Second task — depends on first
@@ -139,18 +144,24 @@ chorus_pm_add_task_draft({
   description: "Unit and integration tests...",
   priority: "medium",
   storyPoints: 2,
-  acceptanceCriteria: "- [ ] Test coverage > 80%",
+  acceptanceCriteriaItems: [
+    { description: "Test coverage > 80%", required: true }
+  ],
   dependsOnDraftUuids: ["<draftUuid-from-first-task>"]
 })
 ```
 
+> To edit a draft's criteria later via `chorus_pm_update_task_draft`, pass a non-empty `acceptanceCriteriaItems` to replace them; omit the field to leave them unchanged. The field cannot be used to clear criteria.
+
 **Task priority:** `low`, `medium`, `high`
 
 ### Step 4: Review and Refine Drafts
 
 ```
-# Review current state
-chorus_get_proposal({ proposalUuid: "<proposal-uuid>" })
+# Review current state. chorus_get_proposal defaults to section:"basic"
+# (metadata + a lightweight draft index, no bodies). Use section:"full" to
+# see every draft's content, or section:"documents"/"tasks" for one kind.
+chorus_get_proposal({ proposalUuid: "<proposal-uuid>", section: "full" })
 
 # Update a document draft
 chorus_pm_update_document_draft({
@@ -210,7 +221,7 @@ After submission, a `chorus:proposal-reviewer` may run and post a VERDICT commen
 
 1. **Read feedback:**
    ```
-   chorus_get_proposal({ proposalUuid: "<proposal-uuid>" })
+   chorus_get_proposal({ proposalUuid: "<proposal-uuid>", section: "full" })
    chorus_get_comments({ targetType: "proposal", targetUuid: "<proposal-uuid>" })
    ```
    Identify BLOCKERs from the reviewer VERDICT or rejection note.
@@ -332,7 +343,7 @@ Potential issues and how to address them.
 
 Good tasks are:
 - **Module-scoped** — One cohesive functional module per task, not a single function or file
-- **Testable** — Clear, cohesive acceptance criteria (max 6 items per task; group related checks into one criterion but list key coverage, e.g. "All tests pass: service layer unit tests, API integration tests, edge case handling")
+- **Testable** — Clear, cohesive acceptance criteria are **required** on every task (at least one non-blank item; max 6; group related checks into one criterion but list key coverage, e.g. "All tests pass: service layer unit tests, API integration tests, edge case handling")
 - **Sized** — 1-8 story points (hours of agent work)
 - **Ordered** — Use `dependsOnDraftUuids` / `dependsOnTaskUuids` to express execution order
 - **Descriptive** — Include enough context for a developer agent to start without questions. For tasks with cross-module dependencies, reference the tech design's Module Contracts in the AC

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

@@ -1,7 +1,12 @@
 ---
 name: quick-dev
-version: 0.9.0
 description: Quick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.
+license: AGPL-3.0
+metadata:
+  author: chorus
+  version: "0.9.3"
+  category: project-management
+  mcp_server: chorus
 ---
 
 # Quick Dev Skill
@@ -63,7 +68,7 @@ This matters because admin agents can call `chorus_admin_verify_task` to close t
 
 ### Step 1: Create a Quick Task
 
-**Always include `acceptanceCriteriaItems`** — these are the foundation for self-checking in Step 6. Write specific, testable criteria that you can objectively verify after development. Vague AC like "works correctly" defeats the purpose; prefer "returns 200 on GET /api/foo with valid token".
+**`acceptanceCriteriaItems` is required** — `chorus_create_tasks` rejects any task without at least one non-blank criterion (and rejects the whole batch if any task is missing them). These are also the foundation for self-checking in Step 6. Write specific, testable criteria that you can objectively verify after development. Vague AC like "works correctly" defeats the purpose; prefer "returns 200 on GET /api/foo with valid token".
 
 ```
 chorus_create_tasks({
@@ -93,7 +98,7 @@ chorus_claim_task({ taskUuid: "<task-uuid>" })
 
 ### Step 3: Edit Details (if needed)
 
-Use `chorus_update_task` to refine the task after creation. **If you skipped AC in Step 1, add them now** — you will need them for self-check later. Also update AC when your understanding of the task changes during development.
+Use `chorus_update_task` to refine the task after creation. Tasks always have AC (creation requires them), but **update them when your understanding changes during development**. Passing `acceptanceCriteriaItems` **replaces** the task's criteria with the provided non-empty set; omit the field to leave them unchanged (it cannot be used to clear AC).
 
 ```
 chorus_update_task({
@@ -172,7 +177,7 @@ Quick Tasks work with Claude Code Agent Teams just like proposal-based tasks:
 ## Tips
 
 - Keep Quick Tasks small — if you need more than 2-3 tasks, consider using `/proposal`
-- **Always write acceptance criteria at creation time** — they are your self-check contract. Specific, testable AC enables autonomous verification and makes the entire workflow self-contained
+- **Acceptance criteria are required at creation time** — `chorus_create_tasks` rejects tasks without them. They are your self-check contract; specific, testable AC enables autonomous verification and makes the entire workflow self-contained
 - Use `chorus_update_task` to refine tasks (including AC) after creation rather than deleting and recreating
 - Pass `proposalUuid` to attach follow-up or gap-filling tasks to an existing proposal — this keeps related work grouped in the same project context and DAG
 - Quick Tasks show up in the same project task list and DAG as proposal-based tasks

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

@@ -4,7 +4,7 @@ description: Chorus Review workflow — approve/reject proposals, verify tasks,
 license: AGPL-3.0
 metadata:
   author: chorus
-  version: "0.9.0"
+  version: "0.9.3"
   category: project-management
   mcp_server: chorus
 ---
@@ -110,10 +110,12 @@ Prioritize: **Proposals first** (they unblock PM and Developer work), then task
 #### A1: Read the Proposal
 
 ```
-chorus_get_proposal({ proposalUuid: "<proposal-uuid>" })
+chorus_get_proposal({ proposalUuid: "<proposal-uuid>", section: "full" })
 ```
 
-This returns: title, description, input ideas, **document drafts** (PRD, tech design), **task drafts** (with descriptions and acceptance criteria).
+`chorus_get_proposal` defaults to `section: "basic"` — proposal metadata plus a lightweight index of the drafts (uuid, type/title, contentLength, AC count, dependency edges) with **no** document content or full task descriptions. For a review you need the bodies, so pass `section: "full"` to get everything at once (or `section: "documents"` / `section: "tasks"` to read one kind at a time).
+
+The `full` view returns: title, description, input ideas, **document drafts** (PRD, tech design), **task drafts** (with descriptions and acceptance criteria).
 
 #### A2: Quality Checklist
 

package/.next/standalone/public/chorus-plugin/skills/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.9.0"
+  version: "0.9.3"
   category: project-management
   mcp_server: chorus
 ---
@@ -224,7 +224,7 @@ In /yolo mode, the agent generates elaboration questions and answers them itself
    })
    ```
 
-3. **Add task drafts incrementally** (use returned `draftUuid` for dependency chaining):
+3. **Add task drafts incrementally** (use returned `draftUuid` for dependency chaining). `acceptanceCriteriaItems` is **required** on every draft — at least one non-blank criterion, or the call is rejected:
    ```
    # First task
    result1 = chorus_pm_add_task_draft({

package/.next/standalone/public/install-codex.sh

@@ -14,8 +14,8 @@
 #      [plugins."chorus@chorus-plugins"] enabled = true into ~/.codex/config.toml,
 #      so Codex auto-enables the plugin on first launch (falls back to one-click
 #      `/plugins → Install` if auto-install does not fire).
-#   4. Installs a lazy hook wrapper under ~/.codex/hooks/chorus/ so Chorus hooks
-#      work even before the plugin cache is materialized.
+#   4. Enables Codex lifecycle hooks. Chorus hook scripts are bundled in the
+#      plugin manifest and loaded by Codex after the plugin is installed/enabled.
 
 set -euo pipefail
 
@@ -35,6 +35,158 @@ CONFIG_TOML="$CODEX_HOME/config.toml"
 
 is_tty() { [ -t 0 ] && [ -t 1 ]; }
 
+clean_legacy_chorus_hooks_json() {
+  local hooks_json="$1"
+  local tmp backup removed
+
+  tmp="$(mktemp "${TMPDIR:-/tmp}/chorus-hooks.XXXXXX")"
+  backup="${hooks_json}.chorus-legacy-bak"
+  cp "$hooks_json" "$backup"
+
+  if command -v node >/dev/null 2>&1; then
+    removed="$(node - "$hooks_json" "$tmp" <<'NODE'
+const fs = require("fs");
+const input = process.argv[2];
+const output = process.argv[3];
+let removed = 0;
+
+function isLegacyCommand(value) {
+  return typeof value === "string" && value.indexOf("hooks/chorus/run-hook.sh") !== -1;
+}
+
+function clean(value, parentKey) {
+  if (Array.isArray(value)) {
+    return value
+      .map((item) => clean(item, parentKey))
+      .filter((item) => item !== undefined);
+  }
+
+  if (value && typeof value === "object") {
+    if (isLegacyCommand(value.command)) {
+      removed += 1;
+      return undefined;
+    }
+
+    const hadHooksArray = Array.isArray(value.hooks);
+    const out = {};
+    for (const [key, child] of Object.entries(value)) {
+      const cleaned = clean(child, key);
+      if (cleaned === undefined) continue;
+      if (Array.isArray(cleaned) && cleaned.length === 0 && (key === "hooks" || parentKey === "hooks")) continue;
+      out[key] = cleaned;
+    }
+
+    if (hadHooksArray && (!Array.isArray(out.hooks) || out.hooks.length === 0)) {
+      return undefined;
+    }
+    return out;
+  }
+
+  return value;
+}
+
+let data = JSON.parse(fs.readFileSync(input, "utf8"));
+data = clean(data, "") || {};
+if (data.hooks && typeof data.hooks === "object" && !Array.isArray(data.hooks)) {
+  for (const key of Object.keys(data.hooks)) {
+    if (Array.isArray(data.hooks[key]) && data.hooks[key].length === 0) {
+      delete data.hooks[key];
+    }
+  }
+  if (Object.keys(data.hooks).length === 0) {
+    delete data.hooks;
+  }
+}
+fs.writeFileSync(output, JSON.stringify(data, null, 2) + "\n");
+process.stdout.write(String(removed));
+NODE
+    )" || {
+      rm -f "$tmp"
+      warn "Could not parse $hooks_json with node; leaving legacy hooks unchanged."
+      warn "Backup created at $backup"
+      return 1
+    }
+  elif command -v python3 >/dev/null 2>&1; then
+    removed="$(python3 - "$hooks_json" "$tmp" <<'PY'
+import json
+import sys
+
+input_path = sys.argv[1]
+output_path = sys.argv[2]
+removed = 0
+
+def is_legacy_command(value):
+    return isinstance(value, str) and "hooks/chorus/run-hook.sh" in value
+
+def clean(value, parent_key=""):
+    global removed
+    if isinstance(value, list):
+        return [item for item in (clean(child, parent_key) for child in value) if item is not None]
+    if isinstance(value, dict):
+        if is_legacy_command(value.get("command")):
+            removed += 1
+            return None
+        had_hooks_array = isinstance(value.get("hooks"), list)
+        out = {}
+        for key, child in value.items():
+            cleaned = clean(child, key)
+            if cleaned is None:
+                continue
+            if isinstance(cleaned, list) and not cleaned and (key == "hooks" or parent_key == "hooks"):
+                continue
+            out[key] = cleaned
+        if had_hooks_array and (not isinstance(out.get("hooks"), list) or not out["hooks"]):
+            return None
+        return out
+    return value
+
+with open(input_path, "r", encoding="utf-8") as f:
+    data = json.load(f)
+
+data = clean(data) or {}
+if isinstance(data.get("hooks"), dict):
+    for key in list(data["hooks"].keys()):
+        if isinstance(data["hooks"][key], list) and not data["hooks"][key]:
+            del data["hooks"][key]
+    if not data["hooks"]:
+        del data["hooks"]
+
+with open(output_path, "w", encoding="utf-8") as f:
+    json.dump(data, f, indent=2)
+    f.write("\n")
+
+print(removed, end="")
+PY
+    )" || {
+      rm -f "$tmp"
+      warn "Could not parse $hooks_json with python3; leaving legacy hooks unchanged."
+      warn "Backup created at $backup"
+      return 1
+    }
+  else
+    rm -f "$tmp"
+    warn "Cannot auto-clean $hooks_json because neither node nor python3 is available."
+    warn "Backup created at $backup"
+    return 1
+  fi
+
+  if [ "${removed:-0}" = "0" ]; then
+    rm -f "$tmp"
+    warn "No legacy Chorus hook entries were removed from $hooks_json."
+    warn "Backup created at $backup"
+    return 1
+  fi
+
+  if grep -q '[^[:space:]{}]' "$tmp" 2>/dev/null; then
+    mv "$tmp" "$hooks_json"
+    ok "Removed $removed legacy Chorus hook entr$( [ "$removed" = "1" ] && printf 'y' || printf 'ies' ) from $hooks_json"
+  else
+    rm -f "$tmp" "$hooks_json"
+    ok "Removed $removed legacy Chorus hook entr$( [ "$removed" = "1" ] && printf 'y' || printf 'ies' ) and deleted now-empty $hooks_json"
+  fi
+  ok "Backup saved at $backup"
+}
+
 # If piped through `curl | bash`, stdin is the script body. Re-open from /dev/tty
 # so interactive prompts still work — but only if a real TTY is available AND we
 # actually need to prompt for input. Both CHORUS_URL and CHORUS_API_KEY being set
@@ -181,104 +333,61 @@ TOML
 
 ok "Wrote [mcp_servers.chorus] and [plugins.\"chorus@chorus-plugins\"] → ${CONFIG_TOML}"
 
-# ---------- step 5: install hooks ----------
-hdr "5/5  Installing Chorus hooks"
+# ---------- step 5: enable hooks ----------
+hdr "5/5  Enabling Codex lifecycle hooks"
 
-# Install a tiny wrapper that lazily resolves the newest plugin cache at
-# hook-run time. This lets us write hooks.json BEFORE `/plugins → Install`
-# has materialized the plugin cache — first-run UX becomes truly one-shot.
-WRAPPER_DIR="$CODEX_HOME/hooks/chorus"
-WRAPPER="$WRAPPER_DIR/run-hook.sh"
-mkdir -p "$WRAPPER_DIR"
-cat > "$WRAPPER" <<'WRAP'
-#!/usr/bin/env bash
-# Chorus hook wrapper (installed by public/install-codex.sh).
-# Resolves the newest installed Chorus plugin version at runtime and execs
-# the named hook script from its hooks/ directory. Exits 0 (no-op) if the
-# plugin has not been installed yet, so Codex sessions still start cleanly.
-set -eu
-HOOK_NAME="${1:-}"
-if [ -z "$HOOK_NAME" ]; then
-  echo '{}' ; exit 0
-fi
-shift
-CODEX_HOME_RESOLVED="${CODEX_HOME:-$HOME/.codex}"
-PLUGIN_ROOT="$CODEX_HOME_RESOLVED/plugins/cache/chorus-plugins/chorus"
-if [ ! -d "$PLUGIN_ROOT" ]; then
-  echo '{}' ; exit 0
-fi
-VER="$(ls -1 "$PLUGIN_ROOT" 2>/dev/null | sort -V | tail -1)"
-if [ -z "$VER" ]; then
-  echo '{}' ; exit 0
-fi
-SCRIPT="$PLUGIN_ROOT/$VER/hooks/$HOOK_NAME"
-if [ ! -x "$SCRIPT" ]; then
-  if [ -f "$SCRIPT" ]; then
-    chmod +x "$SCRIPT" 2>/dev/null || true
+HOOKS_JSON="$CODEX_HOME/hooks.json"
+if [ -f "$HOOKS_JSON" ] && grep -q "hooks/chorus/run-hook.sh" "$HOOKS_JSON" 2>/dev/null; then
+  warn "Found legacy copied Chorus hook entries in $HOOKS_JSON."
+  warn "These can duplicate the plugin-bundled Chorus hooks now loaded by Codex."
+  warn "Legacy entries:"
+  grep -n "hooks/chorus/run-hook.sh" "$HOOKS_JSON" 2>/dev/null | sed 's/^/    /' >&2 || true
+
+  if [ -r /dev/tty ] && [ -w /dev/tty ]; then
+    printf "  Clean legacy Chorus entries from %s now? [y/N]: " "$HOOKS_JSON" > /dev/tty
+    read -r clean_legacy_hooks_answer < /dev/tty
+    case "$clean_legacy_hooks_answer" in
+      y|Y|yes|YES|Yes)
+        clean_legacy_chorus_hooks_json "$HOOKS_JSON" || true
+        ;;
+      *)
+        warn "Keeping legacy hooks unchanged. Use /hooks to disable them or remove matching entries manually to avoid duplicates."
+        ;;
+    esac
   else
-    echo '{}' ; exit 0
+    warn "No interactive TTY available; keeping legacy hooks unchanged."
+    warn "Re-run this installer in a terminal to auto-clean them, or remove matching entries manually."
   fi
 fi
-exec "$SCRIPT" "$@"
-WRAP
-chmod +x "$WRAPPER"
-ok "Installed hook wrapper → $WRAPPER"
 
-HOOKS_JSON="$CODEX_HOME/hooks.json"
-if [ -f "$HOOKS_JSON" ] && ! grep -q "hooks/chorus/run-hook.sh\|chorus-plugins/chorus" "$HOOKS_JSON" 2>/dev/null; then
-  warn "Found a non-Chorus $HOOKS_JSON — not overwriting."
-  warn "  Add Chorus hook entries manually (command = $WRAPPER on-session-start.sh | on-post-submit-proposal.sh | on-post-submit-for-verify.sh)."
-else
-  cat > "$HOOKS_JSON" <<HJSON
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "startup|resume|clear",
-        "hooks": [
-          { "type": "command", "command": "$WRAPPER on-session-start.sh", "timeout": 20, "statusMessage": "Chorus: checkin" }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": ".*chorus_pm_submit_proposal",
-        "hooks": [
-          { "type": "command", "command": "$WRAPPER on-post-submit-proposal.sh", "timeout": 10 }
-        ]
-      },
-      {
-        "matcher": ".*chorus_submit_for_verify",
-        "hooks": [
-          { "type": "command", "command": "$WRAPPER on-post-submit-for-verify.sh", "timeout": 10 }
-        ]
-      }
-    ]
-  }
-}
-HJSON
-  ok "Wrote $HOOKS_JSON (routing through $WRAPPER)"
-fi
-
-# Enable the codex_hooks feature flag in config.toml (idempotent).
+# Keep the current canonical feature key. `codex_hooks` is a deprecated alias;
+# remove any old hook feature setting from [features] before writing `hooks = true`
+# so reruns do not create duplicate TOML keys.
 if grep -qE "^\[features\]" "$CONFIG_TOML"; then
-  if ! grep -qE "^codex_hooks\s*=\s*true" "$CONFIG_TOML"; then
-    tmp="$(mktemp "${TMPDIR:-/tmp}/chorus-features.XXXXXX")"
-    awk '
-      /^\[features\][[:space:]]*$/ { print; print "codex_hooks = true"; inserted=1; next }
-      { print }
-    ' "$CONFIG_TOML" > "$tmp" && mv "$tmp" "$CONFIG_TOML"
-    ok "Added codex_hooks = true under existing [features]"
-  else
-    ok "codex_hooks feature flag already enabled"
-  fi
+  tmp="$(mktemp "${TMPDIR:-/tmp}/chorus-features.XXXXXX")"
+  awk '
+    /^\[features\][[:space:]]*$/ {
+      in_features = 1
+      print
+      print "hooks = true"
+      next
+    }
+    /^\[/ {
+      in_features = 0
+    }
+    in_features && /^[[:space:]]*(hooks|codex_hooks)[[:space:]]*=/ {
+      next
+    }
+    { print }
+  ' "$CONFIG_TOML" > "$tmp" && mv "$tmp" "$CONFIG_TOML"
+  ok "Set [features] hooks = true"
 else
   cat >> "$CONFIG_TOML" <<'TFEAT'
 
 [features]
-codex_hooks = true
+hooks = true
 TFEAT
-  ok "Appended [features] codex_hooks = true"
+  ok "Appended [features] hooks = true"
 fi
 
 # ---------- epilogue ----------
@@ -296,7 +405,8 @@ so one manual click is the fallback path).
 
 Verify anytime:
   ${BOLD}codex mcp list${RESET}         # 'chorus' row, Auth = 'Bearer token'
-  ${BOLD}codex features list${RESET}    # codex_hooks + plugins both true
+  ${BOLD}codex features list${RESET}    # hooks + plugins both true
+  ${BOLD}/hooks${RESET}                 # review/trust bundled Chorus hooks after launch
 
 Then in Codex type ${BOLD}\$chorus${RESET} (or \$develop, \$review, \$proposal, …) to
 activate a skill. To change your API key later, just re-run this installer.

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