chore: interview before fixes and keep HANDOFF.md tiny

Require a short user interview before implementing bugs/features, and overwrite or clear HANDOFF.md so it never accumulates session history.

Co-authored-by: Cursor <cursoragent@cursor.com>

.cursor/rules/handoff.mdc

@@ -5,7 +5,13 @@ alwaysApply: true
 
 # Handoff (token control)
 
-Agents **cannot** create a new Cursor chat. When a handoff is needed, write `agents-docs/HANDOFF.md` and tell the user to start a **new chat** with `@agents-docs/HANDOFF.md`.
+Agents **cannot** create a new Cursor chat. When a handoff is needed, **overwrite** `agents-docs/HANDOFF.md` and tell the user to start a **new chat** with `@agents-docs/HANDOFF.md`.
+
+## File size rule (mandatory)
+
+- **Never append** to `HANDOFF.md`. Always replace the entire file.
+- One active handoff only — no history stack in this file.
+- Keep sections short (bullets, paths, not log dumps).
 
 ## When to hand off
 
@@ -13,12 +19,19 @@ Agents **cannot** create a new Cursor chat. When a handoff is needed, write `age
 - Thread is long (many tool rounds, large pastes, repeated failed approaches) and more major work remains
 - Switching to a clearly separate objective
 
-## What to do
+## What to do (new handoff)
 
-1. Overwrite `agents-docs/HANDOFF.md` — set `Status: active`; fill Goal, Completed, Changed files, Decisions, Failed approaches, Current issue, Next steps, Commands.
+1. **Overwrite** `agents-docs/HANDOFF.md` completely — `Status: active`; fill Goal, Completed, Changed files, Decisions, Failed approaches, Current issue, Next steps, Commands (brief).
 2. Stop major new work in this chat after writing the handoff (unless the user says continue here).
-3. Tell the user the one-liner to paste in the new chat.
+3. Tell the user the one-liner for the new chat.
+
+## When the task is finished
+
+After the user-approved work is done (or they abandon the handoff objective):
+
+1. **Clear** `agents-docs/HANDOFF.md`: set `Status: none` and empty all section bodies (restore the short template — do not leave old Completed/Next steps lying around).
+2. Do this in the same turn you claim done, so the next chat does not reload stale handoff context.
 
 ## New-chat bootstrap
 
-If `agents-docs/HANDOFF.md` has `Status: active`, read it first and continue Next steps. Do not reload the whole monorepo or redo Completed work.
+If `Status: active`, read the handoff first and continue Next steps. Do not reload the whole monorepo or redo Completed work. When that work is finished → **clear** the file as above.

.cursor/rules/interview-before-fix.mdc

@@ -0,0 +1,20 @@
+---
+description: Interview the user before implementing fixes; no guessing
+alwaysApply: true
+---
+
+# Interview before implement
+
+Before writing or changing product code for a bug/feature ask:
+
+1. Read the ask (and the one Obsidian bug note if named). Do **not** start a large codebase rewrite yet.
+2. Reply with a **short interview** (bullets only):
+   - What you think the bug/goal is (1–2 sentences)
+   - What’s missing / unclear
+   - Choices (A/B/C) with a **recommended** default
+   - Proposed scope (files/areas you will touch; what you will not)
+   - How you will prove done
+3. **Stop and wait** for the user’s answers. Do not implement until they approve or choose.
+4. Then implement exactly what they chose — no silent extra scope.
+
+Skip the interview only when the user says e.g. “just fix it”, “no interview”, or the handoff already records approved Next steps/decisions and they said continue.