You could try to evolve from programmer (aka code monkey) to software engineer (for lack of a better term) by taking responsibility for a larger part of the toolchain. It might not be necessary for your project, but it'll give you plenty of learning opportunities and experience that is invaluable in larger projects.
I'm thinking about the ecosystem for docs/test/CI/build/packaging. IMHO it's seems a good place to start given that you want to code still (much like myself). Writing plugins for these kind of things is good training, and it forces you to read other people's code, which is pretty vital in growing a career.
If you're afraid of being replaced by someone doing the same job but cheaper, I heartily recommend reading Linchpin by Seth Godin. I finished it myself just before the holidays.
Short version: Make sure you do your job so excellently and proactively that your actual work can't be described in a binder. Then you can't be replaced or outsourced, becuase they can't afford to lose you.
And if they don't want you to do a kick-ass job, leave and go work someplace else.