discardOutgoing skipped finished resting edges, so a persistAtRest drawer
opened by a node revealed during a back operation stayed attached after
that back was cancelled and the node returned to history. Found by the
property tests (1000-seed run).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Faarh2Ts6StJPcz2mRiHiR
Gestures
- Cancel a captured gesture on lostpointercapture, on a new primary
pointer-down, and when its component unmounts, so operations are
never left stuck mid-transition. Bindings gain onLostpointercapture.
- Warn (console.warn) when navigate() fails or the scene rejects an
operation; stay quiet when two recognizers race for one origin.
- OriginGesture and OriginGestureSurface props are reactive. Changes
apply from the next pointer-down; recognizers are kept per list
position so re-renders never interrupt a drag.
- Remove the legacy direction/edge/threshold/action gesture form
(OriginGestureOptions, legacy OriginGesture props, MaybeOriginAction).
Scene
- Honour choreography commitVelocity (default 0.3, as before).
- Scene errors are OriginSceneError with a stable code.
- update() during settling now really catches an operation: the spring
stops, and only the latest finish() decides the outcome.
- Fix graph corruption found by the new property tests, all present on
main: replacements escaping a cancelled push, edges left dangling when
their current target differs from the original one, revealed targets
keeping operations after their back is cancelled, history pointing at
removed entries after replace, visual cycles from back through an
undecided replace, exposed nodes reactivated as active, and a cancel
cascade that could empty the whole scene.
Tests
- Add property tests checking structural invariants after every step of
random operation sequences and pointer streams (PROPERTY_SEEDS).
- Add recognizer tests for stuck gestures, warnings, reactive props,
and commitVelocity. Drop the main-comparison suites; keep benchmarks.
Also fix the origins demo's two pre-existing type errors.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Faarh2Ts6StJPcz2mRiHiR
- Memoize each operation's choreography effect set in a computed, so
nodes sharing an edge stop re-evaluating it (linear, not quadratic,
in chain depth).
- Cache the scene viewport and refresh it from a ResizeObserver and at
each begin(), instead of measuring the container per node per frame.
- Index operations by origin key so outgoing lookups no longer scan
every operation; all map changes go through attach()/detach().
- Resolve px and % gesture edge distances arithmetically; only other
CSS lengths use the off-screen probe. Verified in Chromium to match
the probe within its 1/64px layout rounding.
The differential suites against main still match exactly. Benchmarks
vs main: styleForNode 2.0x (3 live ops) and 2.4x (10 live ops),
rendered frames 1.14x.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Faarh2Ts6StJPcz2mRiHiR
`.onCommit(handler)` is available at every builder stage after the
direction, returns the same stage, and accumulates handlers in order.
Handlers run once, synchronously at release, when the operation commits
and before the settling animation, with the same context `.complete()`
receives. A throwing handler is reported without stopping later handlers
or the operation. Intended for haptic feedback such as
`navigator.vibrate`.
Named onCommit rather than then so builder stages never become
thenables. The builder now threads one frozen draft through its stages.
OriginOperationHandle gains a read-only `intent`, which the recognizer
reads right after finish() to know whether the release committed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Faarh2Ts6StJPcz2mRiHiR
- Merge the small modules into 12 files: shared, choreography,
navigation, scene/{types,graph,scene}, gesture/{definition,recognizer}.
- SceneGraph now owns the begin/update/commit/cancel history rules as
methods, with the step helpers as private methods.
- createOriginScene returns a markRaw'd Scene class; operation handles
are an OperationHandle class instead of inline object literals.
- GestureRecognizer gains static create()/policyFor() factories, absorbing
the separate policy module.
- Pure helpers used by classes (matchesStart, pointOf, stepSpring,
composeNodeStyle, nodeEffectLayers, shouldCommit, ...) are exported
consts so they can be tested directly.
- Add haptics tests showing where navigator.vibrate can be triggered.
Public exports, types, and behavior are unchanged; the differential
suites against main still pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Faarh2Ts6StJPcz2mRiHiR
Rewrite the core-v2 internals without changing the public API or runtime
behavior. The four large files (types, scene, motion, gesture) become
layered modules with one responsibility each:
- shared/: geometry and environment helpers
- view/: originView recipes
- choreography/: effect types, presets, and composeEffects compositing
- actions/: forward/back/replace/above/under via one overload resolver
- scene/: SceneGraph storage, transitions (history rules), compositor
(styles and interactivity), spring (pure stepper + rAF driver), and
createOriginScene, which only wires them and owns async timing
- composables/: useOrigin and the node-scope injection key
- gesture/: builder, definition->policy normalization, start admission,
DirectionalTracker, and a GestureRecognizer session state machine
replacing fifteen loose closure variables
- components/: renderers and gesture hosts, plus their prop types
Verification (packages/core-v2/verify): differential fuzzing drives
main and this branch with identical random operation sequences and
pointer streams and requires identical scene state, styles, contexts,
callbacks, and promise results at every step. It caught every planted
mutation that applied. Benchmarks are at parity.
Also fix a pre-existing test that called the defineProps macro inside a
runtime defineComponent, and correct API.md's description of the flick
commit threshold to match the runtime.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Faarh2Ts6StJPcz2mRiHiR
Claude
Harvmaster