From 8b4b9b2edfc7ad1f355c7c5c0fe0dc944b0bb732 Mon Sep 17 00:00:00 2001
From: Carlo Costanzo <2160436+CCOSTAN@users.noreply.github.com>
Date: Wed, 15 Apr 2026 09:35:54 -0400
Subject: [PATCH] Harden OneNote cleanup prompt

Require dependency checks and a clear failure response for scheduled cleanup runs.
---
 config/packages/onenote_indexer.yaml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/config/packages/onenote_indexer.yaml b/config/packages/onenote_indexer.yaml
index b03b80ef..febe3775 100644
--- a/config/packages/onenote_indexer.yaml
+++ b/config/packages/onenote_indexer.yaml
@@ -138,7 +138,11 @@ automation:
           diagnostics: "scheduled_time=03:15:00"
           request: >-
             Run OneNote duplicate cleanup and apply deletions.
-            Include delete reconciliation, then send a brief conversational morning summary.
+            Start with any dependency check needed before cleanup or delete reconciliation.
+            If cleanup does not finish cleanly or index health is not confirmed, report back with:
+            Headline: Cleanup did not finish cleanly; index health is not confirmed.
+            Action: Retry cleanup after dependency check.
+            Otherwise include delete reconciliation, then send a brief conversational morning summary.
             Tell me whether cleanup finished and whether anything actually changed.
             Only include detailed counts or backend metrics if pages were removed, something failed, or you need my attention.