Distinguish pinned workflow status from message previews

[bb-slop-cop]

Human comments

What was wrong

The workflows plugin independently renders a message directive and an active-run composer banner for the same running workflow. Both surfaces used the same primary label and status content, so adjacent instances had no persistent identity distinguishing the pinned live status from the historical message preview. The verified reproduction and root-cause report is https://get-bb.github.io/reports/issues/3162.html.

What changed

The composer-only workflow card now shows a compact Active prefix and uses an Active workflow: <name> accessible label. The message preview keeps its existing Workflow: <name> identity. A component regression test renders both registrations for one run and verifies the distinction. There are no wire, protocol, CLI, guide, dependency, or data changes.

How you verified

• Before the production change, the focused regression test failed because the composer card did not contain Active.
• After the change, the focused regression test passed.
• pnpm exec turbo run test typecheck --filter=bb-plugin-workflows passed: 223 tests and the package typecheck.
• The real production components were rendered together in the repository Ladle harness; browser inspection confirmed one Workflow: Review the release preview and one visible ACTIVE composer card with the Active workflow: Review the release accessible label.
• pnpm exec oxfmt --check plugins/workflows/src/app.tsx plugins/workflows/src/app.test.tsx and git diff --check passed.
• The branch changes 56 total text lines across two files and contains no binary changes.
• The public-model scan was clean for the push range.
• The verify-bb inventory check remains blocked by a pre-existing unmapped browser CLI family on the trusted base; the affected workflows UI recipe was verified through the focused test and production-component browser harness without starting a workflow.

Fixes #3162

AGENT GENERATED

[SawyerHood]

Closing because adding an Active label distinguishes the two workflow cards but does not remove the duplication reported in #3162. A replacement should address the intended workflow-card behavior. This closure does not mark the underlying issue as fixed.

Closing at Sawyer’s request following the relevance review against main at b9fdeec.

AGENT GENERATED