reneco-advanced-input-module 0.0.14 → 0.0.16

package/dist/cjs/voice-input-module.cjs.entry.js

@@ -491,8 +491,9 @@ class OpenAILLMService {
           8. The current GMT datetime is ${new Date().toGMTString()}
           9. Respect the constraints written between parenthesis for readonly status (readonly fields MUST NOT be filled with values), min and max values, whatever the transcription says
           10. IMPORTANT: Fields marked as "readonly" are presentation elements (headers, labels) that provide context but MUST NOT receive values
-          11. IMPORTANT: Some field names may appear multiple times in the form (e.g., in different sub-sections marked by readonly headers). If the user repeats values for the same field name, fill all occurrences in order. If there is ANY doubt about which occurrence to fill, leave ALL of them empty to avoid errors
+          11. IMPORTANT: Some field names may appear multiple times in the form (e.g., in different sub-sections marked by readonly headers). Pay close attention to the user's spoken context to determine which occurrence they are referring to. Only fill the specific occurrence mentioned by the user. If there is ANY doubt about which occurrence to fill, leave ALL of them empty to avoid errors
           12. Use readonly fields as contextual hints to understand form structure and field grouping, but never fill them
+          13. CRITICAL: For select fields, options like "No", "Non", "Non applicable", "Inconnu", "Unknown", "N/A" are VALID VALUES that can be selected. When the user says these words, treat them as legitimate option choices, NOT always as negations or refusals to answer
 
           Respond with JSON in this exact format: {"fields": [{"name": "field_name", "value": "extracted_value"}]}`;
                 let userPrompt = `
@@ -562,8 +563,9 @@ class OpenAILLMService {
         9. The current GMT datetime is ${new Date().toGMTString()}
         10. Respect the constraints written between parenthesis for readonly status (readonly fields MUST NOT be filled with values), min and max values, whatever the transcription says
         11. IMPORTANT: Fields marked as "readonly" are presentation elements (headers, labels) that provide context but MUST NOT receive values
-        12. IMPORTANT: Some field names may appear multiple times in the form (e.g., in different sub-sections marked by readonly headers). If the user repeats values for the same field name, fill all occurrences in order. If there is ANY doubt about which occurrence to fill, leave ALL of them empty to avoid errors
+        12. IMPORTANT: Some field names may appear multiple times in the form (e.g., in different sub-sections marked by readonly headers). Pay close attention to the user's spoken context to determine which occurrence they are referring to. Only fill the specific occurrence mentioned by the user. If there is ANY doubt about which occurrence to fill, leave ALL of them empty to avoid errors
         13. Use readonly fields as contextual hints to understand form structure and field grouping, but never fill them
+        14. CRITICAL: For select fields, options like "No", "Non", "Non applicable", "Inconnu", "Unknown", "N/A" are VALID VALUES that can be selected. When the user says these words, treat them as legitimate option choices, NOT always as negations or refusals to answer
 
         Respond with JSON in this exact format: {"schema": {...}}`;
             let userPrompt = `