If you do not want to provide the user directly a current copy of your source code to downloaded, you can "accompanied [it] by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software".
Then you should be able to fulfill a request for the source code used at an exact date and time 2 years ago even when you already discontinued the product and let go of all people involved. If such a request comes from controlled country like Iran or a recently banned company like Huawei or ZTE it could also get funny for your legal department.
I am not a lawyer, please consult one if you want to find loopholes in contracts.
Imagine getting a (binary) copy of GCC and the README said —
this is version X.Y.Z. Please wait up to two months to download the source code. Until then, you can download the source code for X.Y.Z-2.
IANAL either, but my interpretation was always that you had to treat AGPL code in the same way as GPL, except for the fact that access by remote/internet users was considered a distribution.
Just like sibling commenter haukem pointed out, GPL does not mandate that you distribute the source code alongside the binary, as long as there is an official channel to request the source code.
GPL license predates version control, and code often had to be snail-mailed at the time. This can lead to funny situations like famous hacker Naomi Wu dropping by hardware manufacturer offices to get the GPL source code. [0]
So yes, you could distribute a binary version of FunnySoft v1.3, and it could take a few days/weeks/months to get a copy of the actual source code.
[0] https://nitter.snopyta.org/RealSexyCyborg/status/14287069892...