Closing Issues A graph that turns "close GitHub issue + capture what I learned" into a structural DAG. The synthesis text is validated upfront, the close happens against the GitHub API, and an optional post-close callback runs detached so the close ack is unblocked. Why a synthesis, not a "done" comment Closing an issue produces two artifacts: - The Issue itself — implementation log. The diff and commit history already show what was done. - The closing comment / synthesis — what was learned . Lasts longer than the diff in mental cache. Good closing comments lead with why , not what . Failure…