fix(mcp,cli): session directory empty when not specified via --directory

[alexandervazquez98]

Pre-flight Checks

• Searched existing issues — issue engram sync --cloud fails on legacy mutation payloads (existing users skip cloud-upgrade preflight) #230 covers legacy payloads but not this specific directory population gap
• I understand this issue needs status:approved before any PR

Bug Description

When or MCP is called without the flag, sessions are created with (empty string) instead of falling back to the current working directory.

This affects 3 locations in the codebase:

Location	Function	Directory Source
cmd/engram/main.go:876	cmdSave	Hardcoded ""
internal/mcp/mcp.go:792	handleSave	Hardcoded "" (ignores detRes.Path)
internal/mcp/mcp.go:1228	handleSessionStart	Request arg only (ignores detRes.Path)

The infrastructure exists to detect the correct directory via which returns , but this value is never used for session creation.

Steps to Reproduce

1. Run without
2. Check — it's empty ("")
3. Run — fails with "session payload directory is required"

Expected Behavior

When is not specified, session creation should fall back to or use from .

Actual Behavior

Session created with — causes sync failures downstream.

Environment

• Engram Version: 1.13.1
• Agent: OpenCode / any MCP agent

Proposed Fix

Add fallback in all 3 locations:

Related Issues

• engram sync --cloud fails on legacy mutation payloads (existing users skip cloud-upgrade preflight) #230 (legacy payload repair — related root cause)
• This bug causes NEW sessions to also have empty directory, compounding the issue

Tags

• bug
• cloud-sync
• session

[Alan-TheGentleman]

Fixed in v1.14.6. Manual CLI saves now create the manual-save session with the current working directory instead of an empty directory, matching the MCP cwd fix shipped earlier. Release: https://github.com/Gentleman-Programming/engram/releases/tag/v1.14.6