markform 0.1.13 → 0.1.14

package/examples/simple/simple-with-skips.session.yaml

@@ -125,25 +125,51 @@ turns:
     context:
       system_prompt: |-
         # Form Instructions
-        Carefully research answers to all questions in the form, using all available tools you have.
 
-        Guidelines:
-        1. Focus on required fields first (severity: "required"), then address optional fields (severity: "recommended")
-        2. You MUST address ALL issues shown to you - both required AND recommended (optional)
-        3. NEVER fabricate or guess information - only use data you can verify
-        4. If you cannot find verifiable information for a field, use skip_field to mark it as skipped with a reason
-        5. For string fields: use appropriate text from verified sources
-        6. For number fields: use appropriate numeric values from verified sources
-        7. For single_select: choose one valid option ID
-        8. For multi_select: choose one or more valid option IDs
-        9. For checkboxes: use the appropriate state for the checkbox mode:
-           - Mode "simple": done (checked) or todo (unchecked)
-           - Mode "multi": done, todo, or na (not applicable)
-           - Mode "explicit": yes or no (must explicitly answer)
+        Research and fill the form fields using all available tools. Focus on accuracy over completeness.
 
-        CRITICAL: Accuracy is more important than completeness. Use skip_field when information cannot be verified.
+        ## Guidelines
+        1. Address required fields first (severity: "required"), then optional fields (severity: "recommended")
+        2. NEVER fabricate or guess information - only use data you can verify
+        3. If you cannot find verifiable information, use skip_field with a reason
 
-        Always use the fill_form tool to submit your field values.
+        ## Patch Format Examples
+
+        Use the fill_form tool with patches in these formats:
+
+        | Type | Example |
+        |------|---------|
+        | string | `{ op: "set_string", fieldId: "name", value: "Acme Corp" }` |
+        | number | `{ op: "set_number", fieldId: "age", value: 32 }` |
+        | string_list | `{ op: "set_string_list", fieldId: "tags", value: ["ai", "ml"] }` |
+        | url | `{ op: "set_url", fieldId: "website", value: "https://example.com" }` |
+        | url_list | `{ op: "set_url_list", fieldId: "sources", value: ["https://a.com", "https://b.com"] }` |
+        | date | `{ op: "set_date", fieldId: "event_date", value: "2024-06-15" }` |
+        | year | `{ op: "set_year", fieldId: "founded", value: 2024 }` |
+        | single_select | `{ op: "set_single_select", fieldId: "priority", value: "high" }` |
+        | multi_select | `{ op: "set_multi_select", fieldId: "categories", value: ["frontend", "backend"] }` |
+        | checkboxes | `{ op: "set_checkboxes", fieldId: "tasks", value: { "task1": "done", "task2": "todo" } }` |
+        | table | `{ op: "set_table", fieldId: "team", value: [{ "name": "Alice", "role": "Engineer" }] }` |
+
+        ## Important: checkboxes vs multi_select
+
+        These two types look similar but have DIFFERENT value formats:
+
+        - **multi_select** → array of option IDs: `["opt1", "opt2"]`
+        - **checkboxes** → object mapping IDs to states: `{ "opt1": "done", "opt2": "todo" }`
+
+        **Checkbox states by mode:**
+        - Mode "simple": `"done"` or `"todo"`
+        - Mode "multi": `"done"`, `"todo"`, `"incomplete"`, `"active"`, or `"na"`
+        - Mode "explicit": `"yes"` or `"no"` (if unknown, use abort_field)
+
+        **WRONG:** `{ op: "set_checkboxes", value: ["task1", "task2"] }`
+        **RIGHT:** `{ op: "set_checkboxes", value: { "task1": "done", "task2": "done" } }`
+
+        ## Skipping Fields
+
+        If you cannot find verifiable information:
+        `{ op: "skip_field", fieldId: "...", reason: "Could not find verified data" }`
 
 
         # Instructions for agent role
@@ -344,7 +370,7 @@ turns:
         - **age** (field): Required field "Age" is empty
           Severity: required, Priority: P1
           Type: number
-          Set: { op: "set_number", fieldId: "age", value: 123 }
+          Set: { op: "set_number", fieldId: "age", value: 42 }
           This field is required.
 
         - **categories** (field): Required field "Categories" has no selections
@@ -359,19 +385,19 @@ turns:
           Type: checkboxes
           Options: backed_up, notified
           Mode: explicit
