Rename queued messages to follow-ups

[brsbl]

Human comments

What was wrong

The queued-message stack used the internal state label “Queued” as its visible heading and throughout its accessible names. That made the surface sound implementation-led, gave secondary chrome too much visual weight, and left sighted and assistive-technology terminology inconsistent once the heading changed.

What changed

• Rename the visible stack heading to “Follow-ups” and reduce it from medium to normal weight.
• Use follow-up terminology consistently across the section label, expand/collapse and drag controls, row actions, action menu, and inline editor.
• Update focused component and thread-detail assertions for the new accessible names.
• Keep internal queued-message APIs, types, and persisted contracts unchanged.

How you verified

• git diff --check
• Chrome for Testing 151: exact branch web app at 1440×1000, using the same persisted thread, route, queued item, composer state, and viewport on merge base 8d926c312 and PR head 59044be0f.
• Local CI-equivalent tests were not run per repository policy; focused assertions were updated for remote CI.

Before — merge base

After — PR head

BB-Thread-ID: thr_yyjgejjc8w

AGENT GENERATED