Produces invalid Python code: `TypeError: execute_activity() takes from 1 to 2 positional arguments but 3 positional arguments (and 1 keyword-only argument) were given`

[donald-pinckney]

Bad code:

await workflow.execute_activity(
                send_confirmation_email,
                order,
                tracking_number,
                start_to_close_timeout=timedelta(seconds=30),
            )

Try to repro with:

/temporal-developer make an example temporal workflow which is a multi-step order processing workflow, and which may have business logic level failures at some of the later steps. Do it in Python, in a directory at python/

[donald-pinckney]

Claude's explanation of how the skill is unclear:

The skill references never explicitly state that execute_activity accepts only a single arg. All the examples happen to
use single-arg activities, so they don't violate the rule — but they also don't call it out.

For instance, references/python/patterns.md shows the saga pattern with calls like:

await workflow.execute_activity(reserve_inventory, order, ...)
await workflow.execute_activity(charge_payment, order, ...)

These all work because they pass one arg. But there's no note anywhere saying "activities take exactly one input
parameter — use a dataclass to bundle multiple values." A developer (or an LLM) seeing these patterns will naturally
write a two-arg activity and pass both args positionally, which fails at runtime.

The fix for the skill would be to add an explicit callout in references/python/python.md (or the error-handling/patterns
docs), something like:

▎ execute_activity accepts at most one positional argument. If your activity needs multiple inputs, bundle them into a
single dataclass.