@ritualai/cli 0.7.5 → 0.7.6

package/skills/vscode/ritual/references/resume-flow.md

@@ -23,7 +23,7 @@ Same as `/ritual build` Step 1. Project-pinned workspace from `.ritual/config.js
 
 If the workspace has **zero explorations**: tell the user politely and pivot.
 
-> No in-flight explorations in this workspace yet. Want me to start a fresh one? **Run `/ritual build <your problem>`.**
+> No in-flight explorations in this workspace yet. Start a new Ritual build with `/ritual build <your problem>`.
 
 End the flow here. Don't bounce them into `/ritual build` automatically — explicit user intent beats implicit handoff.
 
@@ -52,7 +52,7 @@ If there are multiple plausible targets, group by state badge and show:
 > - **{name}** — {…}
 >   *…*
 >
-> **✅ ready to implement** (1)
+> **✅ ready for build brief** (1)
 > - **{name}** — {…}
 >   *Last touched {N} days ago. Next: generate the build brief.*
 >
@@ -64,9 +64,9 @@ State badge → user-facing label + suggested next step (same table as `/ritual
 |---|---|---|---|
 | 📍 | `in_progress` | "still in discovery" | Continue discovery |
 | 💬 | `awaiting_admin` | "waiting on admin to accept recommendations" | Admin review |
-| ✅ | `ready` | "ready to implement" | Generate the build brief |
+| ✅ | `ready` | "ready for build brief" | Generate the build brief |
 | 🛠 | `in_flight` | "implementation in progress" | Refresh the build brief on remaining work |
-| ✓ | `done` | "fully shipped" | Suggest `/ritual lineage` on the files OR `/ritual drift` (when shipped) to check for new changes since |
+| ✓ | `done` | "shipped with follow-ups" if open deferrals exist; otherwise "shipped context" | Address follow-ups or use `/ritual lineage` on touched files. Hide fully complete shipped work by default. |
 | ⚠ | `implemented_ahead` | "code shipped before admin acceptance" | Surface to user, ask admin to reconcile |
 
 Silence on no-data (CLI Tenet #6): if a state bucket is empty, don't render it. Don't print "**🛠 implementation in progress** (0)".