Attach screenshots to Screen 2 + Screen 3 tickets (AC-111..AC-115)

Attach a screenshot per ticket so engineers see the target UI without opening the spec. Tickets are AC-111 (render extension preview), AC-112 (agent-driven edits), AC-113 customer journey loop narration, AC-114 (email previews on demand), AC-115 (Screen 3 activation deep-link). No MCP path for Jira attachments — must use raw Atlassian REST API. Endpoint: POST /rest/api/3/issue/{key}/attachments with header X-Atlassian-Token: no-check. Use curl with the Atlassian API token (likely in load-secrets.sh). Source-asset options to decide first: 1. Render shared/onboarding-agent-v7/2026-04-14-v7-implementation-visual.html at a fixed viewport, screenshot each section (preview / edit / journey / email / activation). Cleanest mapping to spec. 2. Figma export — if Zach has dedicated Figma frames for v7 Screen 2. 3. Live UI screenshots from staging if the surfaces are partially built. Per-ticket asset: - AC-111: thank-you-page with extension preview rendered (mockup shape from spec lines 54-85) - AC-112: same preview with agent edit affordance / before-after render - AC-113: numbered-list loop narration widget (5 steps) - AC-114: email preview placeholder (welcome email + reward notification) - AC-115: deep-link click → Shopify checkout editor screenshot, or instructional graphic for the activation flow Suggested next-session steps: (1) confirm source with Zach, (2) generate 5 images, (3) curl-upload each via REST API, (4) verify attachments appear in each ticket.