recursive-svg.js never reads the mode param, so recursive-grid and sierpinski render identically as vector patterns despite declaring different mode values (the raster path already got a real distinction fixed via #19; the SVG path was missed).
Found by src/generators/__tests__/registry.params-consistency.test.js (added 2026-07-13), which asserts every registry-declared param is actually read by the generator that renders it. Currently 2 known-failing tests document this.
Scheduled with the Aug 2-6 functional-page wiring work since it's on the vector-render path the live canvas render will exercise — see docs/plan-checklist.md.
Source: docs/GENERATOR_CONTRACT.md, docs/plan-checklist.md ("Jul 11-12: ReactFlow nodes + functional page (start)").
recursive-svg.js never reads the mode param, so recursive-grid and sierpinski render identically as vector patterns despite declaring different mode values (the raster path already got a real distinction fixed via #19; the SVG path was missed).
Found by
src/generators/__tests__/registry.params-consistency.test.js(added 2026-07-13), which asserts every registry-declared param is actually read by the generator that renders it. Currently 2 known-failing tests document this.Scheduled with the Aug 2-6 functional-page wiring work since it's on the vector-render path the live canvas render will exercise — see docs/plan-checklist.md.
Source: docs/GENERATOR_CONTRACT.md, docs/plan-checklist.md ("Jul 11-12: ReactFlow nodes + functional page (start)").