#22094 ci(next): web bundles job red on every feat-cmux-next push (sync-motion import)

Summary

`cmux-next web bundles (source-keyed cache)` fails on every feat-cmux-next push (e.g. 9d185eb, 2c73ced, run 39300730843): `tests/test_web_bundle_key_inputs.sh` builds its scratch repo from a fixed list that only had `schemas/settings`, so `webviews/src/motion/syncMotion.gallery.tsx`'s import of `schemas/sync-motion/streams.json` (added in c611de179d37) resolved to no file.

• Commit 1 (test): archive all of `schemas/`. The test then reports the real gap: the import is missing from `cmux-next-web-bundle-publish.yml` push paths and `cmux_next_route.py` `BUNDLE_INPUTS`.
• Commit 2 (fix): add `schemas/sync-motion` to both.

Testing

• `bash tests/test_web_bundle_key_inputs.sh`: red at commit 1, `web-bundle-key inputs: ok` at commit 2.
• `python -m unittest tests/test_cmux_next_route.py tests/test_cmux_next_route_replay.py`: 40 OK.

Changelog: none

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Fixes the cmux-next web bundle CI job, which failed on every push to feat-cmux-next because the sync motion gallery's import of schemas/sync-motion/streams.json wasn't recognized as a bundle input.

• The key input test now archives all of schemas/ instead of only schemas/settings, so it surfaces missing imports instead of failing on unresolved files.
• schemas/sync-motion is now included in the publish workflow's push paths and in BUNDLE_INPUTS, so changes to it trigger the bundle publish and tier.
• Verified with bash tests/test_web_bundle_key_inputs.sh and the route unit tests (40 pass).