Genuine questions: what do you think the request was? To build the plan? To prepare the commit? Do you never have a second thought after looking at your output, or realize you forgot something you wanted to include? Could it be that they saw "one new function", thought "boy, there should really be two... what happened?" and changed their mind?
To your original comment, it would be like calling your intern to ask them to order lunch, and them letting you know the sandwich place you asked them to order from was closed, and should they just put in an order for next Tuesday at an entirely different restaurant instead? And then that intern hearing, "no, that's not what I want" saying "well, I don't respect your 'no'" and doing it anyways.
"Do X" -> "Here are the anticipated actions (which might deviate from your explicit intent), should I implement?" -> "no, that's not actually what I want"
is a clear instruction set and a completely normal thought pattern.
Genuine questions: what do you think the request was? To build the plan? To prepare the commit? Do you never have a second thought after looking at your output, or realize you forgot something you wanted to include? Could it be that they saw "one new function", thought "boy, there should really be two... what happened?" and changed their mind?
To your original comment, it would be like calling your intern to ask them to order lunch, and them letting you know the sandwich place you asked them to order from was closed, and should they just put in an order for next Tuesday at an entirely different restaurant instead? And then that intern hearing, "no, that's not what I want" saying "well, I don't respect your 'no'" and doing it anyways.
"Do X" -> "Here are the anticipated actions (which might deviate from your explicit intent), should I implement?" -> "no, that's not actually what I want"
is a clear instruction set and a completely normal thought pattern.