refactor(frontend): abstract user-prompted state changes into a reducer

[cpu-ram]

Below is a tentative list of reference materials to review prior to selecting an implementation.

https://react.dev/learn/extracting-state-logic-into-a-reducer
https://react.dev/reference/react/useReducer
https://react.dev/learn/scaling-up-with-reducer-and-context
https://react.dev/learn/you-might-not-need-an-effect
https://react.dev/learn/keeping-components-pure

https://react.dev/learn/queueing-a-series-of-state-updates
https://react.dev/learn/updating-objects-in-state
https://react.dev/learn/updating-arrays-in-state

https://redux.js.org/tutorials/essentials/part-1-overview-concepts

[cpu-ram]

I read the extracting-state-logic article, solved the sample exercises. Seems quite applicable.

[cpu-ram]

I read the scaling-up-with-reducer-and-context article — there's nothing new to me in it, I have implemented all of it in TST.

[cpu-ram]

I read the keeping-components-pure article. Nothing new here.

[cpu-ram]

Read queueing-a-series-of-state-updates, all clear.

[cpu-ram]

Read https://react.dev/learn/responding-to-events — good manual on event propagation.

Read the famed you-might-not-need-an-effect. Good material! Covers many principles I should review in all new future work. Among other things, it covers useMemo() and cleanup functions meant to prevent data corruption from race conditions.

you-might-not-need references https://react.dev/learn/synchronizing-with-effects#fetching-data — I read that too, very informative.

Next I will do the exercises for you-might-not-need-an-effect and synchronizing-with-effects, and then I will read through the Redux Essentials manual.