Yes it's a temporary workaround which fixes the problem. It deserves further works but thanks to the workaround, the problem isn't there anymore. Your point?
Point being that they were just clarifying the situation as they are probably one of the most informed people on the situation (with the other reply in this subthread being a first party bluesky dev and therefore one of the other SMEs on the topic).