[bketelsen]

Extensions coordinating work across repositories currently have to start every linked session in the source session's folder. Add optional cwd to both host.linkedSessions.start() and the conversation-bound human API so a coordinator in project A can start a specialist in project B. Omitting it preserves the existing behavior.

The destination uses the normal folder-picker validation and becomes the child's working directory before its first request. Its project instructions and shell tools use that folder; the source stays in place. Existing access, model, spend, replay, and admission checks remain in effect. The API mechanism lives in core; repository ownership and team workflow stay in extensions, with no new core settings or stored document kinds.

Validation:

• npm run format, npm run check, and npm run lint
• npm test: 350 passing tests
• Regression coverage for the first request's destination AGENTS.md, an actual pwd tool call, unchanged source folder, inherited default, invalid folders, replay, and human-bound starts
• Confirmed the project-context/tool regression test fails on unpatched upstream main

[bketelsen]

thanks for the merge and the amazing tool. I'm loving pi-pocket.