-          Set: { op: "set_checkboxes", fieldId: "confirmations", value: { "opt1": "done", "opt2": "todo" } }
+          Set: { op: "set_checkboxes", fieldId: "confirmations", value: { "backed_up": "yes", "notified": "no" } }
           This field is required.
 
         - **email** (field): Required field "Email" is empty
           Severity: required, Priority: P1
           Type: string
-          Set: { op: "set_string", fieldId: "email", value: "..." }
+          Set: { op: "set_string", fieldId: "email", value: "text here" }
           This field is required.
 
         - **event_date** (field): Required field "Event Date" is empty
           Severity: required, Priority: P1
           Type: date
-          Set: { op: "set_date", fieldId: "event_date", value: "2024-01-15" }
+          Set: { op: "set_date", fieldId: "event_date", value: "2024-06-15" }
           This field is required.
 
         - **founded_year** (field): Required field "Founded Year" is empty
@@ -383,7 +409,7 @@ turns:
         - **name** (field): Required field "Name" is empty
           Severity: required, Priority: P1
           Type: string
-          Set: { op: "set_string", fieldId: "name", value: "..." }
+          Set: { op: "set_string", fieldId: "name", value: "text here" }
           This field is required.
 
         - **priority** (field): Required field "Priority" has no selection
@@ -396,7 +422,7 @@ turns:
         - **tags** (field): Required field "Tags" is empty
           Severity: required, Priority: P1
           Type: string_list
-          Set: { op: "set_string_list", fieldId: "tags", value: ["...", "..."] }
+          Set: { op: "set_string_list", fieldId: "tags", value: ["item1", "item2"] }
           This field is required.
 
         - **tasks_multi** (field): All items in "Tasks (Multi Mode)" must be completed
@@ -404,7 +430,7 @@ turns:
           Type: checkboxes
           Options: research, design, implement, test
           Mode: multi
-          Set: { op: "set_checkboxes", fieldId: "tasks_multi", value: { "opt1": "done", "opt2": "todo" } }
+          Set: { op: "set_checkboxes", fieldId: "tasks_multi", value: { "research": "done", "design": "todo" } }
           This field is required.
 
         # General Instructions
@@ -415,25 +441,51 @@ turns:
       request:
         system: |-
           # Form Instructions
-          Carefully research answers to all questions in the form, using all available tools you have.
 
-          Guidelines:
-          1. Focus on required fields first (severity: "required"), then address optional fields (severity: "recommended")
-          2. You MUST address ALL issues shown to you - both required AND recommended (optional)
-          3. NEVER fabricate or guess information - only use data you can verify
-          4. If you cannot find verifiable information for a field, use skip_field to mark it as skipped with a reason
-          5. For string fields: use appropriate text from verified sources
-          6. For number fields: use appropriate numeric values from verified sources
-          7. For single_select: choose one valid option ID
-          8. For multi_select: choose one or more valid option IDs
-          9. For checkboxes: use the appropriate state for the checkbox mode:
-             - Mode "simple": done (checked) or todo (unchecked)
-             - Mode "multi": done, todo, or na (not applicable)
-             - Mode "explicit": yes or no (must explicitly answer)
+          Research and fill the form fields using all available tools. Focus on accuracy over completeness.
+
+          ## Guidelines
+          1. Address required fields first (severity: "required"), then optional fields (severity: "recommended")
+          2. NEVER fabricate or guess information - only use data you can verify
+          3. If you cannot find verifiable information, use skip_field with a reason
+
+          ## Patch Format Examples
+
+          Use the fill_form tool with patches in these formats:
+
+          | Type | Example |
+          |------|---------|
+          | string | `{ op: "set_string", fieldId: "name", value: "Acme Corp" }` |
+          | number | `{ op: "set_number", fieldId: "age", value: 32 }` |
+          | string_list | `{ op: "set_string_list", fieldId: "tags", value: ["ai", "ml"] }` |
+          | url | `{ op: "set_url", fieldId: "website", value: "https://example.com" }` |
+          | url_list | `{ op: "set_url_list", fieldId: "sources", value: ["https://a.com", "https://b.com"] }` |
+          | date | `{ op: "set_date", fieldId: "event_date", value: "2024-06-15" }` |
+          | year | `{ op: "set_year", fieldId: "founded", value: 2024 }` |
+          | single_select | `{ op: "set_single_select", fieldId: "priority", value: "high" }` |
+          | multi_select | `{ op: "set_multi_select", fieldId: "categories", value: ["frontend", "backend"] }` |
+          | checkboxes | `{ op: "set_checkboxes", fieldId: "tasks", value: { "task1": "done", "task2": "todo" } }` |
+          | table | `{ op: "set_table", fieldId: "team", value: [{ "name": "Alice", "role": "Engineer" }] }` |
+
+          ## Important: checkboxes vs multi_select
 
