@chorus-aidlc/chorus 0.6.6 → 0.6.7

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.7.3"
+  version: "0.7.4"
   category: project-management
   mcp_server: chorus
 ---
@@ -242,13 +242,13 @@ In /yolo mode, the agent generates elaboration questions and answers them itself
    ```
    chorus_pm_submit_proposal({ proposalUuid: "<proposal-uuid>" })
    ```
-   The PostToolUse hook will auto-spawn `chorus:proposal-reviewer`. Do NOT manually spawn it.
+   After this call, the PostToolUse hook injects context instructing you to spawn `chorus:proposal-reviewer`. You MUST spawn it yourself in **foreground** (do NOT set `run_in_background`) — it is NOT auto-launched.
 
 ---
 
 ### Phase 2: Proposal Review Loop
 
-After `chorus_pm_submit_proposal`, the PostToolUse hook auto-spawns `chorus:proposal-reviewer` as a read-only sub-agent. Wait for it to complete, then:
+After `chorus_pm_submit_proposal`, the PostToolUse hook injects context instructing you to spawn `chorus:proposal-reviewer`. You MUST manually spawn it as a read-only sub-agent in **foreground** (do NOT set `run_in_background`). Wait for it to complete, then:
 
 1. **Read the reviewer's VERDICT:**
    ```
@@ -279,7 +279,7 @@ After `chorus_pm_submit_proposal`, the PostToolUse hook auto-spawns `chorus:prop
      ```
      chorus_pm_submit_proposal({ proposalUuid: "<proposal-uuid>" })
      ```
-     The hook spawns the reviewer again for Round 2.
+     After resubmission, the hook injects context again — spawn the reviewer yourself for Round 2.
 
 3. **Max rounds:** Loop up to `maxProposalReviewRounds` (from plugin config, default 3). If exhausted:
    ```
@@ -323,7 +323,7 @@ loop:
   # 4. Wait for all sub-agents to complete
   #    Each sub-agent follows the /develop workflow:
   #    claim -> in_progress -> develop -> report -> self-check AC -> submit_for_verify
-  #    PostToolUse hook auto-spawns task-reviewer after submit_for_verify
+  #    PostToolUse hook injects context — main agent must spawn task-reviewer after submit_for_verify
 
   # 5. Proceed to Phase 4 (verification) for this wave
   wave += 1
@@ -350,11 +350,11 @@ for each task in unblocked:
   chorus_report_criteria_self_check({ taskUuid: "<task-uuid>", criteria: [...] })
   chorus_submit_for_verify({ taskUuid: "<task-uuid>", summary: "..." })
 
-  # PostToolUse hook still triggers task-reviewer
+  # PostToolUse hook injects context — you must spawn task-reviewer yourself
   # Proceed to Phase 4 verification for this task before moving to next
 ```
 
-The fallback is slower (sequential, not parallel) but still completes the pipeline. All reviewer hooks and verification work the same way.
+The fallback is slower (sequential, not parallel) but still completes the pipeline. The PostToolUse hook injects reviewer instructions the same way in both modes — you must always spawn the reviewer manually.
 
 ---
 
@@ -371,13 +371,17 @@ for each task in wave_tasks:
     # Sub-agent may have failed; skip or handle
     continue
 
-  # 2. Read task-reviewer VERDICT
+  # 2. Spawn task-reviewer in FOREGROUND (hook injects context — you must spawn it yourself)
+  #    Do NOT set run_in_background — you need the VERDICT before proceeding
+  Agent({ subagent_type: "chorus:task-reviewer", prompt: "Review task <task-uuid>..." })
+
+  # 3. Read task-reviewer VERDICT
   comments = chorus_get_comments({ targetType: "task", targetUuid: "<task-uuid>" })
-  # Find most recent VERDICT comment
+  # Find the most recent comment containing "VERDICT:"
 
