PR Custody

docs: correct enum-rename slugs in 2026-03-28 changelog

@venkat82checks n/achecks…docs/fix-pr17949-enum-renames → next1 files · +1329 −153review: @Sushmithamalleshupdated 1mo ago

GitHub

▸Description· 3 comments · 1 noise

Summary

Follow-up to #2941. The "Renamed enum slugs" section of the 2026-03-28 changelog (docs/content/changelog/03-28-26-tool-consolidation-enum-renames.mdx) lists 347 Old Enum → New Enum pairs that don't line up with the actual class-name-derived slugs delivered by mercury PR #17949 (commit 12d585aa7e, "fix: rename low-usage action class names to cleaner slugs"). This PR replaces that section with the verified table.

How slugs are formed

enum = inflection.underscore(cls.__name__).upper()
slug = enum if enum.startswith(TOOLKIT) else f"{TOOLKIT}_{enum}"

Slug is derived from the class name of the action, not the file name and not the name attribute. (Source: mercury/tools/_base/action.py set_metadata / set_tool.)

Audit results vs. existing docs section

Category	Count
Original docs pairs that match PR #17949 exactly	291
Pairs with wrong New Enum (PR's actual new differs)	1
Pairs whose old class never existed in any commit	5
Pairs that refer to renames done in other PRs (or tool removals)	20
Pairs claiming a rename that never happened (old class still present at HEAD with original slug)	30
Real PR #17949 renames missing from docs	1,217
Total entries originally listed	347
Total entries in this rewrite	1,509

Notable corrections

SUPABASE_UPDATES_PROJECT_S_SUPAVISOR_CONFIG → docs said SUPABASE_UPDATE_SUPAVISOR_CONFIG; actual is SUPABASE_UPDATE_PROJECT_SUPAVISOR_CONFIG (class UpdateProjectSupavisorConfig at apps/supabase/actions/generated/updates_project_s_supavisor_config.py).
SLACK_DELETE_MESSAGE is not a real slug. The chat-deletion action is class DeletesAMessageFromAChat, slug SLACK_DELETES_A_MESSAGE_FROM_A_CHAT. Removed from the table.
All eight PIPEDRIVE_*A_* entries (ADD_A_DEAL, ADD_A_NOTE, DELETE_A_PERSON, GET_DETAILS_OF_A_PERSON, LIST_PARTICIPANTS_OF_A_DEAL, UPDATE_A_DEAL, UPDATE_A_LEAD, UPDATE_A_PERSON) still exist at HEAD with their original slugs — removed from the renames table.
14 Slack entries that claimed renames (e.g. SLACK_FETCH_TEAM_INFO → SLACK_GET_TEAM_INFO) were never executed; class names still match the original slug. Removed.
Whole toolkits previously omitted that PR #17949 actually renamed: PostHog (179), Trello (63), Salesforce (48), Vercel (39), Twitter (35), Google Analytics (25), Dropbox (18), Icypeas (5), Reddit (2), YouTube (2), Apollo, Facebook, Hyperbrowser, Telegram (1 each).

Front-matter description / intro paragraphs

Updated count from "1,545 enum slugs across 24 toolkits" → "1,509 enum slugs across 37 toolkits" to match the rewritten table.

Out of scope

This PR does not change the "Deprecated tools" or "Consolidated (removed) tools" sections — those describe a different consolidation effort and are unrelated to the class-rename audit.

Test plan

Spot-check 10–20 random entries from the rewritten table against the actual class definition in mercury (apps/<toolkit>/actions/) to confirm inflection.underscore(cls.__name__).upper() matches the listed New Enum.
Confirm <Accordions>...</Accordions> block renders correctly on docs.composio.dev preview.
Confirm none of the 30 "rename never happened" entries listed in the audit show up in the new table.

@claude[bot]agent1mo ago

Claude finished @venkat82's task in 4m 34s —— View job

Review

I checked the PR against docs/.claude/agents/docs-reviewer.md (the docs-reviewer prompt focuses on whether a developer copying from the docs would get stuck or be misled).

Read docs/.claude/agents/docs-reviewer.md review criteria
Run git diff origin/next...HEAD
Apply the review checklist
Post feedback

Verdict: Looks good. The rewrite addresses the only kind of issue this changelog can mislead developers about: an Old → New enum mapping that doesn't match what the SDK actually accepts. A few observations below — none blocking.

What I verified

Counts agree across the doc. Frontmatter description (1,509 enum slugs across 37 toolkits), the section-intro paragraph (1,509 ... across 37 toolkits), and the actual table all match: 37 Accordion blocks under ## Renamed enum slugs, summed (N renamed) titles = 1,509, and grep -c "^| \" = 1,509` inside that section.
MDX structure is sound. <Accordions> open/close = 3/3 and <Accordion> open/close = 72/72 across the file. No new components introduced — pure content change, so Twoslash/MDX build risk is minimal.
Frontmatter valid. title, description, date present; date is YYYY-MM-DD.
No duplicate Old enums and no duplicate New enums in the renames section. No row where the toolkit prefix on the Old side disagrees with the New side.
Spot-checked the explicit corrections from the PR description:

▸ 1 bot/status comment hidden

@vercel[bot]1mo ago

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	May 9, 2026 2:23pm

loading diff…

Summary

How slugs are formed

enum = inflection.underscore(cls.__name__).upper() slug = enum if enum.startswith(TOOLKIT) else f"{TOOLKIT}_{enum}"

Slug is derived from the class name of the action, not the file name and not the name attribute. (Source: mercury/tools/_base/action.py set_metadata / set_tool.)

Audit results vs. existing docs section

Category

Count

Original docs pairs that match PR #17949 exactly

291

Pairs with wrong New Enum (PR's actual new differs)

Pairs whose old class never existed in any commit

Pairs that refer to renames done in other PRs (or tool removals)

Pairs claiming a rename that never happened (old class still present at HEAD with original slug)

Real PR #17949 renames missing from docs

1,217

Total entries originally listed

347

Total entries in this rewrite

1,509

Notable corrections

SUPABASE_UPDATES_PROJECT_S_SUPAVISOR_CONFIG → docs said SUPABASE_UPDATE_SUPAVISOR_CONFIG; actual is SUPABASE_UPDATE_PROJECT_SUPAVISOR_CONFIG (class UpdateProjectSupavisorConfig at apps/supabase/actions/generated/updates_project_s_supavisor_config.py).

SLACK_DELETE_MESSAGE is not a real slug. The chat-deletion action is class DeletesAMessageFromAChat, slug SLACK_DELETES_A_MESSAGE_FROM_A_CHAT. Removed from the table.

All eight PIPEDRIVE_*A_* entries (ADD_A_DEAL, ADD_A_NOTE, DELETE_A_PERSON, GET_DETAILS_OF_A_PERSON, LIST_PARTICIPANTS_OF_A_DEAL, UPDATE_A_DEAL, UPDATE_A_LEAD, UPDATE_A_PERSON) still exist at HEAD with their original slugs — removed from the renames table.

14 Slack entries that claimed renames (e.g. SLACK_FETCH_TEAM_INFO → SLACK_GET_TEAM_INFO) were never executed; class names still match the original slug. Removed.

Whole toolkits previously omitted that PR #17949 actually renamed: PostHog (179), Trello (63), Salesforce (48), Vercel (39), Twitter (35), Google Analytics (25), Dropbox (18), Icypeas (5), Reddit (2), YouTube (2), Apollo, Facebook, Hyperbrowser, Telegram (1 each).

Front-matter description / intro paragraphs

Updated count from "1,545 enum slugs across 24 toolkits" → "1,509 enum slugs across 37 toolkits" to match the rewritten table.

Out of scope

This PR does not change the "Deprecated tools" or "Consolidated (removed) tools" sections — those describe a different consolidation effort and are unrelated to the class-rename audit.

Test plan

Spot-check 10–20 random entries from the rewritten table against the actual class definition in mercury (apps/<toolkit>/actions/) to confirm inflection.underscore(cls.__name__).upper() matches the listed New Enum.

Confirm <Accordions>...</Accordions> block renders correctly on docs.composio.dev preview.

Confirm none of the 30 "rename never happened" entries listed in the audit show up in the new table.

Project

Deployment

Actions

Updated (UTC)

docs

Ready

Preview, Comment

May 9, 2026 2:23pm

@claude[bot]agent1mo ago

Claude finished @venkat82's task in 4m 4s —— View job

Review (re-run after `8dea37c`)

I checked the PR against docs/.claude/agents/docs-reviewer.md (the docs-reviewer prompt focuses on whether a developer copying from the docs would get stuck or be misled). The new commit 8dea37c drops 64 rename rows whose target actions were later removed by mercury PR #18496, and re-aligns 11 stale slugs to match HEAD. Re-verifying the file at HEAD:

Read docs/.claude/agents/docs-reviewer.md review criteria
Run git diff origin/next...HEAD
Apply the review checklist
Post feedback

Verdict: Looks good. The latest commit cleanly addresses the only category of issue this changelog can mislead developers about — Old → New mappings whose New side doesn't match what the SDK accepts today. A few small notes; nothing blocking.

What I verified at HEAD

All counts agree across the doc. Frontmatter description (1,445 enum slugs across 37 toolkits), intro paragraph at line 358 (1,445 ... across 37 toolkits), 37 <Accordion> blocks under ## Renamed enum slugs, sum of (N renamed) titles = 1,445, and grep -c "^| \"` inside the section = 1,445.
MDX structure intact. <Accordions> open/close = 3/3, <Accordion> open/close = 72/72. Pure content change — no new components.
No duplicate Old enums and no duplicate New enums in the renames section.
The 64 dropped rows reconcile exactly with the commit message. Truly-dropped (i.e. removed and not re-added under reordering) per toolkit: Stripe 37, Shopify 18, Salesforce 7, Pipedrive 1, Attio 1 → total 64 = 1,509 − 1,445. ✓
All 11 HEAD-aligned slugs from the commit message are present at HEAD with the new target: GITHUB_CHECK_PERSON_FOLLOWED_BY_AUTH_USER, GITHUB_EXPORT_SBOM_FOR_REPO, GITHUB_GET_ALL_DEPLOYMENT_PROTECTION_RULES_FOR_ENV, OUTLOOK_DELETE_USER_MAIL_CHILD_FOLDER_MSG_EXT, HUBSPOT_RESTORE_EMAIL_REVISION, BOX_LIST_HOLD_FILE_VERSIONS, BOX_UPDATE_BARRIER_SEGMENT, GOOGLEDRIVE_GET_FILE_PROPERTY, GOOGLEDRIVE_LIST_FILE_PROPERTIES, GOOGLEDRIVE_UPDATE_FILE_PROPERTY, POSTHOG_PROJECT_FUNNEL_ADVANCED_ANALYTICS.
Intro examples still resolve. DELETE_A_GIST → DELETE_GIST, GET_A_CODESPACE_FOR_THE_AUTHENTICATED_USER → GET_CODESPACE, ADD_MEMBERS_FOR_PROJECT → ADD_MEMBERS_TO_PROJECT all appear (with toolkit prefix) in the rewritten tables.
Frontmatter valid. title, description, date (YYYY-MM-DD) all present.

Non-blocking observations (optional, won't mislead a developer)

Section intro at line 358 says "more concise." Of the 1,445 entries, ~234 (16%) actually lengthen the slug — concentrated in Trello (32), Vercel (22), Salesforce (19), Shopify (~16), and a long tail. The data is still faithful to mercury PR #17949 (slug = inflection.underscore(cls.__name__).upper()), but more consistent / follow class-name conventions would match the data better than more concise. Same observation as my prior review; tighter now (since the heaviest verbose-to-verbose Stripe/Shopify rows were dropped) but still applies. Optional.
PR description has Twitter (35); file has Twitter (36 renamed) with 36 actual entries. The file is internally consistent — only the PR description is off by one. No fix needed in the doc.
Out of scope but flagging again for a follow-up PR: the Deprecated tools section at line ~197 still has PIPEDRIVE_ADD_A_NOTE → PIPEDRIVE_PIPEDRIVE_ADD_NOTE and PIPEDRIVE_GET_DETAILS_OF_A_PERSON → PIPEDRIVE_PIPEDRIVE_GET_PERSON (double PIPEDRIVE_ prefix on the right side). The PR explicitly excludes that section. Pre-existing — not a blocker here.

· branch: docs/fix-pr17949-enum-renames ·

docs: correct enum-rename slugs in 2026-03-28 changelog

Summary

How slugs are formed

Audit results vs. existing docs section

Notable corrections

Front-matter description / intro paragraphs

Out of scope

Test plan

Review

What I verified

Summary

How slugs are formed

Audit results vs. existing docs section

Notable corrections

Front-matter description / intro paragraphs

Out of scope

Test plan

Review

What I verified

Non-blocking observations

Review (re-run after `8dea37c`)

What I verified at HEAD

Non-blocking observations (optional, won't mislead a developer)

Review (re-run after `70be86c`)

What I verified at HEAD

Non-blocking observations (carried over from prior reviews)

Summary

How slugs are formed

Audit results vs. existing docs section

Notable corrections

Front-matter description / intro paragraphs

Out of scope

Test plan

Review

What I verified

Summary

How slugs are formed

Audit results vs. existing docs section

Notable corrections

Front-matter description / intro paragraphs

Out of scope

Test plan

Review

What I verified

Non-blocking observations

Review (re-run after 8dea37c)

What I verified at HEAD

Non-blocking observations (optional, won't mislead a developer)

Review (re-run after 70be86c)

What I verified at HEAD

Non-blocking observations (carried over from prior reviews)

Review (re-run after `8dea37c`)

Review (re-run after `70be86c`)