-          CRITICAL: Accuracy is more important than completeness. Use skip_field when information cannot be verified.
+          These two types look similar but have DIFFERENT value formats:
 
-          Always use the fill_form tool to submit your field values.
+          - **multi_select** → array of option IDs: `["opt1", "opt2"]`
+          - **checkboxes** → object mapping IDs to states: `{ "opt1": "done", "opt2": "todo" }`
+
+          **Checkbox states by mode:**
+          - Mode "simple": `"done"` or `"todo"`
+          - Mode "multi": `"done"`, `"todo"`, `"incomplete"`, `"active"`, or `"na"`
+          - Mode "explicit": `"yes"` or `"no"` (if unknown, use abort_field)
+
+          **WRONG:** `{ op: "set_checkboxes", value: ["task1", "task2"] }`
+          **RIGHT:** `{ op: "set_checkboxes", value: { "task1": "done", "task2": "done" } }`
+
+          ## Skipping Fields
+
+          If you cannot find verifiable information:
+          `{ op: "skip_field", fieldId: "...", reason: "Could not find verified data" }`
 
 
           # Instructions for agent role
@@ -634,7 +686,7 @@ turns:
           - **age** (field): Required field "Age" is empty
             Severity: required, Priority: P1
             Type: number
-            Set: { op: "set_number", fieldId: "age", value: 123 }
+            Set: { op: "set_number", fieldId: "age", value: 42 }
             This field is required.
 
           - **categories** (field): Required field "Categories" has no selections
@@ -649,19 +701,19 @@ turns:
             Type: checkboxes
             Options: backed_up, notified
             Mode: explicit
-            Set: { op: "set_checkboxes", fieldId: "confirmations", value: { "opt1": "done", "opt2": "todo" } }
+            Set: { op: "set_checkboxes", fieldId: "confirmations", value: { "backed_up": "yes", "notified": "no" } }
             This field is required.
 
           - **email** (field): Required field "Email" is empty
             Severity: required, Priority: P1
             Type: string
-            Set: { op: "set_string", fieldId: "email", value: "..." }
+            Set: { op: "set_string", fieldId: "email", value: "text here" }
             This field is required.
 
           - **event_date** (field): Required field "Event Date" is empty
             Severity: required, Priority: P1
             Type: date
-            Set: { op: "set_date", fieldId: "event_date", value: "2024-01-15" }
+            Set: { op: "set_date", fieldId: "event_date", value: "2024-06-15" }
             This field is required.
 
           - **founded_year** (field): Required field "Founded Year" is empty
@@ -673,7 +725,7 @@ turns:
           - **name** (field): Required field "Name" is empty
             Severity: required, Priority: P1
             Type: string
-            Set: { op: "set_string", fieldId: "name", value: "..." }
+            Set: { op: "set_string", fieldId: "name", value: "text here" }
             This field is required.
 
           - **priority** (field): Required field "Priority" has no selection
@@ -686,7 +738,7 @@ turns:
           - **tags** (field): Required field "Tags" is empty
             Severity: required, Priority: P1
             Type: string_list
-            Set: { op: "set_string_list", fieldId: "tags", value: ["...", "..."] }
+            Set: { op: "set_string_list", fieldId: "tags", value: ["item1", "item2"] }
             This field is required.
 
           - **tasks_multi** (field): All items in "Tasks (Multi Mode)" must be completed
@@ -694,7 +746,7 @@ turns:
             Type: checkboxes
             Options: research, design, implement, test
             Mode: multi
-            Set: { op: "set_checkboxes", fieldId: "tasks_multi", value: { "opt1": "done", "opt2": "todo" } }
+            Set: { op: "set_checkboxes", fieldId: "tasks_multi", value: { "research": "done", "design": "todo" } }
             This field is required.
 
           # General Instructions
@@ -881,25 +933,51 @@ turns:
     context:
       system_prompt: |-
         # Form Instructions
-        Carefully research answers to all questions in the form, using all available tools you have.
 
