@shop-os/modelkit 0.2.18 → 0.2.20

package/CHANGELOG.md

@@ -9,6 +9,25 @@ header in the release PR.
 
 ## [Unreleased]
 
+## [0.2.20] - Unreleased
+
+### Added
+- `constraints.audio` (`"always" | "optional" | "never"`): whether a video row's output has sound. Every video row sets it; `supports: ["generateAudio"]` still means only that sound can be switched. Read it with `outputAudio(row)`.
+- `constraints.prompt` (`{ referenceSyntax: "numbered" | "caption" | "descriptive"; maxChars? }`): how a prompt should point at reference N. Gemini image rows and the Gemini Omni rows use `caption` (their adapters send `MediaRef.label`); every other row reads as `numbered`. Read it with `promptConventions(row)`.
+- Both keys are strict on write (`CatalogModelSchema`, pro-backend's pro-admin validation) and tolerant on read: `load.ts` keeps a row with an invalid value and the accessors read it as not set.
+- On read, `load.ts` removes an invalid `constraints.audio` and normalises an invalid `constraints.prompt` (with one warning per row), so a loaded row never carries an invalid value typed as valid. `CatalogSchema` normalises the same way (via `normaliseConventions`, exported from `conventions.ts`); the write schema `CatalogModelSchema` stays strict.
+
+### Fixed
+- `minimax-h3-reference` / `minimax-h3-max-reference`: `capabilities.framesExcludeReferences: true`. A start frame sent with references was silently lost (fal's reference-to-video endpoint ignores frames); the resolver now keeps the frame and drops the references with a warning (coerce) or rejects the pair (error).
+- `flux-2-pro`: `references.images: 8`. The row declared no limit, so every reference reached Prodia.
+
+Mirror every row change on the pro-backend `model_catalog` rows in each environment, after pro-backend is on 0.2.20 (apps read the rows, not this file), and set `constraints.audio: "always"` on the pro-admin-only `p-video-2-pro` row.
+
+## [0.2.19] - Unreleased
+
+### Changed
+- `gemini-3.1-flash-image-preview` (Nano Banana 2) description says "concept boards" instead of "moodboards": Sloosh has no moodboards and shows this text in its model picker. Mirror the change on the pro-backend `model_catalog` row (`display.description`) in each environment; apps read the row, not this file.
+
 ## [0.2.18] - Unreleased
 
 ### Changed

package/README.md

@@ -259,7 +259,7 @@ const defaultKit = createDefaultModelKit({ keys: { pro: keysFromEnv(process.env)
 ## Consumers
 
 Every app takes the published package from npm, not a `workspace:*` link. This is a
-deliberate decision (AGENTS.md §3.1): consumers span three repos and must agree on one
+deliberate decision (AGENTS.md §3): consumers span three repos and must agree on one
 version, the package bundles provider SDKs the Docker whitelist recipe would have to
 rebuild per app, and the Trigger.dev deploys have no `packages/` in their build context.
 The accepted cost: a kit change and its consumer change never land in one PR, and a