[l2ysho]

Note

TL;DR — flags with an uppercase short form (-H, -X) were indented four spaces deeper than lowercase ones in --help, so the FLAGS block didn't line up. The indent check was case-sensitive. One-character fix: /^-[a-z]/ → /^-[a-z]/i. Only apify api has uppercase short flags, so only its help and its docs/reference.md block change.

apify api --help, before:

  -d, --body=<value>      The request body (JSON string).
      --describe=<value>  Print a reference for an endpoint
      -H, --header=<value>    Additional HTTP header(s). Pass a
  -l, --list-endpoints    List all available Apify API
      -X, --method=<option>   The HTTP method to use. Defaults
  -p, --params=<value>    Query parameters as a JSON object,
      --profile=<value>   The stored account to use for this

After:

  -d, --body=<value>      The request body (JSON string).
      --describe=<value>  Print a reference for an endpoint
  -H, --header=<value>    Additional HTTP header(s). Pass a
  -l, --list-endpoints    List all available Apify API
  -X, --method=<option>   The HTTP method to use. Defaults
  -p, --params=<value>    Query parameters as a JSON object,
      --profile=<value>   The stored account to use for this

Long-only flags such as --profile keep their four-space indent, which is what that branch is for.

Adds a regression test that fails on the old regex, and regenerates docs/reference.md.

🤖 Generated with Claude Code

[pkg-pr-new]

Open in StackBlitz

npx https://pkg.pr.new/apify-cli@1562

commit: 5df1fe8

[apify-factory]

Looks good, nothing blocking.

🏭 Apify Factory auto approved ✅ — passed every gate without touching the sides

Every gate passed, and neither the reviewer nor a juror found anything a human needs to look at.

_{Approval locked to 86b478e60 · workflow run}

Withdrawn because the content changed since the last verdict, and pushes are not re-reviewed.