Context summarization loses current working directory and project location

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.3.0 (24D60)

### Expected behaviour

When the context window overflows and conversation history is summarized, Amazon Q should preserve and restore the current working directory and project context. After summarization, Q should continue working in the same directory without needing to re-discover the project location.

### Actual behaviour

When context window overflow triggers history summarization, Amazon Q loses track of the current working directory and project location. After summarization, Q attempts to re-discover the project location, which is time-consuming and often unsuccessful, leading to workflow interruption and repeated navigation attempts.

### Steps to reproduce

1. Navigate to a specific project directory (e.g., "cd project-folder")
2. Begin working on a task that requires multiple interactions (e.g., "fix the failing unit tests")
3. Continue the conversation until context window overflow occurs and history gets summarized
4. Observe that Q no longer knows the current working directory
5. Q will attempt to re-find the project location instead of continuing work in the established directory

### Environment

```yaml

```

Non sono indicati file sorgente, test o punti di ingresso. Inizia riproducendo il problema dopo che una conversazione ha superato il limite di contesto, quindi segui il flusso di riepilogo e il modo in cui vengono rappresentati la directory corrente e il percorso del progetto. Il lavoro è completato quando la conversazione riepilogata conserva questo contesto e il lavoro prosegue nella directory originale senza doverlo individuare nuovamente.

Scritto dal modello di indicizzazione a partire dal testo della issue.