Changes to the internal manifest repository are used in the CQ to generate the pinned manifest used for the CQ run.

However, those manifests are applied and "tested" much differently from other CLs, and don't ever get blamed for CQ failures.

They should very clearly be blamed if we are unable to sync code after applying the CL, but that doesn't happen today, as can be seen in the following failures all caused by my CL:*293055. Those failures continued until the CL was manually marked as non-valid.

https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/12584
https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/12585
https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/12586