{"v":"<p dir=\"auto\"><strong>Done (5 Oct 2026).<\/strong> The service plan&#39;s tasks are now the tasks authorized in VESTA, and they can&#39;t be changed at the visit.<\/p>\n<p dir=\"auto\"><strong>What the supervisor sees<\/strong><\/p>\n<ul dir=\"auto\">\n<li>The service plan step shows &#34;The tasks the client is authorized for&#34;, read-only, in place of the tick list. It says that a wrong task is fixed by asking the office to correct the authorization in VESTA, the same route as the hours (#92).<\/li>\n<li>If VESTA lists no tasks for the client, the step says so instead of showing an empty list.<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>What prints<\/strong><\/p>\n<ul dir=\"auto\">\n<li>The service plan, the coordination of care form and the task guide (#102) all print from that one list.<\/li>\n<li><strong>&#34;Other tasks&#34;<\/strong> is no longer asked. A task VESTA doesn&#39;t list isn&#39;t authorized, so the &#34;Other&#34; task lines on the service plan and the coordination of care form print blank.<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>Checked on dev<\/strong> (production data, demo client): her 8 VESTA tasks show read-only, and the same 8 print on all three forms.<\/p>\n<p dir=\"auto\"><strong>Technical:<\/strong> <code>auth.service_tasks<\/code> joins <code>FORM_V2_FROZEN_KEYS<\/code> (data dictionary 3 \u2192 4). Its shared entry is now source context and also prints on the task guide. A new interview key, <code>shows<\/code>, lets a step display a fixed value read-only. <code>shared.plan.tasks_other<\/code> moves to <code>not_asked<\/code>.<\/p>\n<p dir=\"auto\"><strong>To go live:<\/strong> run <code>form-v2-pipeline.php --packet=SOC_AO --import --replace<\/code>, review and publish on <code>\/admin\/form-v2-publish<\/code>, then choose the new release on <code>\/admin\/form-v2-releases<\/code>. Visits already started keep their current paperwork.<\/p>\n<p dir=\"auto\">Not changed: the 3040&#39;s orientation task grid (A4) still asks about every task.<\/p>\n"}