Files
feuerwerk/tools
adminandClaude Opus 5.5 dc6ab17df9
feuerwerk / gate (push) Successful in 6m13s
feuerwerk / suite (push) Failing after 25m55s
Put new graph nodes, comments and groups on the grid (#439)
With the magnet on, only boxes dragged by hand landed on the grid.
Anything new stayed where it was dropped and had to be nudged.

- A node from the palette, from a dropped link or from a dragged
  behavior snaps its corner to the nearest grid point. All three
  ways go through newNode.
- A comment or group from the palette snaps corner and size to
  whole grid steps and keeps its minimum size. A new group is now
  312 x 192, a new comment 216 x 96.
- "Group these N nodes" moves every edge outward to the next grid
  line, so the margin around the nodes only grows.
- The two helpers snapNewBox and snapBoxOutward live in framing.ts.
- Without the magnet nothing changes.

Tests:
- graph-framing 36/36, 7 new. Two broken variants (rounding
  instead of outward, missing minimum size) both red.
- e2e 36 ALL PASSED, 21 checks, new 36f3. Against the old build
  exactly the two new checks were red.
- Gate on atx: 339 files, 5261 tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 00:13:09 +01: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