Provide a focused workflow-creation view

[pmateusz]

Why

/workflow create currently reads like a long agent transcript. Questions, internal protocol tool calls, large structured payloads, and progress information compete for attention. Users need to see the current question and the plan they are reviewing, not the mechanics used to move data between the agent and workflow engine.

What

Replace the raw creation transcript with a compact, purpose-built experience for the brief, clarification, plan review, generation, validation, and completion stages.

Description

submit_questions and submit_result are framework-owned transport tools. Their calls and acknowledgement results are needed by the engine and session history, but they are not meaningful user actions and should not appear as ordinary tool executions in the creation UI. In particular, the blueprint submitted through submit_result can produce a large wall of structured data.

The view should emphasize one active task at a time, retain enough context to understand where creation is, and keep detailed protocol data available in the underlying session/run record for diagnostics. The separate plan-display issue defines the content shown during approval; this issue owns the overall presentation and visibility of framework internals.

Acceptance criteria

• The current creation stage is clearly visible: brief, clarification, plan review, generation, validation, or complete.
• Questions are presented as focused form controls rather than a raw questionnaire payload.
• submit_questions and submit_result calls and acknowledgement results are hidden from the normal creation transcript.
• Hiding the tools does not remove their payloads from engine processing, resume state, or diagnostic records.
• Non-framework tool activity remains visible when it helps the user understand filesystem changes or a failure.
• Plan approval uses the dedicated readable plan view rather than raw JSON.
• Validation retries show a concise explanation of what failed and that a repair is in progress.
• Completion shows the generated workflow path and the checks that passed.
• TUI mode provides the rich view, with a concise plain-text fallback for modes that cannot render custom components.

[pmateusz]

Amount of output generated by internal engine has been significantly reduced. Not user is seeing thinking block and headers from tool calls: submit_result and submit_questions. These headers are rendered due to a patch for tool calls in the kimchi harness.

[pmateusz]