pi-gsd 2.0.22 → 2.0.24

package/gsd/hooks/gsd-workflow-guard.js

@@ -0,0 +1,98 @@
+#!/usr/bin/env node
+// gsd-hook-version: 1.30.0
+// SHARED CANONICAL FILE - hardlinked into all harness hooks/ directories.
+// Harness config dir is auto-detected from __dirname at runtime.
+// Do NOT hardcode harness-specific paths here. See HOOKS_ARCHITECTURE.md.
+// GSD Workflow Guard - PreToolUse hook
+// Detects when Claude attempts file edits outside a GSD workflow context
+// (no active /gsd- command or Task subagent) and injects an advisory warning.
+//
+// This is a SOFT guard - it advises, not blocks. The edit still proceeds.
+// The warning nudges the agent to use /gsd-quick or /gsd-fast instead of
+// making direct edits that bypass state tracking.
+//
+// Enable via config: hooks.workflow_guard: true (default: false)
+// Only triggers on Write/Edit tool calls to non-.planning/ files.
+
+const fs = require("fs");
+const path = require("path");
+
+let input = "";
+const stdinTimeout = setTimeout(() => process.exit(0), 3000);
+process.stdin.setEncoding("utf8");
+process.stdin.on("data", (chunk) => (input += chunk));
+process.stdin.on("end", () => {
+	clearTimeout(stdinTimeout);
+	try {
+		const data = JSON.parse(input);
+		const toolName = data.tool_name;
+
+		// Only guard Write and Edit tool calls
+		if (toolName !== "Write" && toolName !== "Edit") {
+			process.exit(0);
+		}
+
+		// Check if we're inside a GSD workflow (Task subagent or /gsd- command)
+		// Subagents have a session_id that differs from the parent
+		// and typically have a description field set by the orchestrator
+		if (data.tool_input?.is_subagent || data.session_type === "task") {
+			process.exit(0);
+		}
+
+		// Check the file being edited
+		const filePath = data.tool_input?.file_path || data.tool_input?.path || "";
+
+		// Allow edits to .planning/ files (GSD state management)
+		if (filePath.includes(".planning/") || filePath.includes(".planning\\")) {
+			process.exit(0);
+		}
+
+		// Allow edits to common config/docs files that don't need GSD tracking
+		const allowedPatterns = [
+			/\.gitignore$/,
+			/\.env/,
+			/CLAUDE\.md$/,
+			/AGENTS\.md$/,
+			/GEMINI\.md$/,
+			/settings\.json$/,
+		];
+		if (allowedPatterns.some((p) => p.test(filePath))) {
+			process.exit(0);
+		}
+
+		// Check if workflow guard is enabled
+		const cwd = data.cwd || process.cwd();
+		const configPath = path.join(cwd, ".planning", "config.json");
+		if (fs.existsSync(configPath)) {
+			try {
+				const config = JSON.parse(fs.readFileSync(configPath, "utf8"));
+				if (!config.hooks?.workflow_guard) {
+					process.exit(0); // Guard disabled (default)
+				}
+			} catch (e) {
+				process.exit(0);
+			}
+		} else {
+			process.exit(0); // No GSD project - don't guard
+		}
+
+		// If we get here: GSD project, guard enabled, file edit outside .planning/,
+		// not in a subagent context. Inject advisory warning.
+		const output = {
+			hookSpecificOutput: {
+				hookEventName: "PreToolUse",
+				additionalContext:
+					`⚠️ WORKFLOW ADVISORY: You're editing ${path.basename(filePath)} directly without a GSD command. ` +
+					"This edit will not be tracked in STATE.md or produce a SUMMARY.md. " +
+					"Consider using /gsd-fast for trivial fixes or /gsd-quick for larger changes " +
+					"to maintain project state tracking. " +
+					"If this is intentional (e.g., user explicitly asked for a direct edit), proceed normally.",
+			},
+		};
+
+		process.stdout.write(JSON.stringify(output));
+	} catch (e) {
+		// Silent fail - never block tool execution
+		process.exit(0);
+	}
+});

