Files
feuerwerk/tools
adminandClaude Opus 5.5 6c62aa45d5 Pick Crate 57 through the menu search in e2e 57 (#258)
CI has been red since f84defb. In the full run the scene holds more
than 40 filler objects from module 11. The object menu is height
limited and scrolls, and overlayTexts() only returns the visible rows.
Aim 57 and Crate 57 sit at the end of the scene and were never visible.

- Check None right after opening the menu, it is always the top row.
- Type 57 into the search field before looking for Aim 57 and
  Crate 57 and before clicking Crate 57, like module 7 does with the
  parent picker.
- No product code changes.

Tests:
- Reproduced with modules 1-11 and 57: the old test fails with the
  same cut-off list and "nothing to click: Crate 57" as CI.
- New test: ALL PASSED - 405 checks, all 5 checks of 57 green.
- The full run could not be verified locally. Module 12 fails here
  because the local server holds leftover uploaded images. It is
  green in CI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-28 17:57:37 +02:00
..
Plugins belong to the project, and they load before it: the project file gained the field plugins: ["demo-plugin.js"] (default empty, no formatVersion bump), the Plugins tab's switch writes into it as an ordinary undo step (SetPluginActiveCommand) instead of into a server-wide plugins.json, and the start order is turned around - startPlugins only fetches the list of files, then editor.boot() runs and ProjectStore.load(id, prepare) hands the raw JSON through before it is deserialized, where pluginsOf(raw) reads the list and PluginManager.syncTo() activates exactly those; that is the point of the issue, because what a plugin registers has to stand there before normalizeGraph would throw it away as unknown (#126, #127), a project switch first stops what the new project does not name and then starts what it does, a file the server does not have is passed over silently, and after signing out the manager is dead so a late event cannot start anything in a torn-down session; on the server plugins.json, PluginStore::setActive, isActive, the route PUT ?r=plugins/{file} and the 403 for inactive modules are gone and GET ?r=plugins only answers {file,bytes,updatedAt}, which makes every plugin file fetchable - the consequence accepted in #117, written down in the wiki for #115 and #116; publishPlugins(root) only copies files now, the seeder switches the demo plugin on in the fixture project, and the Plugins tab carries a puzzle piece as its icon while only a plugin's own tab still goes without one (the knob and the socket are cubic curves, not arcs, which Pixi's parser draws as a spike after an L); 3 new e2e checks in module 38 and 5 new unit tests cover the project as the owner of the switch, its undo, the order, pluginsOf against crude input and an unknown file name (#119)
2026-09-20 14:24:27 +02:00