{"v":"<p dir=\"auto\"><strong>Background.<\/strong> Forms V2 is the new paperwork system for client visits. Each visit type (e.g. Start of Care) is a &#34;release&#34;: the forms, where each answer prints, and the interview questions with their order and branching. From 29 Sep 2026 most of that is <strong>built by AI from the command line<\/strong>, and <strong>people check it<\/strong>. Item <strong>P2<\/strong> in <code>docs\/ActionItems.md<\/code> (\u00a76, tooling).<\/p>\n<h2 id=\"user-content-the-problem\" dir=\"auto\">The problem<\/h2>\n<p dir=\"auto\">A reviewer can&#39;t re-read 400+ questions every time something changes. They need to see <strong>what changed<\/strong>.<\/p>\n<h2 id=\"user-content-what-to-do\" dir=\"auto\">What to do<\/h2>\n<ul dir=\"auto\">\n<li>In the Form Explorer (<code>\/admin\/form-explorer<\/code>), show the <strong>draft and the published version side by side<\/strong>.<\/li>\n<li>Show the <strong>difference between two releases<\/strong>: questions added, removed or reworded, changed branching, changed placements, changed prefills. <code>form_v2_release_compare()<\/code> already works this out. It needs a screen.<\/li>\n<li>Ideally, link each change to the issue that asked for it (these action items).<\/li>\n<\/ul>\n<h2 id=\"user-content-related\" dir=\"auto\">Related<\/h2>\n<p dir=\"auto\">P1 (Form Explorer, done), P3 (#127, publishing pipeline), P4 (#128, human sign-off before production).<\/p>\n"}