@alfadocs/ui-kit-debug 1.30.0 → 1.32.0

package/dist/agent-catalog.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "packageVersion": "1.30.0",
+  "packageVersion": "1.32.0",
   "components": [
     {
       "kind": "component",
@@ -1592,7 +1592,7 @@
         },
         "item": {
           "attr": "data-event-id",
-          "description": "Emitted on every rendered FullCalendar event by the kit event renderer. Used by focusEvent. Cards also carry data-kind=\"task\"|\"draft\"|\"appointment\" and data-status for classification."
+          "description": "Emitted on every rendered FullCalendar event by the kit event renderer. Used by focusEvent. Cards also carry data-kind=\"task\"|\"draft\"|\"pending-details\"|\"appointment\" and data-status for classification."
         }
       }
     },
@@ -7673,7 +7673,7 @@
             ]
           },
           "idempotent": false,
-          "description": "Toggle the pinned state of the note with the given id.",
+          "description": "Toggle the pinned state of the note with the given id. Refused for a deleted note or one whose actions.pin is false.",
           "descriptionKey": "ui.agent.notesPanel.actions.togglePin"
         },
         {
@@ -11248,7 +11248,20 @@
           "name": "set_value",
           "safety": "write",
           "argsType": "{ value: string }",
-          "description": "Select the radio with the given value.",
+          "argsSchema": {
+            "type": "object",
+            "properties": {
+              "value": {
+                "type": "string",
+                "description": "Value of the radio to select (its data-option-id)."
+              }
+            },
+            "required": [
+              "value"
+            ]
+          },
+          "idempotent": true,
+          "description": "Select the radio with the given value. A value that matches no enabled radio is ignored.",
           "descriptionKey": "ui.agent.radioGroup.actions.setValue"
         }
       ],
@@ -11914,7 +11927,7 @@
               "note": "Select the \"it\" option."
             }
           ],
-          "description": "Select the option with the given value.",
+          "description": "Select the option with the given value. A value that is not among the options, or belongs to a disabled option, is ignored and the selection stays as it was.",
           "descriptionKey": "ui.agent.select.actions.setValue"
         },
         {
@@ -16876,6 +16889,14 @@
           "component": "radio-group",
           "as": "deleteScope"
         },
