Retry session capture in git hooks when data not yet available

[jcleira]

Description

When the git hook fires (e.g., post-commit), the AI session log or checkpoint data may not be fully flushed to disk yet. Implement a retry loop in the hook execution path that waits and re-attempts reading session data for a short window (e.g., up to 2-3 seconds with exponential backoff) before giving up or proceeding without it.

Why

Race conditions between the hook firing and session data being written can cause checkpoints to be silently dropped, leading to incomplete attribution. Retrying ensures session data is captured even when the agent writes it slightly after the commit hook fires.

Source

• Origin: Handle cursor logs being not there in time entireio/cli#713
• Detected from: entireio-cli-pulls

Target Repos

• cli

Acceptance Criteria

• Hook retries reading session data if the expected file is missing or empty at first check
• Retry window is bounded (no infinite loop) and configurable
• If data is eventually found within the retry window, it is captured normally
• If data is never found, hook exits cleanly without error and logs a warning

Context Hints

• cli/internal/hook/
• cli/internal/session/

---

Comment /minion build or add the minion-approved label to begin implementation.

[jcleira]

Auto-approved after review window. Minion execution will begin shortly.

[jcleira]

Minion completed successfully.

PRs created:

• [minion] Retry session capture in git hooks when data not yet available cli#18