docs: document donut totals, table row grouping, bar orientation, and chat-driven dbt pulls - #11603

• Read PR diff and changed files
• Check docs conventions (docs-mintlify/CLAUDE.md)
• Verify accuracy/consistency of each of the 4 doc changes
• Check existing review threads for duplicates (none existed)
• Post review

Docs-only change, all four edits land in /docs-mintlify (correct — /docs is deprecated), no new pages so docs.json is rightly untouched. Prose is concise and in the house voice; no padding. Security/performance/testing focus areas don't apply here. I could not verify the underlying product behavior — cubedevinc/cubejs-enterprise isn't reachable from this checkout — so accuracy claims below are limited to internal consistency with the rest of the docs.

Inline comments

Not inline-able (lines outside the diff)

Medium — table.mdx:282, Row grouping missing from the Style-tab section list. That paragraph enumerates the Style tab as "Headers, Values, Totals, Columns, Borders, and Pagination". The PR adds a seventh section but doesn't add it to the list, so the enumeration is now wrong. Fix this →

Low — pie.mdx:18, Donut blurb is now partly stale. It says the hollow center "can be used to surface a summary value via a [KPI] tile on a dashboard" — true before, but the new ## Total section means the center total is now built in and on by default. A reader hits the KPI-tile workaround first and the native feature ten lines later. Suggest a short pointer to #total there, framing the KPI tile as the option for surfacing something other than the measure total.

Low — bar.mdx:52-54, "with a tooltip explaining why". The sentence tells the reader a tooltip exists but not what it says, which doesn't help someone reading the docs rather than the UI. The two disable conditions are already spelled out in the same sentence, so the clause can just go.

Low — dbt.mdx:389-394, unverifiable behavioral claims. "The agent starts a sync, follows its progress, opens the review branch it creates, and summarizes the generated cubes" is a fairly specific promise about a non-deterministic agent. If the agent doesn't reliably open the branch, this reads as a bug when it doesn't happen. Consider softening to what the agent can do. Also worth confirming the example prompts ("check for dbt updates and pull them", "what happened with my recent dbt syncs?") actually route to the right tools.

Things done well

• Frontmatter description on bar.mdx was updated alongside the body — easy to forget, and it was the only frontmatter that went stale.
• The removed ### Horizontal section's content (long labels, many categories, reading direction) was carried into the new ## Orientation section rather than dropped.
• Internal links check out: /docs/explore-analyze/analytics-chat and /docs/explore-analyze/charts/configuration/color-and-stacking both resolve to existing files.
• Documenting the disabled states (bar orientation, row grouping) is the kind of detail that usually gets skipped and generates support tickets.