R360: the ease and its switch come out again (#153, #175) - #177
Merged
Conversation
Dawid's decision of 12.09.2026, the day after it shipped: the product is losing functions rather than gaining them. So the eased travel goes, the owner's Motion switch goes with it, and #175 — which was to make the ease two owner-set amounts — is closed unmerged and never reached `main`. What is left is what a thrown orbit cannot be without: a release still coasts and slows to a stop. That is the one curve the arithmetic keeps, and it is not there for the look of it — constant slowing is where the motion `coastAfterDrag` measures out actually puts a thing. The coast used to ask the switch for permission. It asks nobody now: a release coasts unless the pointer was cancelled rather than lifted, or the visitor's system asks for less motion. A work saved while the switch existed may still carry `glide` in its parameters. Nothing breaks: the schema object drops keys it does not know on the way in, so such a work reads as one without a switch, which is what it now is. No migration, and none needed. SPEC A13 says five parameters again, and says what happened to the sixth. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dawid's decision of 12.09.2026, the day after it shipped: the product is losing functions rather than gaining them.
Out: the eased travel from #153 and the owner's Motion switch over it. #175, which was to turn that switch into two owner-set amounts, is closed unmerged — none of it ever reached
main.What is left
A release still coasts: a thrown orbit keeps turning and slows to a stop. That is the one curve the arithmetic keeps, and it is not kept for the look of it — constant slowing is where the motion
coastAfterDragmeasures out actually puts a thing.A click on the ring, on a marker, or on a cue button travels at one pace from beginning to end, as it did before 11.09.
What that touched
orbit.ts: theeasedcurve andglides()are gone;TravelCurveissteady | slowing. The coast no longer asks the switch for permission — a release coasts unless the pointer was cancelled rather than lifted, or the visitor's system asks for less motion.frame-set-shared.ts:glideis out of the params schema, and out ofisDefaultR360Params.r360-params.tsx: the Motion control is gone from the edit form; five parameters again.schema.tsloses the field from the stored-row type and says five parameters in its comment; the unit tests lose the glide cases;works.spec.tsloses the switch walkthrough.Saved works
A work saved while the switch existed may still carry
glideinr360_params. Nothing breaks and nothing needs doing: the params object drops keys it does not know on the way in, so such a work reads as one without a switch — which is what it now is. No migration.Verified
pnpm checkgreen,pnpm buildgreen,r360.spec.ts+works.spec.ts20/20 against the test database — including the #153 case that a reduced-motion visitor is not thrown, which is still true and still the coast's own rule.🤖 Generated with Claude Code