A manual pipeline creation instantiates every pipeline in .crow/, so one whose
only manual condition is a bare `event: manual` fires on any manual trigger in
this repo. auto-apply-patches, weekly-patch-proposals and trial-build-registry
were in that state and all ran unintentionally alongside a manual
process-updates run.
- gate each on a variable named after the pipeline, defaulting to 'false', as
repair-built-stamp.yaml documents and the other pipelines already do
- refresh the stale run-manually comments, which still referenced a `task`
variable that no pipeline evaluates
pat-s
70dc82fd9e