package/{.gsd/harnesses/pi/get-shit-done → gsd}/references/continuation-format.md

@@ -13,7 +13,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 `{command to copy-paste}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -29,7 +29,7 @@ Standard format for presenting next steps after completing a command or workflow
 1. **Always show what it is** - name + description, never just a command path
 2. **Pull context from source** - ROADMAP.md for phases, PLAN.md `<objective>` for plans
 3. **Command in inline code** - backticks, easy to copy-paste, renders as clickable link
-4. **`/clear` explanation** - always include, keeps it concise but explains why
+4. **`/new` explanation** - always include, keeps it concise but explains why
 5. **"Also available" not "Other options"** - sounds more app-like
 6. **Visual separators** - `---` above and below to make it stand out
 
@@ -46,7 +46,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 `/gsd-execute-phase 2`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -71,7 +71,7 @@ Add note that this is the last plan and what comes after:
 
 `/gsd-execute-phase 2`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -93,7 +93,7 @@ Add note that this is the last plan and what comes after:
 
 `/gsd-plan-phase 2`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -122,7 +122,7 @@ Show completion status before next action:
 
 `/gsd-plan-phase 3`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -151,7 +151,7 @@ When there's no clear primary action:
 
 **To research unknowns:** `/gsd-research-phase 3`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 ```
@@ -171,7 +171,7 @@ All 4 phases shipped
 
 `/gsd-new-milestone`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 ```
@@ -213,18 +213,18 @@ Extract: `**02-03: Refresh Token Rotation** - Add /api/auth/refresh with sliding
 ```
 ## To Continue
 
-Run `/clear`, then paste:
+Run `/new`, then paste:
 /gsd-execute-phase 2
 ```
 
 User has no idea what 02-03 is about.
 
-### Don't: Missing /clear explanation
+### Don't: Missing /new explanation
 
 ```
 `/gsd-plan-phase 3`
 
-Run /clear first.
+Run /new first.
 ```
 
 Doesn't explain why. User might skip it.

package/{.gsd/harnesses/pi/get-shit-done → gsd}/references/ui-brand.md

