cadence shell uses temp directories instead of CWD

Bug: cadence shell uses temp directories instead of CWD

Reported by: Patrick Marchwiak

Issue

• Running cadence shell (or cadence) uses temporary directories rather than the directory it was started in
• Code written during a session isn't persisted to disk
• Can't resume sessions — no memory of previous work

Expected behavior

• Should behave like claude — write to the current directory and support session resumption

Proposed resolution

• Fix cadence shell to use the current working directory instead of a temp dir
• Ensure session state persists for resumption

Workaround for now

• Use cadence auto for local dev work — it correctly writes files and handles sessions
• Only use cadence / cadence shell for quick questions, not repo work