mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-19 23:05:21 +00:00
* feat(website): show orchestration and remote in an animated hero mockup The homepage hero now has five scenes: Orchestration, Remote, Code review, Pull requests, and Plugins. Orchestration and Remote were missing before, and they are what separates Paseo from a single-machine agent app. Orchestration, Code review, and Plugins play a script once the mockup is 60% on screen, and again on every pill click. Each script is a list of beats (wait, click, type, user, agent, tools, turnEnd, mark) laid end to end. A non-React clock owns the time and components read one fact at a time, so only the part that changed renders. A pointer clicks the composer, the subagents pill, and the review controls. Reduced motion shows each finished scene. The right panel is 300px for the file tree and grows to 424px for the pull request and the plugin. Picking a pill scrolls the pills and the mockup into view. * fix(website): keep a picked hero scene playing and scroll it into view the same in every browser A pill click before the mockup was 60% on screen played its scene, and then the visibility start played the same scene again from zero. The player now starts the opening scene only when no scene has played, and the hero stops the clock when it unmounts. Picking a pill used scrollIntoView with `nearest`. For an element taller than the window, each engine picks its own edge, and WebKit left the pill 25% visible in a 1280x600 window. The hero now computes the scroll itself: the least that shows the pills and the mockup, never past the pills at the top. * fix(website): scroll a picked hero scene by where the hero settles, not where it slides The hero slides up 40px as it enters. A pill clicked during the slide measured the frame 40px low, so the scroll stopped with the pills 24px above the window once the slide ended. This was the cause of the WebKit failure in CI. The earlier explanation, that engines differ on scrollIntoView, was wrong. The scroll now measures the frame from layout offsets, which ignore the slide. The test holds the page clock so the slide stays at its first frame. * test(website): hold the hero's slide-in still when a pill is picked during it The test stopped the page timers but let time run, so it caught the bug only when the click landed in the first second after load. It now pauses the clock before the page loads and checks that the slide is still in progress at the click. * test(website): put the hero's 40px slide-in back by hand in the slide-in test The test held the page clock to freeze the slide, but WebKit did not hold it, so the test failed on its own precondition. It now waits for the slide to end, puts the 40px offset on the container, picks a scene, and removes the offset. Reduced motion makes the scroll instant, so the test asserts the result without waiting for a scroll to settle. * fix(website): start the opening hero scene in a window shorter than most of the mockup The scene waited for 60% of the mockup to be on screen. A window shorter than 60% of the mockup, such as a wide browser with devtools docked at the bottom, never reaches that, so the scene never started. It now starts when a line 60% of the way down the mockup is on screen. That is the same moment in an ordinary window, and a short window reaches it as the page scrolls past.