-        Guidelines:
-        1. Focus on required fields first (severity: "required"), then address optional fields (severity: "recommended")
-        2. You MUST address ALL issues shown to you - both required AND recommended (optional)
-        3. NEVER fabricate or guess information - only use data you can verify
-        4. If you cannot find verifiable information for a field, use skip_field to mark it as skipped with a reason
-        5. For string fields: use appropriate text from verified sources
-        6. For number fields: use appropriate numeric values from verified sources
-        7. For single_select: choose one valid option ID
-        8. For multi_select: choose one or more valid option IDs
-        9. For checkboxes: use the appropriate state for the checkbox mode:
-           - Mode "simple": done (checked) or todo (unchecked)
-           - Mode "multi": done, todo, or na (not applicable)
-           - Mode "explicit": yes or no (must explicitly answer)
+        Research and fill the form fields using all available tools. Focus on accuracy over completeness.
+
+        ## Guidelines
+        1. Address required fields first (severity: "required"), then optional fields (severity: "recommended")
+        2. NEVER fabricate or guess information - only use data you can verify
+        3. If you cannot find verifiable information, use skip_field with a reason
+
+        ## Patch Format Examples
+
+        Use the fill_form tool with patches in these formats:
+
+        | Type | Example |
+        |------|---------|
+        | string | `{ op: "set_string", fieldId: "name", value: "Acme Corp" }` |
+        | number | `{ op: "set_number", fieldId: "age", value: 32 }` |
+        | string_list | `{ op: "set_string_list", fieldId: "tags", value: ["ai", "ml"] }` |
+        | url | `{ op: "set_url", fieldId: "website", value: "https://example.com" }` |
+        | url_list | `{ op: "set_url_list", fieldId: "sources", value: ["https://a.com", "https://b.com"] }` |
+        | date | `{ op: "set_date", fieldId: "event_date", value: "2024-06-15" }` |
+        | year | `{ op: "set_year", fieldId: "founded", value: 2024 }` |
+        | single_select | `{ op: "set_single_select", fieldId: "priority", value: "high" }` |
+        | multi_select | `{ op: "set_multi_select", fieldId: "categories", value: ["frontend", "backend"] }` |
+        | checkboxes | `{ op: "set_checkboxes", fieldId: "tasks", value: { "task1": "done", "task2": "todo" } }` |
+        | table | `{ op: "set_table", fieldId: "team", value: [{ "name": "Alice", "role": "Engineer" }] }` |
+
+        ## Important: checkboxes vs multi_select
+
+        These two types look similar but have DIFFERENT value formats:
+
+        - **multi_select** → array of option IDs: `["opt1", "opt2"]`
+        - **checkboxes** → object mapping IDs to states: `{ "opt1": "done", "opt2": "todo" }`
+
+        **Checkbox states by mode:**
+        - Mode "simple": `"done"` or `"todo"`
+        - Mode "multi": `"done"`, `"todo"`, `"incomplete"`, `"active"`, or `"na"`
+        - Mode "explicit": `"yes"` or `"no"` (if unknown, use abort_field)
+
+        **WRONG:** `{ op: "set_checkboxes", value: ["task1", "task2"] }`
+        **RIGHT:** `{ op: "set_checkboxes", value: { "task1": "done", "task2": "done" } }`
 
-        CRITICAL: Accuracy is more important than completeness. Use skip_field when information cannot be verified.
+        ## Skipping Fields
 
-        Always use the fill_form tool to submit your field values.
+        If you cannot find verifiable information:
+        `{ op: "skip_field", fieldId: "...", reason: "Could not find verified data" }`
 
 
         # Instructions for agent role
@@ -1129,31 +1207,31 @@ turns:
           Type: checkboxes
           Options: read_guidelines, agree_terms
           Mode: simple
-          Set: { op: "set_checkboxes", fieldId: "tasks_simple", value: { "opt1": "done", "opt2": "todo" } }
+          Set: { op: "set_checkboxes", fieldId: "tasks_simple", value: { "read_guidelines": "done", "agree_terms": "todo" } }
           This field is required.
 
         - **website** (field): Required field "Website" is empty
           Severity: required, Priority: P1
           Type: url
-          Set: { op: "set_url", fieldId: "website", value: "https://..." }
+          Set: { op: "set_url", fieldId: "website", value: "https://example.com" }
           This field is required.
 
         - **notes** (field): Optional field not yet addressed
           Severity: recommended, Priority: P3
           Type: string
-          Set: { op: "set_string", fieldId: "notes", value: "..." }
+          Set: { op: "set_string", fieldId: "notes", value: "text here" }
           Skip: { op: "skip_field", fieldId: "notes", reason: "..." }
 
         - **optional_date** (field): Optional field not yet addressed
           Severity: recommended, Priority: P3
           Type: date
-          Set: { op: "set_date", fieldId: "optional_date", value: "2024-01-15" }
+          Set: { op: "set_date", fieldId: "optional_date", value: "2024-06-15" }
           Skip: { op: "skip_field", fieldId: "optional_date", reason: "..." }
 
         - **optional_number** (field): Optional field not yet addressed
           Severity: recommended, Priority: P3
           Type: number
-          Set: { op: "set_number", fieldId: "optional_number", value: 123 }
+          Set: { op: "set_number", fieldId: "optional_number", value: 42 }
           Skip: { op: "skip_field", fieldId: "optional_number", reason: "..." }
 
         - **optional_year** (field): Optional field not yet addressed
@@ -1167,25 +1245,25 @@ turns:
           Type: table
           Columns: task (required), estimate_hrs, link
           Rows: min: 0, max: 10
-          Set: { op: "set_table", fieldId: "project_tasks", value: [{ "task": "...", "estimate_hrs": "...", "link": "..." }, ...] }
+          Set: { op: "set_table", fieldId: "project_tasks", value: [{ "task": "...", "estimate_hrs": "...", "link": "..." }] }
           Skip: { op: "skip_field", fieldId: "project_tasks", reason: "..." }
 
         - **references** (field): Optional field not yet addressed
           Severity: recommended, Priority: P3
           Type: url_list
-          Set: { op: "set_url_list", fieldId: "references", value: ["https://...", "https://..."] }
+          Set: { op: "set_url_list", fieldId: "references", value: ["https://a.com", "https://b.com"] }
           Skip: { op: "skip_field", fieldId: "references", reason: "..." }
 
         - **related_url** (field): Optional field not yet addressed
           Severity: recommended, Priority: P3
           Type: url
-          Set: { op: "set_url", fieldId: "related_url", value: "https://..." }
+          Set: { op: "set_url", fieldId: "related_url", value: "https://example.com" }
           Skip: { op: "skip_field", fieldId: "related_url", reason: "..." }
 
         - **score** (field): Optional field not yet addressed
           Severity: recommended, Priority: P3
           Type: number
-          Set: { op: "set_number", fieldId: "score", value: 123 }
+          Set: { op: "set_number", fieldId: "score", value: 42 }
           Skip: { op: "skip_field", fieldId: "score", reason: "..." }
 
         # General Instructions
@@ -1196,25 +1274,51 @@ turns:
       request:
         system: |-
           # Form Instructions
-          Carefully research answers to all questions in the form, using all available tools you have.
 
-          Guidelines:
-          1. Focus on required fields first (severity: "required"), then address optional fields (severity: "recommended")
-          2. You MUST address ALL issues shown to you - both required AND recommended (optional)
-          3. NEVER fabricate or guess information - only use data you can verify
-          4. If you cannot find verifiable information for a field, use skip_field to mark it as skipped with a reason
-          5. For string fields: use appropriate text from verified sources
-          6. For number fields: use appropriate numeric values from verified sources
-          7. For single_select: choose one valid option ID
-          8. For multi_select: choose one or more valid option IDs
-          9. For checkboxes: use the appropriate state for the checkbox mode:
-             - Mode "simple": done (checked) or todo (unchecked)
-             - Mode "multi": done, todo, or na (not applicable)
-             - Mode "explicit": yes or no (must explicitly answer)
+          Research and fill the form fields using all available tools. Focus on accuracy over completeness.
 
-          CRITICAL: Accuracy is more important than completeness. Use skip_field when information cannot be verified.
+          ## Guidelines
+          1. Address required fields first (severity: "required"), then optional fields (severity: "recommended")
+          2. NEVER fabricate or guess information - only use data you can verify
+          3. If you cannot find verifiable information, use skip_field with a reason
 
-          Always use the fill_form tool to submit your field values.
+          ## Patch Format Examples
+
+          Use the fill_form tool with patches in these formats:
+
+          | Type | Example |
+          |------|---------|
+          | string | `{ op: "set_string", fieldId: "name", value: "Acme Corp" }` |
+          | number | `{ op: "set_number", fieldId: "age", value: 32 }` |
+          | string_list | `{ op: "set_string_list", fieldId: "tags", value: ["ai", "ml"] }` |
+          | url | `{ op: "set_url", fieldId: "website", value: "https://example.com" }` |
+          | url_list | `{ op: "set_url_list", fieldId: "sources", value: ["https://a.com", "https://b.com"] }` |
+          | date | `{ op: "set_date", fieldId: "event_date", value: "2024-06-15" }` |
+          | year | `{ op: "set_year", fieldId: "founded", value: 2024 }` |
+          | single_select | `{ op: "set_single_select", fieldId: "priority", value: "high" }` |
+          | multi_select | `{ op: "set_multi_select", fieldId: "categories", value: ["frontend", "backend"] }` |
+          | checkboxes | `{ op: "set_checkboxes", fieldId: "tasks", value: { "task1": "done", "task2": "todo" } }` |
+          | table | `{ op: "set_table", fieldId: "team", value: [{ "name": "Alice", "role": "Engineer" }] }` |
+
+          ## Important: checkboxes vs multi_select
+
+          These two types look similar but have DIFFERENT value formats:
+
+          - **multi_select** → array of option IDs: `["opt1", "opt2"]`
+          - **checkboxes** → object mapping IDs to states: `{ "opt1": "done", "opt2": "todo" }`
+
+          **Checkbox states by mode:**
+          - Mode "simple": `"done"` or `"todo"`
+          - Mode "multi": `"done"`, `"todo"`, `"incomplete"`, `"active"`, or `"na"`
+          - Mode "explicit": `"yes"` or `"no"` (if unknown, use abort_field)
+
+          **WRONG:** `{ op: "set_checkboxes", value: ["task1", "task2"] }`
+          **RIGHT:** `{ op: "set_checkboxes", value: { "task1": "done", "task2": "done" } }`
+
+          ## Skipping Fields
+
+          If you cannot find verifiable information:
+          `{ op: "skip_field", fieldId: "...", reason: "Could not find verified data" }`
 
 
           # Instructions for agent role
@@ -1444,31 +1548,31 @@ turns:
             Type: checkboxes
             Options: read_guidelines, agree_terms
             Mode: simple
-            Set: { op: "set_checkboxes", fieldId: "tasks_simple", value: { "opt1": "done", "opt2": "todo" } }
+            Set: { op: "set_checkboxes", fieldId: "tasks_simple", value: { "read_guidelines": "done", "agree_terms": "todo" } }
             This field is required.
 
           - **website** (field): Required field "Website" is empty
             Severity: required, Priority: P1
             Type: url
-            Set: { op: "set_url", fieldId: "website", value: "https://..." }
+            Set: { op: "set_url", fieldId: "website", value: "https://example.com" }
             This field is required.
 
           - **notes** (field): Optional field not yet addressed
             Severity: recommended, Priority: P3
             Type: string
-            Set: { op: "set_string", fieldId: "notes", value: "..." }
+            Set: { op: "set_string", fieldId: "notes", value: "text here" }
             Skip: { op: "skip_field", fieldId: "notes", reason: "..." }
 
           - **optional_date** (field): Optional field not yet addressed
             Severity: recommended, Priority: P3
             Type: date
-            Set: { op: "set_date", fieldId: "optional_date", value: "2024-01-15" }
+            Set: { op: "set_date", fieldId: "optional_date", value: "2024-06-15" }
             Skip: { op: "skip_field", fieldId: "optional_date", reason: "..." }
 
           - **optional_number** (field): Optional field not yet addressed
             Severity: recommended, Priority: P3
             Type: number
-            Set: { op: "set_number", fieldId: "optional_number", value: 123 }
+            Set: { op: "set_number", fieldId: "optional_number", value: 42 }
             Skip: { op: "skip_field", fieldId: "optional_number", reason: "..." }
 
           - **optional_year** (field): Optional field not yet addressed
@@ -1482,25 +1586,25 @@ turns:
             Type: table
             Columns: task (required), estimate_hrs, link
             Rows: min: 0, max: 10
-            Set: { op: "set_table", fieldId: "project_tasks", value: [{ "task": "...", "estimate_hrs": "...", "link": "..." }, ...] }
+            Set: { op: "set_table", fieldId: "project_tasks", value: [{ "task": "...", "estimate_hrs": "...", "link": "..." }] }
             Skip: { op: "skip_field", fieldId: "project_tasks", reason: "..." }
 
           - **references** (field): Optional field not yet addressed
             Severity: recommended, Priority: P3
             Type: url_list
-            Set: { op: "set_url_list", fieldId: "references", value: ["https://...", "https://..."] }
+            Set: { op: "set_url_list", fieldId: "references", value: ["https://a.com", "https://b.com"] }
             Skip: { op: "skip_field", fieldId: "references", reason: "..." }
 
           - **related_url** (field): Optional field not yet addressed
             Severity: recommended, Priority: P3
             Type: url
-            Set: { op: "set_url", fieldId: "related_url", value: "https://..." }
+            Set: { op: "set_url", fieldId: "related_url", value: "https://example.com" }
             Skip: { op: "skip_field", fieldId: "related_url", reason: "..." }
 
           - **score** (field): Optional field not yet addressed
             Severity: recommended, Priority: P3
             Type: number
-            Set: { op: "set_number", fieldId: "score", value: 123 }
+            Set: { op: "set_number", fieldId: "score", value: 42 }
             Skip: { op: "skip_field", fieldId: "score", reason: "..." }
 
           # General Instructions
@@ -1597,25 +1701,51 @@ turns:
     context:
       system_prompt: |-
         # Form Instructions
-        Carefully research answers to all questions in the form, using all available tools you have.
 
-        Guidelines:
-        1. Focus on required fields first (severity: "required"), then address optional fields (severity: "recommended")
-        2. You MUST address ALL issues shown to you - both required AND recommended (optional)
-        3. NEVER fabricate or guess information - only use data you can verify
-        4. If you cannot find verifiable information for a field, use skip_field to mark it as skipped with a reason
-        5. For string fields: use appropriate text from verified sources
-        6. For number fields: use appropriate numeric values from verified sources
-        7. For single_select: choose one valid option ID
-        8. For multi_select: choose one or more valid option IDs
-        9. For checkboxes: use the appropriate state for the checkbox mode:
-           - Mode "simple": done (checked) or todo (unchecked)
-           - Mode "multi": done, todo, or na (not applicable)
-           - Mode "explicit": yes or no (must explicitly answer)
+        Research and fill the form fields using all available tools. Focus on accuracy over completeness.
+
+        ## Guidelines
+        1. Address required fields first (severity: "required"), then optional fields (severity: "recommended")
+        2. NEVER fabricate or guess information - only use data you can verify
+        3. If you cannot find verifiable information, use skip_field with a reason
+
+        ## Patch Format Examples
+
+        Use the fill_form tool with patches in these formats:
+
+        | Type | Example |
+        |------|---------|
+        | string | `{ op: "set_string", fieldId: "name", value: "Acme Corp" }` |
+        | number | `{ op: "set_number", fieldId: "age", value: 32 }` |
+        | string_list | `{ op: "set_string_list", fieldId: "tags", value: ["ai", "ml"] }` |
+        | url | `{ op: "set_url", fieldId: "website", value: "https://example.com" }` |
+        | url_list | `{ op: "set_url_list", fieldId: "sources", value: ["https://a.com", "https://b.com"] }` |
+        | date | `{ op: "set_date", fieldId: "event_date", value: "2024-06-15" }` |
+        | year | `{ op: "set_year", fieldId: "founded", value: 2024 }` |
+        | single_select | `{ op: "set_single_select", fieldId: "priority", value: "high" }` |
+        | multi_select | `{ op: "set_multi_select", fieldId: "categories", value: ["frontend", "backend"] }` |
+        | checkboxes | `{ op: "set_checkboxes", fieldId: "tasks", value: { "task1": "done", "task2": "todo" } }` |
+        | table | `{ op: "set_table", fieldId: "team", value: [{ "name": "Alice", "role": "Engineer" }] }` |
+
+        ## Important: checkboxes vs multi_select
 
-        CRITICAL: Accuracy is more important than completeness. Use skip_field when information cannot be verified.
+        These two types look similar but have DIFFERENT value formats:
 
-        Always use the fill_form tool to submit your field values.
+        - **multi_select** → array of option IDs: `["opt1", "opt2"]`
+        - **checkboxes** → object mapping IDs to states: `{ "opt1": "done", "opt2": "todo" }`
+
+        **Checkbox states by mode:**
+        - Mode "simple": `"done"` or `"todo"`
+        - Mode "multi": `"done"`, `"todo"`, `"incomplete"`, `"active"`, or `"na"`
+        - Mode "explicit": `"yes"` or `"no"` (if unknown, use abort_field)
+
+        **WRONG:** `{ op: "set_checkboxes", value: ["task1", "task2"] }`
+        **RIGHT:** `{ op: "set_checkboxes", value: { "task1": "done", "task2": "done" } }`
+
+        ## Skipping Fields
+
+        If you cannot find verifiable information:
+        `{ op: "skip_field", fieldId: "...", reason: "Could not find verified data" }`
 
 
         # Instructions for agent role
@@ -1874,7 +2004,7 @@ turns:
           Type: table
           Columns: name (required), role, start_date
           Rows: min: 0, max: 5
