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 ad1b8af203b7f34455384faca6c5b086f81f9d5d..ef586c1d8fe3bebc714025c5e85a593ee31e75f2 100644
--- a/components/chrome_cleaner/public/constants/constants.h
+++ b/components/chrome_cleaner/public/constants/constants.h
@@ -79,6 +79,11 @@ 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[];
+extern const wchar_t kCleanupStartedTimestampValueName[];

[ftirelo, 2017/06/06 19:28:16]

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.

+
 // Registry value names where metrics are written to.
 extern const wchar_t kEndTimeValueName[];
 extern const wchar_t kEngineErrorCodeValueName[];