docs(bulk-enrichment): document enrichment run status bar

[george-dilthey]

What changed

Added a ### Monitoring run progress subsection to docs/bulk-enrichment.md at the end of the "Run Setup settings (Audiences)" section. The section describes the new run status bar — a visual progress indicator that appears in the enrichment review panel after an Audiences bulk enrichment has run, showing completed (green) and failed (red) row counts. Clicking the bar navigates to the Runs view for detailed history.

Why

Deploy clay-run/clay-base bbc7ae5...c44698d (https://github.com/clay-run/clay-base/actions/runs/33697370739) shipped commit aec81cac (feat(enrichments v2): adding a run status bar #48798), which added a new AudienceEnrichmentRunStatusBar component to the audience enrichment review sidebar. The feature has no Eppo feature flag gate and is live for all users with Audiences bulk enrichments on Growth and Enterprise plans.

Other changes in the same deploy not documented here:

• c44698d1 — canvas auto-arrange button now scopes to selected nodes when 2+ are selected (verified PASS, no existing canvas docs section to update)
• 8d5b98f6 — audiences CSV export: null fields now render as blank cells instead of \N (bug fix, no prior doc coverage of the old behavior)
• 9c1003e2 / 644e94c9 — claygents browsing in enrichment panel (gated behind ShowClaygentsInWorkflowsEnrichmentsPicker Eppo flag, not documenting per INTERNAL rule)
• a231b218 — CLI agent date filter guidance (internal CLI help text, not customer-facing docs)
• 4d5d4d02 — admin audit log filters (admin-only tooling)
• dc95a634 — campaigns ClickPipes (infrastructure)

Source link(s)

• Deploy workflow: https://github.com/clay-run/clay-base/actions/runs/33697370739
• Compare: https://github.com/clay-run/clay-base/compare/bbc7ae536dcffa18e537d2928772fabbcef7874b...c44698d1fe90da3f3dc6c1b07105f79c5d03b653
• Code evidence (verifier verdict: PASS):
  • /workspace/clay-base/apps/frontend/src/components/TaskAgent/AudienceEnrichmentRunStatusBar.tsx:10-41 — component renders ProgressBarContainer with green (completed) and red (failed) segments; the entire bar is a <button> that calls onViewRuns
  • /workspace/clay-base/apps/frontend/src/components/TaskAgent/AudienceEnrichmentReviewStep.tsx:243-247 — renders <AudienceEnrichmentRunStatusBar> conditionally on runCounts being truthy; no Eppo feature flag anywhere in either file

Uncertainties

None. The verifier confirmed PASS with no feature flag. The component is live for all users with Audiences-enabled workspaces.

Related observations

• The run status bar would also fit naturally in docs/audiences.md under "Reviewing enrichment results" — however, audiences.md has 13 open PRs (PRs docs(audiences): clarify legacy plan access and add why-not-visible FAQ #2345, docs(audiences): add archive cross-reference for Salesforce-deleted records #2348, docs(audiences): document OR filter group with AND exclusion pattern #2349, docs(audiences): document that Lookup in Audiences cannot scope to a segment, add workaround FAQ #2354, docs(audiences): document Salesforce export full-load behavior, API monitoring, and Last Enriched timestamp #2356, docs(audiences): add FAQ for moving audience segments between workspaces #2370, docs(audiences): replace non-existent Continue button with Upsert segment record instructions #2383, docs(audiences): document ad sync beta availability and per-workspace connections #2395, docs(audiences): document enrichment workflow beta option #2415, docs(audiences): note that company fields don't carry through Find People to People records #2432, docs(audiences): clarify Snowflake workflow trigger and add test-workspace note #2478, docs(audiences): document BigQuery SQL query edit behavior and [DELETED] source cleanup #2500, docs(audiences): add FAQ for same-domain company accounts and parent/child relationships #2504), none of which cover this feature but which caused pre_pr_check to flag the file as congested. The run status bar is documented here in bulk-enrichment.md instead, where the "Run Setup settings (Audiences)" section is the natural home.
• Canvas auto-arrange behavior change (commit c44698d1): when 2+ workflow nodes are selected, the bottom-right broom button now arranges only the selected nodes and its tooltip changes to "Auto-arrange selected nodes". Verified PASS by sub-agent. No existing docs page covers the workflow canvas auto-arrange feature — would need a new section in a canvas/workflow editor doc that doesn't yet exist.

Confidence: high

Closes DOC-2295

[linear-code]

DOC-2295