@@ -74,7 +74,7 @@ Always at end of major completions.
 
 `{copy-paste command}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ───────────────────────────────────────────────────────────────
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/templates/DEBUG.md

@@ -32,7 +32,7 @@ reproduction: [how to trigger]
 started: [when it broke / always broken]
 
 ## Eliminated
-<!-- APPEND only - prevents re-investigating after /clear -->
+<!-- APPEND only - prevents re-investigating after /new -->
 
 - hypothesis: [theory that was wrong]
   evidence: [what disproved it]
@@ -68,7 +68,7 @@ files_changed: []
 **Current Focus:**
 - OVERWRITE entirely on each update
 - Always reflects what the agent is doing RIGHT NOW
-- If the agent reads this after /clear, it knows exactly where to resume
+- If the agent reads this after /new, it knows exactly where to resume
 - Fields: hypothesis, test, expecting, next_action
 
 **Symptoms:**
@@ -81,7 +81,7 @@ files_changed: []
 - APPEND only - never remove entries
 - Prevents re-investigating dead ends after context reset
 - Each entry: hypothesis, evidence that disproved it, timestamp
-- Critical for efficiency across /clear boundaries
+- Critical for efficiency across /new boundaries
 
 **Evidence:**
 - APPEND only - never remove entries
@@ -140,7 +140,7 @@ files_changed: []
 
 <resume_behavior>
 
-When the agent reads this file after /clear:
+When the agent reads this file after /new:
 
 1. Parse frontmatter → know status
 2. Read Current Focus → know exactly what was happening

package/{.gsd/harnesses/pi/get-shit-done → gsd}/templates/UAT.md

@@ -174,7 +174,7 @@ blocked: [N]
 - `/gsd-verify-work {phase}` picks up from first pending/blocked test
 - When all items resolved, status advances to "complete"
 
-**Resume after /clear:**
+**Resume after /new:**
 1. Read frontmatter → know phase and status
 2. Read Current Test → know where we are
 3. Find first [pending] result → continue from there

package/gsd/workflows/add-phase.md

@@ -0,0 +1,135 @@
+<gsd-version v="1.12.5" />
+
+<gsd-arguments>
+  <settings>
+    <keep-extra-args />
+  </settings>
+  <arg name="description" type="string" optional />
+</gsd-arguments>
+
+<gsd-execute>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="init" />
+      <arg string="phase-op" />
+      <arg string="0" />
+    </args>
+    <outs>
+      <out type="string" name="init" />
+    </outs>
+  </shell>
+  <if>
+    <condition>
+      <starts-with>
+        <left name="init" />
+        <right type="string" value="@file:" />
+      </starts-with>
+    </condition>
+    <then>
+      <string-op op="split">
+        <args>
+          <arg name="init" />
+          <arg type="string" value="@file:" />
+        </args>
+        <outs>
+          <out type="string" name="init-file" />
+        </outs>
+      </string-op>
+      <shell command="cat">
+        <args>
+          <arg name="init-file" wrap='"' />
+        </args>
+        <outs>
+          <out type="string" name="init" />
+        </outs>
+      </shell>
+    </then>
+  </if>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="phase" />
+      <arg string="add-batch" />
+      <arg name="description" wrap='"' />
+    </args>
+    <outs>
+      <out type="string" name="batch-result" />
+    </outs>
+  </shell>
+</gsd-execute>
+
+## Context (pre-injected by WXP)
+
+**Init:**
+<gsd-paste name="init" />
+
+**Phases added:**
+<gsd-paste name="batch-result" />
+
+<process>
+
+<step name="parse_arguments">
+If no description was provided (check `<gsd-paste name="description" />` is empty):
+
+```
+ERROR: Phase description required
+Usage: /gsd-add-phase <description>
+       /gsd-add-phase <desc1> + <desc2> + ...
+Example: /gsd-add-phase Add authentication system
+```
+
+Exit.
+</step>
+
+<step name="check_result">
+The `batch-result` JSON above was already executed by WXP before this message
+reached you. Parse it:
+
+- If it contains an error field → report the error and exit.
+- Otherwise extract `phases[]` — each has `phase_number`, `padded`, `name`,
+  `slug`, `directory`.
+
+Do NOT run `pi-gsd-tools phase add` again, do NOT inspect `.planning/phases/`
+or ROADMAP.md — everything is already done.
+</step>
+
+<step name="completion">
+Present a completion summary:
+
+```
+Added <count> phase(s):
+
+<for each phase in phases[]>
+• Phase <phase_number>: <name>
+  Directory: <directory>
+</for>
+
+Roadmap updated: .planning/ROADMAP.md
+State updated:   .planning/STATE.md
+
+---
+
+## ▶ Next Up
+
+**Phase <last phase_number>: <last name>**
+
+`/gsd-plan-phase <last phase_number>`
+
+<sub>`/clear` first → fresh context window</sub>
+
+---
+
+**Also available:**
+- `/gsd-add-phase <description>` — add another phase
+- `/gsd-plan-phase <N>` — plan any of the new phases
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] `pi-gsd-tools phase add-batch` executed by WXP (not by the agent)
+- [ ] Phase directories created under `.planning/phases/`
+- [ ] ROADMAP.md updated with all new phase entries
+- [ ] STATE.md Roadmap Evolution updated (handled inside add-batch)
+- [ ] Agent presented the pre-injected result — no filesystem exploration
+</success_criteria>

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/audit-milestone.md

@@ -289,7 +289,7 @@ All requirements covered. Cross-phase integration verified. E2E flows complete.
 
 /gsd-complete-milestone {version}
 
-<sub>/clear first → fresh context window</sub>
+<sub>/new first → fresh context window</sub>
 
 ───────────────────────────────────────────────────────────────
 
@@ -334,7 +334,7 @@ Phases needing validation: run `/gsd-validate-phase {N}` for each flagged phase.
 
 /gsd-plan-milestone-gaps
 
