@syncedco/motion 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,106 @@
+# Changelog
+
+All notable changes to this project are documented here.
+
+The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## Versioning policy
+
+- **Recipe IDs are public API.** Removing or renaming one is a major change.
+- **Recipe behaviour** carries its own `version` field in the manifest. A
+  visual change to an existing recipe is a minor bump; a change to its root
+  selector, required slots or parameter bounds is a major one.
+- **The attribute prefix is `data-motion-`.** Renaming it is a major change.
+- **Bundle budgets** in `scripts/check-size.mjs` are part of the contract. They
+  are raised deliberately, never quietly.
+
+## [0.1.0] - 2026-09-25
+
+Initial release: the recipe schema, compiler, registry and runtime; sixty
+recipes across twelve families; the CLI and local MCP server; React, Vue,
+Svelte, Astro and WordPress adapters; and the recipe gallery.
+
+The notes below record what changed during pre-release hardening.
+
+### Removed — breaking
+
+- **The `data-sf-*` attribute vocabulary is gone.** Every authoring attribute
+  is now `data-motion-*`, with no alias layer and no compatibility shim.
+  Runtime state attributes are `data-motion-runtime`, `data-motion-reduced`,
+  `data-motion-scroll-locked` and `data-motion-recipe`; custom events are
+  `motion:*`; the package's own custom properties are `--motion-*`. Synced
+  Flow's `--sf-colour-*`, `--sf-space-*` and `data-sf-theme` are untouched.
+
+  To migrate, rename `data-sf-` to `data-motion-` in your markup. There is no
+  deprecation period because the package has not been published.
+
+- `normalizeMotionAliases`, `canonicalSelector`, `CANONICAL_ATTRIBUTE_PREFIX`
+  and `LEGACY_ATTRIBUTE_PREFIX` are removed, along with the CLI's
+  `--legacy-prefix` flag. Dropping the alias pass also removes a full-tree
+  attribute walk from every mount.
+
+### Added
+
+- `@syncedco/motion/recipes` exports all sixty recipes individually, so a page
+  can bundle only the ones it uses.
+- `@syncedco/motion/full` registers every optional GSAP plugin in one import,
+  preserving the previous batteries-included behaviour.
+- `@syncedco/motion/plugins` exposes the optional plugin set for selective use.
+- `data-motion-*` is the attribute vocabulary throughout. The runtime marks
+  state with `data-motion-runtime`, `data-motion-reduced`,
+  `data-motion-scroll-locked` and `data-motion-recipe`, and the package's own
+  custom properties are `--motion-*`.
+- `synced-motion add <id...>` prints ready-to-paste markup with every required
+  slot, and warns when a recipe needs an optional plugin.
+- `synced-motion --version` and per-command `--help`.
+- Playwright browser tests covering one recipe per family: clean mount,
+  perceivable content, teardown and reduced motion, plus menu focus behaviour.
+- `npm run size:check` enforces per-scenario gzip budgets against the built
+  package as a consumer installs it.
+- `docs/RECIPE-REFERENCE.md`, generated from the registry and verified in CI.
+- `docs/API.md` documenting the JavaScript surface: options, the runtime,
+  registries, `inspect()` diagnostics, the `setup` context and exported types.
+- `docs/PERFORMANCE.md` covering entry points, per-recipe imports, optional
+  plugins, budgets and runtime cost.
+- `CONTRIBUTING.md` and a `docs/README.md` index.
+- Continuous integration across Node 20, 22 and 24, a browser-test job, a
+  tag-driven publish workflow and a GitHub Pages build for the gallery.
+
+### Changed
+
+- **Authoring metadata no longer reaches the browser.** Recipes are split into
+  lean runtime specs and separate authoring metadata; prose, preview data and
+  fixture markup stay in the tooling path.
+- **Optional GSAP plugins are opt-in.** The core imports gsap and ScrollTrigger
+  only. The forty-three recipes needing nothing else are unaffected; the other
+  seventeen are skipped with an actionable diagnostic until their plugin is
+  supplied.
+- `createMotionRegistry` and `validateMotionRecipe` accept a `mode` option. The
+  default (`complete`) is unchanged.
+- The menu moves focus when its entrance completes rather than on a fixed
+  timer.
+
+### Fixed
+
+- The menu no longer fails to move focus into its panel. Focus was being set
+  180 ms after opening, while the items were still `visibility: hidden` from
+  their entrance tween, so the call silently did nothing.
+- Destroying the runtime no longer leaves an expanded menu panel visible; the
+  authored `hidden`, `aria-hidden` and `aria-expanded` state is restored.
+- The menu closes on an outside click, and only returns focus to its trigger
+  when focus was inside the panel.
+- A font-loading or window `load` event resolving after `destroy()` no longer
+  refreshes a torn-down runtime.
+- Thirteen exports (`createMenus`, `createReveals`, `createSplitText` and
+  others) shipped without type declarations. Declaration coverage is now
+  verified against the real runtime exports of every entry point.
+- The MCP server reports the real package version instead of a hard-coded one.
+
+### Payload
+
+| Scenario | Before | After |
+| --- | --- | --- |
+| Three recipes | 16.2 kB gzip | 5.8 kB gzip |
+| All sixty recipes | 25.4 kB gzip | 16.9 kB gzip |
+| GSAP plugins forced on consumers | 6 | 1 (ScrollTrigger) |

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,26 @@
+# Code Of Conduct
+
+Synced Motion aims to be a practical, respectful open-source project.
+
+## Expected Behaviour
+
+- Be considerate and constructive.
+- Keep feedback focused on the work.
+- Assume good intent, and ask for clarification when something is unclear.
+- Respect maintainers' time and project scope.
+- Welcome people with different levels of animation, accessibility, GSAP, and
+  frontend experience.
+
+## Unacceptable Behaviour
+
+- Harassment, threats, or personal attacks.
+- Discriminatory language or behaviour.
+- Repeated off-topic, hostile, or bad-faith comments.
+- Publishing private information without permission.
+- Pressuring maintainers for unpaid commercial support.
+
+## Reporting
+
+Report conduct concerns to SyncedCo through [syncedco.com](https://syncedco.com).
+Maintainers may remove comments, close issues, or block contributors when needed
+to keep the project healthy.

package/CONTRIBUTING.md

@@ -0,0 +1,100 @@
+# Contributing
+
+Thanks for considering a contribution. By taking part you agree to the
+[code of conduct](CODE_OF_CONDUCT.md). For vulnerabilities, follow the
+[security policy](SECURITY.md) rather than opening an issue. For questions and
+bug reports, see [support](SUPPORT.md).
+
+## Setup
+
+```bash
+npm install
+npx playwright install chromium   # for browser tests
+```
+
+## The gate
+
+```bash
+npm run check
+```
+
+This is what CI runs. In order:
+
+| Step | What it proves |
+| --- | --- |
+| `flow:check`, `flow:lint`, `flow:doctor` | The showcase's design system is valid and its generated CSS is current. |
+| `units:check` | No stray `px`; fixed dimensions use tokens or `rem`. |
+| `test` | Unit and DOM behaviour under jsdom. |
+| `build` | The package builds and declarations are copied. |
+| `types:check` | A consumer on NodeNext can import every subpath, and every runtime export is declared. |
+| `size:check` | No bundle budget regressed. |
+| `docs:check` | `docs/RECIPE-REFERENCE.md` matches the registry. |
+| `motion:validate`, `motion:doctor` | Every recipe passes the schema; project wiring is intact. |
+| `mcp:check` | The MCP server starts and exposes its tools. |
+
+Browser tests are separate because they need a real engine:
+
+```bash
+npm run test:browser        # headless
+npm run test:browser:ui     # interactive
+```
+
+**Run them whenever you change a pattern's DOM, focus or timing behaviour.**
+jsdom has no layout, so ScrollTrigger never fires, SplitText never splits, Flip
+measures nothing, and an element that is `visibility: hidden` will still accept
+focus. Every one of those has hidden a real bug.
+
+## Adding a recipe
+
+1. Write the pattern factory in `src/patterns/`. It takes a context object and
+   returns a cleanup function, an object with `destroy()`, or an array of
+   either.
+2. Add the runtime spec to `src/recipes/specs.js`. Annotate both the
+   `spec(...)` call and the nested `setupFactory(...)` call with
+   `/* @__PURE__ */` so the recipe stays tree-shakeable.
+3. Add the prose to `src/recipes/authoring.js`. Never put prose or fixture
+   markup in `specs.js` — it would ship to every visitor.
+4. Add it to `builtinMotionSpecs`.
+5. `npm run docs:build` to regenerate the reference.
+6. Add a unit test, and a browser test if it involves focus, layout or timing.
+7. `npm run check && npm run test:browser`.
+
+The validator will reject the recipe if it targets `html`, `body` or `:root`,
+animates a layout property without `performance.allowLayout`, omits a declared
+reduced-motion strategy, no-JavaScript behaviour or accessibility note, or
+lacks a fixture whose markup contains the root and every required slot.
+
+See [the recipe system](docs/RECIPES.md) for the full contract.
+
+## What the project will not accept
+
+- jQuery, or a page-builder runtime dependency.
+- A hard dependency on Synced Flow. The package is standalone.
+- Optional GSAP plugins imported from the core. They belong in
+  `src/plugins.js` and `@syncedco/motion/full`.
+- Authoring metadata reachable from the browser runtime.
+- Motion that hides content it might fail to reveal.
+- Inline colours, spacing or typography. Motion animates transforms, opacity
+  and semantic state.
+- A recipe with no cleanup path.
+
+## Style
+
+Match the surrounding code: no semicolons, single quotes, two-space indent,
+named exports. Comments explain why, not what.
+
+## Commits and releases
+
+Do not commit, push, publish or deploy without approval. Releases are
+automated from [Conventional Commits](https://www.conventionalcommits.org/):
+`fix:` is a patch and `feat:` is a minor. While the version is below 1.0.0, a
+breaking change (`feat!:` or a `BREAKING CHANGE:` footer) is also a minor; from
+1.0.0 it is a major. Do not bump `package.json` or edit released
+`CHANGELOG.md` entries by hand.
+
+Every push to `main` updates a release pull request with the next version and
+changelog. Merging it tags `vX.Y.Z`, creates the GitHub release, runs the full
+gate including browser tests, and publishes to npm through trusted publishing.
+
+See [CHANGELOG.md](CHANGELOG.md) for the versioning policy — recipe IDs and the
+attribute prefix are public API, and bundle budgets are part of the contract.

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2026 SyncedCo Limited
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

package/README.md

@@ -0,0 +1,278 @@
+# Synced Motion
+
+Accessible scroll and interaction animation for the web, in two attributes.
+
+Sixty production recipes built on GSAP, where reduced motion, keyboard
+behaviour, no-JavaScript fallbacks and deterministic cleanup are part of the
+contract instead of something you remember to add later.
+
+Framework-neutral. No jQuery, no page builder runtime, no generated class
+names. Works in plain HTML, React, Vue, Svelte, Astro and WordPress.
+
+```bash
+npm install @syncedco/motion gsap
+```
+
+## Five minutes
+
+```js
+import { createSyncedMotion } from '@syncedco/motion'
+import '@syncedco/motion/styles.css'
+
+const motion = createSyncedMotion()
+```
+
+```html
+<h1 data-motion-reveal="up">Engaging experiences without framework debt.</h1>
+
+<ul data-motion-stagger>
+  <li data-motion-stagger-item>Discover</li>
+  <li data-motion-stagger-item>Compose</li>
+  <li data-motion-stagger-item>Ship</li>
+</ul>
+```
+
+That is the whole integration. The heading rises in as it enters the viewport,
+the list cascades, and both stay exactly where you authored them if JavaScript
+never runs or the visitor prefers reduced motion.
+
+Call `motion.destroy()` on route change or hot reload.
+
+Don't know the attribute you need? Ask for it:
+
+```bash
+npx synced-motion add reveal-rise
+```
+
+## What makes it different
+
+Most animation libraries hand you a tween and leave the hard parts to you.
+Here every recipe must declare, and is tested against, four things:
+
+| | |
+| --- | --- |
+| **Reduced motion** | What happens under `prefers-reduced-motion`. Never "nothing moves and the content is now invisible". |
+| **Without JavaScript** | The authored state stays readable. Motion never hides content it might fail to reveal. |
+| **Accessibility** | Reading order, focus order and native semantics are unchanged. |
+| **Cleanup** | `destroy()` returns the DOM to how you wrote it. Verified in a real browser. |
+
+The validator enforces this: it will not let a recipe target `body`, animate
+layout properties without explicitly opting in, or ship without a declared
+fallback.
+
+## Pay for what you use
+
+The core imports GSAP and ScrollTrigger. Nothing else.
+
+```js
+// All sixty recipes, ScrollTrigger only.        16.9 kB gzip
+import { createSyncedMotion } from '@syncedco/motion'
+
+// Only what this page uses.                      5.8 kB gzip
+import { createMotionRuntime, createMotionRegistry } from '@syncedco/motion'
+import { revealRise, marquee } from '@syncedco/motion/recipes'
+
+createMotionRuntime({
+  registry: createMotionRegistry([revealRise, marquee], { mode: 'runtime' }),
+})
+```
+
+Seventeen recipes need an optional GSAP plugin (SplitText, Flip, DrawSVG,
+MorphSVG or MotionPath). Rather than putting all five in your bundle, the core
+skips those recipes and tells you exactly what is missing:
+
+```js
+motion.inspect().skipped
+// [{ id: 'split-lines-rise', reason: 'missing-dependency',
+//    dependencies: ['SplitText'],
+//    fix: 'Pass { dependencies: { SplitText } } or import from "@syncedco/motion/full".' }]
+```
+
+Two ways to resolve it:
+
+```js
+// Everything, one import.
+import { createSyncedMotion } from '@syncedco/motion/full'
+
+// Or just the plugin you actually need.
+import { SplitText } from 'gsap/SplitText'
+createSyncedMotion({ dependencies: { SplitText } })
+```
+
+These numbers are enforced by `npm run size:check`, measured against the built
+package as a consumer installs it.
+
+## Browse the recipes
+
+```bash
+npm run gallery
+```
+
+Search all sixty, inspect their slots and fallbacks, tune bounded parameters,
+simulate reduced motion, and copy the markup. Or read
+[the generated reference](docs/RECIPE-REFERENCE.md), which is produced from the
+registry so it cannot drift from the code.
+
+## Command line and agents
+
+The CLI and the local MCP server share one side-effect-free service, so an
+agent and a human get identical answers.
+
+```bash
+npx synced-motion add reveal-rise           # ready-to-paste markup
+npx synced-motion suggest "cinematic pinned story"
+npx synced-motion catalog --json
+npx synced-motion scan --file src/page.html # find roots, report missing slots
+npx synced-motion compose "restrained but cinematic" --file src/page.html
+npx synced-motion doctor
+npx synced-motion mcp                       # local stdio MCP server
+```
+
+The MCP server is local and provider-agnostic. It uploads nothing and needs no
+account. See [CLI and MCP tools](docs/TOOLING.md).
+
+## Frameworks and CMSs
+
+```js
+import { useSyncedMotion } from '@syncedco/motion/react'
+import { useSyncedMotion } from '@syncedco/motion/vue'
+import { syncedMotion } from '@syncedco/motion/svelte'
+import { createAstroMotion } from '@syncedco/motion/astro'
+import { createWordPressMotion } from '@syncedco/motion/wordpress'
+```
+
+React and Vue are optional peer dependencies. Svelte, Astro and WordPress use
+small lifecycle adapters that keep their runtimes out of the core bundle. See
+[Framework and CMS integrations](docs/INTEGRATIONS.md).
+
+## Pairs well with Synced Flow
+
+Synced Motion works with any CSS — Tailwind, vanilla, CSS modules, your own
+design system. It has no dependency on Synced Flow and never will.
+
+That said, the two were built to the same rule, and it shows when you use them
+together: **Flow decides what things look like, Motion decides how they
+arrive.** Nothing in this package writes a colour, a spacing value or a font
+size, so a theme change in Flow can never be undermined by a stale value baked
+into an animation. There is no overlap to reconcile and no fight over
+specificity.
+
+```bash
+npm install @syncedco/flow @syncedco/motion gsap
+```
+
+```html
+<!-- sf-* owns the look. data-motion-* owns the arrival. -->
+<section class="sf-section">
+  <div class="sf-container sf-stack">
+    <p class="sf-kicker" data-motion-reveal="fade">A motion system</p>
+    <h1 class="sf-text-display" data-motion-split="lines">
+      Engaging experiences without framework debt.
+    </h1>
+  </div>
+</section>
+```
+
+The two vocabularies stay legible side by side: you can read that markup and
+know exactly which package is responsible for what. Motion toggles semantic
+state — `data-active`, `aria-current`, `aria-expanded` — and your CSS decides
+how that state looks, which is the same seam whether or not the CSS is Flow's.
+
+Keep brand tokens in `synced-flow.config.mjs`. This repository's showcase is a
+worked example of the pairing; run `npm run dev` to see it.
+
+## Writing your own recipe
+
+The built-ins are not a fixed menu. A custom recipe is the same contract:
+
+```js
+import { createMotionRegistry, createMotionRuntime, defineMotionRecipe } from '@syncedco/motion'
+
+const reveal = defineMotionRecipe({
+  schemaVersion: '1',
+  id: 'project-reveal',
+  version: '1.0.0',
+  title: 'Project reveal',
+  description: 'Reveals project cards in their local section.',
+  intent: 'Introduce project cards when the section enters the viewport.',
+  family: 'reveals',
+  tags: ['reveal', 'cards'],
+  root: { selector: '[data-motion-projects]' },
+  slots: [{ name: 'root' }, { name: 'items', selector: '[data-motion-project]', multiple: true }],
+  parameters: { duration: { type: 'number', default: 0.6, min: 0, max: 2 } },
+  triggers: [{ type: 'viewport' }],
+  reducedMotion: { strategy: 'final' },
+  noJs: { behavior: 'Cards remain visible in their authored final state.' },
+  accessibility: { notes: 'Reading and focus order never change.' },
+  performance: { class: 'low' },
+  dependencies: ['gsap'],
+  preview: { fixture: 'default', viewport: 'standard', activation: 'auto' },
+  fixtures: [{
+    id: 'default',
+    label: 'Default',
+    markup: '<section data-motion-projects><article data-motion-project>Project</article></section>',
+    parameters: {},
+  }],
+  setup({ gsap, slots, parameters, reduced }) {
+    if (reduced) return
+    const tween = gsap.from(slots.items, {
+      autoAlpha: 0, y: '1.5rem', duration: parameters.duration, stagger: 0.08,
+    })
+    return () => tween.revert()
+  },
+})
+
+createMotionRuntime({ registry: createMotionRegistry([reveal]) })
+```
+
+Your recipe appears in the gallery, the CLI and the MCP server automatically.
+See [the recipe system](docs/RECIPES.md).
+
+## Principles
+
+- reduced motion by default;
+- usable content when JavaScript fails;
+- semantic state over inline visual values;
+- transforms and opacity before layout animation;
+- deterministic cleanup;
+- framework-neutral browser APIs;
+- no jQuery, no page builder runtime.
+
+## Documentation
+
+[Full index](docs/README.md).
+
+- [Recipe reference](docs/RECIPE-REFERENCE.md) — all sixty, generated
+- [Declarative attribute API](docs/ATTRIBUTE-API.md)
+- [JavaScript API](docs/API.md)
+- [Bundle size and performance](docs/PERFORMANCE.md)
+- [Motion recipe system](docs/RECIPES.md)
+- [CLI and MCP tools](docs/TOOLING.md)
+- [Framework and CMS integrations](docs/INTEGRATIONS.md)
+- [Capability blueprint](docs/CAPABILITIES.md)
+- [Webflow migration workflow](docs/WEBFLOW-MIGRATION.md)
+- [Changelog](CHANGELOG.md)
+
+## Contributing
+
+```bash
+npm install
+npm run check          # design system, units, tests, build, types, budgets, docs
+npm run test:browser   # Playwright; run npx playwright install chromium first
+```
+
+`npm run check` is the same gate CI runs. See [CONTRIBUTING.md](CONTRIBUTING.md)
+and the [code of conduct](CODE_OF_CONDUCT.md).
+
+- [Support](SUPPORT.md) — where to ask, and what to include
+- [Security policy](SECURITY.md) — please don't file vulnerabilities publicly
+- [Trademarks](TRADEMARKS.md) — the licence covers the code, not the branding
+
+## Scope
+
+This recreates the published-page capabilities an expressive marketing site
+needs. It is not a hosted visual editor, a CMS, or a hosting product.
+
+## Licence
+
+MIT © SyncedCo Limited. Maintained by [SyncedCo](https://syncedco.com).

package/SECURITY.md

@@ -0,0 +1,36 @@
+# Security Policy
+
+## Supported Versions
+
+Security fixes target the latest published version and the current `main`
+branch.
+
+## Reporting A Vulnerability
+
+Please do not open a public GitHub issue for suspected vulnerabilities.
+
+Report security concerns to SyncedCo through [syncedco.com](https://syncedco.com)
+and include:
+
+- affected package version or commit
+- affected command, entry point, recipe, or integration
+- reproduction steps
+- expected and actual impact
+- any relevant logs or runtime diagnostics from `motion.inspect()`
+
+We will review the report, confirm whether the issue is valid, and coordinate a
+fix before public disclosure where appropriate.
+
+## Scope
+
+Security reports may include issues in the CLI, the local MCP server, package
+distribution, the framework and CMS adapters, recipe `setup` execution, or the
+examples and gallery.
+
+Note that recipe `setup` functions are executable code. Registering a recipe
+from an untrusted source runs that code with the privileges of the page, in the
+same way importing any third-party module does. Treat recipe manifests from
+outside your project as untrusted input.
+
+General support questions, animation behaviour, and feature requests should use
+[GitHub issues](https://github.com/SyncedCo/synced-motion/issues).

package/SUPPORT.md

@@ -0,0 +1,38 @@
+# Support
+
+Synced Motion is maintained by SyncedCo.
+
+- Website: [syncedco.com](https://syncedco.com)
+- GitHub: [github.com/SyncedCo/synced-motion](https://github.com/SyncedCo/synced-motion)
+- Issues: [github.com/SyncedCo/synced-motion/issues](https://github.com/SyncedCo/synced-motion/issues)
+- Security: [SECURITY.md](SECURITY.md)
+- Contributing: [CONTRIBUTING.md](CONTRIBUTING.md)
+
+## Community Support
+
+Use GitHub issues for reproducible bugs, documentation problems, CLI issues,
+and focused feature requests for the open-source core.
+
+Before opening an issue, please include:
+
+- the package version and the GSAP version
+- the framework or environment
+- the recipe ID, or the markup that should have animated
+- the output of `motion.inspect()`, which reports what mounted, what was
+  skipped and why, and any errors
+- the expected and actual behaviour
+
+If a recipe did nothing, check `inspect().skipped` first: a
+`missing-dependency` entry means an optional GSAP plugin was not supplied, and
+`missing-slots` means the markup was missing a required element. Both include
+the fix.
+
+## Commercial And Team Support
+
+For paid implementation, motion-system audits, accessibility review, migration
+from Webflow interactions, training, workshops, or team support, contact
+SyncedCo through [syncedco.com](https://syncedco.com).
+
+Commercial services are optional support around the open-source core. Premium
+templates, hosted tools, and paid starter kits are not included in this package
+unless explicitly released separately.

package/TRADEMARKS.md

@@ -0,0 +1,14 @@
+# Trademark And Brand Use
+
+The MIT licence covers the Synced Motion software. It does not grant trademark,
+brand, logo, or endorsement rights.
+
+Names such as Synced, SyncedCo, and Synced Motion may be used to truthfully
+refer to this project, compatibility, forks, or integrations.
+
+Do not use Synced, SyncedCo, or Synced Motion names, logos, or branding in a way
+that suggests official sponsorship, endorsement, partnership, or ownership
+unless SyncedCo has given written permission.
+
+Forks and derived projects should use a distinct name if they are distributed as
+their own product.

package/bin/synced-motion.mjs

@@ -0,0 +1,5 @@
+#!/usr/bin/env node
+import { runMotionCli } from '../dist/cli.js'
+
+const result = await runMotionCli()
+if (result.code) process.exitCode = result.code

package/dist/astro.d.ts

@@ -0,0 +1,15 @@
+import type { MotionRuntime, MotionRuntimeOptions } from './index.js'
+
+export interface AstroMotionOptions extends Omit<MotionRuntimeOptions, 'root'> {
+  document?: Document
+  root?: Document | Element | string | (() => Document | Element | null | undefined)
+}
+
+export interface AstroMotionController {
+  readonly runtime: MotionRuntime | undefined
+  mount(): MotionRuntime | undefined
+  refresh(): void
+  destroy(): void
+}
+
+export declare function createAstroMotion(options?: AstroMotionOptions): AstroMotionController