I think the account close changes look good.

I'm curious the values are being extracted from ExecuteOrder now instead of passing the struct along directly as before?

Do you mean here?

I did this because I lazily passed a mutable reference to the whole ExecuteOrder composite before. I think passing each account from this context reflecting whether each account should be a static ref or mut ref feels better. What do you think?

As I look at this more, it's an interesting trade off of whether to pass specific references of each account from the composite. Or to pass the composite to leave it less error-prone to reference each account in the composite.

I guess inside the shared method I could specify static references to specific accounts. Is that preferred?

As I look at this more, it's an interesting trade off of whether to pass specific references of each account from the composite. Or to pass the composite to leave it less error-prone to reference each account in the composite.

I guess inside the shared method I could specify static references to specific accounts. Is that preferred?

Made the change here: 731df93. This does feel better. What do you think?

Going to merge this. @johnsaigle if you have a strong opinion about how the refs should be passed, I'll put up another PR after we discuss it.