@unrulysystems/native-motion-core 0.1.0-alpha.0

package/dist/driver/reference.d.cts

@@ -0,0 +1,53 @@
+import type { Driver, PropTargetTo, PropTransition } from "./types.cjs";
+/**
+ * This backend's OWN verdict on a fold, for one transition and one target, with the boundary
+ * validation `command()` runs first deliberately NOT in the path.
+ *
+ * It exists because the parity floor that guards this rung was structurally half-blind without it
+ * (fix-up review MAJOR): `prepareDriverCommand` calls `validateTransitionRefusal` before reaching
+ * any generator, so a floor that reads `command()`'s throw sees validation's own refusal echoed back
+ * as "the driver refused". Every over-refusal therefore passed — a mutation that made validation
+ * reject 36 executable configs left the floor green. Only a verdict taken from BELOW validation can
+ * decide whether validation is measuring the fold the way this backend does.
+ *
+ * Returns the fold's refusal, or null when this backend would construct and run the generator.
+ *
+ * `from` is a real parameter, not a convenience: a null-first keyframe array (`[null, 100]`, the
+ * from-current form) resolves its first keyframe FROM the live value, so with `from` pinned at 0 it
+ * is indistinguishable from `[0, 100]` and the target axis loses a shape it claims to sweep (round-5
+ * review MINOR).
+ *
+ * Test seam for this package's own parity floor — NOT part of any published entry: exporting it from
+ * `internal-driver` would pull this whole backend into the seam the worklet driver imports.
+ */
+export declare function referenceFoldRefusal(transition: PropTransition, to: PropTargetTo, from?: number): Error | null;
+/**
+ * The same verdict at the RETARGET seam — the second half of the parity floor's oracle.
+ *
+ * Rounds 4-6 each fixed one axis pinned to a constant (`repeat`, then `repeatDelay`), and round 7
+ * found the pattern one level up: the floor's ORACLE was itself pinned to a constant — the `start`
+ * seam of the reference backend — while `buildRepeatedGenerator` has four seams (two backends x two
+ * phases). The retarget seam is not a duplicate of `start`:
+ *
+ *   - it reseeds the scan from the live VALUE, so the distance it measures is the distance from
+ *     wherever the animation currently IS — a different trajectory than `start` measured, which is
+ *     why it can refuse where `start` ran (round-7 review MAJOR). It also carries the live velocity
+ *     into the reseed; that is structurally present but NOT the demonstrated variable — sweeping the
+ *     dwell from 0 to 480ms at a fixed distance changes no verdict, and removing the dwell entirely
+ *     leaves the floor green (round-8 review MINOR). Distance is what moves it;
+ *   - it cannot reach the keyframes lane at all — `DriverCommand`'s retarget targets are numbers, so
+ *     `targetIsNumeric` is constantly true here. The floor's target axis is structurally
+ *     inexpressible at this seam, and its axis is the LIVE STATE instead.
+ *
+ * Taken from BELOW validation for the same reason as `referenceFoldRefusal`: `command()` validates
+ * first, so reading its throw would make the driver echo the boundary and the floor could only ever
+ * catch over-acceptance.
+ *
+ * A fold that cannot even START is reported as refused — "would this backend run it at a retarget"
+ * is answered `no` either way, and conflating them here would make the phase axis lie about which
+ * seam refused.
+ *
+ * Test seam for this package's own parity floor — NOT part of any published entry.
+ */
+export declare function referenceRetargetFoldRefusal(transition: PropTransition, startTo: PropTargetTo, from: number, retargetTo: number, dwellMs: number): Error | null;
+export declare function createReferenceDriver(): Driver;

package/dist/driver/reference.d.ts

@@ -0,0 +1,53 @@
+import type { Driver, PropTargetTo, PropTransition } from "./types.js";
+/**
+ * This backend's OWN verdict on a fold, for one transition and one target, with the boundary
+ * validation `command()` runs first deliberately NOT in the path.
+ *
+ * It exists because the parity floor that guards this rung was structurally half-blind without it
+ * (fix-up review MAJOR): `prepareDriverCommand` calls `validateTransitionRefusal` before reaching
+ * any generator, so a floor that reads `command()`'s throw sees validation's own refusal echoed back
+ * as "the driver refused". Every over-refusal therefore passed — a mutation that made validation
+ * reject 36 executable configs left the floor green. Only a verdict taken from BELOW validation can
+ * decide whether validation is measuring the fold the way this backend does.
+ *
+ * Returns the fold's refusal, or null when this backend would construct and run the generator.
+ *
+ * `from` is a real parameter, not a convenience: a null-first keyframe array (`[null, 100]`, the
+ * from-current form) resolves its first keyframe FROM the live value, so with `from` pinned at 0 it
+ * is indistinguishable from `[0, 100]` and the target axis loses a shape it claims to sweep (round-5
+ * review MINOR).
+ *
+ * Test seam for this package's own parity floor — NOT part of any published entry: exporting it from
+ * `internal-driver` would pull this whole backend into the seam the worklet driver imports.
+ */
+export declare function referenceFoldRefusal(transition: PropTransition, to: PropTargetTo, from?: number): Error | null;
+/**
+ * The same verdict at the RETARGET seam — the second half of the parity floor's oracle.
+ *
+ * Rounds 4-6 each fixed one axis pinned to a constant (`repeat`, then `repeatDelay`), and round 7
+ * found the pattern one level up: the floor's ORACLE was itself pinned to a constant — the `start`
+ * seam of the reference backend — while `buildRepeatedGenerator` has four seams (two backends x two
+ * phases). The retarget seam is not a duplicate of `start`:
+ *
+ *   - it reseeds the scan from the live VALUE, so the distance it measures is the distance from
+ *     wherever the animation currently IS — a different trajectory than `start` measured, which is
+ *     why it can refuse where `start` ran (round-7 review MAJOR). It also carries the live velocity
+ *     into the reseed; that is structurally present but NOT the demonstrated variable — sweeping the
+ *     dwell from 0 to 480ms at a fixed distance changes no verdict, and removing the dwell entirely
+ *     leaves the floor green (round-8 review MINOR). Distance is what moves it;
+ *   - it cannot reach the keyframes lane at all — `DriverCommand`'s retarget targets are numbers, so
+ *     `targetIsNumeric` is constantly true here. The floor's target axis is structurally
+ *     inexpressible at this seam, and its axis is the LIVE STATE instead.
+ *
+ * Taken from BELOW validation for the same reason as `referenceFoldRefusal`: `command()` validates
+ * first, so reading its throw would make the driver echo the boundary and the floor could only ever
+ * catch over-acceptance.
+ *
+ * A fold that cannot even START is reported as refused — "would this backend run it at a retarget"
+ * is answered `no` either way, and conflating them here would make the phase axis lie about which
+ * seam refused.
+ *
+ * Test seam for this package's own parity floor — NOT part of any published entry.
+ */
+export declare function referenceRetargetFoldRefusal(transition: PropTransition, startTo: PropTargetTo, from: number, retargetTo: number, dwellMs: number): Error | null;
+export declare function createReferenceDriver(): Driver;