Skip to content

Free, open-source AI video generator for Mac. Run LTX-2.5 and MiniMax H3 (Hailuo) locally on Apple Silicon: text-to-video and image-to-video with sound, lip-sync, character LoRA training, songs from lyrics (YuE2) and image editing (Qwen-Image-Edit). One-click install via Pinokio. Offline: no cloud, no API key, no NVIDIA GPU.

docs: harden branch policy — agents must push to dev, never to main without explicit OK

mrbizarrof5283f1dc3b9
diff --git a/.clinerules b/.clinerules
index 3cf6fb6..120c236 100644
--- a/.clinerules
+++ b/.clinerules
@@ -167,28 +167,47 @@ new patch versions without a venv rebuild — used when we added
### Branch model — `main` is production, `dev` is staging (Y1.015+)
-- **`main`** is what real users get. Pinokio's Discover URL points here;
- every commit pushed to `main` is shipped to every user the next time
- they click Update. Treat it accordingly.
+**TL;DR for agents — non-negotiable:**
+
+> **Push every commit to `dev`. Never push to `main` unless Salo
+> explicitly says "push to main" / "ship to production" / "merge to
+> main".** "It works on my machine" is not permission. "The tests
+> pass" is not permission. Salo has a Phosphene Dev panel in his
+> Pinokio that pulls from `dev`; he tests there, then tells you when
+> to promote.
+
+The why:
+
+- **`main`** is what real users get. Pinokio's Discover URL points
+ here; every commit pushed to `main` is shipped to every user the
+ next time they click Update. Treat it as production.
- **`dev`** is the staging branch. Push WIP commits here freely. The
local "Phosphene Dev" Pinokio panel (set up via
`scripts/setup_dev_panel.sh`) tracks this branch on port 8199 and
- shows a DEV badge in the header.
-- **Workflow**: develop on `dev` → push to `origin/dev` → click Update
- in the Phosphene Dev panel → test what real users will experience →
- once verified, merge `dev` → `main` and push. That's when users get
- the change.
+ shows an amber DEV badge in the header.
+- **Workflow**:
+ 1. Default to working on `dev`. `git checkout dev` at the start of
+ any session that touches Phosphene; if you're on `main`, switch.
+ 2. Commit + push to `origin/dev` whenever a logical change is done.
+ 3. **Stop there.** Tell Salo it's on dev. Wait for explicit
+ instruction to promote.
+ 4. When Salo says push to main: `git checkout main && git merge dev
+ --ff-only && git push origin main`. Then `git checkout dev` so
+ subsequent work continues on dev.
+ 5. If a fast-forward isn't possible (rare — usually a hotfix landed
+ on main directly), say so and ask before doing anything destructive.
- The panel auto-detects which profile it is from `git rev-parse
--abbrev-ref HEAD`: branch == `dev` → port 8199 + DEV badge; anything
else → port 8198 + normal header. No config files to edit per panel.
-- `update.js` is also branch-aware as of Y1.015 (`git pull --ff-only
- origin <current branch>`) so the dev panel's Update pulls dev and
- the production panel's Update pulls main, from the same shared code.
+- `update.js` is branch-aware as of Y1.015 (`git pull --ff-only origin
+ <current branch>`) so the dev panel's Update pulls dev and the
+ production panel's Update pulls main, from the same shared code.
- The dev panel symlinks `mlx_models/` from the production install
(saves ~36 GB of duplicate weights). State / outputs / uploads stay
separate per panel.
-- Don't push experimental commits directly to main. Always go via dev.
- The whole point of the staging panel is to verify before users hit it.
+- Hotfixes bypassing dev — only allowed when Salo explicitly authorises
+ ("hotfix straight to main" or similar). Otherwise, even one-line
+ fixes go via dev → tested in Phosphene Dev panel → merged.
### Git policy — NEVER FORCE-PUSH `origin/main`
- A history-rewrite + force-push on 2026-05-01 (to scrub identity
diff --git a/.cursorrules b/.cursorrules
index 3cf6fb6..120c236 100644
--- a/.cursorrules
+++ b/.cursorrules
@@ -167,28 +167,47 @@ new patch versions without a venv rebuild — used when we added
### Branch model — `main` is production, `dev` is staging (Y1.015+)
-- **`main`** is what real users get. Pinokio's Discover URL points here;
- every commit pushed to `main` is shipped to every user the next time
- they click Update. Treat it accordingly.
+**TL;DR for agents — non-negotiable:**
+
+> **Push every commit to `dev`. Never push to `main` unless Salo
+> explicitly says "push to main" / "ship to production" / "merge to
+> main".** "It works on my machine" is not permission. "The tests
+> pass" is not permission. Salo has a Phosphene Dev panel in his
+> Pinokio that pulls from `dev`; he tests there, then tells you when
+> to promote.
+
+The why:
+
+- **`main`** is what real users get. Pinokio's Discover URL points
+ here; every commit pushed to `main` is shipped to every user the
+ next time they click Update. Treat it as production.
- **`dev`** is the staging branch. Push WIP commits here freely. The
local "Phosphene Dev" Pinokio panel (set up via
`scripts/setup_dev_panel.sh`) tracks this branch on port 8199 and
- shows a DEV badge in the header.
-- **Workflow**: develop on `dev` → push to `origin/dev` → click Update
- in the Phosphene Dev panel → test what real users will experience →
- once verified, merge `dev` → `main` and push. That's when users get
- the change.
+ shows an amber DEV badge in the header.
+- **Workflow**:
+ 1. Default to working on `dev`. `git checkout dev` at the start of
+ any session that touches Phosphene; if you're on `main`, switch.
+ 2. Commit + push to `origin/dev` whenever a logical change is done.
+ 3. **Stop there.** Tell Salo it's on dev. Wait for explicit
+ instruction to promote.
+ 4. When Salo says push to main: `git checkout main && git merge dev
+ --ff-only && git push origin main`. Then `git checkout dev` so
+ subsequent work continues on dev.
+ 5. If a fast-forward isn't possible (rare — usually a hotfix landed
+ on main directly), say so and ask before doing anything destructive.
- The panel auto-detects which profile it is from `git rev-parse
--abbrev-ref HEAD`: branch == `dev` → port 8199 + DEV badge; anything
else → port 8198 + normal header. No config files to edit per panel.
-- `update.js` is also branch-aware as of Y1.015 (`git pull --ff-only
- origin <current branch>`) so the dev panel's Update pulls dev and
- the production panel's Update pulls main, from the same shared code.
+- `update.js` is branch-aware as of Y1.015 (`git pull --ff-only origin
+ <current branch>`) so the dev panel's Update pulls dev and the
+ production panel's Update pulls main, from the same shared code.
- The dev panel symlinks `mlx_models/` from the production install
(saves ~36 GB of duplicate weights). State / outputs / uploads stay
separate per panel.
-- Don't push experimental commits directly to main. Always go via dev.
- The whole point of the staging panel is to verify before users hit it.
+- Hotfixes bypassing dev — only allowed when Salo explicitly authorises
+ ("hotfix straight to main" or similar). Otherwise, even one-line
+ fixes go via dev → tested in Phosphene Dev panel → merged.
### Git policy — NEVER FORCE-PUSH `origin/main`
- A history-rewrite + force-push on 2026-05-01 (to scrub identity
diff --git a/.windsurfrules b/.windsurfrules
index 3cf6fb6..120c236 100644
--- a/.windsurfrules
+++ b/.windsurfrules
@@ -167,28 +167,47 @@ new patch versions without a venv rebuild — used when we added
### Branch model — `main` is production, `dev` is staging (Y1.015+)
-- **`main`** is what real users get. Pinokio's Discover URL points here;
- every commit pushed to `main` is shipped to every user the next time
- they click Update. Treat it accordingly.
+**TL;DR for agents — non-negotiable:**
+
+> **Push every commit to `dev`. Never push to `main` unless Salo
+> explicitly says "push to main" / "ship to production" / "merge to
+> main".** "It works on my machine" is not permission. "The tests
+> pass" is not permission. Salo has a Phosphene Dev panel in his
+> Pinokio that pulls from `dev`; he tests there, then tells you when
+> to promote.
+
+The why:
+
+- **`main`** is what real users get. Pinokio's Discover URL points
+ here; every commit pushed to `main` is shipped to every user the
+ next time they click Update. Treat it as production.
- **`dev`** is the staging branch. Push WIP commits here freely. The
local "Phosphene Dev" Pinokio panel (set up via
`scripts/setup_dev_panel.sh`) tracks this branch on port 8199 and
- shows a DEV badge in the header.
-- **Workflow**: develop on `dev` → push to `origin/dev` → click Update
- in the Phosphene Dev panel → test what real users will experience →
- once verified, merge `dev` → `main` and push. That's when users get
- the change.
+ shows an amber DEV badge in the header.
+- **Workflow**:
+ 1. Default to working on `dev`. `git checkout dev` at the start of
+ any session that touches Phosphene; if you're on `main`, switch.
+ 2. Commit + push to `origin/dev` whenever a logical change is done.
+ 3. **Stop there.** Tell Salo it's on dev. Wait for explicit
+ instruction to promote.
+ 4. When Salo says push to main: `git checkout main && git merge dev
+ --ff-only && git push origin main`. Then `git checkout dev` so
+ subsequent work continues on dev.
+ 5. If a fast-forward isn't possible (rare — usually a hotfix landed
+ on main directly), say so and ask before doing anything destructive.
- The panel auto-detects which profile it is from `git rev-parse
--abbrev-ref HEAD`: branch == `dev` → port 8199 + DEV badge; anything
else → port 8198 + normal header. No config files to edit per panel.
-- `update.js` is also branch-aware as of Y1.015 (`git pull --ff-only
- origin <current branch>`) so the dev panel's Update pulls dev and
- the production panel's Update pulls main, from the same shared code.
+- `update.js` is branch-aware as of Y1.015 (`git pull --ff-only origin
+ <current branch>`) so the dev panel's Update pulls dev and the
+ production panel's Update pulls main, from the same shared code.
- The dev panel symlinks `mlx_models/` from the production install
(saves ~36 GB of duplicate weights). State / outputs / uploads stay
separate per panel.
-- Don't push experimental commits directly to main. Always go via dev.
- The whole point of the staging panel is to verify before users hit it.
+- Hotfixes bypassing dev — only allowed when Salo explicitly authorises
+ ("hotfix straight to main" or similar). Otherwise, even one-line
+ fixes go via dev → tested in Phosphene Dev panel → merged.
### Git policy — NEVER FORCE-PUSH `origin/main`
- A history-rewrite + force-push on 2026-05-01 (to scrub identity
diff --git a/AGENTS.md b/AGENTS.md
index 3cf6fb6..120c236 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -167,28 +167,47 @@ new patch versions without a venv rebuild — used when we added
### Branch model — `main` is production, `dev` is staging (Y1.015+)
-- **`main`** is what real users get. Pinokio's Discover URL points here;
- every commit pushed to `main` is shipped to every user the next time
- they click Update. Treat it accordingly.
+**TL;DR for agents — non-negotiable:**
+
+> **Push every commit to `dev`. Never push to `main` unless Salo
+> explicitly says "push to main" / "ship to production" / "merge to
+> main".** "It works on my machine" is not permission. "The tests
+> pass" is not permission. Salo has a Phosphene Dev panel in his
+> Pinokio that pulls from `dev`; he tests there, then tells you when
+> to promote.
+
+The why:
+
+- **`main`** is what real users get. Pinokio's Discover URL points
+ here; every commit pushed to `main` is shipped to every user the
+ next time they click Update. Treat it as production.
- **`dev`** is the staging branch. Push WIP commits here freely. The
local "Phosphene Dev" Pinokio panel (set up via
`scripts/setup_dev_panel.sh`) tracks this branch on port 8199 and
- shows a DEV badge in the header.
-- **Workflow**: develop on `dev` → push to `origin/dev` → click Update
- in the Phosphene Dev panel → test what real users will experience →
- once verified, merge `dev` → `main` and push. That's when users get
- the change.
+ shows an amber DEV badge in the header.
+- **Workflow**:
+ 1. Default to working on `dev`. `git checkout dev` at the start of
+ any session that touches Phosphene; if you're on `main`, switch.
+ 2. Commit + push to `origin/dev` whenever a logical change is done.
+ 3. **Stop there.** Tell Salo it's on dev. Wait for explicit
+ instruction to promote.
+ 4. When Salo says push to main: `git checkout main && git merge dev
+ --ff-only && git push origin main`. Then `git checkout dev` so
+ subsequent work continues on dev.
+ 5. If a fast-forward isn't possible (rare — usually a hotfix landed
+ on main directly), say so and ask before doing anything destructive.
- The panel auto-detects which profile it is from `git rev-parse
--abbrev-ref HEAD`: branch == `dev` → port 8199 + DEV badge; anything
else → port 8198 + normal header. No config files to edit per panel.
-- `update.js` is also branch-aware as of Y1.015 (`git pull --ff-only
- origin <current branch>`) so the dev panel's Update pulls dev and
- the production panel's Update pulls main, from the same shared code.
+- `update.js` is branch-aware as of Y1.015 (`git pull --ff-only origin
+ <current branch>`) so the dev panel's Update pulls dev and the
+ production panel's Update pulls main, from the same shared code.
- The dev panel symlinks `mlx_models/` from the production install
(saves ~36 GB of duplicate weights). State / outputs / uploads stay
separate per panel.
-- Don't push experimental commits directly to main. Always go via dev.
- The whole point of the staging panel is to verify before users hit it.
+- Hotfixes bypassing dev — only allowed when Salo explicitly authorises
+ ("hotfix straight to main" or similar). Otherwise, even one-line
+ fixes go via dev → tested in Phosphene Dev panel → merged.
### Git policy — NEVER FORCE-PUSH `origin/main`
- A history-rewrite + force-push on 2026-05-01 (to scrub identity
diff --git a/CLAUDE.md b/CLAUDE.md
index 3cf6fb6..120c236 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -167,28 +167,47 @@ new patch versions without a venv rebuild — used when we added
### Branch model — `main` is production, `dev` is staging (Y1.015+)
-- **`main`** is what real users get. Pinokio's Discover URL points here;
- every commit pushed to `main` is shipped to every user the next time
- they click Update. Treat it accordingly.
+**TL;DR for agents — non-negotiable:**
+
+> **Push every commit to `dev`. Never push to `main` unless Salo
+> explicitly says "push to main" / "ship to production" / "merge to
+> main".** "It works on my machine" is not permission. "The tests
+> pass" is not permission. Salo has a Phosphene Dev panel in his
+> Pinokio that pulls from `dev`; he tests there, then tells you when
+> to promote.
+
+The why:
+
+- **`main`** is what real users get. Pinokio's Discover URL points
+ here; every commit pushed to `main` is shipped to every user the
+ next time they click Update. Treat it as production.
- **`dev`** is the staging branch. Push WIP commits here freely. The
local "Phosphene Dev" Pinokio panel (set up via
`scripts/setup_dev_panel.sh`) tracks this branch on port 8199 and
- shows a DEV badge in the header.
-- **Workflow**: develop on `dev` → push to `origin/dev` → click Update
- in the Phosphene Dev panel → test what real users will experience →
- once verified, merge `dev` → `main` and push. That's when users get
- the change.
+ shows an amber DEV badge in the header.
+- **Workflow**:
+ 1. Default to working on `dev`. `git checkout dev` at the start of
+ any session that touches Phosphene; if you're on `main`, switch.
+ 2. Commit + push to `origin/dev` whenever a logical change is done.
+ 3. **Stop there.** Tell Salo it's on dev. Wait for explicit
+ instruction to promote.
+ 4. When Salo says push to main: `git checkout main && git merge dev
+ --ff-only && git push origin main`. Then `git checkout dev` so
+ subsequent work continues on dev.
+ 5. If a fast-forward isn't possible (rare — usually a hotfix landed
+ on main directly), say so and ask before doing anything destructive.
- The panel auto-detects which profile it is from `git rev-parse
--abbrev-ref HEAD`: branch == `dev` → port 8199 + DEV badge; anything
else → port 8198 + normal header. No config files to edit per panel.
-- `update.js` is also branch-aware as of Y1.015 (`git pull --ff-only
- origin <current branch>`) so the dev panel's Update pulls dev and
- the production panel's Update pulls main, from the same shared code.
+- `update.js` is branch-aware as of Y1.015 (`git pull --ff-only origin
+ <current branch>`) so the dev panel's Update pulls dev and the
+ production panel's Update pulls main, from the same shared code.
- The dev panel symlinks `mlx_models/` from the production install
(saves ~36 GB of duplicate weights). State / outputs / uploads stay
separate per panel.
-- Don't push experimental commits directly to main. Always go via dev.
- The whole point of the staging panel is to verify before users hit it.
+- Hotfixes bypassing dev — only allowed when Salo explicitly authorises
+ ("hotfix straight to main" or similar). Otherwise, even one-line
+ fixes go via dev → tested in Phosphene Dev panel → merged.
### Git policy — NEVER FORCE-PUSH `origin/main`
- A history-rewrite + force-push on 2026-05-01 (to scrub identity
diff --git a/GEMINI.md b/GEMINI.md
index 3cf6fb6..120c236 100644
--- a/GEMINI.md
+++ b/GEMINI.md
@@ -167,28 +167,47 @@ new patch versions without a venv rebuild — used when we added
### Branch model — `main` is production, `dev` is staging (Y1.015+)
-- **`main`** is what real users get. Pinokio's Discover URL points here;
- every commit pushed to `main` is shipped to every user the next time
- they click Update. Treat it accordingly.
+**TL;DR for agents — non-negotiable:**
+
+> **Push every commit to `dev`. Never push to `main` unless Salo
+> explicitly says "push to main" / "ship to production" / "merge to
+> main".** "It works on my machine" is not permission. "The tests
+> pass" is not permission. Salo has a Phosphene Dev panel in his
+> Pinokio that pulls from `dev`; he tests there, then tells you when
+> to promote.
+
+The why:
+
+- **`main`** is what real users get. Pinokio's Discover URL points
+ here; every commit pushed to `main` is shipped to every user the
+ next time they click Update. Treat it as production.
- **`dev`** is the staging branch. Push WIP commits here freely. The
local "Phosphene Dev" Pinokio panel (set up via
`scripts/setup_dev_panel.sh`) tracks this branch on port 8199 and
- shows a DEV badge in the header.
-- **Workflow**: develop on `dev` → push to `origin/dev` → click Update
- in the Phosphene Dev panel → test what real users will experience →
- once verified, merge `dev` → `main` and push. That's when users get
- the change.
+ shows an amber DEV badge in the header.
+- **Workflow**:
+ 1. Default to working on `dev`. `git checkout dev` at the start of
+ any session that touches Phosphene; if you're on `main`, switch.
+ 2. Commit + push to `origin/dev` whenever a logical change is done.
+ 3. **Stop there.** Tell Salo it's on dev. Wait for explicit
+ instruction to promote.
+ 4. When Salo says push to main: `git checkout main && git merge dev
+ --ff-only && git push origin main`. Then `git checkout dev` so
+ subsequent work continues on dev.
+ 5. If a fast-forward isn't possible (rare — usually a hotfix landed
+ on main directly), say so and ask before doing anything destructive.
- The panel auto-detects which profile it is from `git rev-parse
--abbrev-ref HEAD`: branch == `dev` → port 8199 + DEV badge; anything
else → port 8198 + normal header. No config files to edit per panel.
-- `update.js` is also branch-aware as of Y1.015 (`git pull --ff-only
- origin <current branch>`) so the dev panel's Update pulls dev and
- the production panel's Update pulls main, from the same shared code.
+- `update.js` is branch-aware as of Y1.015 (`git pull --ff-only origin
+ <current branch>`) so the dev panel's Update pulls dev and the
+ production panel's Update pulls main, from the same shared code.
- The dev panel symlinks `mlx_models/` from the production install
(saves ~36 GB of duplicate weights). State / outputs / uploads stay
separate per panel.
-- Don't push experimental commits directly to main. Always go via dev.
- The whole point of the staging panel is to verify before users hit it.
+- Hotfixes bypassing dev — only allowed when Salo explicitly authorises
+ ("hotfix straight to main" or similar). Otherwise, even one-line
+ fixes go via dev → tested in Phosphene Dev panel → merged.
### Git policy — NEVER FORCE-PUSH `origin/main`
- A history-rewrite + force-push on 2026-05-01 (to scrub identity
diff --git a/QWEN.md b/QWEN.md
index 3cf6fb6..120c236 100644
--- a/QWEN.md
+++ b/QWEN.md
@@ -167,28 +167,47 @@ new patch versions without a venv rebuild — used when we added
### Branch model — `main` is production, `dev` is staging (Y1.015+)
-- **`main`** is what real users get. Pinokio's Discover URL points here;
- every commit pushed to `main` is shipped to every user the next time
- they click Update. Treat it accordingly.
+**TL;DR for agents — non-negotiable:**
+
+> **Push every commit to `dev`. Never push to `main` unless Salo
+> explicitly says "push to main" / "ship to production" / "merge to
+> main".** "It works on my machine" is not permission. "The tests
+> pass" is not permission. Salo has a Phosphene Dev panel in his
+> Pinokio that pulls from `dev`; he tests there, then tells you when
+> to promote.
+
+The why:
+
+- **`main`** is what real users get. Pinokio's Discover URL points
+ here; every commit pushed to `main` is shipped to every user the
+ next time they click Update. Treat it as production.
- **`dev`** is the staging branch. Push WIP commits here freely. The
local "Phosphene Dev" Pinokio panel (set up via
`scripts/setup_dev_panel.sh`) tracks this branch on port 8199 and
- shows a DEV badge in the header.
-- **Workflow**: develop on `dev` → push to `origin/dev` → click Update
- in the Phosphene Dev panel → test what real users will experience →
- once verified, merge `dev` → `main` and push. That's when users get
- the change.
+ shows an amber DEV badge in the header.
+- **Workflow**:
+ 1. Default to working on `dev`. `git checkout dev` at the start of
+ any session that touches Phosphene; if you're on `main`, switch.
+ 2. Commit + push to `origin/dev` whenever a logical change is done.
+ 3. **Stop there.** Tell Salo it's on dev. Wait for explicit
+ instruction to promote.
+ 4. When Salo says push to main: `git checkout main && git merge dev
+ --ff-only && git push origin main`. Then `git checkout dev` so
+ subsequent work continues on dev.
+ 5. If a fast-forward isn't possible (rare — usually a hotfix landed
+ on main directly), say so and ask before doing anything destructive.
- The panel auto-detects which profile it is from `git rev-parse
--abbrev-ref HEAD`: branch == `dev` → port 8199 + DEV badge; anything
else → port 8198 + normal header. No config files to edit per panel.
-- `update.js` is also branch-aware as of Y1.015 (`git pull --ff-only
- origin <current branch>`) so the dev panel's Update pulls dev and
- the production panel's Update pulls main, from the same shared code.
+- `update.js` is branch-aware as of Y1.015 (`git pull --ff-only origin
+ <current branch>`) so the dev panel's Update pulls dev and the
+ production panel's Update pulls main, from the same shared code.
- The dev panel symlinks `mlx_models/` from the production install
(saves ~36 GB of duplicate weights). State / outputs / uploads stay
separate per panel.
-- Don't push experimental commits directly to main. Always go via dev.
- The whole point of the staging panel is to verify before users hit it.
+- Hotfixes bypassing dev — only allowed when Salo explicitly authorises
+ ("hotfix straight to main" or similar). Otherwise, even one-line
+ fixes go via dev → tested in Phosphene Dev panel → merged.
### Git policy — NEVER FORCE-PUSH `origin/main`
- A history-rewrite + force-push on 2026-05-01 (to scrub identity