Log git command failures during /close-issue to ensure traceable finalization and surface silent errors

🗂️ Body

Summary

Some git operations in the /close-issue MCP workflow (e.g., git add on deleted files) can fail silently and trigger fallback behavior. These failures often go unnoticed but point to deeper file state or workflow inconsistencies.

This issue proposes wrapping all git commands in the workflow with error logging to produce a structured trace of exit codes, making silent failures visible during retros or follow-up automation.

---

Goals

Ensure all git command failures (non-zero exit codes) are logged during the /close-issue process.

Enable visibility into fallback behavior and unexpected edge cases.

Retain trace logs for later review or future automation triggers.

---

Output

For every git command run during /close-issue, log:

Timestamp

Exit code

Command

Context (e.g., “finalizing issue #123”)

Trace format: JSONL
Output file: /logs/git_confessions/YYYY-MM-DD.jsonl

---

Principle

> “Silent failures delay feedback. Logged failures invite iteration.”

Start by locating the /close-issue MCP workflow and every git command entry point, including the git add case mentioned in the issue. Verify the existing fallback paths and define completion against the requested JSONL fields, dated output path, and coverage of non-zero git exits.

Written by the indexing model from the issue text.