dreamcontext 0.8.3 → 0.8.5

package/dist/skill-packs/goal-skill/SKILL.md

@@ -64,7 +64,7 @@ flowchart TD
     P5 -->|cap reached| ESC2[ESCALATE to user — do NOT proceed]
     P5 -->|PASS| P6{Phase 6 — goal-validator runs the chosen method: PASS?}
     P6 -->|FAIL| P4
-    P6 -->|PASS| DONE[Goal reached — task to in_review, ask the user to complete]
+    P6 -->|PASS| DONE[Goal reached — validation passed, mark task completed + tell the user]
 ```
 
 ### Phase 0 — Scope & validation method (ask the user)
@@ -143,9 +143,11 @@ recorded in the task and returns `PASS | FAIL` with evidence (exact command + ou
 
 - **FAIL** → append the failure report to the task (`dreamcontext tasks log`), and route
   **back to Phase 4** (IMPLEMENT). Loop IMPLEMENT → REVIEW → VALIDATE until validation PASSES.
-- **PASS** → the goal is reached. `dreamcontext tasks status <slug> in_review "all criteria
-  met; validation passed via <method>"`, then **ask the user to confirm completion** —
-  `tasks complete` is a user action; you never auto-complete.
+- **PASS** → the goal is reached. The user-chosen validation method *is* the definition of
+  done, and it passed with evidence — so close it: `dreamcontext tasks status <slug> completed
+  "all criteria met; validation passed via <method>"`, then **tell the user it's done** (what
+  shipped + the evidence). Only leave it in `in_review` instead if the validation surfaced
+  something a human should still eyeball before closing.
 
 ## Convergence rules (how the loops end)
 
