Propagate originating session ID to automatic devlogs

Summary

Updated the automatic devlog extension to include the originating Pi session ID in its transcript handoff and worker prompt, and updated the devlog skill to submit supplied session IDs as provenance in the CLI JSON. A mocked worker handoff test confirmed the original ID appeared in both locations and exited successfully.

Decisions

• Use the originating TUI session ID rather than the detached worker’s session ID
• Treat session_id as caller-supplied provenance distinct from the CLI-generated entry ID

Learnings

• Older devlog CLI versions may ignore the session_id field until persistence support is added