-          Set: { op: "set_table", fieldId: "team_members", value: [{ "name": "...", "role": "...", "start_date": "..." }, ...] }
+          Set: { op: "set_table", fieldId: "team_members", value: [{ "name": "...", "role": "...", "start_date": "..." }] }
           Skip: { op: "skip_field", fieldId: "team_members", reason: "..." }
 
         # General Instructions
@@ -1885,25 +2015,51 @@ turns:
       request:
         system: |-
           # Form Instructions
-          Carefully research answers to all questions in the form, using all available tools you have.
 
-          Guidelines:
-          1. Focus on required fields first (severity: "required"), then address optional fields (severity: "recommended")
-          2. You MUST address ALL issues shown to you - both required AND recommended (optional)
-          3. NEVER fabricate or guess information - only use data you can verify
-          4. If you cannot find verifiable information for a field, use skip_field to mark it as skipped with a reason
-          5. For string fields: use appropriate text from verified sources
-          6. For number fields: use appropriate numeric values from verified sources
-          7. For single_select: choose one valid option ID
-          8. For multi_select: choose one or more valid option IDs
-          9. For checkboxes: use the appropriate state for the checkbox mode:
-             - Mode "simple": done (checked) or todo (unchecked)
-             - Mode "multi": done, todo, or na (not applicable)
-             - Mode "explicit": yes or no (must explicitly answer)
+          Research and fill the form fields using all available tools. Focus on accuracy over completeness.
+
+          ## Guidelines
+          1. Address required fields first (severity: "required"), then optional fields (severity: "recommended")
+          2. NEVER fabricate or guess information - only use data you can verify
+          3. If you cannot find verifiable information, use skip_field with a reason
+
+          ## Patch Format Examples
+
+          Use the fill_form tool with patches in these formats:
+
+          | Type | Example |
+          |------|---------|
+          | string | `{ op: "set_string", fieldId: "name", value: "Acme Corp" }` |
+          | number | `{ op: "set_number", fieldId: "age", value: 32 }` |
+          | string_list | `{ op: "set_string_list", fieldId: "tags", value: ["ai", "ml"] }` |
+          | url | `{ op: "set_url", fieldId: "website", value: "https://example.com" }` |
+          | url_list | `{ op: "set_url_list", fieldId: "sources", value: ["https://a.com", "https://b.com"] }` |
+          | date | `{ op: "set_date", fieldId: "event_date", value: "2024-06-15" }` |
+          | year | `{ op: "set_year", fieldId: "founded", value: 2024 }` |
+          | single_select | `{ op: "set_single_select", fieldId: "priority", value: "high" }` |
+          | multi_select | `{ op: "set_multi_select", fieldId: "categories", value: ["frontend", "backend"] }` |
+          | checkboxes | `{ op: "set_checkboxes", fieldId: "tasks", value: { "task1": "done", "task2": "todo" } }` |
+          | table | `{ op: "set_table", fieldId: "team", value: [{ "name": "Alice", "role": "Engineer" }] }` |
+
+          ## Important: checkboxes vs multi_select
+
+          These two types look similar but have DIFFERENT value formats:
+
+          - **multi_select** → array of option IDs: `["opt1", "opt2"]`
+          - **checkboxes** → object mapping IDs to states: `{ "opt1": "done", "opt2": "todo" }`
+
+          **Checkbox states by mode:**
+          - Mode "simple": `"done"` or `"todo"`
+          - Mode "multi": `"done"`, `"todo"`, `"incomplete"`, `"active"`, or `"na"`
+          - Mode "explicit": `"yes"` or `"no"` (if unknown, use abort_field)
+
+          **WRONG:** `{ op: "set_checkboxes", value: ["task1", "task2"] }`
+          **RIGHT:** `{ op: "set_checkboxes", value: { "task1": "done", "task2": "done" } }`
 
-          CRITICAL: Accuracy is more important than completeness. Use skip_field when information cannot be verified.
+          ## Skipping Fields
 
-          Always use the fill_form tool to submit your field values.
+          If you cannot find verifiable information:
+          `{ op: "skip_field", fieldId: "...", reason: "Could not find verified data" }`
 
 
           # Instructions for agent role
@@ -2162,7 +2318,7 @@ turns:
             Type: table
             Columns: name (required), role, start_date
             Rows: min: 0, max: 5
-            Set: { op: "set_table", fieldId: "team_members", value: [{ "name": "...", "role": "...", "start_date": "..." }, ...] }
+            Set: { op: "set_table", fieldId: "team_members", value: [{ "name": "...", "role": "...", "start_date": "..." }] }
             Skip: { op: "skip_field", fieldId: "team_members", reason: "..." }
 
           # General Instructions