chore: commit after each task and run graphify update at session end

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

.cursor/hooks/README.md

@@ -4,7 +4,7 @@ Two hooks, both small, both readable in a minute, both safe to delete. They exis
 
 | Hook | Event | What it does |
 | --- | --- | --- |
-| `session-context.mjs` | `sessionStart` | Injects the session's starting facts: whether the model lanes are bound (and whether the picker drifted from the recorded lead), the handoff's next action, and any of the four capped context files currently over its cap. |
+| `session-context.mjs` | `sessionStart` | Injects the session's starting facts: whether the model lanes are bound (and whether the picker drifted from the recorded lead), the handoff's next action, any of the four capped context files currently over its cap, and the standing workflow (commit after each task; `graphify update .` at session end). |
 | `guard-destructive.mjs` | `beforeShellExecution` | Returns `ask` — never `deny` — for force pushes, `rm -rf`, migrations, deploys, infra changes, pipe-to-shell, and friends, with the reason named and the gate quoted back to the agent. Routine `git push` is deliberately not on the list. |
 
 ## Why these two

.cursor/hooks/session-context.mjs

@@ -132,6 +132,10 @@ function main(payload) {
     notes.push(`Context caps EXCEEDED: ${over.join(" · ")}. Run /memory-sync before adding anything.`);
   }
 
+  notes.push(
+    "Workflow: commit after each landed task (no secrets). Session end: graphify update .",
+  );
+
   return notes.length
     ? { additional_context: `Project state (from .cursor/hooks/session-context.mjs):\n- ${notes.join("\n- ")}` }
     : {};