lexforge-debuglisted

<!-- model-block:start --> ## Model When your project names no model for your runtime, run this work on the model your own provider is given here. What the project names replaces this table. | Provider | Model | |---|---| | anthropic | claude-sonnet-5 | | openai | gpt-5.6-terra | | google | gemini-3.7-flash | | deepseek | deepseek-v4-flash | | z.ai | glm-4.7-flash | A provider outside the table names nothing, so work on the model at work. <!-- model-block:end --> <!-- queue-rule:start --> <!-- model-gate:start --> ## Model gate `provider` and `model` name the model this work runs on. Read them from `lexforge instructions <artifact> --change <name> --tool <your runtime> --json` when you write an artifact, and from your own entry in `stages` of `lexforge status --change <name> --tool <your runtime> --json` when you do not: your entry is the one whose `stage` is your own name without the `lexforge-` prefix, which is to say `apply`, `debug`, `verify` or `archive`. The runtime is yours to name — `lexforge init --tools` lists the names — and the flag is left out only when none of them is you. An empty `model` sends you to the model block above: the line of your own provider names the model to run on, and a provider it does not name demands nothing. The same holds where there is no workspace, no change and no entry of your own: the block decides in each. Running on that model: work, and say nothing about models. Running on another one: start a subagent on the assigned model,