change-previewlisted

# Symphony Change Preview Generate a standalone `change-preview.html` that helps Pedro quickly understand what changed. This is a thin orchestration skill for Symphony/the runner. Claude does the creative artifact work through its `frontend-design` skill. ## Boundary - Verification evidence is internal trust work for the agent: tests, screenshots, traces, logs, production checks, and whatever else proves the change works. - The change preview is Pedro-facing comprehension: a clear HTML artifact that explains what changed and what matters. - Claude owns the preview direction through its `frontend-design` skill. The Symphony runner does not choose the sections, media, mockups, or visual style. - Use the repo, PR/diff, available evidence, and app behavior as inputs. - Mockups, diagrams, and simplified UI are allowed when they improve comprehension. Label captured evidence, illustrative material, and caveats honestly. - The HTML must be responsive enough to read comfortably on Pedro's iPhone and MacBook. Use mobile-first CSS, stack dense grids on narrow screens, avoid fixed-width content, prevent horizontal scroll, and keep headings/buttons/labels inside their containers at common iPhone widths. - Do not edit product source, git state, trackers, PRs, or deployment state while generating the preview. - Do not handcraft a fallback HTML preview in Codex. If Claude fails, times out, or does not create the requested HTML, report the failure with the helper logs and stop the previe