Post-cleanup settings reset.

components/chrome_cleaner/public/constants/constants.h

Index: components/chrome_cleaner/public/constants/constants.h
diff --git a/components/chrome_cleaner/public/constants/constants.h b/components/chrome_cleaner/public/constants/constants.h
index 9ca9a5d317c3278047b7952e19cb37ddc8d84c6a..ced4934ec17823b21ce3eb9a9fe8ec8b9181dbdb 100644
--- a/components/chrome_cleaner/public/constants/constants.h
+++ b/components/chrome_cleaner/public/constants/constants.h
@@ -70,6 +70,15 @@ extern const wchar_t kCleanerSubKey[];
 // The suffix for registry key paths where scan times will be written to.
 extern const wchar_t kScanTimesSubKey[];
 
+// Registry value names where the timestamps for cleanup start and completion
+// are written to.
+extern const wchar_t kCleanupConfirmedTimestampValueName[];
+// Note to reviewer: I'm thinking of removing the need for the start ts and
+// rely only on the confirmation ts, that would be erased once a cleanup
+// starts and written to when it completes (either with or without a reboot).
+// Please help me find the flaw in the reasoning. Thanks.
+extern const wchar_t kCleanupStartedTimestampValueName[];
+
 // Registry value names where metrics are written to.
 extern const wchar_t kEndTimeValueName[];
 extern const wchar_t kEngineErrorCodeValueName[];