docs(audiences): document View Claygent column-header shortcut

[george-dilthey]

What changed

Added a paragraph to docs/audiences.md documenting the new "View Claygent" column-header dropdown option in Companies audiences. The new ### Claygent-managed columns sub-section (inserted between ### Signals and ### Connecting a workflow to a segment) explains that workspace admins and members can click an AI-managed column header in a Companies audience and select View Claygent to open the Claygent configuration that writes to that column.

Why

Deployed in clay-run/clay-base 80f4944...eb65070 (https://github.com/clay-run/clay-base/actions/runs/29392703062). Commit 49259871 ("feat(agt-408): link agent defined fields to agent, #44099") added a new View Claygent dropdown item to AI-managed column headers in Audiences. The feature lets users navigate directly from a Claygent-populated column in a Companies audience back to the Claygent's configuration sidebar. Prior to this deploy, audiences.md contained no mention of Claygent-managed columns or this navigation path.

This deploy also included three other commits — a batched Clickhouse query optimization (backend-only, no docs impact), a correction to MCP tool-hint metadata (readOnlyHint/destructiveHint annotations — internal protocol metadata not documented in customer docs), and an observability logging improvement (internal only). Only the Audiences UI change was customer-facing and undocumented.

Source link(s)

• Deploy workflow: https://github.com/clay-run/clay-base/actions/runs/29392703062
• Compare: https://github.com/clay-run/clay-base/compare/80f4944afa721e622105f05e0f4e5db2f4a2b6f6...eb650700ea5dfeb6c88a4658bbe4cd55ee7e2e58
• Implementing PR: clay-run/clay-base #44099
• Verifier evidence:
  • apps/frontend/src/state/Audiences/fieldToAgentConfigMapping.ts:24 — getAssociatedAccountAgentConfig returns null if isArchived || entityType !== AudienceEntityType.Account || !canManageActions
  • apps/frontend/src/components/Audiences/AudiencesHeaderCell.tsx:146-151 — "View Claygent" DropdownItem rendered only when onViewAssociatedClaygent is defined
  • apps/api/v3/audiences/services/audience-abilities.service.ts — ManageActions granted to WorkspaceAdmin and WorkspaceMember only; no Eppo flag gate
  • Slack: #team-agents-pr-notifications bot (2026-07-15) confirms PR #44099 merged, feature is unflagged

Uncertainties

None. Verifier returned PASS. Feature is live with no flag gate, gated only by the standard canManageActions RBAC permission (WorkspaceAdmin and WorkspaceMember). The three restrictions stated in the doc (Companies only, non-archived, admins/members) are all confirmed at fieldToAgentConfigMapping.ts:24.

Related observations

• The MCP hint fix (commit a29e54a0) corrects readOnlyHint and destructiveHint annotations on several MCP tools. The mcp-settings.md doc covers admin settings, not tool-level metadata — no docs impact.
• The audiences.md does not document the Audiences "Actions" panel (the sidebar UI where Claygents with AUDIENCE_WRITEBACK activation are created and managed). This is a related gap but out of scope for this deploy-triggered PR.
• Five other open PRs also edit docs/audiences.md — none cover Claygent-managed columns: PR docs(audiences): add Databricks as beta import source #1485 (Databricks import), PR docs(audiences): add field-filter warning to Snowflake and BigQuery import steps #1507 (Snowflake/BigQuery field mapping notes), PR docs(audiences): document Salesforce custom object export limitation and workaround #1528 (signal export to Salesforce custom objects FAQ), PR docs(audiences): add FAQ clarifying dedup scope — Audiences only, not Clay tables #1547 (deduplication FAQ), PR docs(audiences): add CSV export workaround via Add to workbook #1550 (CSV export via Add to workbook), PR docs(audiences): document nested sub-field mapping in bulk enrichments #1558 (bulk enrichment sub-field mapping).

Confidence: high

Closes DOC-1166

[linear-code]

DOC-1166