Reconcile the request queue on startup.

components/offline_pages/core/background/cleanup_task.cc

Index: components/offline_pages/core/background/cleanup_task.cc
diff --git a/components/offline_pages/core/background/cleanup_task.cc b/components/offline_pages/core/background/cleanup_task.cc
index ab02e4f0ee278e4aae3abc972632347143cf251b..84e2a7864d4c24f9c466899da980bcd411166657 100644
--- a/components/offline_pages/core/background/cleanup_task.cc
+++ b/components/offline_pages/core/background/cleanup_task.cc
@@ -88,11 +88,6 @@ void CleanupTask::GetExpiredRequestIds(
         OfflinerPolicyUtils::CheckRequestExpirationStatus(request.get(),
                                                           policy_);
 
-    // TODO(petewil): The strategy of checking the state below relies on a
-    // reconciliation task, so at startup we convert any OFFLINING requests to
-    // AVAILABLE.  Otherwise, requests in the OFFLINING state when chromium dies
-    // will never be cleaned up.
-
     // If we are not working on this request in an offliner, and it is not
     // valid, put it on a list for removal.  We make the exception for current
     // requests because the request might expire after being chosen and before