@@ -166,7 +168,7 @@ recorded in the task and returns `PASS | FAIL` with evidence (exact command + ou
 | "I'll let the implementer review its own work." | Self-review is not review. Use a clean-context `reviewer`. |
 | "I'll skip asking the user how to validate, tests are obviously the way." | Phase 0 is non-negotiable. Validation criteria are the user's call. |
 | "We've looped 4 times, but I think this next one fixes it." | Cap is 3. Escalate. The user decides whether to keep going. |
-| "I'll auto-complete the task, validation passed." | `complete` is user-only. Move to `in_review` and ask. |
+| "I'll mark it complete because I *think* it's done." | Done is defined by Phase 6 validation passing with evidence — not by your hunch. Complete only after PASS. |
 
 ## Rationalization table
 
@@ -182,7 +184,7 @@ recorded in the task and returns `PASS | FAIL` with evidence (exact command + ou
 - **Orchestrator never writes production code.** Dispatch sub-agents.
 - **Plan reviewers run in parallel**, in one message. Sequential dispatch defeats the design.
 - **Never skip Phase 0's validation-method question.**
-- **Never auto-`complete` the task** — that's the user's action; you stop at `in_review`.
+- **`complete` only after Phase 6 PASS** — validation passing with evidence is the definition of done; never complete on a hunch, and never before validation.
 - **Tell `reviewer` to run `git diff` itself**; don't paste diffs into prompts.
 - **Caps are hard** (3 per loop). At the cap, escalate — never declare done.
 - **Use the `dreamcontext` skill** throughout — the task doc is the source of truth.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dreamcontext",
-  "version": "0.8.3",
+  "version": "0.8.5",
   "description": "dreamcontext — the persistent brain for your AI agents. Remembers what you built, knows how your project works.",
   "type": "module",
   "bin": {

package/skill/SKILL.md

@@ -408,10 +408,10 @@ dreamcontext tasks insert <name> changelog "Implemented pagination for /api/task
 # Lifecycle
 dreamcontext tasks log <name> "what was done"                           # Quick changelog entry (MANDATORY)
 dreamcontext tasks status <name> in_review "Ready for review"           # Bump status (todo|in_progress|in_review|completed)
-dreamcontext tasks complete <name> "summary"                            # Mark complete (user only; sleep agent never auto-completes)
+dreamcontext tasks complete <name> "summary"                            # Convenience for marking complete
 ```
 
-**Status convention:** `todo` -> `in_progress` -> `in_review` -> `completed`. The sleep agent bumps tasks it touched to `in_review` (never `completed`) so the user can verify before declaring done. This prevents the "task rotting in todo" failure mode.
+**Status convention:** `todo` -> `in_progress` -> `in_review` -> `completed`. The sleep agent picks the status that matches reality — `completed` for work that's demonstrably done, low-risk, and already validated, and `in_review` only when a human genuinely must verify something (a behaviour change, a design decision, a risky/critical-path change). It does **not** reflexively park everything in `in_review`; finished work that needs no review is closed, so neither "task rotting in todo" nor "task rotting half-closed in in_review" happens.
 
 Task insert sections: `why`, `user_stories`, `acceptance_criteria`, `constraints`, `technical_details`, `notes`, `changelog`
 
@@ -601,7 +601,7 @@ All commands prefixed with `dreamcontext`. For reading/searching, use native too
 | `tasks rice <name> [--reach N] [--impact N] [--confidence N] [--effort N] [--clear]` | Print or update RICE values; no flags prints current values |
 | `tasks insert <name> <section> <content>` | Insert into task section |
 | `tasks status <name> <todo\|in_progress\|in_review\|completed> [reason...]` | Change task status (logs to changelog) |
-| `tasks complete <name>` | Complete task (user only; sleep agent uses `tasks status ... in_review`) |
+| `tasks complete <name>` | Complete task (convenience for `tasks status <name> completed`) |
 | `tasks log <name> <content>` | Log task progress |
 | `bookmark add "<message>" [-s 1\|2\|3] [--task <slug>]` | Bookmark an important moment with optional task link |
 | `bookmark list` | Show current bookmarks |

package/skill-packs/goal-skill/SKILL.md

@@ -64,7 +64,7 @@ flowchart TD
     P5 -->|cap reached| ESC2[ESCALATE to user — do NOT proceed]
     P5 -->|PASS| P6{Phase 6 — goal-validator runs the chosen method: PASS?}
     P6 -->|FAIL| P4
-    P6 -->|PASS| DONE[Goal reached — task to in_review, ask the user to complete]
+    P6 -->|PASS| DONE[Goal reached — validation passed, mark task completed + tell the user]
 ```
 
 ### Phase 0 — Scope & validation method (ask the user)
@@ -143,9 +143,11 @@ recorded in the task and returns `PASS | FAIL` with evidence (exact command + ou
 
 - **FAIL** → append the failure report to the task (`dreamcontext tasks log`), and route
   **back to Phase 4** (IMPLEMENT). Loop IMPLEMENT → REVIEW → VALIDATE until validation PASSES.
-- **PASS** → the goal is reached. `dreamcontext tasks status <slug> in_review "all criteria
-  met; validation passed via <method>"`, then **ask the user to confirm completion** —
-  `tasks complete` is a user action; you never auto-complete.
+- **PASS** → the goal is reached. The user-chosen validation method *is* the definition of
+  done, and it passed with evidence — so close it: `dreamcontext tasks status <slug> completed
+  "all criteria met; validation passed via <method>"`, then **tell the user it's done** (what
+  shipped + the evidence). Only leave it in `in_review` instead if the validation surfaced
+  something a human should still eyeball before closing.
 
 ## Convergence rules (how the loops end)
 
@@ -166,7 +168,7 @@ recorded in the task and returns `PASS | FAIL` with evidence (exact command + ou
 | "I'll let the implementer review its own work." | Self-review is not review. Use a clean-context `reviewer`. |
 | "I'll skip asking the user how to validate, tests are obviously the way." | Phase 0 is non-negotiable. Validation criteria are the user's call. |
 | "We've looped 4 times, but I think this next one fixes it." | Cap is 3. Escalate. The user decides whether to keep going. |
-| "I'll auto-complete the task, validation passed." | `complete` is user-only. Move to `in_review` and ask. |
+| "I'll mark it complete because I *think* it's done." | Done is defined by Phase 6 validation passing with evidence — not by your hunch. Complete only after PASS. |
 
 ## Rationalization table
 
@@ -182,7 +184,7 @@ recorded in the task and returns `PASS | FAIL` with evidence (exact command + ou
 - **Orchestrator never writes production code.** Dispatch sub-agents.
 - **Plan reviewers run in parallel**, in one message. Sequential dispatch defeats the design.
 - **Never skip Phase 0's validation-method question.**
-- **Never auto-`complete` the task** — that's the user's action; you stop at `in_review`.
+- **`complete` only after Phase 6 PASS** — validation passing with evidence is the definition of done; never complete on a hunch, and never before validation.
 - **Tell `reviewer` to run `git diff` itself**; don't paste diffs into prompts.
 - **Caps are hard** (3 per loop). At the cap, escalate — never declare done.
 - **Use the `dreamcontext` skill** throughout — the task doc is the source of truth.

package/dist/dashboard/assets/channel-3OfE-PZ3.js

@@ -1 +0,0 @@
-import{aq as o,ar as n}from"./index-rIZLhbl7.js";const t=(r,a)=>o.lang.round(n.parse(r)[a]);export{t as c};

package/dist/dashboard/assets/classDiagram-6PBFFD2Q-Dpt9qwZI.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-4TB4RGXK--piiFXgS.js";import{_ as i}from"./index-rIZLhbl7.js";import"./chunk-FMBD7UC4-C1Le6hxh.js";import"./chunk-YZCP3GAM-BNc94uy1.js";import"./chunk-55IACEB6-C7uvmawY.js";import"./chunk-EDXVE4YY-BuWBKOPY.js";var u={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{u as diagram};

package/dist/dashboard/assets/classDiagram-v2-HSJHXN6E-Dpt9qwZI.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-4TB4RGXK--piiFXgS.js";import{_ as i}from"./index-rIZLhbl7.js";import"./chunk-FMBD7UC4-C1Le6hxh.js";import"./chunk-YZCP3GAM-BNc94uy1.js";import"./chunk-55IACEB6-C7uvmawY.js";import"./chunk-EDXVE4YY-BuWBKOPY.js";var u={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{u as diagram};

package/dist/dashboard/assets/clone-CZ-InUnR.js

@@ -1 +0,0 @@
-import{b as r}from"./graph-BMW3t-Jz.js";var e=4;function a(o){return r(o,e)}export{a as c};