chore: keep @runfusion/fusion and runfusion.ai npm versions in sync

- Add `["@runfusion/fusion", "runfusion.ai"]` to changesets `fixed` so
  future changesets bump both packages to the same version number.
- Catch up `runfusion.ai` from 0.0.8 to 0.1.1 so the fixed group starts
  from an aligned baseline; changelog entry notes the rationale.

No functional change to the alias package (`index.js` is unchanged).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

packages/cli-alias/CHANGELOG.md

@@ -1,5 +1,9 @@
 # runfusion.ai
 
+## 0.1.1
+
+Catch-up version bump so `runfusion.ai` stays in sync with `@runfusion/fusion`. The two packages are now grouped under changesets `fixed` in `.changeset/config.json` and will always share a version number from here on.
+
 ## 0.0.8
 
 ### Patch Changes

packages/cli-alias/package.json

@@ -1,6 +1,6 @@
 {
   "name": "runfusion.ai",
-  "version": "0.0.8",
+  "version": "0.1.1",
   "license": "MIT",
   "description": "Launch Fusion with `npx runfusion.ai` — tiny alias for @runfusion/fusion.",
   "homepage": "https://runfusion.ai",