Skip to content

Add bolt-count and intensity controls for lightning and storm - #2

Draft
supsup wants to merge 5 commits into
mainfrom
marlow/lattex364-fx-knobs-slice1-20261002
Draft

supsup wants to merge 5 commits into
mainfrom
marlow/lattex364-fx-knobs-slice1-20261002

Conversation

@supsup

@supsup supsup commented Oct 26, 2026 •

Copy link
Copy Markdown
Owner

Adds optional fx.bolts (1-8, default2) and fx.intensity (0-300, default100) for lightning and storm. Omitted options preserve predecessor output bytes. Intensity0 avoids bolt setup and playback; positive intensity changes bounded appearance while reduced motion retains its gentle branch. Mixed keyframe triggers and scroll cleanup remain live.

Verified exact tip 4419e1696e5f97920de2df96f13a2bd8a82bde5d: forced full build with fresh XML, 1,212 tests (1,195core+17browser), zero failures/errors/skips; seven bounded causal faults, each one intended failure with three unaffected controls, then byte-exact restoration and green controls. Exact-source causal/full evidence.

Native Chrome evidence:32fixtures/148observations/16comparisons and six actual scroll-abort cycles at fixed inner900x613/DPR1. Covers bounds/malformed DOM, intensity0/1/100/300, reduced motion, mixed animation triggers, replay and queued-callback cleanup. Native clock/random remain unforced; exact seeded work equality is verified separately in GraalJS. Counters do not establish identical CPU/GPU cost, OS preference or physical input. Canvas width/blur use a recorded one-float-ULP tolerance.

Plan 364ff77a-79b1-4cb4-ba6b-03bb6e2ee223. Required Fixpoint+Lattice exact-tip final review and non-author landing remain. No Stafficy sanitizer adoption or public release is included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant