What's wrong with this entry?
The WorktreeCreate hook event now supports hook-specific output providing the absolute path to the created worktree directory.
- JavaScript hooks return
{ hookEventName: "WorktreeCreate", worktreePath: "<path>" } - Command hooks print the path on stdout instead
- Enables custom worktree workflows via hooks
WorktreeCreate hook output (search for "Hook-specific output for the WorktreeCreate event")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.