-<sub>/clear first → fresh context window</sub>
+<sub>/new first → fresh context window</sub>
 
 ───────────────────────────────────────────────────────────────
 
@@ -376,7 +376,7 @@ All requirements met. No critical blockers. Accumulated tech debt needs review.
 
 /gsd-plan-milestone-gaps
 
-<sub>/clear first → fresh context window</sub>
+<sub>/new first → fresh context window</sub>
 
 ───────────────────────────────────────────────────────────────
 </offer_next>

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/complete-milestone.md

@@ -234,7 +234,7 @@ Tag: v[X.Y]
 
 `/gsd-new-milestone`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 ```

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/discuss-phase-assumptions.md

@@ -653,7 +653,7 @@ Created: .planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md
 
 `/gsd-plan-phase ${PHASE}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/discuss-phase.md

@@ -913,7 +913,7 @@ Created: .planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md
 
 `/gsd-plan-phase ${PHASE} ${GSD_WS}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -1045,7 +1045,7 @@ This keeps the auto-advance chain flat - discuss, plan, and execute all run at t
   Auto-advance pipeline finished: discuss → plan → execute
 
   Next: /gsd-discuss-phase ${NEXT_PHASE} --auto ${GSD_WS}
-  <sub>/clear first → fresh context window</sub>
+  <sub>/new first → fresh context window</sub>
   ```
 - **PLANNING COMPLETE** → Planning done, execution didn't complete:
   ```

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/execute-phase.md

@@ -751,7 +751,7 @@ Items saved to `{phase_num}-HUMAN-UAT.md` - they will appear in `/gsd-progress`
 
 `/gsd-plan-phase {X} --gaps ${GSD_WS}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 Also: `cat {phase_dir}/{phase_num}-VERIFICATION.md` - full report
 Also: `/gsd-verify-work {X} ${GSD_WS}` - manual testing first
