fix(push): support --wait-for-finish=0 as fire-and-forget

Skip the post-build tag-apply wait when --wait-for-finish=0 so the flag
is truly fire-and-forget regardless of how fast the build completed.
Document the 0 semantics in the flag help text.

Also picks up stale doc regeneration from #1128 (--describe / --search
wording).

Author: l2ysho

docs/reference.md

@@ -69,10 +69,11 @@ ARGUMENTS
 FLAGS
   -d, --body=<value>      The request body (JSON string).
                           Use "-" to read from stdin.
-      --describe=<value>  Describe an endpoint: print every HTTP
-                          method on a path, its summary, and path parameters.
-                          Accepts a path like "actor-runs/{runId}" or
-                          "/v2/actor-runs/{runId}".
+      --describe=<value>  Print a reference for an endpoint
+                          path: its HTTP methods, summary, and path parameters.
+                          Leading slashes and a version prefix in the path are
+                          optional. For example, "actor-runs/{runId}" and
+                          "/v2/actor-runs/{runId}" are both accepted.
       -H, --header=<value>    Additional HTTP header(s). Pass a
                           single "key:value" string, or a JSON object like
                           '{"X-Foo": "bar", "X-Baz": "qux"}' to send multiple
@@ -85,9 +86,11 @@ FLAGS
                           <options: GET|POST|PUT|PATCH|DELETE>
   -p, --params=<value>    Query parameters as a JSON object,
                           e.g. '{"limit": 1, "desc": true}'.
-  -s, --search=<value>    Filter --list-endpoints by a
-                          space-separated query. Each token must appear
-                          (case-insensitive) in method, path, or summary.
+  -s, --search=<value>    Filter results returned by
+                          --list-endpoints. The query is case-insensitive and split
+                          into tokens by spaces. For an endpoint to be returned,
+                          every token must appear in that endpoint's method, path,
+                          or summary.
 ```
 
 ##### `apify telemetry`
@@ -742,7 +745,8 @@ FLAGS
                                  is taken from the '.actor/actor.json' file.
   -w, --wait-for-finish=<value>  Seconds for waiting
                                  to build to finish, if no value passed, it waits
-                                 forever.
+                                 forever. Pass 0 to return as soon as the build is
+                                 queued (fire-and-forget).
 ```
 
 ##### `apify actors pull` / `apify pull`

src/commands/actors/push.ts

@@ -93,7 +93,8 @@ export class ActorsPushCommand extends ApifyCommand<typeof ActorsPushCommand> {
 		}),
 		'wait-for-finish': Flags.string({
 			char: 'w',
-			description: 'Seconds for waiting to build to finish, if no value passed, it waits forever.',
+			description:
+				'Seconds for waiting to build to finish, if no value passed, it waits forever. Pass 0 to return as soon as the build is queued (fire-and-forget).',
 			required: false,
 		}),
 		'open': Flags.boolean({
@@ -397,8 +398,9 @@ Skipping push. Use --force to override.`,
 		// Platform updates `taggedBuilds[buildTag]` asynchronously after the
 		// build finishes. Wait until the tag points at this build so callers
 		// (including --json automation) that immediately
-		// `actor.start({ build: buildTag })` don't race it.
-		if (build.status === ACTOR_JOB_STATUSES.SUCCEEDED && buildTag) {
+		// `actor.start({ build: buildTag })` don't race it. Skipped when
+		// --wait-for-finish=0 (fire-and-forget).
+		if (build.status === ACTOR_JOB_STATUSES.SUCCEEDED && buildTag && waitForFinishMillis !== 0) {
 			run({ message: `Applying build tag "${buildTag}"...` });
 			const tagDeadline = Date.now() + 5_000;
 			let tagApplied = false;