react-hooks-js/preserve-manual-memoization

Validate that React Compiler can preserve or exceed the observable guarantees of existing manual memoization

Validation prompt

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

Confirm the exact compiler diagnostic and the intent of the existing useMemo, useCallback, or React.memo boundary. The lint reports when compilation would infer dependencies or memoization behavior that does not preserve the manual memo's guarantees. A dependency can be omitted only when React documents the captured value as stable, such as a state setter or reducer dispatch; do not assume an arbitrary callback or object is stable.

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.

Preserve the existing memoization contract while making its dependencies complete and compiler-compatible. Add the genuinely reactive dependency or refactor the calculation so the same identity and recomputation boundaries remain explicit. Do not delete useMemo, useCallback, or React.memo solely to silence this lint: removal can change observable identity or downstream effect behavior even when compilation succeeds. Verify identity-sensitive consumers and focused tests. See https://react.dev/reference/eslint-plugin-react-hooks/lints/preserve-manual-memoization

Repository-wide copy prompt

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