It does in the sense of intent -- if they built the tool for the express purpose of avoiding copyright restriction, they would do more than hide it in a random

It does in the sense of intent -- if they built the tool for the express purpose of avoiding copyright restriction, they would do more than hide it in a random unit test or code comment. Putting it in the README itself would be a far stronger signal of intentional malfeasance. In the unit test... it's pretty clear the original developer's intent was simply to pick a video, and chose a trivially popular one (taylor swift), with likely no mind towards copyright (or its avoidance). That is, the tool happens to be capable of the job, because it simply has purpose to download videos, with no awareness of copyright law.