My team has to take over a project from an external company. They've provided the last state of trunk to us as a zip file and are trying to convince us, to accept this as a complete delivery of their development.
I strongly object this, as I consider source code as the following:
code = history of single commits + project structure (read branches, tags) + documentation (as much as there is)
In other words I deem this as a very incomplete delivery of a project, that would would do nothing but making future development more error prone. Needless to say, we cannot rely on support by the former developers to questions that arise because of legacy code.
I'm aware this question could be considered somewhat opinion based, but maybe it is still possible to find hard facts that define source code and when it can be considered complete?
Is there any literature that I can cite on that topic?