cursor update & path extraction utility (#77)

* feat(cursor): Add project-level hooks support

Cursor now supports project-level hooks at `.cursor/hooks.json` in
addition to user-level hooks at `~/.cursor/hooks.json`.

Changes:
- Update CursorHarness::settings_path() to respect global parameter
- Project init creates .cursor/hooks.json (project-level)
- Global init creates ~/.cursor/hooks.json (user-level)
- Update example scripts to use project-level hooks
- Fix check_appointment_time.py to handle patient_name lookups
- Add tests for cursor init hook locations

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* cleanup repo and examples

* feat(cursor): Add lifecycle events, schema updates, and stop continuation

New lifecycle events (fire-and-forget):
- afterShellExecution: command, output, duration
- afterMCPExecution: tool_name, tool_input, result_json, duration
- afterAgentResponse: text
- afterAgentThought: text, duration_ms

Schema updates:
- Common fields: model, cursor_version, user_email (all optional)
- Response fields: snake_case (user_message, agent_message)
- beforeSubmitPrompt: user_message on block
- stop: loop_count input field

Stop hook agent looping:
- Block decision returns followup_message
- Cursor submits as next user message (max 5 auto-followups)
- Mirrors Claude Code's block+reason pattern

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* clean up example for cursor

* more robust form of protected paths

* command path extraction is proper

* finalize cursor example

* chore: fmt and checks

* introduce shell-words for command string parsing

* test readme idea

* test readme idea

* test readme idea

* test readme idea

* test readme idea

* test readme idea

* test readme idea

* test readme idea

* test readme idea

* test readme idea

* test readme idea

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

Author: backnotprop

.gitignore

@@ -103,3 +103,6 @@ notes.note
 # todo: considering enabling again later
 .claude/commands
 temp-reference/
+
+
+temp-specs

Cargo.lock

@@ -22,14 +22,18 @@ Make AI agents follow the rules.
 - **LLM-as-a-judge** for more dynamic governance.
 - **Trigger alerts** and put _bad_ agents in timeout when they repeatedly violate rules.
 
-Cupcake intercepts agent events and evaluates them against **user-defined rules** written in **[Open Policy Agent (OPA)](https://www.openpolicyagent.org/) [Rego](https://www.openpolicyagent.org/docs/policy-language)** or **Typescript policy programs** that abstract Rego. Agent actions can be blocked, modified, and auto-corrected by providing the agent helpful feedback. Additional benefits include reactive automation for tasks you dont need to rely on the agent to conduct (like linting after a file edit).
+Cupcake intercepts agent events and evaluates them against **user-defined rules** written in **[Open Policy Agent (OPA)](https://www.openpolicyagent.org/) [Rego](https://www.openpolicyagent.org/docs/policy-language).** Agent actions can be blocked, modified, and auto-corrected by providing the agent helpful feedback. Additional benefits include reactive automation for tasks you dont need to rely on the agent to conduct (like linting after a file edit).
 
 ## Updates
 
 **`2025-12-09`**: Official open source release. Roadmap will be produced in Q1 2026.
 
 **`2025-04-04`**: We produce the [feature request](https://github.com/anthropics/claude-code/issues/712) for Claude Code Hooks. Runtime alignment requires integration into the agent harnesses, and we pivot away from filesystem and os-level monitoring of agent behavior (early cupcake PoC).
 
+[Follow on X for a regular updates.](https://x.com/CupcakeSecures)
+
+## Resources
+
 ## Supported Agent Harnesses
 
 Cupcake provides lightweight **native integrations** for multiple AI coding agents:

README.md

@@ -1,16 +1,18 @@
 # Cursor Harness Configuration
 
-## Critical Difference from Claude Code
+## Project-Level and User-Level Hooks
 
-**Cursor hooks MUST be installed globally** at `~/.cursor/hooks.json`. Unlike Claude Code which supports both project-level (`.claude/settings.json`) and global (`~/.claude/settings.json`) configurations, **Cursor does not support project-level hooks**.
+Cursor now supports both project-level and user-level hooks, similar to Claude Code.
 
-Reference: [Cursor Hooks Documentation](https://cursor.com/docs/agent/hooks.md)
+**Hook Priority Order (highest to lowest):** Enterprise → Project → User
 
-## The Configuration Behavior
+Reference: [Cursor Hooks Documentation](https://docs.cursor.com/context/hooks)
+
+## Configuration Behavior
 
 ### `cupcake init --harness cursor` (Project Init)
 
-Creates hooks at `~/.cursor/hooks.json` (global) with **relative policy paths**:
+Creates hooks at `.cursor/hooks.json` (project-level) with **relative policy paths**:
 
 ```json
 {
@@ -36,7 +38,7 @@ Creates hooks at `~/.cursor/hooks.json` (global) with **relative policy paths**:
 
 ### `cupcake init --global --harness cursor` (Global Init)
 
-Creates hooks at `~/.cursor/hooks.json` (global) with **absolute policy paths**:
+Creates hooks at `~/.cursor/hooks.json` (user-level) with **absolute policy paths**:
 
 ```json
 {
@@ -59,20 +61,23 @@ Creates hooks at `~/.cursor/hooks.json` (global) with **absolute policy paths**:
 #### `CursorHarness::settings_path()`
 
 ```rust
-fn settings_path(&self, _global: bool) -> PathBuf {
-    // Cursor hooks MUST always be in ~/.cursor/hooks.json (global)
-    // Cursor does not support project-level hooks like Claude Code does.
-    // The hooks are always read from the user's home directory.
-    // Reference: https://cursor.com/docs/agent/hooks.md
-    dirs::home_dir()
-        .unwrap_or_else(|| PathBuf::from("~"))
-        .join(".cursor")
-        .join("hooks.json")
+fn settings_path(&self, global: bool) -> PathBuf {
+    // Cursor now supports both project-level and user-level hooks
+    // Priority order: Enterprise → Project → User
+    // Reference: https://docs.cursor.com/context/hooks
+    if global {
+        // User-level hooks: ~/.cursor/hooks.json
+        dirs::home_dir()
+            .unwrap_or_else(|| PathBuf::from("~"))
+            .join(".cursor")
+            .join("hooks.json")
+    } else {
+        // Project-level hooks: .cursor/hooks.json
+        Path::new(".cursor").join("hooks.json")
+    }
 }
 ```
 
-**Key point**: The `global` parameter is ignored (prefixed with `_`). Cursor hooks are **always** written to the global location.
-
 #### `CursorHarness::generate_hooks()`
 
 ```rust
@@ -99,18 +104,6 @@ fn generate_hooks(&self, policy_dir: &Path, global: bool) -> Result<Value> {
 }
 ```
 
-**Key point**: The `global` parameter determines whether to use absolute or relative paths in the hook commands, NOT the location of the hooks file.
-
-## Bug History
-
-### Original Bug (Fixed 2025-09-03)
-
-**Problem**: `CursorHarness::settings_path()` returned `.cursor/hooks.json` (project-level) when `global=false`, but Cursor ignores project-level hook files.
-
-**Result**: Running `cupcake init --harness cursor` created `.cursor/hooks.json` in the project directory, which Cursor never read.
-
-**Fix**: Changed `settings_path()` to always return `~/.cursor/hooks.json` regardless of the `global` parameter.
-
 ## Testing
 
 ### Verify Project Init
@@ -119,8 +112,8 @@ fn generate_hooks(&self, policy_dir: &Path, global: bool) -> Result<Value> {
 cd /tmp/test-project
 cupcake init --harness cursor
 
-# Verify hooks created at global location
-cat ~/.cursor/hooks.json
+# Verify hooks created at project location
+cat .cursor/hooks.json
 
 # Should show relative path: --policy-dir .cupcake
 ```
@@ -130,27 +123,26 @@ cat ~/.cursor/hooks.json
 ```bash
 cupcake init --global --harness cursor
 
-# Verify hooks created at global location
+# Verify hooks created at user location
 cat ~/.cursor/hooks.json
 
 # Should show absolute path: --policy-dir /Users/alice/.config/cupcake
 ```
 
 ## Comparison with Claude Code
 
-| Aspect                    | Claude Code                    | Cursor                    |
-| ------------------------- | ------------------------------ | ------------------------- |
-| **Project hooks**         | `.claude/settings.json` ✅     | Not supported ❌          |
-| **Global hooks**          | `~/.claude/settings.json` ✅   | `~/.cursor/hooks.json` ✅ |
-| **Hook location choice**  | Respects `--global` flag       | Always global             |
-| **Policy path (project)** | `$CLAUDE_PROJECT_DIR/.cupcake` | `.cupcake` (relative)     |
-| **Policy path (global)**  | Absolute path                  | Absolute path             |
-| **Process cwd**           | Project root (via env var)     | Workspace root (direct)   |
+| Aspect                    | Claude Code                    | Cursor                       |
+| ------------------------- | ------------------------------ | ---------------------------- |
+| **Project hooks**         | `.claude/settings.json` ✅     | `.cursor/hooks.json` ✅      |
+| **User hooks**            | `~/.claude/settings.json` ✅   | `~/.cursor/hooks.json` ✅    |
+| **Hook location choice**  | Respects `--global` flag       | Respects `--global` flag     |
+| **Policy path (project)** | `$CLAUDE_PROJECT_DIR/.cupcake` | `.cupcake` (relative)        |
+| **Policy path (global)**  | Absolute path                  | Absolute path                |
+| **Process cwd**           | Project root (via env var)     | Workspace root (direct)      |
 
 ## Key Takeaways
 
-1. **Cursor hooks are ALWAYS global** - stored at `~/.cursor/hooks.json`
-2. **Project init uses relative paths** - `.cupcake` resolves via workspace cwd
-3. **Global init uses absolute paths** - points to `~/.config/cupcake/`
-4. **The `global` parameter affects policy paths, not hook file location** (for Cursor)
-5. **Cursor spawns hooks with cwd=workspace root** - enabling relative path resolution
+1. **Cursor supports both project and user-level hooks** - stored at `.cursor/hooks.json` and `~/.cursor/hooks.json`
+2. **Project init creates project-level hooks** - `.cursor/hooks.json` with relative policy paths
+3. **Global init creates user-level hooks** - `~/.cursor/hooks.json` with absolute policy paths
+4. **Cursor spawns hooks with cwd=workspace root** - enabling relative path resolution

cupcake-cli/src/CLAUDE.md

@@ -116,15 +116,20 @@ impl HarnessConfig for CursorHarness {
         "Cursor"
     }
 
-    fn settings_path(&self, _global: bool) -> PathBuf {
-        // Cursor hooks MUST always be in ~/.cursor/hooks.json (global)
-        // Cursor does not support project-level hooks like Claude Code does.
-        // The hooks are always read from the user's home directory.
-        // Reference: https://cursor.com/docs/agent/hooks.md
-        dirs::home_dir()
-            .unwrap_or_else(|| PathBuf::from("~"))
-            .join(".cursor")
-            .join("hooks.json")
+    fn settings_path(&self, global: bool) -> PathBuf {
+        // Cursor now supports both project-level and user-level hooks
+        // Priority order: Enterprise → Project → User
+        // Reference: https://docs.cursor.com/context/hooks
+        if global {
+            // User-level hooks: ~/.cursor/hooks.json
+            dirs::home_dir()
+                .unwrap_or_else(|| PathBuf::from("~"))
+                .join(".cursor")
+                .join("hooks.json")
+        } else {
+            // Project-level hooks: .cursor/hooks.json
+            Path::new(".cursor").join("hooks.json")
+        }
     }
 
     fn generate_hooks(&self, policy_dir: &Path, global: bool) -> Result<Value> {