#3466 fix(cli): tell the two trace init project dead ends apart (PFM-7409)

Fixes the misleading error chainloop trace init shows when the caller can neither create a project nor add a workflow to an existing one.

The single message blamed the projects the caller can see for not accepting a workflow, which describes nothing when the caller sees no project at all — the case reported in PFM-7409, an organization the caller has no project membership in.

It is now split into the two distinct dead ends:

• no project membership: you do not belong to any project in this organization, and cannot create a new one; ask an administrator to add you to one
• projects visible but read-only: you can only view the projects in this organization, and cannot create a new one; ask an administrator for write access to one

The workflow wording is gone from both, since it named an internal permission rather than anything the user asked for at that point in the wizard.

AI assistance: this change was produced with Claude Code; the commit carries an Assisted-by: Claude Code trailer.

🤖 Generated with Claude Code