BUG agent session creates PR that doesn't get linked properly

### Short summary

PR not linked to session

### Affected version or release

v0.2.5

### Installation context

_No response_

### What happened?

This happens to me on every other PR. Very annoying for obvious reasons.

The MCP function the agent tries to use to open the PR fails with 422, apparently because we work off of forks and can't create branches on the main repo. Then, it usually asks me if it is allowed to use `gh` to open the PR, and I approve. But it's about 50-50 on whether the PR actually gets linked. I've had some sessions try to update whatever local DB state is missing the linkage but that never helped either.

Happy to provide examples for investigation if it helps.

### Steps to reproduce

_No response_

### Expected behavior

PR gets linked

### Additional context

Happy to provide IDs if you tell me how to retrieve them.

Comienza recopilando los ID de sesión y de PR de un ejemplo afectado y, después, compara la ruta MCP 422 con el fallback aprobado de gh al trabajar desde un fork. Se considera terminado cuando el PR creado está vinculado de forma coherente a su sesión del agente, incluso cuando falla la creación de la rama de MCP.

Escrito por el modelo de indexación a partir del texto del issue.