Stay in context#
Open the intended task and read its latest answer. Use the field’s recording interaction, then inspect the generated text. The route is useful when you are already working inside the task detail panel rather than invoking a global shortcut.
Type exact names or identifiers afterward if recognition changes them. Inspect the draft’s object and constraints before sending. A visibly active recording state is not proof that usable text was produced.
Know what was tested#
The release describes this interaction, while the documented complete real-user voice acceptance specifically covers the Fn route. Do not extend that acceptance to every field gesture and focus combination without testing it.
If capture behaves unexpectedly, reproduce with a short invented sentence and note whether the task or focus changed. Avoid repeated recordings over a useful draft until you understand the insertion result. SPECS 01 temple controls are a separate development path and should not be assumed to duplicate this interaction today.