We have all the information necessary to recognize flaky tests. We should use it to prompt the gardener to mark the test as flaky.
The flakiness should be revealed in the "Failing Tests" view, so that you could have a choice to mark a test as either failing or flaky. It might also be useful to show an item in the ui.notifications.TestsFailing "causes" list, indicating that a test is flaky -- and provide a "Mark as Flaky" button there, too. An edge case where you have 400 tests failing, and 300 of them are also flaky, thus making "causes" list be extremely long seems unlikely.
Punt to v2.
avoid a trip to the flakiness dashboard - is the test flaky? - since when?