Cursor subagentStop has no subagent_id; Entire correlation key goes empty

Summary

Official Cursor hooks docs list subagent_id on subagentStart but not on subagentStop. Entire's parseSubagentStop sets ToolUseID/SubagentID from subagent_id, so real Stop payloads yield an empty correlation key.

Impact

• Start writes pre-task-<id>.json; Stop looks up pre-task-.json → miss.
• DetectFileChanges(nil) treats all untracked files as new (spurious task checkpoints).
• Real pre-task files are never cleaned up (orphans in .entire/tmp/).
• Parallel subagent Stops all collide on the empty key.

Stop does include task and agent_transcript_path, which can be used to recover the id.

Expected

Resolve the Start-side pre-task id on Stop when subagent_id is absent (e.g. match stored task description, or unambiguous single active pre-task).

Refs

• https://cursor.com/docs/hooks.md (subagentStart vs subagentStop input tables)

Read parseSubagentStop and the pre-task handling around .entire/tmp; compare Cursor’s subagentStart and subagentStop payload tables, including task and agent_transcript_path. Done means Stop resolves the Start-side id without subagent_id, avoids empty-key collisions, cleans the matching pre-task file, and prevents spurious DetectFileChanges(nil) results.