model-check

# /socialforge:model-check — which model to call, decided today SocialForge does not know which model to use. That is deliberate. A model id written into a plugin is a claim about the day it was written, and this plugin gets run long after that day. Six ids used to sit on the execution path. One video fallback stayed pinned to a superseded generation for about six months, and nothing in the system could say so — which matters because a retired id does not degrade gracefully. It fails at the exact moment the two providers ahead of it have already failed and the fallback is all that is left. So the code asks for a **kind** of model. You find out what currently satisfies it. ## The rule **Never supply a model id from memory.** Not from this file, not from a recipe, not from what a model was called last time you looked. If `model_book.py` says `unknown` or `stale`, go and read the provider's catalogue. ## What the code asks for ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/model_book.py" --action kinds ``` Capabilities, not products — `video.image-to-video`, not a version number. A kind outlives every model that has ever satisfied it, which is the entire point. ## Finding the current best 1. See where to look, and what is odd about each provider: ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/model_book.py" --action discovery ``` Two things it will tell you that save time: **Higgsfield puts the model in the URL path** (so a hardcoded path is a hardcoded model), and *...