fix(studio): restore editor control bindings for React 19

[zedarvates]

Audio effects, asset filtering, canvas controls and keyframes referenced corrupted local names and failed on render or interaction. Restore their real state, props, existing editor store/action and callbacks. Also fix the general Templates category's null marker and stop keyframe rendering from sorting the parent's array.

Partial follow-up to #74, draft stacked on #77 at b0018678cc7ca67e229264d0b6bb6dc1eb6e3a3a. Current head: af83b71145191bb964f2109261adbe15234cdd87. No merge or commercial availability is claimed.

The scheduling helpers preserve exact callback argument tuples and browser-compatible timer types. Their JavaScript is byte-identical after type erasure. Correct the old throttle test's trailing-call assumption to match the existing leading-only implementation; restore real timers after each test.

A new strict audio/keyframe/scheduling contract exposed Lucide 0.468.0 importing ReactSVG, absent from React 19 declarations (upstream issue). Upgrade only the UI's Lucide requirement/lock to 0.474.0, the first inspected published version after 0.468.0 that removes the import. All other locked versions and optional/platform entries, root/Electron locks and full application compiler settings/inclusions remain unchanged. No fake React export or relaxed compiler flag is added.

Local evidence — clean Studio-only installation, Node 24.19.0 / npm 11.9.0:

• Eight new editor interaction tests fail before the component repairs and pass afterwards. Real hooks, Zustand stores, Radix, DnD and icons are retained; graphics boundaries are substituted.
• All 24 focused tests in five files pass, as do the shared-library audit (5,713 bindings in 966 files), both existing strict bridge programs and the new strict control program with negative argument-type cases.
• The production bundle succeeds.
• Full unchanged tsc -b still fails with 1,206 diagnostics, down from 1,249 on the exact fix(studio): restore corrupted import bindings and paths #77 base in the same setup. No diagnostic remains in the five modified production source files. Earlier local/hosted counts used different installations and are separate measurements.

Current-head hosted evidence — af83b71145191bb964f2109261adbe15234cdd87:

• Renderer Node 22.12.0 and Node 24.19.0 succeed: clean installation, the shared-library audit, all three strict contract programs, 24 tests in five files and production bundles.
• Node 24 also passes the bounded fresh Chromium launcher check with providers/backends blocked. Browser steps on Node 22 are skipped by matrix design.
• Full application types fails, exit 1, with 1,274 diagnostics. The diagnostic artifact is retained. The renderer workflow therefore concludes failure; successful focused jobs do not complete Creative Studio build blockers: missing modules and renderer type contracts #74.
• Shared controls CI succeeds on the same head.
• No SonarCloud check/report or commit-status context is exposed through GitHub on this head. fix(studio): restore shared editor controls and root provider wiring #75's older passed gate is separate evidence; no security-alert closure is inferred.

Review and remaining blockers: review the restored control bindings, template separation, immutable keyframe rendering, leading-only scheduling contract and minimal Lucide upgrade. Zero-error full application compilation, domain/module/optional Electron contracts, real media/project/generation fixtures and the primary Electron launcher remain unfinished. Displayed zoom and preview callbacks do not establish canvas zoom geometry, media playback or processing. The #70/#63/#73 dependency combination has not been retested with this batch.

Scope and commands.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud