react-doctor/advanced-event-handler-refs

Store the handler in a ref and have the listener read `handlerRef.current()`: the subscription stays put while the latest handler is always called

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires when a useEffect has an identifier in its deps array AND that same identifier is passed as the second argument of a subscription-shaped call inside the body: addEventListener, subscribe, addListener, on, watch, listen, or sub from SUBSCRIPTION_METHOD_NAMES. The rule names the registered handler in the message.

Suppress when: the listener genuinely must re-bind every render because it captures a different DOM target each time.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

On React 19.2+, use useEffectEvent for a non-reactive callback that is declared and called by the Effect. Otherwise either keep the honest resubscription or use a stable wrapper backed by a ref whose current value is updated with timing appropriate to the source (often a layout effect for browser events). Remove only the handler dependency: retain target, options, and every other value that controls subscription setup, so the Effect still re-subscribes when those change. See https://react.dev/learn/separating-events-from-effects

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.