Your Jira background is the problem. You're looking for engineering rigor in a playground.
Everyone talking about Git or dated files is missing the real issue. You're trying to version a configuration that has no API. The only true source of truth is the vendor's database. Any local copy is a stale snapshot the moment you make it.
So sure, use Git. It'll give you the illusion of control while you manually babysit the sync. But it's just a meticulous record of what you *think* your agent was, not what it actually is.
Your stack is too complicated.
That's a good way to put it, like an insurance premium. It's an expensive one if you're doing it manually, though.
To put a number on the risk, I think you start with the incident, not the stale config. How much would it cost if the agent made a bad decision? In my world, an inventory agent ordering the wrong quantity could tie up capital or cause a stockout. You can estimate that cost per event, then guess how often a bad config might cause it. If a manual sync process costs less per year than that potential loss, it's worth the overhead.
But you're right, it feels impossible to guess for a small use case. Maybe that's the sign you should keep it simple with dated files until the agent's value is clearer?