[Bug] ESLint react-hooks plugin upgrade (7.0.1→7.1.1) breaks CI with new set-state-in-effect rule

[realproject7]

Problem

eslint-plugin-react-hooks was bumped from 7.0.1 → 7.1.1 in package-lock.json during the airdrop PR batch. Version 7.1.1 introduces a new react-hooks/set-state-in-effect rule that flags setState() calls directly inside useEffect bodies. This breaks CI for 3 components that previously passed.

Root Cause

The lockfile update happened during npm install @openzeppelin/merkle-tree (PR #893). The semver range ^7.0.0 resolved to 7.1.1 which includes the stricter rule.

Affected Files

File	Line	Issue
src/components/RatingWidget.tsx	77	setSelectedRating() inside useEffect
src/components/AgentManage.tsx	129	setEditName() etc. inside useEffect
src/hooks/useDraft.ts	43	setRestored() inside useEffect
src/components/ReadingMode.tsx	22	Unused storylineId variable (warning, not error)

Fix

Already applied in PR #917 (hotfix branch task/913-fix-metadata-type):

• RatingWidget: Replaced setState-in-effect with ref comparison pattern (compare prevMyRatingRef to detect changes during render)
• AgentManage: Wrapped metadata field population in queueMicrotask()
• useDraft: Wrapped setRestored(true) in queueMicrotask()
• ReadingMode: Added eslint-disable comment for unused destructured prop

Note

This ticket is tracked for record-keeping. The fix is already included in PR #917. No additional work needed unless PR #917's approach needs revision.

References

• eslint-plugin-react-hooks changelog: set-state-in-effect rule added in 7.1.x
• PR [#913] Fix TypeScript build errors blocking all deployments #917 contains the fix commits

[realproject7]

Fixed via PR #917 — lint errors resolved by the same hotfix commit.