attach-to-ticket

# Attach to ticket Save assets — pasted images, local files, URLs — into a ticket's planning directory and reference them from its ticket file, so a fresh session picks them up. **Local only** — never query or modify the tracker (no API calls, no re-fetch, no comments or edits); downloading an asset URL the user supplies or a not-downloaded entry names is fine, tracker-hosted or not. Edit nothing in the documents beyond the entries below and the REQUIREMENTS line of step 6. ## Your task 1. **Collect the assets.** The images pasted with the invocation, plus paths and URLs in its text; images pasted earlier only when the user points at them. Nothing pasted or pointed at → ask which, listing the images seen in the session. Done when every supplied asset is collected or dropped by the user. 2. **Resolve the ticket.** Named in the argument or already in the session (fetched, read, discussed) → proceed. Otherwise guess (branch name, latest planning directory) and confirm before writing; nothing to guess from → ask. No planning directory for it yet → stop and point to fetch-ticket; don't create one. 3. **Pick the document** — unless the user names one: the ticket file, latest `-vN` (file or directory) when re-fetched, the `<id>-` one in a shared directory; the REQUIREMENTS file when no ticket file exists. Several candidates left → ask. 4. **Map assets to entries.** Descriptions map to assets in paste order; "image 2 is …" overrides. If the document has ...