-
-
Notifications
You must be signed in to change notification settings - Fork 0
sustainabot: add SafeDOMExample.res→.affine standing recipe #214
Copy link
Copy link
Open
Labels
automationBots, schedulers, dispatch, self-healing, fan-outBots, schedulers, dispatch, self-healing, fan-outenhancementNew capability or improvement to existing behaviourNew capability or improvement to existing behaviourmeta:recurringRecurs on a schedule or by trigger; never finally closedRecurs on a schedule or by trigger; never finally closed
Description
Metadata
Metadata
Assignees
Labels
automationBots, schedulers, dispatch, self-healing, fan-outBots, schedulers, dispatch, self-healing, fan-outenhancementNew capability or improvement to existing behaviourNew capability or improvement to existing behaviourmeta:recurringRecurs on a schedule or by trigger; never finally closedRecurs on a schedule or by trigger; never finally closed
Context
gitbot-fleet#208 ran a one-time sweep of
SafeDOMExample.res→SafeDOMExample.affineacross 125+ repos. Today's otpiser#11 + estate sweep revealed that three template repos kept regenerating the .res variant on every new repo, so the sweep needs to be a STANDING sustainabot recipe rather than a one-shot.Template-side fixes landed today in:
But sustainabot should still carry a standing recipe for any new fork / external clone that introduces the .res copy.
Recipe
Add to
recipes/safedom-example-affine.yaml:The
skip_ifpredicate prevents the recipe from firing on repos with non-SafeDOM.resfiles (which need affinescript#57 Phase 2 first). Today's empirical skip-set:Source of truth
gh api repos/hyperpolymath/burble/contents/examples/SafeDOMExample.affine?ref=main(cached at burble main).Cross-refs: hypatia#336 (corresponding hypatia detection rule).
Filed from session sweeping otpiser#11 + estate-wide drift.