This may be a better fit for a different site, but I couldn't really find one that served the intersection of software engineering and business norms. My primary concern here is about something I thought was a business norm: a couple of hours of post-handoff cooperation when a new developer is brought in to start work.
I was brought on as a subcontractor on a project. That project continued for several months in active development, and was (very abruptly) canceled without notice -- literally just 'invoice your remaining hours and goodbye'.
The code base was handed over to the super client, as were the working Heroku instances. Moving on, I've discovered that my client has been getting some support requests -- basically an hour or so's phone meeting with the new developer to run him down on what has been done.
I always thought that a reasonable amount of handover support -- an hour or two on the phone to give a quick rundown on the code, how it's laid out, why it's laid out that way, current issues, etc etc -- was a norm. But my client is refusing to do any such thing. I am worried about how professional it does (or rather, does not) make him look, and how that may reflect on me as a subcontractor.
The situation is further complicated by the fact that, late in the project life cycle, the decision was made to shift me from sub-contractor to contractor. My client was basically shifted from a contract to develop software to a contract to manage a team of contractors doing further development. I haven't been contacted directly by super-client, but I now technically have my own relationship with him and want to plan ahead in case he reaches out to me.