🤖 feat: show per-task kinds and intents in multi-task task_await summaries

[ibetitsmike]

Summary

Multi-task task_await completion rows previously said only N tasks completed, hiding what actually finished. The collapsed row now lists each completed task's kind and spawn intent/title: a single detail stays inline in the header (unchanged from #3793), while multiple details render as stacked truncated lines below it.

Background

#3793 added the kind · intent/title detail for single-task awaits but deliberately kept multi-task summaries count-only. In practice that forces expanding every multi-task await row to see which background work landed. A comma-joined inline list was considered first but truncates quickly and reads poorly because , and · separators compete, so multiple details stack as one line per task.

Implementation

• The single-task detail computation now runs for every completed result, reusing the same kind derivation (bash:/wfr_/wst_ handles or spawn agentId) and sanitizeDisplayableModelIntent fallback chain per task.
• With exactly one detail it remains the inline header suffix; with more, a stacked list renders below the header, gated to collapsed + success state since the expanded view already shows per-task result rows.
• Tasks with no resolvable kind/intent/title are skipped rather than rendering empty lines.

Validation

• Storybook screenshots (built Storybook, dark theme) comparing inline comma-joined vs stacked layouts for 1/2/3-task completions; stacked layout verified to align with header text and truncate per line.

---

Generated with mux • Model: anthropic:claude-fable-5 • Thinking: xhigh

[ibetitsmike]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 3dfade24d4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".