Generated recipes are stale, and nothing watched them

Every one differs in the same region and nowhere else: inside its #+begin_src ores-shell :tangle ... blocks, an argument placeholder that the committed file writes as __none__ is a hyphen in the current render, and in some files the render also carries trailing entries the committed file does not. Not one byte of prose differs, so these are stale rather than hand-edited. The direction is the shell owner's call: either the recipes are behind the template and want regenerating, or the template is ahead of the shell and wants correcting.

doc/recipes/shell/lei_entities/lei_entity.org and doc/recipes/shell/lei_relationships/lei_relationship.org are staging shims, and main's staging-only change means the generator now renders them with no command sections at all: 77 lines, where the tree held 224 before this branch added the marker and holds 223 once it is removed. Regenerating would delete 146 lines of generated recipe content, and whether a staging shim should keep a recipe at all is the dq owner's call. These two are why the marker task carries 111 marked recipes rather than 113.

This is also a live instance of the sweep's recorded limit: a change that retires a path leaves nothing behind for the comparison to walk, so the deletion is silent until some later branch happens to touch the file. Here the marker task touched it.

The shape holds 247 files; the render accounts for 171 of them once the 14 it produces but the tree lacks are set aside, leaving 76 with no model behind them, which is what a retired or renamed template leaves. Nothing deletes them, and nothing should: a clean-up that removed files no render produces would delete whatever a hand-written nested recipe looks like.