docs: capture remaining 0.24.0 screenshots that need a live environment (approval prompt, first-chat, channel resolution)

[Aaronontheweb]

A handful of 0.24.0 screenshots can't be captured with the hermetic VHS + Docker rig used for the init/config refresh (#69, #70) — they need a live model and/or a real channel workspace with tokens. Tracking the specific gaps here so anyone with that environment can knock them out. Everything else (5-step init, config dashboard + all sub-area editors, existing-install menu/reset) is already captured and shipped.

1. Tool-approval prompt — current 5-button UI

• File: public/assets/approval-prompt.png (refresh in place)
• Used by: channels/slack.md (the "Tool approval" section)
• Current: stale 4-button prompt — Approve once / Approve for this chat / Approve always / Deny.
• Needed: the current 5-button prompt — Once / This chat / Always here / Always anywhere / Deny (0.24.0 split the old "Always" into here/anywhere).
• How: a real Slack workspace with netclaw connected, then a live agent proposing a restricted tool (e.g. shell_execute) so the interactive approval message renders in-thread.
• Bonus: a Discord and/or Mattermost equivalent — both post button approvals (Mattermost only when CallbackUrl is set), and those pages currently have no approval visual.

2. First-chat TUI

• File: screenshots/output/chat-session-start.png (the only remaining <!-- TODO(screenshots) --> in the docs)
• Used by: getting-started/quickstart.md ("First chat session")
• Needed: the chat TUI right after netclaw init auto-launches, showing the agent's intro / personality-bootstrapping question.
• How: a real provider/model — the qwen2:0.5b capture model doesn't produce a representative session. (A stale May-2025 image exists at this path; it should be overwritten.)

3. Channel resolve-before-add, in action

• File: screenshots/output/config-channels-resolve.png (new)
• Used by: cli/config.md (Channels section) — and would enrich the channel pages.
• Needed: the add-channel flow where a typed channel name resolves to a canonical ID (ideally also the rejection of an unresolvable name).
• How: a real Slack/Discord/Mattermost bot token so the resolution probe hits the live platform API.

4. (Optional) Personal-posture wizard counter

• Used by: getting-started/quickstart.md (Personal is the primary audience)
• Current: the embedded wizard shots are a Team/Public run (Step X of 5); the prose already notes Personal is 4 steps.
• Needed (if desired): a Personal-posture run so the counter reads Step X of 4. These would be new filenames — the current init-01/02/05-* files are shared with cli/init.md, which documents the full 5-step flow (incl. the Team-only Enabled Features step).

---

Capture pipeline: new TUI shots go through screenshots/tapes/*.tape → screenshots/output/ (source of truth; npm run copy-screenshots rsyncs to public/). The reusable keystroke flows live in netclaw-dev/netclaw under tests/smoke/tapes/. The approval/chat shots, however, need a real session rather than a tape.

Follow-up to #69 / #70 (epic #55, the post-#1368 screenshot campaign).