Open source CapCut alternative.
TypeScript
docs: require model retirement during catalog updates
David Lee44500272a09
diff --git a/AGENTS.md b/AGENTS.mdindex 17610ee5..4972426f 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -64,6 +64,7 @@ Every Cut change has to hold on every surface, and the plan for it says how:- 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.+- GPT and Claude model updates include retirement. Verify provider availability and lifecycle in official docs; retire superseded picker entries when a supported successor covers their role, retaining distinct capability or cost tiers. Distinguish Donkey retirement from provider deprecation. Update callers and defaults, migrate saved selections to explicit replacements within the same provider, and preserve chat history. Verify new selections and resumed chats in the same change.- Configuration is code with a runtime override. Tunables, switches and thresholds are declared in the settings registry (`site/src/lib/config/registry.ts`) with a default and a schema, overridden from su, and read through it everywhere; env is for secrets. An experiment is variants over settings, drawn by an audience; a feature that people might tune ships its setting in the same change.- Fail hard. One provider, one model, one code path per job; a missing API key, service, or capability is an error surfaced to the caller. No secondary providers, no retry-on-another-model paths, no `env.X || default` softening. A fallback exists only when it is absolutely necessary — a surface that genuinely cannot carry the feature — and the summary and the guide say so.- 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 17610ee5..4972426f 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -64,6 +64,7 @@ Every Cut change has to hold on every surface, and the plan for it says how:- 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.+- GPT and Claude model updates include retirement. Verify provider availability and lifecycle in official docs; retire superseded picker entries when a supported successor covers their role, retaining distinct capability or cost tiers. Distinguish Donkey retirement from provider deprecation. Update callers and defaults, migrate saved selections to explicit replacements within the same provider, and preserve chat history. Verify new selections and resumed chats in the same change.- Configuration is code with a runtime override. Tunables, switches and thresholds are declared in the settings registry (`site/src/lib/config/registry.ts`) with a default and a schema, overridden from su, and read through it everywhere; env is for secrets. An experiment is variants over settings, drawn by an audience; a feature that people might tune ships its setting in the same change.- Fail hard. One provider, one model, one code path per job; a missing API key, service, or capability is an error surfaced to the caller. No secondary providers, no retry-on-another-model paths, no `env.X || default` softening. A fallback exists only when it is absolutely necessary — a surface that genuinely cannot carry the feature — and the summary and the guide say so.- 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.