@@ -889,7 +889,7 @@ Subagents: fresh context each (200k-1M depending on model). No polling (Task blo
 For 1M+ context models, consider:
 - Passing richer context (code snippets, dependency outputs) directly to executors instead of just file paths
 - Running small phases (≤3 plans, no dependencies) inline without subagent spawning overhead
-- Relaxing /clear recommendations - context rot onset is much further out with 5x window
+- Relaxing /new recommendations - context rot onset is much further out with 5x window
 </context_efficiency>
 
 <failure_handling>

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/execute-plan.md

@@ -533,7 +533,7 @@ If `USER_SETUP_CREATED=true`: display `⚠️ USER SETUP REQUIRED` with path + e
 | summaries = plans, current < highest phase | **B: Phase done**     | Show completion, suggest `/gsd-plan-phase {Z+1}` + `/gsd-verify-work {Z}` + `/gsd-discuss-phase {Z+1}`                                                  |
 | summaries = plans, current = highest phase | **C: Milestone done** | Show banner, suggest `/gsd-complete-milestone` + `/gsd-verify-work` + `/gsd-add-phase`                                                                  |
 
-All routes: `/clear` first for fresh context.
+All routes: `/new` first for fresh context.
 </step>
 
 </process>

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/help.md

@@ -270,7 +270,7 @@ Systematic debugging with persistent state across context resets.
 - Gathers symptoms through adaptive questioning
 - Creates `.planning/debug/[slug].md` to track investigation
 - Investigates using scientific method (evidence → hypothesis → test)
-- Survives `/clear` - run `/gsd-debug` with no args to resume
+- Survives `/new` - run `/gsd-debug` with no args to resume
 - Archives resolved issues to `.planning/debug/resolved/`
 
 Usage: `/gsd-debug "login button doesn't work"`
@@ -553,9 +553,9 @@ Example config:
 
 ```
 /gsd-new-project        # Unified flow: questioning → research → requirements → roadmap
-/clear
+/new
 /gsd-plan-phase 1       # Create plans for first phase
-/clear
+/new
 /gsd-execute-phase 1    # Execute all plans in phase
 ```
 
@@ -577,7 +577,7 @@ Example config:
 
 ```
 /gsd-complete-milestone 1.0.0
-/clear
+/new
 /gsd-new-milestone  # Start next milestone (questioning → research → requirements → roadmap)
 ```
 
@@ -595,7 +595,7 @@ Example config:
 ```
 /gsd-debug "form submission fails silently"  # Start debug session
 # ... investigation happens, context fills up ...
-/clear
+/new
 /gsd-debug                                    # Resume from where you left off
 ```
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/insert-phase.md

@@ -153,7 +153,7 @@ Project state updated: .planning/STATE.md
 
 `/gsd-plan-phase {decimal_phase}`
 
-<sub>`/clear` first -> fresh context window</sub>
+<sub>`/new` first -> fresh context window</sub>
 
 ---
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/map-codebase.md

@@ -382,7 +382,7 @@ Created .planning/codebase/:
 
 `/gsd-new-project`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/new-milestone.md

@@ -489,7 +489,7 @@ pi-gsd-tools commit "docs: create milestone v[X.Y] roadmap ([N] phases)" --files
 
 `/gsd-discuss-phase [N] ${GSD_WS}` - gather context and clarify approach
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 Also: `/gsd-plan-phase [N] ${GSD_WS}` - skip discussion, plan directly
 ```

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/new-project.md

@@ -1209,7 +1209,7 @@ PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qi "UI hint.*yes" && echo "true"
 
 /gsd-discuss-phase 1 - gather context and clarify approach
 
-<sub>/clear first → fresh context window</sub>
+<sub>/new first → fresh context window</sub>
 
 ---
 
@@ -1231,7 +1231,7 @@ PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qi "UI hint.*yes" && echo "true"
 
 /gsd-discuss-phase 1 - gather context and clarify approach
 
-<sub>/clear first → fresh context window</sub>
+<sub>/new first → fresh context window</sub>
 
 ---
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/plan-milestone-gaps.md

@@ -202,7 +202,7 @@ pi-gsd-tools commit "docs(roadmap): add gap closure phases {N}-{M}" --files .pla
 
 `/gsd-plan-phase {N}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/plan-phase.md

@@ -859,7 +859,7 @@ Verification: {Passed | Passed with override | Skipped}
 
 /gsd-execute-phase {X} ${GSD_WS}
 
-<sub>/clear first → fresh context window</sub>
+<sub>/new first → fresh context window</sub>
 
 ───────────────────────────────────────────────────────────────
 

package/{.gsd/harnesses/pi/get-shit-done → gsd}/workflows/progress.md

@@ -273,7 +273,7 @@ Read its `<objective>` section.
 
 `/gsd-execute-phase {phase} ${GSD_WS}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 ```
@@ -303,7 +303,7 @@ PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" ||
 
 `/gsd-plan-phase {phase-number} ${GSD_WS}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 ```
@@ -319,7 +319,7 @@ PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" ||
 
 `/gsd-discuss-phase {phase}` - gather context and clarify approach
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -342,7 +342,7 @@ PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" ||
 
 `/gsd-discuss-phase {phase} ${GSD_WS}` - gather context and clarify approach
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -368,7 +368,7 @@ UAT.md exists with gaps (diagnosed issues). User needs to plan fixes.
 
 `/gsd-plan-phase {phase} --gaps ${GSD_WS}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -394,7 +394,7 @@ UAT.md exists with `status: partial` - testing session ended before all items re
 
 `/gsd-verify-work {phase} ${GSD_WS}` - resume testing from where you left off
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -450,7 +450,7 @@ NEXT_HAS_UI=$(echo "$NEXT_PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true
 
 `/gsd-discuss-phase {Z+1}` - gather context and clarify approach
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -475,7 +475,7 @@ NEXT_HAS_UI=$(echo "$NEXT_PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true
 
 `/gsd-discuss-phase {Z+1} ${GSD_WS}` - gather context and clarify approach
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -503,7 +503,7 @@ All {N} phases finished!
 
 `/gsd-complete-milestone ${GSD_WS}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -534,7 +534,7 @@ Ready to plan the next milestone.
 
 `/gsd-new-milestone ${GSD_WS}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 ```