{"v":"<p dir=\"auto\">Done in the files (not yet committed or published):<\/p>\n<ul dir=\"auto\">\n<li><strong>Definition<\/strong> (<code>docs\/forms\/forms-3040.json<\/code>): <code>ori_report_health_problems<\/code> is now a Yes\/No (<code>checkbox<\/code>) instead of free text. Its help text lists the two problems as the paper prints them (Fall or Injury, Rash or Skin Breakdown), so they show with the question.<\/li>\n<li><strong>Interview<\/strong> (<code>SOC_AO.json<\/code>): the wording is unchanged (&#34;Which health problems must the attendant report?&#34;). The help now says to answer Yes once the attendant has been told.<\/li>\n<li><strong>Printing<\/strong> (<code>docs\/form-placements\/forms-3040.json<\/code>): a Yes puts an X in item 10-4&#39;s box (it was not placed before) and a \u2713 beside each of the two printed problems. A No prints nothing. Checked on a proof.<\/li>\n<li><strong>Pipeline fix<\/strong> found along the way: the interview import was seeded from the <em>published<\/em> definitions but checked against the new ones, so a field whose type changed was refused on every run. The import now reads the definitions about to be published. Pinned in <code>test-form-v2-pipeline-state<\/code>.<\/li>\n<\/ul>\n<p dir=\"auto\">Defaulting it to Yes is left to #101, which is still open.<\/p>\n<p dir=\"auto\">To ship: <code>form-v2-pipeline.php --packet=SOC_AO --import<\/code> (already rehearsed clean on dev), then review and publish on <code>\/admin\/form-v2-publish<\/code>.<\/p>\n"}