Ok, so given your position I can see how learning a new framework might be something you would be tired of, especially as you suspect that the knowledge you gain will be obsolete in 2 years and how much time do you want to spend learning cruft which doesn't last, because you've already done than 10 times.
I'd say the answer is to move up the career ladder. Let the new people learn the new framework, your value add is you know the types of mistakes people make when working in a new framework (programmer mistakes and manager/planing mistakes), and with your support the younger team members will be 10x as productive. Your steady hand gets the project delivered on time/budget despite the massive underestimation of technology risk.
I'd say the answer is to move up the career ladder. Let the new people learn the new framework, your value add is you know the types of mistakes people make when working in a new framework (programmer mistakes and manager/planing mistakes), and with your support the younger team members will be 10x as productive. Your steady hand gets the project delivered on time/budget despite the massive underestimation of technology risk.
And you can do this w/o moving into management.