docs(apify-actor-development): clarify apify push builds but does not run — trigger a run explicitly

[DaveHanns]

Rationale

apify push uploads source and builds a new Actor version, but it does not execute the Actor. A successful push exits 0 and prints a Console URL, which reads as "done" — yet the runs tab stays empty until something invokes the Actor. Agents (and users following Quick start step 8) frequently stop at apify push and consider the deploy complete, missing the fact that "deploy and produce output" requires an explicit run trigger.

This PR expands ## Quick start workflow with a step 9 that names the distinction, and adds a matching subsection under ## Commands alongside ### Remote Actor calls with the concrete invocation options (apify call, apify actors start + apify runs wait, Standby URL hit) and a status: SUCCEEDED check to close the loop.

Added content (preview)

Step 9 in Quick start:

Trigger a run - apify push only builds; it does not execute the Actor. If the task is "deploy and produce output", follow up with apify call <actor-id> (blocking) or apify actors start <actor-id> --input '{...}' then apify runs wait <runId> (non-blocking). Confirm apify runs info <runId> reports status: SUCCEEDED.

New subsection under ## Commands:

apify push builds, it does not run

apify push only uploads source and builds a new Actor version — it does not execute the Actor. If the task is "deploy and produce output", follow up with an explicit invocation:

• apify call <actor-id> — blocking, prints the run summary.
• apify actors start <actor-id> --input '{...}' then apify runs wait <runId> — non-blocking start plus wait.
• For Standby Actors: hit the Standby URL once so the platform spins up a run.

End every deploy workflow with a check that apify runs info <runId> reports status: SUCCEEDED. A successful apify push exits 0 and prints a Console URL, which is easy to read as "done" even when the runs tab is still empty.

Surfaced during an evaluation of Apify surfaces for agent-driven Actor development.