Feature/v14 migration

.github/workflows/release.yml

@@ -0,0 +1,35 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    env:
+      FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: actions/setup-node@v6
+        with:
+          node-version: 20
+          cache: npm
+
+      - run: npm ci
+
+      - run: npm run build:prod
+
+      - name: Package dist as zip
+        run: cd dist && zip -r ../animabf.zip .
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2.6.1
+        with:
+          files: |
+            animabf.zip
+            dist/system.json

.gitignore

@@ -13,3 +13,8 @@ package/
 /packs
 
 *.code-workspace
+
+# Local Kiro/agents files
+.kiro/
+.agents/
+AGENTS.md

docs/releasing.md

@@ -0,0 +1,22 @@
+# How to publish a release (fork)
+
+1. Make sure all changes are committed and pushed to the fork:
+   ```bash
+   git push fork <branch>
+   ```
+
+2. Update the version in `src/system.json` if needed, commit, and push.
+
+3. Push a version tag — this triggers the release workflow:
+   ```bash
+   git tag v<version>
+   git push fork v<version>
+   ```
+
+4. GitHub Actions will:
+   - Run `npm run build:prod`
+   - Zip `dist/` → `animabf.zip`
+   - Create a GitHub Release on the fork with `animabf.zip` and `system.json` attached
+
+The release will be visible at:
+`https://github.com/LarsLTS/AnimaBeyondFoundry/releases`