Remove 4444's and `Oldest Unaudited` audit strategies.

[KolbyML]

I think we should remove 4444's audit then as once we reach 100% saturation of history it is no longer the value metric. 4444's audit was added when the only value thing was pre-merge and the only thing we could provide is pre-merge. I think saying we support the full history is a lot more impressive, then advertising we support 4444's.

So I think we should only have 2 audit modes

• latest
• random

From the conversation in this #411 issue, I am pretty convinced full history is the better north star now, 4444's audit served its purpose. If we support full history, then we support 4444's.

I want us to 10-100x the rate we do audits as well 😤, we can delete older audits I would rather have a more up to date recent view.

[carver]

Clients that are gearing up for history expiry definitely care that we have 100% reliability in the target range of data. That is true now, but we want to be able to continue showing that it's true at least until expiry is fully rolled out to all clients. (and probably for some time after)

👍🏻 to faster audits, which I think #401 will address nicely for premerge data. There are some CPU limits that probably constrain audit speed at the moment, which is under investigation: #415

No objection to dropping Oldest Unaudited from the audit dashboard. Seems it has been shut off for a while.