+        {
+          "component": "radio-group",
+          "as": "seriesScope"
+        },
+        {
+          "component": "button",
+          "as": "seriesScopeChange"
+        },
         {
           "component": "dropdown-menu",
           "as": "signatureMenu"
@@ -17026,7 +17047,7 @@
         {
           "name": "dock_tool",
           "safety": "read",
-          "description": "Open one of the rail's tools — Appointments, the appointment editor / details panel, the waiting list, the online bookings or the free-slot finder — or read which one is docked. A host declares which of the five it can back with real data, so read the strip rather than assuming all five: a tool the host withheld is absent, and anything routed at it docks Appointments instead. Closing returns to the Appointments panel rather than collapsing the rail, so no path leaves an empty dock. Docking moves no focus; a polite live region announces the panel that arrived.",
+          "description": "Open a workspace rail tool: Appointments, appointment editor / details, waiting list, patient notes, online bookings or free-slot finder. Read the actual strip: hosts may withhold tools, and patient-notes is registered only with patient context. Notes uses the host's note permissions, independently of appointment-edit rights. Clearing its patient context returns to the previous available tool and focuses its rail button. Opening notes from a panel may address a note id and moves focus into Notes. Closing other tools returns to Appointments.",
           "descriptionKey": "ui.agent.calendar.workflows.dockTool",
           "uiActions": [
             "control-room-rail.open",
@@ -17057,6 +17078,21 @@
             "appointment.list"
           ]
         },
+        {
+          "name": "read_appointment_details",
+          "safety": "phi",
+          "description": "Read one appointment in the docked details panel. With the host's details read, any card click, including a patient-less block and a chip whose names are still loading, focuses the appointment and docks a read-only panel: appointment, booking, money, contact, treatments, signing and series sections, the patient's latest three notes and a History sub-view. See more or a note opens the separate Notes rail tool when the host offers it. While the read is loading, failed or refused the panel shows that status instead. Edit, withheld from a read-only viewer, opens the editor. Without the host's read a pending chip stays inert and the editor form is the details. Reads patient-identifiable data.",
+          "descriptionKey": "ui.agent.calendar.workflows.readAppointmentDetails",
+          "uiActions": [
+            "calendar.focus_event"
+          ],
+          "stateReads": [
+            "control-room-rail.activeToolId"
+          ],
+          "apiActions": [
+            "appointment.read"
+          ]
+        },
         {
           "name": "create_appointment",
           "safety": "phi",
@@ -17086,13 +17122,14 @@
             "control-room-rail.activeToolId"
           ],
           "apiActions": [
+            "patient.search",
             "appointment.create"
           ]
         },
         {
           "name": "edit_appointment",
           "safety": "phi",
-          "description": "Amend an existing appointment. Clicking its card docks the SAME panel in details mode — the identity strip, the prefilled form, the read-only extras and the History sub-view — so there is one editing paradigm and no separate Edit jump. Change any field and save; for a member of a repeating series the save asks how far it reaches. On save the rail returns to the Appointments panel and a toast names the day, carrying a \"Go to\" action when that day is off screen, on a hidden weekend or filtered out. Writes patient-identifiable data.",
+          "description": "Amend an existing appointment in the docked editor. With the host's details read the editor opens from Edit on the details panel and Cancel or Save returns there; without it the details panel is the form. A remote host first loads canonical data; loading, failure and whole-appointment refusal expose no editable form. When that data carries a series, the editor first asks the scope: this occurrence, this and following, or the whole series. Honour the returned patient, care, description and recurrence capabilities. A refused recurring scope cannot be treated as an ordinary edit. Save waits for host acceptance before closing or announcing success; rejection preserves the entered draft for correction or retry. Writes patient-identifiable data.",
           "descriptionKey": "ui.agent.calendar.workflows.editAppointment",
           "uiActions": [
             "calendar.focus_event",
@@ -17114,6 +17151,8 @@
             "calendar.currentDate"
           ],
           "apiActions": [
+            "appointment.read",
+            "patient.search",
             "appointment.update",
             "appointmentSeries.applyScope"
           ]
@@ -17137,7 +17176,7 @@
         {
           "name": "move_appointment",
           "safety": "phi",
-          "description": "Reschedule an appointment either by dragging its card to a new slot or by arming \"Move…\" in the details panel and then clicking the target slot — the panel stays docked and a banner tinted with the appointment's own colour names what is being placed. Either route ends in the confirmation dialog, which offers the SMS and e-mail notify channels (kept even when the appointment recurs, where the platform drops them) and, for a series member, the recurring scope. Cancelling reverts the card and commits nothing. Writes patient-identifiable data.",
+          "description": "Reschedule an appointment either by dragging its card to a new slot or by arming \"Move…\" in the details panel and then clicking the target slot — the panel stays docked and a banner tinted with the appointment's own colour names what is being placed. Either route ends in the confirmation dialog, which offers the SMS and e-mail notify channels and, for a series member, the recurring scope. A host recurring parent always confirms, asks the scope and hides the notify channels, as the platform does. Cancelling reverts the card and commits nothing. Writes patient-identifiable data.",
           "descriptionKey": "ui.agent.calendar.workflows.moveAppointment",
           "uiActions": [
             "calendar.focus_event",
@@ -17219,7 +17258,7 @@
         {
           "name": "manage_patient_notes",
           "safety": "phi",
-          "description": "Read and write the patient's notes from the Notes sub-view beside History: add a note through the composer, pin one, edit one in a dialog or delete one behind an alert dialog. Every write goes to the host, which stamps the note's id, time and author — the kit attributes nothing to a clinical note. With no host seam, or without the edit permission, the sub-view is a read-only timeline. The rows carry ids and pin / flag / clinical markers only; the body and the author are never exposed as state. Writes patient-identifiable clinical data.",
+          "description": "Read and write the patient's notes from the conditional Notes rail tool: add a note through the composer, pin one, edit one in a dialog or delete one behind an alert dialog. Every write goes to the host, which stamps the note's id, time and author. The kit attributes nothing to a clinical note. An HTML note edits in a rich text editor and saves as HTML; a clinical or deleted note offers no edit. With no host seam, or when the host's seam is not writable, the tool is a read-only timeline. Explicit note permissions take precedence over appointment-edit permission. Details and the editor have no Notes sub-view. The rows carry ids and pin / flag / clinical markers only; the body and author are never exposed as state. Writes patient-identifiable clinical data.",
           "descriptionKey": "ui.agent.calendar.workflows.managePatientNotes",
           "uiActions": [
             "notes-panel.add_note",
@@ -17227,7 +17266,8 @@
             "dialog.open",
             "dialog.close",
             "dialog.dismiss",
-            "text-area.set_value"
+            "text-area.set_value",
+            "rich-text-editor.set_content"
           ],
           "stateReads": [
             "notes-panel.notes",
@@ -17273,6 +17313,20 @@
             "signature.request"
           ]
         },
+        {
+          "name": "create_document",
+          "safety": "phi",
+          "description": "Open the appointment details create menu through data-action=\"open-create-document\" and select an offered data-action=\"create-document-<kind>\" item: bill, folder, template, empty, identification or webcam. The host supplies permitted kinds and owns navigation, confirmation and persistence. Appointment read-only mode does not withhold document rights. A selection starts the host workflow; it does not prove that a document or bill was created. May write patient-identifiable data.",
+          "descriptionKey": "ui.agent.calendar.workflows.createDocument",
+          "uiActions": [
+            "dropdown-menu.open",
+            "dropdown-menu.close"
+          ],
+          "stateReads": [
+            "dropdown-menu.isOpen"
+          ],
+          "apiActions": []
+        },
         {
           "name": "message_patient_whatsapp",
           "safety": "phi",
@@ -17348,7 +17402,7 @@
         {
           "name": "find_free_slot",
           "safety": "read",
-          "description": "Search the practice for bookable time in the finder panel. Operator and chair scope are grouped checklists behind a popover per axis — a select-all row first, operators sectioned under their groups, nothing ticked searching every eligible resource — beside the care, the duration, the date range and, for a care that needs one, a medical-device select. The results list groups the slots under a day heading; a click steers the grid to that day and docks the editor prefilled with the date, time, duration, chair, operator and any seeded patient or care. The 185-day range warning is advisory (the search still runs), \"Show more slots\" pushes the To date out by 30 days and re-searches, and an alert names which business hours are missing when the practice or its operators hold none (it links to the scheduler only where the host supplies that navigation, which this workspace does not). Read-only until a slot is booked.",
+          "description": "Search the practice for bookable time in the finder panel. Operator and chair scope are grouped checklists behind a popover per axis — a select-all row first, operators sectioned under their groups, nothing ticked searching every eligible resource — beside the care, the duration, the date range and, for a care that needs one, a medical-device select. The results list groups the slots under a day heading; when the viewer may write appointments, a click steers the grid to that day and docks the editor prefilled with the date, time, duration, chair, operator and any seeded patient or care; read-only viewers see the list and projection only, under a lock note, with no Book. The 185-day range warning is advisory (the search still runs), \"Show more slots\" pushes the To date out by 30 days and re-searches, and an alert names which business hours are missing when the practice or its operators hold none (it links to the scheduler only where the host supplies that navigation, which this workspace does not). Projected bands open a modal list of original options by click, Enter or Space; only an explicit Book action uses the finder booking path. Read-only viewers can scroll those options without Book. Dismissal restores focus to the band.",
           "descriptionKey": "ui.agent.calendar.workflows.findFreeSlot",
           "uiActions": [
             "collapsible.toggle",
@@ -17376,7 +17430,7 @@
         {
           "name": "triage_online_booking",
           "safety": "phi",
-          "description": "Work the online-bookings panel — the platform's bookings page hosted in the rail, badged with the bookings of the last thirty days still missing a patient or an operator. A row can be shown on the grid, which selects it and docks its details, or completed, which docks the editor prefilled with what the person typed on the booking site so the missing patient or operator can be filled in and saved. Completing writes patient-identifiable data.",
+          "description": "Review the online-bookings queue independently of the visible dates. The host owns membership and loading/error state. Show a row on the grid; completion is available only when the host enables it and the user can edit. Review-only rows remain in the queue on selection and cannot be dragged, resized or edited. Unknown last-seen data never marks a booking New. Completing writes patient-identifiable data.",
           "descriptionKey": "ui.agent.calendar.workflows.triageOnlineBooking",
           "uiActions": [
             "calendar.focus_event",
@@ -19370,6 +19424,14 @@
           "component": "document-preview",
           "as": "documentPreviewTool"
         },
+        {
+          "component": "button",
+          "as": "documentsToSign"
+        },
+        {
+          "component": "dialog",
+          "as": "signatureRequestModal"
+        },
         {
           "component": "chat-container",
           "as": "messageThread"
@@ -19698,14 +19760,33 @@
         {
           "name": "request_document_signature",
           "safety": "phi",
-          "description": "Send the selected document out for the patient's signature. The banner's unsigned-documents count is the same signal, so read it to see what is already pending before requesting another. Puts a patient-identifiable document into an outbound signing envelope.",
+          "description": "Send one document out for the patient's signature. A pending document's Request signature row action opens the signature request modal with that document's signed versions table above the request form; for Via QR, the QR step follows in the same dialog (the full contract is signature-request.agent.ts). The banner's unsigned-documents count is the same signal, so read it to see what is already pending before requesting another. Puts a patient-identifiable document into an outbound signing envelope.",
           "descriptionKey": "ui.agent.patientFolder.workflows.requestDocumentSignature",
           "uiActions": [
-            "file-manager.select_items"
+            "file-manager.select_items",
+            "dialog.close"
           ],
           "stateReads": [
             "file-manager.selection",
-            "patient-summary-card.summary"
+            "patient-summary-card.summary",
+            "dialog.isOpen"
+          ],
+          "apiActions": [
+            "signatureRequest.create"
+          ]
+        },
+        {
+          "name": "request_required_signatures",
+          "safety": "phi",
+          "description": "Ask the patient to sign every outstanding item in one request. The banner's Documents to sign button (a user-driven button with no adapter action) opens the signature request modal in required documents mode: the unsigned documents and anamnesis interviews, each with its own operator picker, one signer roster for the batch, and a link sent outcome after submit. A signer the host marks as under 18 shows a warning that never blocks the request. Read the banner's counts first to know what will be listed.",
+          "descriptionKey": "ui.agent.patientFolder.workflows.requestRequiredSignatures",
+          "uiActions": [
+            "dialog.close",
+            "dialog.dismiss"
+          ],
+          "stateReads": [
+            "patient-summary-card.summary",
+            "dialog.isOpen"
           ],
           "apiActions": [
             "signatureRequest.create"
@@ -21376,25 +21457,70 @@
           "component": "dialog",
           "as": "requestModal"
         },
+        {
+          "component": "skeleton",
+          "as": "signaturesLoading"
+        },
+        {
+          "component": "signature-status-chip",
+          "as": "signatureStatus",
+          "entity": "signature"
+        },
+        {
+          "component": "tooltip",
+          "as": "signerBreakdown",
+          "entity": "signature"
+        },
+        {
+          "component": "icon-button",
+          "as": "viewSignature",
+          "entity": "signature"
+        },
+        {
+          "component": "icon-button",
+          "as": "downloadSignature",
+          "entity": "signature"
+        },
+        {
+          "component": "dropdown-menu",
+          "as": "downloadMenu",
+          "entity": "signature"
+        },
+        {
+          "component": "icon-button",
+          "as": "shareSignature",
+          "entity": "signature"
+        },
+        {
+          "component": "dropdown-menu",
+          "as": "shareMenu",
+          "entity": "signature"
+        },
+        {
+          "component": "icon-button",
+          "as": "deleteSignature",
+          "entity": "signature"
+        },
+        {
+          "component": "dialog",
+          "as": "deleteConfirmation",
+          "entity": "signature"
+        },
         {
           "component": "select",
           "as": "operatorSigner"
         },
         {
-          "component": "checkbox",
+          "component": "select",
           "as": "operatorChannel"
         },
-        {
-          "component": "info-tip",
-          "as": "operatorChannelHint"
-        },
         {
           "component": "select",
           "as": "signerPerson",
           "entity": "signer"
         },
         {
-          "component": "checkbox",
+          "component": "select",
           "as": "signerChannel",
           "entity": "signer"
         },
@@ -21403,11 +21529,28 @@
           "as": "otpWaiver",
           "entity": "signer"
         },
+        {
+          "component": "select",
+          "as": "batchChannel"
+        },
+        {
+          "component": "switch",
+          "as": "batchOtpWaiver"
+        },
         {
           "component": "alert",
           "as": "otpWarning",
           "entity": "signer"
         },
+        {
+          "component": "alert",
+          "as": "batchOtpWarning"
+        },
+        {
+          "component": "alert",
+          "as": "minorSignerWarning",
+          "entity": "signer"
+        },
         {
           "component": "alert",
           "as": "submissionError"
@@ -21420,6 +21563,10 @@
           "component": "button",
           "as": "addSigner"
         },
+        {
+          "component": "button",
+          "as": "addSignee"
+        },
         {
           "component": "icon-button",
           "as": "removeSigner",
@@ -21432,13 +21579,149 @@
         {
           "component": "button",
           "as": "close"
+        },
+        {
+          "component": "spinner",
+          "as": "qrPending"
+        },
+        {
+          "component": "qr-code",
+          "as": "signingQrCode",
+          "entity": "signer"
+        },
+        {
+          "component": "alert",
+          "as": "qrMissing",
+          "entity": "signer"
+        },
+        {
+          "component": "button",
+          "as": "qrPrevious"
+        },
+        {
+          "component": "button",
+          "as": "qrNext"
+        },
+        {
+          "component": "button",
+          "as": "qrDone"
+        },
+        {
+          "component": "list",
+          "as": "requiredItemsList",
+          "entity": "requiredItem"
+        },
+        {
+          "component": "skeleton",
+          "as": "requiredItemsLoading"
+        },
+        {
+          "component": "select",
+          "as": "itemOperator",
+          "entity": "requiredItem"
+        },
+        {
+          "component": "select",
+          "as": "itemOperatorChannel",
+          "entity": "requiredItem"
+        },
+        {
+          "component": "button",
+          "as": "assignAllToMe"
+        },
+        {
+          "component": "alert",
+          "as": "assignLaterNote"
+        },
+        {
+          "component": "alert",
+          "as": "operatorChannelNote"
+        },
+        {
+          "component": "button",
+          "as": "buyMoreSignatures"
+        },
+        {
+          "component": "button",
+          "as": "outcomeCancel"
         }
       ],
       "workflows": [
+        {
+          "name": "review_signatures",
+          "safety": "phi",
+          "description": "When the host passes `signatures` (or `signaturesLoading`), the request form shows the document's past signature requests at its top, on the same screen as the operator and signers, as on platform: a table named Signed versions (section data-section=\"signed-versions\") with the columns Date, Signature type and Actions and one row per request (data-signature-id), newest first. Date is the weekday, date and time in the active locale; Signature type is the legal level (Simple or Advanced, hidden with showLegalLevel=false), the channel (SMS, e-mail, WhatsApp, on this device or Via QR) and a SignatureStatusChip whose tooltip names who signed, who is still awaited and who signed on a party's behalf. Loading shows skeleton rows; no records shows one line saying there are no signed versions. Hosts that pass neither prop get the plain form.",
+          "descriptionKey": "ui.agent.signatureRequest.workflows.reviewSignatures",
+          "uiActions": [],
+          "stateReads": [
+            "dialog.isOpen"
+          ],
+          "apiActions": [
+            "signature.list"
+          ]
+        },
+        {
+          "name": "view_signature",
+          "safety": "phi",
+          "description": "Open one signed document from its row's View button; the host receives onViewSignature(id). The button shows only when the host passes that callback.",
+          "descriptionKey": "ui.agent.signatureRequest.workflows.viewSignature",
+          "uiActions": [],
+          "apiActions": [
+            "signature.view"
+          ]
+        },
+        {
+          "name": "download_signature",
+          "safety": "phi",
+          "description": "Download one signed document from its row; the host receives onDownloadSignature(id, 'full' | 'anonymised'). When the record has an anonymised version the Download button opens a menu with Full version and Anonymised version (menu id signature-download-<record id>); otherwise it asks for 'full' directly. The button shows only when the host passes that callback.",
+          "descriptionKey": "ui.agent.signatureRequest.workflows.downloadSignature",
+          "uiActions": [
+            "dropdown-menu.open",
+            "dropdown-menu.close"
+          ],
+          "stateReads": [
+            "dropdown-menu.isOpen"
+          ],
+          "apiActions": [
+            "signature.download"
+          ]
+        },
+        {
+          "name": "share_signature",
+          "safety": "phi",
+          "description": "Share one signed document from its row's Share menu (menu id signature-share-<record id>): link, e-mail or WhatsApp, in that order. The host receives onShareSignature(id, 'link' | 'email' | 'whatsapp') and does the sharing. The host decides which targets a row offers: the record's shareTargets, else the modal's signatureShareTargets, else all three. The button shows only when the host passes that callback and the row has at least one target.",
+          "descriptionKey": "ui.agent.signatureRequest.workflows.shareSignature",
+          "uiActions": [
+            "dropdown-menu.open",
+            "dropdown-menu.close"
+          ],
+          "stateReads": [
+            "dropdown-menu.isOpen"
+          ],
+          "apiActions": [
+            "signature.share"
+          ]
+        },
+        {
+          "name": "delete_signature",
+          "safety": "destructive",
+          "description": "Delete one signed document from its row's Delete button. It opens a confirmation, an alert dialog (dialog id signature-delete-<record id>) asking whether to delete this signed document, with the row's date under the question and Cancel and Delete. Only Delete calls onDeleteSignature(id); the host deletes and drops the record. Cancel, Esc or dialog.close / dialog.dismiss close it without deleting, and focus returns to the row's Delete button. Once the host drops the record, focus moves to the next row's first action (else the previous row's, else the line saying there are no signed versions) and a polite status says the signature was deleted. The button shows only when the host passes that callback.",
+          "descriptionKey": "ui.agent.signatureRequest.workflows.deleteSignature",
+          "uiActions": [
+            "dialog.close",
+            "dialog.dismiss"
+          ],
+          "stateReads": [
+            "dialog.isOpen"
+          ],
+          "apiActions": [
+            "signature.delete"
+          ]
+        },
         {
           "name": "assign_operator",
           "safety": "write",
-          "description": "Pick the operator who must counter-sign (or \"Assign later\" to leave the request unassigned). \"Assign to me\" claims it for the signed-in operator.",
+          "description": "Pick the operator who must counter-sign (or \"Assign later\" to leave the request unassigned). The operators are listed in host order, then \"Assign later\". An operator the host marks disabled shows greyed out with the host's reason under the name (the trigger is described by every greyed-out operator and reason) and cannot be picked; set_value refuses them. An operator the host marks deleted is listed only while they are the current value, and is never seeded. \"Assign to me\" claims it for the signed-in operator.",
           "descriptionKey": "ui.agent.signatureRequest.workflows.assignOperator",
           "uiActions": [
             "select.set_value"
@@ -21451,7 +21734,7 @@
         {
           "name": "manage_signer_roster",
           "safety": "write",
-          "description": "Build the patient-side signer roster: pick who signs in each row (the patient or their configured signee, e.g. a legal guardian), add a second signer up to the cap, or remove a row. People already on the roster are excluded from the other rows.",
+          "description": "Build the patient-side signer roster: pick who signs in each row (the patient or their configured signee, e.g. a legal guardian), add a second signer up to the cap, or remove a row. People already on the roster are excluded from the other rows; set_value with one of them, or anyone not offered in that row, leaves the row unchanged. In required documents mode the roster signs the whole batch: the main signer (row data-signer-role=\"main\"), then at most one second signee (data-signer-role=\"second\", a group named Second signee). The second signee is offered only when every listed item is a document that can carry a second signature (anamnesis interviews never can), the main signer's channel is on this device (the batch channel with channelMode batch, else the main signer's own row), and the main signer is a registered signee, not the patient (isPatient); otherwise Add signer is disabled and a visible line says why. The patient is never offered as the second signee. Changing the main signer removes the second signee, announced via a live region. Moving the main signer's channel off this device only hides them (they are not submitted) and announces why; back on this device they return. Per signer, the second signee has their own channel beside their name. A second signee who is the main signer again, is no longer on offer, or cannot receive their own channel (the batch channel in batch mode) shows a message under their row (data-note=\"second-signee-issue\") and keeps Request signature disabled. When the host marks a person as under 18 (isMinor), their row shows a warning note (data-note=\"minor-signer\") to check whether a second signee is needed; it never blocks the request, and the kit does not compute age. In required documents mode, while the patient has no registered signee (no signer option without isPatient) and the host passes onAddSignee, a link-style Add signatory button under the Patient signers heading calls it; it is user-driven with no adapter action, and the host adds the new person to signerOptions.",
           "descriptionKey": "ui.agent.signatureRequest.workflows.manageSignerRoster",
           "uiActions": [
             "select.set_value"
@@ -21464,20 +21747,20 @@
         {
           "name": "choose_delivery_channel",
           "safety": "write",
-          "description": "Choose how each signer's request is delivered via the per-row channel checkboxes (mutually exclusive — checking one channel unchecks the others): SMS, e-mail, WhatsApp, or signing on this device. On-device signers sign sequentially in roster order. The assigned operator has the same mutually exclusive checkboxes with SMS, e-mail, or on this device — the operator's own system-defined channel arrives pre-checked, and the on-device option is enabled only while a patient signer also signs on this device (an info tip explains the greyed-out state; an automatic fallback to the operator's default is announced via a live region when the last on-device patient row leaves).",
+          "description": "Choose how each signer's request is delivered in the channel dropdown beside their name, a select named Signature channel (one choice): SMS, e-mail, WhatsApp, signing on this device, or via QR (the signer scans a QR code the dialog shows in its QR step after the request; offered to every patient-side signer by default). Each signer row (data-signer-id) holds its dropdown, with the id signature-request-signer-channel-<row number>; the operator dropdown's id is signature-request-operator-channel. Each option carries data-option-id with the channel; set_value with a channel the dropdown does not offer or has disabled leaves the choice unchanged. A signer's available channels can hide any of these, Via QR included. A signer's unavailableChannels instead show a channel greyed out with the host's reason under it (e.g. SMS and WhatsApp with No mobile number): set_value refuses it, the row never falls back to it, and a signer with no channel left shows the reasons under the row and keeps Request signature disabled. On-device signers sign sequentially in roster order. The assigned operator has the same dropdown, named Operator signature channel, with SMS, e-mail, or on this device and never Via QR: the operator's own system-defined channel (defaultChannel, from their settings) arrives preselected and follows a newly picked operator, while a channel changed by hand is kept until the operator changes; the on-device option is enabled only while a patient signer also signs on this device (while disabled, its reason shows under the option and describes the trigger; an automatic fallback to the operator's default is announced via a live region when the last on-device patient row leaves). A host can replace that rule with resolveChannels: it receives the choices after every channel change (and on open) and returns the channels to use and to offer, e.g. the operator and the patient on this device together; set_value may then move another person's channel too (the operator or another signer), announced via the same live region. Channels are per signer by default, in the request form and in required documents mode. With channelMode batch there is no channel beside each name: one labelled Signature channel select (id signature-request-batch-channel) under the signers heading sets the channel for the whole roster, with SMS, e-mail, WhatsApp and Via QR offered when the main signer or the patient (isPatient) can receive them, greyed out only when neither can, and on this device always offered. It starts on e-mail, or SMS when the main signer is the patient and can receive it, unless the host passes initialBatchChannel; in required documents mode changing the main signer returns it to that default (initialBatchChannel is read only on open), announced via the live region. resolveChannels receives the batch channel as every signer's channel and moves the batch through the main signer's returned channel. In required documents mode with showOperatorChannels, each item with an assigned operator also has that operator's channel select (SMS, e-mail or on this device), named Operator signature channel for <item name> with the id signature-request-item-operator-channel-<item id>; it starts on the operator's defaultChannel and follows a newly picked operator (Assign to me included), keeping a channel changed by hand until then. Items on Assign later have none.",
           "descriptionKey": "ui.agent.signatureRequest.workflows.chooseDeliveryChannel",
           "uiActions": [
-            "checkbox.set_checked"
+            "select.set_value"
           ],
           "stateReads": [
-            "checkbox.checked"
+            "select.value"
           ],
           "apiActions": []
         },
         {
           "name": "waive_otp",
           "safety": "write",
-          "description": "Toggle a signer's on-device OTP waiver. Waiving OTP lowers the evidentiary value of that signature; the pattern surfaces a warning alert while waived.",
+          "description": "Toggle a signer's on-device OTP waiver. Waiving OTP lowers the evidentiary value of that signature; the pattern surfaces a warning alert while waived. With channelMode batch there is one switch for the whole roster (Do not require OTP from the patient), shown only while the batch channel is on this device: it starts on when the patient cannot receive SMS, whoever the main signer is, and is on and disabled when the main signer is the patient and cannot receive SMS. The choice resets when the batch channel changes. Its warning (batchOtpWarning) is one batch-level alert outside every signer row; as on platform it shows while the waiver is on, and on every channel while it is forced. Per signer in required documents mode, the main signer's own switch follows the same rules (starts on, or on and disabled, described by the warning) and resets when that row's channel changes; other rows are the user's choice.",
           "descriptionKey": "ui.agent.signatureRequest.workflows.waiveOtp",
           "uiActions": [
             "switch.toggle",
@@ -21491,14 +21774,13 @@
         {
           "name": "request_signature",
           "safety": "phi",
-          "description": "Send the signature request. Notifies every roster signer over their selected channel and hands the submission to the host.",
+          "description": "Send the signature request. Notifies every roster signer over their selected channel and hands the submission to the host. When any signer chose Via QR the dialog stays open and moves to its QR step. With channelMode batch the submission carries signMode (the batch channel, also on every signer). In required documents mode it also carries operatorAssignments (item id to operator id, null for assign later), requiredItemIds and, with showOperatorChannels, operatorChannels (item id to the operator's channel, for assigned items), with operatorChannel null; the main signer OTP waiver is skipOtp on the main signer, set only on this device.",
           "descriptionKey": "ui.agent.signatureRequest.workflows.requestSignature",
           "uiActions": [
             "dialog.close"
           ],
           "stateReads": [
             "select.value",
-            "checkbox.checked",
             "switch.checked",
             "dialog.isOpen"
           ],
@@ -21506,6 +21788,61 @@
             "signature.request"
           ]
         },
+        {
+          "name": "show_qr_code",
+          "safety": "phi",
+          "description": "After a request with a signer on the Via QR channel, the same dialog shows its QR step: a loading state until the host passes the server-issued links, then one code per QR signer with the signer name and expiry (the code or its error carries data-signer-id). With several QR signers, the user moves between codes with Previous and Next (\"1 of 2\"); Done on the last code tells the host the codes were handed over (onQrDone) and closes the dialog. Previous, Next and Done are user-driven buttons with no adapter action. Closing through dialog.close, or dismissing the waiting state with dialog.dismiss, does not fire onQrDone. A QR signer with no link shows an error in place of the code. The operator is never offered Via QR.",
+          "descriptionKey": "ui.agent.signatureRequest.workflows.showQrCode",
+          "uiActions": [
+            "dialog.close",
+            "dialog.dismiss"
+          ],
+          "stateReads": [
+            "qr-code.value",
+            "dialog.isOpen"
+          ],
+          "apiActions": []
+        },
+        {
+          "name": "review_required_items",
+          "safety": "phi",
+          "description": "When the host passes `requiredItems` (or `requiredItemsLoading`), the form asks one patient to sign every outstanding item in one batch: documents to sign and anamnesis interviews to complete, as two lists named with their counts. Each row (data-required-item-id) shows the item name only, with no signing status: the documents API of the host says only whether an item is signed. Items marked signed are left out; when none is left the dialog shows the all signed outcome. Loading shows skeleton rows. The single operator row and the signed versions table do not appear in this mode.",
+          "descriptionKey": "ui.agent.signatureRequest.workflows.reviewRequiredItems",
+          "uiActions": [],
+          "stateReads": [
+            "dialog.isOpen"
+          ],
+          "apiActions": [
+            "signature.listRequired"
+          ]
+        },
+        {
+          "name": "assign_item_operators",
+          "safety": "write",
+          "description": "In required documents mode, pick the operator for each item that needs an operator signature (requiresOperator), or \"Assign later\", listed first. Each picker is named \"Operator for <item name>\" and has the id signature-request-item-operator-<item id>. Greyed-out and deleted operators follow the same rules as the single operator picker: a disabled operator shows its reason and set_value refuses them, a deleted one shows only in a picker still assigned to them. \"Assign to me\" (shown when the host passes currentOperatorId) sets every picker to the signed-in operator; it is a user-driven button with no adapter action. An info note shows while any picker is on Assign later, and another says each operator receives the request by e-mail or SMS per their own settings, unless the host passes showOperatorChannels: then each assigned item shows its operator's channel instead (see choose_delivery_channel).",
+          "descriptionKey": "ui.agent.signatureRequest.workflows.assignItemOperators",
+          "uiActions": [
+            "select.set_value"
+          ],
+          "stateReads": [
+            "select.value"
+          ],
+          "apiActions": []
+        },
+        {
+          "name": "show_outcome",
+          "safety": "read",
+          "description": "When the host passes `outcome`, the dialog replaces every other view with a final screen whose heading and description carry the message, and focus moves to the heading: 'linkSent' (the secure link went out; in required documents mode the heading says the documents were sent to the patient), 'allSigned' (nothing left to sign) or 'creditsExhausted' (no electronic signature documents left). Close ends it; on 'creditsExhausted' a Buy more documents button calls onBuyMoreSignatures when the host passes it, and a Cancel button, when the host passes onOutcomeCancel, returns the dialog to the form and calls it so the host clears outcome (both user-driven, no adapter action).",
+          "descriptionKey": "ui.agent.signatureRequest.workflows.showOutcome",
+          "uiActions": [
+            "dialog.close",
+            "dialog.dismiss"
+          ],
+          "stateReads": [
+            "dialog.isOpen"
+          ],
+          "apiActions": []
+        },
         {
           "name": "dismiss",
           "safety": "destructive",