-  # 3. Act on VERDICT
-  if VERDICT is PASS or PASS WITH NOTES:
-    # Mark all AC as passed
+  # 4. Act on VERDICT — three possible outcomes:
+  if VERDICT is "PASS":
+    # All AC verified, no issues. Mark AC and verify.
     chorus_mark_acceptance_criteria({
       taskUuid: "<task-uuid>",
       criteria: [
@@ -388,7 +392,13 @@ for each task in wave_tasks:
     chorus_admin_verify_task({ taskUuid: "<task-uuid>" })
     # Task is now "done" -- unblocks dependents
 
-  if VERDICT is FAIL:
+  if VERDICT is "PASS WITH NOTES":
+    # All AC verified, minor non-blocking notes. Still mark AC and verify.
+    chorus_mark_acceptance_criteria({ ... })
+    chorus_admin_verify_task({ taskUuid: "<task-uuid>" })
+
+  if VERDICT is "FAIL":
+    # BLOCKERs found. Do NOT verify. Reopen for rework.
     chorus_admin_reopen_task({ taskUuid: "<task-uuid>" })
     # Task returns to "open", will be picked up in next wave
 ```

package/README.md

@@ -35,6 +35,8 @@ creates   analyzes       drafts PRD            codes &      reviews   closes
 
 ## What's New
 
+**[v0.6.6](https://chorus-ai.dev/blog/chorus-v0.6.6-release/)** — npm one-click install (`npx @chorus-aidlc/chorus`), document export (MD/PDF/Word), proposal revoke, faster agent checkin with work status at a glance.
+
 **[v0.6.2](https://chorus-ai.dev/blog/chorus-v0.6.2-release/)** — Embedded PGlite mode (zero-dependency deployment), structured logging with Pino, stateless MCP for horizontal scaling, default port changed to 8637.
 
 **[v0.6.1](https://chorus-ai.dev/blog/chorus-v0.6.1-release/)** — `/yolo` skill: full-auto AI-DLC pipeline (Idea → Proposal → Execute → Verify) with Agent Team parallel execution.

package/README.zh.md

@@ -26,6 +26,8 @@ creates   analyzes       drafts PRD            codes &      reviews   closes
 
 ## 最近更新
 
+**[v0.6.6](https://chorus-ai.dev/zh/blog/chorus-v0.6.6-release/)** — npm 一键安装（`npx @chorus-aidlc/chorus`）、文档导出（MD/PDF/Word）、Proposal 撤回、优化 Agent Checkin 快速获取工作状态。
+
 **[v0.6.2](https://chorus-ai.dev/zh/blog/chorus-v0.6.2-release/)** — 嵌入式 PGlite 模式（零依赖部署）、Pino 结构化日志、无状态 MCP 支持水平扩展、默认端口改为 8637。
 
 **[v0.6.1](https://chorus-ai.dev/zh/blog/chorus-v0.6.1-release/)** — `/yolo` 技能：全自动 AI-DLC 流水线（Idea → Proposal → Execute → Verify），支持 Agent Team 并行执行。

package/chorus.mjs

@@ -16,6 +16,25 @@ import { fileURLToPath } from "node:url";
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 
+// ---------------------------------------------------------------------------
+// Dependency resolution (hoist-safe — see issue #214)
+// ---------------------------------------------------------------------------
+// Use import.meta.resolve so the correct copy of each dependency is found
+// regardless of how the user's package manager laid out node_modules
+// (nested, hoisted to global root, yarn classic link, etc.).
+
+function resolveOrDie(specifier) {
+  try {
+    return fileURLToPath(import.meta.resolve(specifier));
+  } catch {
+    console.error(`\nERROR: cannot resolve dependency "${specifier}".`);
+    console.error(`This usually means your package manager hoisted deps in an`);
+    console.error(`unexpected layout. Try reinstalling with npm, or see`);
+    console.error(`https://github.com/Chorus-AIDLC/Chorus/issues/214 for context.`);
+    process.exit(1);
+  }
+}
+
 // ---------------------------------------------------------------------------
 // CLI argument parsing (zero dependencies)
 // ---------------------------------------------------------------------------
@@ -149,15 +168,12 @@ async function main() {
     // Start embedded PGlite
     console.log(`Starting embedded PostgreSQL (PGlite) on port ${PGLITE_PORT}...`);
 
-    const serverScript = join(
-      __dirname,
-      "node_modules",
-      "@electric-sql",
-      "pglite-socket",
-      "dist",
-      "scripts",
-      "server.js"
-    );
+    // @electric-sql/pglite-socket does not expose `./dist/scripts/server.js`
+    // via the "exports" field, so we resolve the package entry (which IS
+    // exported) and derive the sibling server.js path. This remains
+    // hoist-safe — see issue #214.
+    const pgliteSocketEntry = resolveOrDie("@electric-sql/pglite-socket");
+    const serverScript = resolve(dirname(pgliteSocketEntry), "scripts", "server.js");
 
     pgliteProcess = fork(serverScript, [
       `--db=${join(dataDir, "pglite")}`,
@@ -166,7 +182,13 @@ async function main() {
     ], { stdio: "ignore", detached: false });
 
     pgliteProcess.on("error", (err) => {
-      console.error("PGlite process error:", err.message);
+      // MODULE_NOT_FOUND is unreachable after the resolveOrDie fix above, but
+      // guard against regressions (see issue #214).
+      if (err.code === "MODULE_NOT_FOUND") {
+        console.error(`PGlite server script unreachable: ${err.message}`);
+      } else {
+        console.error("PGlite process error:", err.message);
+      }
       process.exit(1);
     });
 
@@ -191,9 +213,9 @@ async function main() {
 
   // 3. Run database migrations
   console.log("Running database migrations...");
-  const prismaPath = join(__dirname, "node_modules", ".bin", "prisma");
+  const prismaBin = resolveOrDie("prisma/build/index.js");
   try {
-    execSync(`"${prismaPath}" migrate deploy`, {
+    execSync(`"${process.execPath}" "${prismaBin}" migrate deploy`, {
       cwd: __dirname,
       stdio: "inherit",
       env: { ...process.env },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chorus-aidlc/chorus",
-  "version": "0.6.6",
+  "version": "0.6.7",
   "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": {
@@ -25,9 +25,7 @@
     ".next/standalone/",
     "prisma/schema.prisma",
     "prisma/migrations/",
-    "prisma.config.ts",
-    "node_modules/@electric-sql/",
-    "node_modules/dotenv/"
+    "prisma.config.ts"
   ],
   "scripts": {
     "dev": "next dev --turbopack --port 8637",