There was an error published in Development139, 3926-3937.

Fig. S6 was incorrect. The correct Fig. S6, as shown below, now appears in the supplementary data.

We apologise to the authors and readers for this mistake.