Auto Email Sender

Auto Email Sender

Use auto-email-sender --json as the automation interface. Live command contracts and returned state are authoritative.

Find and call

• For an unfamiliar intent, use capabilities --intent "<user goal>" --limit 3 --with-contract. Prefer a matching command's summary and risk over its ranking alone. Broaden with capabilities --resource <resource> when needed. Use root capabilities only to learn the product's resource map.
• Use the attached execution_contract; otherwise read describe --command <command> for missing input or effect information. Reuse contracts and complete action links already in context; use contract_revision / scope_revision with --since when checking for changes. Request --section input, output, globals, or another section only for missing detail; --view full is for a full contract inspection.
• Use ordinary flags for simple calls. For text, arrays, or returned actions, use invoke --command <command> --input - with a JSON object on stdin (or a UTF-8 file). Keys are parameter names from describe; repeatable parameters take arrays. Global options stay outside that JSON. Omitted or null input uses parser defaults; clear only through declared clear controls.

Continue from results

• Read stable IDs, state, counts, warnings, and available_actions. Use the action's input as invoke input and supply only missing required_input. An action is an available choice, not permission or a recommendation to take it.
• In action_groups, choose IDs from the group: merge input constants with input_bindings (id = one chosen ID, [id] = a one-element array). This preserves grouping without guessing parameter names. Do not execute every offered action.
• Read only what the task needs: --fields for columns, --expand <field-or-JSON-pointer> for omitted content. Follow continuation.input for another page. truncated means some content was omitted, not that the operation failed.
• For complete collections use --output-file <path>.jsonl with --all. For recovery_action, preserve earlier input when requested, overlay its input and global_options, and replace required placeholders. Follow the same rule on errors such as RESULT_TOO_LARGE; do not keep increasing stdout limits. Use only filter fields/operators declared in describe --section output.
• Prefer present for selecting/opening results in the app. Prefer frozen selection plans for acting on a filtered set. Use a returned wait action for running work; awaiting_user means the user must act, and timed_out means the observation ended. Neither means the job succeeded or should be retried.
• Preserve the returned request ID when retrying the same operation. On EXTERNAL_EXECUTION_UNKNOWN, read the affected object/status first; do not repeat the external action blindly. On APP_UNAVAILABLE, ask the user to open the app and wait for loading; never launch it. Use doctor --strict for diagnosis.