assimilation/harness/cursor overview

Orchestrate babysitter SDK integration into Cursor IDE/CLI. Cursor is a VS Code fork with built-in AI capabilities. It has: - A CLI (`cursor`) with headless agent mode (`cursor agent --print -p "prompt"`) - Hooks system (1.7+): beforeSubmitPrompt, beforeShellExecution, beforeMCPExecution, afterFileEdit, afterAgentResponse, stop — configured via .cursor/hooks.json - NOTE: As of writing, hooks only fire in IDE mode, NOT in headless CLI mode. The sessionStart hook fires in headless, but afterAgentResponse and stop do not. This is a known limitation that may change — the research phase must verify current state. - Config: .cursor/ directory, .cursorrules for rules - MCP server support for tool access - VS Code extension model (not a standalone plugin system) - Already has minimal KNOWN_HARNESSES entry (HeadlessPrompt only, no callerEnvVars) Key challenge: hooks don't work in headless CLI mode, so the continuation mechanism is limited. The process must research the current state of Cursor hooks in CLI mode and determine whether stop-hook, in-turn, or a hybrid approach is appropriate.