Open source CapCut alternative.
TypeScript
docs: ship iOS to TestFlight after a commit run
David Le768f98af8ab8
diff --git a/AGENTS.md b/AGENTS.mdindex 1097f5b9..859f1346 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -47,6 +47,7 @@ Every Cut change has to hold on all four surfaces, and the plan for it says how:- Keep guide source entrypoints short and readable. Do not write exhaustive file inventories. Prefer a small maintainer map by subsystem or one to seven high-signal paths, and link to a source path only when it gives someone a clear place to start.- When asked to commit, group the working changes into logical commits by concern rather than one catch-all commit, then merge into `main`. Write messages as `type(scope): summary`, where `type` is a Conventional Commits kind (`feat`, `fix`, `docs`, `refactor`, `chore`, etc.) and `scope` is the area touched (e.g. `feat(site)`, `fix(app)`, `refactor(site)`); `scope` may be omitted when an area does not apply, as in `docs:`. Do not push unless asked.- End the commit subject with ` [rebuild]` when the change ships inside the Mac app and needs a new build: `apps/`, the Cut engine (`site/src/cut/engine/`, `site/src/cut/server/`, and the `site/src/cut/lib/` modules they compile in — `types`, `ports`, `hosts`, `looks`, `colorGrade`, `cueAlign`, `backend/`), or bundled tooling (`tools/`, the bundled-tools scripts). The label is what triggers a release, so an app change without it never reaches users; hosted-site-only changes take no label.+- After a commit run finishes, ship iOS: when the committed changes touch `apps/ios/` and the working tree is clean, run `scripts/ship-ios-testflight.sh` once the merge into `main` lands, so the build reaches TestFlight. The script archives from the committed ref, so it goes after the commits.- Prefer deleting over documenting what was removed. Guides describe what is supported now, not what used to be.- Build forward by default. Prefer updating callers and contracts to the new supported shape instead of preserving old compatibility paths; ask before adding or keeping backwards-compatibility shims.- After finishing a task, summarize what you did. Ground the summary in the actual code changes — name the files and behavior that changed, not the intent you set out with. If nothing changed, say so. When the change has a shape worth seeing — a system flow or a UI layout — include a small ASCII diagram of it.diff --git a/CLAUDE.md b/CLAUDE.mdindex 1097f5b9..859f1346 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -47,6 +47,7 @@ Every Cut change has to hold on all four surfaces, and the plan for it says how:- Keep guide source entrypoints short and readable. Do not write exhaustive file inventories. Prefer a small maintainer map by subsystem or one to seven high-signal paths, and link to a source path only when it gives someone a clear place to start.- When asked to commit, group the working changes into logical commits by concern rather than one catch-all commit, then merge into `main`. Write messages as `type(scope): summary`, where `type` is a Conventional Commits kind (`feat`, `fix`, `docs`, `refactor`, `chore`, etc.) and `scope` is the area touched (e.g. `feat(site)`, `fix(app)`, `refactor(site)`); `scope` may be omitted when an area does not apply, as in `docs:`. Do not push unless asked.- End the commit subject with ` [rebuild]` when the change ships inside the Mac app and needs a new build: `apps/`, the Cut engine (`site/src/cut/engine/`, `site/src/cut/server/`, and the `site/src/cut/lib/` modules they compile in — `types`, `ports`, `hosts`, `looks`, `colorGrade`, `cueAlign`, `backend/`), or bundled tooling (`tools/`, the bundled-tools scripts). The label is what triggers a release, so an app change without it never reaches users; hosted-site-only changes take no label.+- After a commit run finishes, ship iOS: when the committed changes touch `apps/ios/` and the working tree is clean, run `scripts/ship-ios-testflight.sh` once the merge into `main` lands, so the build reaches TestFlight. The script archives from the committed ref, so it goes after the commits.- Prefer deleting over documenting what was removed. Guides describe what is supported now, not what used to be.- Build forward by default. Prefer updating callers and contracts to the new supported shape instead of preserving old compatibility paths; ask before adding or keeping backwards-compatibility shims.- After finishing a task, summarize what you did. Ground the summary in the actual code changes — name the files and behavior that changed, not the intent you set out with. If nothing changed, say so. When the change has a shape worth seeing — a system flow or a UI layout — include a small ASCII diagram of it.