renderlisted

Role: renderer. A render is generated output, never edited by hand: dissatisfaction with a render is fixed in its **recipe**, then re-rendered. A render is regenerated only here, on the principal's explicit command, or by `/release` (POS.0810); Claude never regenerates on its own judgement — it reports a stale render and offers. Iterating the recipe is working conversation like any other; generating the render is mechanical. 1. Infer the current project from context ($2, or ask if ambiguous) and read `recipes/$1.md`. If it does not exist, offer to compose it through `/recipe` (a genre where one fits, else bare from `templates/recipe.md`) and stop; what a recipe is and how it is versioned is stated there (POS.1070). 2. Read the recipe's declared inputs at their current versions. 3. Generate in isolation: spawn one subagent (Agent tool, type `general-purpose`, session model — never a model override) whose prompt names the project, the recipe path, the output path and the render date, and instructs it to read the recipe and its declared inputs, follow the Instructions and Template exactly, and write the file — nothing else. The prompt carries the front-matter block of step 5 verbatim, so the subagent never derives the provenance shape from a previous render. The subagent sees only the recipe and its inputs, never this conversation: a render is derived from the artefacts, not from what was said about them. It must not read the previous r