The arrogant bit is "here's a link to the source and instructions on how to compile it, feel free to do what you need". A recruiter asking for an editable version wants something they can drop their letterhead on and forward to the client. Handing them a build task assumes they have both the skills and the inclination to meet you on your toolchain. Nobody expects you to be their typesetter either; the difference in skills isn't the problem, assuming the difference away is.
That mismatch is the part I'd actually be screening for. A company is mostly non-engineering people: sales, support, HR, PMs who can't read a diff. The recruiter is the one non-technical person in your hiring pipeline, and how you handle them is a sample of how you'd handle the fifty you'd work alongside. If the instinct is to make them come to your toolchain rather than meet them where they are, that plays out in every meeting and every "quick question" from sales for as long as you're employed. The CV is the one document whose entire purpose is to sell you to a non-technical audience, and handling that poorly is telling.
I've maintained my own CV in LaTeX for ~20 years and would never dream of sending a recruiter a Makefile and telling them to work it out.
Sent to me directly? Fine, I'd read the repo, probably be impressed, might even see if I could improve mine from it. That was never the scenario though.