UECA-React 3.2: a failing test opens the trace where it failed

UECA-React 3.2 introduces several key changes and improvements. A failing test now triggers the display of a trace, showing the specific message or binding that failed. This trace can be viewed using the trace viewer, which is included in the package. The trace viewer can be opened at a specific position using a named address.

The migration guide has been updated to include a rewrite process for apps, involving three phases where agents generate a Markdown document, an LLM wiki, and an implementation plan. Developers are then asked to approve the plan before building the app.

Three agents are responsible for rewriting an app in UECA. They document the app's screens, fields, formats, and business rules, turn the wiki and old code into an implementation plan, and then follow the plan to code, write tests, fix issues, and release notes.

StrictMode is now identical to no StrictMode on both React 19 and 18, and React 18 is available in CI. Errors that previously went unnoticed, such as a failing lifecycle hook under Node, are now caught in the error handler. Additionally, new components like Date, RegExp, Map, and Set are now reported as changes instead of being silently dropped.

The changelog also highlights the importance of upgrading to 3.2.1, as 3.2.0 kept all component modules in production bundles, causing an increase in bundle size. 3.2.1 fixes this issue and includes a new test that builds a small app with Vite and fails if an unused component remains.