Remove the login prompt from taskless init #402

Remove the login prompt from taskless init

taskless init currently stops to ask "Log in to taskless.io now?", after an "Authentication" note explaining that authenticated rules keep conversation history. In 0.11.2 this is sE(), called from the init flow (dist/index.js ~17904–17989).

Why remove it

• Every question in first-run setup is friction. The CLI should get someone to a working check with as few decisions as possible.
• The CLI isn't where we upsell. With the paid-cloud launch (taskless/taskless#206–chore(ci): tag releases, and judge a review by what it posted #210), the free tier is local-only: authoring and running sg and vale rules needs no account. Asking a free user to log in during setup sells them something they don't need yet.
• Login is still reachable when it's needed. taskless auth login stays, and the commands that need an account already say so, e.g. create-remote-rule "(login)" and the auth-required errors.

Proposed change

• Drop the "Log in to taskless.io now?" confirm and its explanatory note from taskless init.
• Keep taskless auth login and the existing "run taskless auth login" guidance on commands that need authentication.
• Keep the setup summary and telemetry consistent. init currently reports prompted / loggedIn; prompted would always be false.

Out of scope

Anything about how paid accounts authenticate for remote generation or runtime rules. That path is unchanged.