feat(cli): claw -i files the ticket through the server

[EdmondDantes]

What

Folds the last frequent CLI writer behind the server. claw -i stops opening the project db and running triage in its own process — it hands the ticket to the server and returns.

• ServerClient::openIssue() — POST /api/projects/{key}/issues with {"title"}, returns the new id from the 201 (400 surfaces the server's reason).
• WorkflowMode::createIssue() — resolves the project key (read-only), ensures a server (autospawning one if none answers), posts the title, prints OK — issue #N opened.
• Removed the CLI's inline triage() (and its now-unused imports); the server already triages behind its create response.

Behaviour

claw -i "…" returns immediately with the confirmation — the server opens the ticket and triages it behind the response, exactly as the dashboard's create button already does, so a model being slow or down never costs the user the ticket or their prompt. The old inline output (issue detail + triage verdict) is gone by design; the verdict lands on the board/claw log.

claw -c stays local — deliberately

Project creation is not routed through the server: it is the bootstrap that creates the very db a server later opens, it must work before any server exists, and the server's POST /api/projects only creates folders inside the workspace while -c registers any folder. Making it server-dependent would break that for no gain — -c is a one-shot local write with no concurrent writer.

Verified live

claw -i "…" on a cold workspace: autospawned a server, opened issue #10, printed OK — issue #10 opened., and returned in the same second (triage running behind it on the server).

Checks

composer qa green — cs, PHPStan level 8, Testo (463 tests). New tests: openIssue returns the id and carries the title; a 400 surfaces the server's reason.