Consistent handling of work tags for rename, delete, and overriding state

[everettbu]

Mirror of facebook/react#35740
Original author: eps1lon

---

Mostly to make it easier to reason locally about this code. Rename and delete relied implicitly on inspectElementRaw to only show state for Class Components but there was already a TODO to expand that which would've crashed rename and delete.

Flagged by Claude + Opus 4.6 (which didn't make the connection with inspectElementRaw and assumed this fixes a crash).

[greptile-apps]

Greptile Overview

Greptile Summary

This change makes delete, rename, and override of "state" consistent with the set of Fiber tags for which DevTools actually exposes state in inspectFiberInstanceRaw. Concretely, the state-editing message handlers now gate the mutation/forceUpdate() calls behind explicit fiber.tag checks, preventing crashes if inspectElementRaw is expanded to show state for more non-class tags in the future.

The change is localized to the backend Fiber renderer message handling in packages/react-devtools-shared/src/backend/fiber/renderer.js and does not affect the frontend UI beyond avoiding invalid state operations.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• The change is small, self-contained, and adds conservative guards around state mutation paths to align with existing inspection behavior; no new APIs or external integrations are introduced.
• No files require special attention

Important Files Changed

Filename	Overview
packages/react-devtools-shared/src/backend/fiber/renderer.js	Adds explicit fiber tag checks for state delete/rename/override so these operations only run for class(-like) components where state is exposed.

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[everettbu]

Upstream PR was closed or merged. Code is synced via branch mirror.