[frances720]

promptless setup on main currently prints “not available yet” and exits. This enables the full setup flow: sign in or create an account, connect GitHub, select documentation and source repositories, review the proposed configuration before applying it, complete onboarding, and optionally backfill recent pull requests.

The existing implementation from #10 was merged into setup-command-groundwork, leaving main with its placeholder. This brings that implementation onto main, updates shell completion and usage documentation, and adds two fixes:

• Verify a newly authorized API key and its requested organization before replacing the saved key. Failed verification, organization mismatch, or browser cancellation preserves the previous credentials.
• Report setup_unavailable when the server lacks the setup status route, instead of exposing an unexplained 404. Specific organization-not-found responses retain their original error.

Validation: typecheck and build pass; all 127 tests pass. New integration tests exercise the real encrypted loopback callback and identity API against a local fixture, including successful signup handoff, wrong-organization credentials, rejected credentials, and cancellation. Built-binary checks verify help, invalid arguments, and non-interactive use. Four terminal walkthroughs against a local fake runtime verify confirmed configuration application, cancellation before writes, a completed rerun with no writes, and the missing-backend error.

Release dependencies: deploy the backend stack before releasing this CLI: new-user organization creation (Promptless/promptless#5358), trial enforcement (Promptless/promptless#5359), setup routes (Promptless/promptless#5372), cardless trial completion (Promptless/promptless#5373), and optional backfill key authentication (Promptless/promptless#5371). The production setup-status probe currently returns 404. No real account, GitHub installation, config, or trial was created during validation. npm publication and a production walkthrough remain outstanding.

[promptless]

I added 0e3fc91 at InlinePizza's request (#agent-escalations): "orgs set up through the CLI should also get auto create PR. update that PR to add auto create PR."

• completeOnboarding now sends {auto_create_pr: true} to POST /organizations/{org}/onboarding/complete. The runtime writes that to policies.default.publishing.auto_create_pr, the same as the dashboard wizard (promptless#5680).
• setup-api.test.ts now asserts that body instead of an empty one. npm test passes 127/127 and npm run typecheck is clean.
• The PR stays a draft. I didn't change anything else.