react-doctor/no-event-trigger-state

Delete the trigger state (`useState(null)` plus the `useEffect` that watches it) and call the side-effect (`post(...)` / `navigate(...)` / `track(...)`) directly inside the event handler that previously called the setter. State should not exist purely to schedule effect runs

Validation prompt

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

Fires when a useState X has setters called ONLY from JSX event handlers AND X isn't read during render AND there's a useEffect([X]) whose body is one IfStatement guarding on X (truthy, !== null/undefined, === Literal, .length, or !) whose consequent invokes an event-shaped side effect. Confirm the state is only an accidental trigger. Debouncing/coalescing, post-commit DOM work, and intentionally observing the committed result are behaviorally different and should be suppressed.

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.

If one event exclusively owns the work and synchronous timing is equivalent, delete the trigger state and watching Effect and call the side effect from that handler. Preserve the Effect or replace it with an explicit scheduler when it intentionally debounces, coalesces, observes committed DOM, or must run after React commits. Test timing-sensitive behavior before removing the state boundary. See https://react.dev/learn/you-might-not-need-an-effect#sending-a-post-request

Repository-wide copy prompt

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