[BUG/UX] Approval cards show worker slug (content-pub-cp2) + leak token-source & raw 429/channel errors instead of a clean summary

[federicodeponte]

Summary

The approval cards expose internal plumbing and use the worker slug as the title, instead of a clean human-readable summary. This makes the approval surface confusing and unprofessional for a reviewer.

What's wrong (see screenshot)

1. Title is the worker slug — e.g. content-pub-cp2. A reviewer sees a meaningless internal name. It should be something like "Publish 'belong' to YouTube + LinkedIn" (action + target + channels).
2. Internal token routing leaks — the preview shows Token source per account: personal1:input, personal2:input. This is implementation detail; it should not be in the user-facing approval.
3. Raw infra errors leak into the approval — the preview includes raw JSON like account personal-1: could not resolve Buffer organization: {"http_error": 429, "body": "{\"errors\":[{\"message\":\"Too many requests... RATE_LIMIT_EXCEEDED ... 24h\"}]} and channel 'youtube' not connected in personal-2. A failed-config run should NOT produce a user-facing "approval" full of stack/JSON noise — it should either fail cleanly (no approval) or show a short human error.

Expected

• Approval title: human-readable action summary, not the worker id.
• Preview: a clean summary (what will post, to which channels, when) with the caption — no token-source internals, no raw HTTP/JSON error dumps.
• Config/infra failures should not surface as normal approvals; if a run errors during propose, mark it failed (not "pending approval") so the share link only lists real, approvable items.

Screenshot

Filed via dogfooding the SF-vlog content pipeline.