diff --git a/cauldron/templates/consolidate.html b/cauldron/templates/consolidate.html index 8669d9b..7ebedf1 100644 --- a/cauldron/templates/consolidate.html +++ b/cauldron/templates/consolidate.html @@ -67,7 +67,7 @@

foods consolidate

scan your mealie household foods, cluster lookalikes by similarity, - let sage pick the survivor + the rest become aliases on it. mealie + let hecate pick the survivor + the rest become aliases on it. mealie rewrites every recipe ingredient to point at the canonical row.
@@ -83,7 +83,7 @@

no run yet. kick one off?

- walks your household catalog, clusters by name similarity, asks sage for the survivor of each cluster. + walks your household catalog, clusters by name similarity, asks hecate for the survivor of each cluster. first run might take 5-15 min depending on cluster count.

diff --git a/cauldron/templates/dedupe_recipes.html b/cauldron/templates/dedupe_recipes.html index 9ff2b53..a29d936 100644 --- a/cauldron/templates/dedupe_recipes.html +++ b/cauldron/templates/dedupe_recipes.html @@ -60,7 +60,7 @@
// dedupe ยท find duplicate recipes

recipe dedupe

- scan your household recipes for duplicates by name similarity. sage + scan your household recipes for duplicates by name similarity. hecate looks at ingredients + step counts + source URLs to decide whether similar-named recipes are actually the same dish. you confirm per cluster โ€” DELETE in Mealie is permanent. @@ -77,7 +77,7 @@ @@ -378,7 +378,7 @@ ${rows}`; card.appendChild(tbl); } else { - // All rows were identity matches โ€” sage thinks this recipe is + // All rows were identity matches โ€” hecate thinks this recipe is // already clean. Show a marker; user can still skip/approve as // a no-op apply (which will be cheap, just refreshes food.id // resolution if any food row got renamed in Mealie).