A good makefile is really nice to use. Not nice to read or trace unfortunately though.
Csv files hide their meaning in external documentation or someone’s head, are extremely unclear in many cases (is this a number or a string? A date?) and is extremely fragile when it comes to people editing them in text editors. They entirely lack checks and verification at the most basic level and worse still they’re often but not always perfectly line based. Many tools then work fine until they completely break you file and you won’t even know. Until I get the file and tell you I guess.
I’ve spent years fixing issues introduced by people editing them like they’re text.
If you’ve got to use tools to not completely bugger them then you might as well use a good format.
I do not have enough information to definitely say whether it’s good or bad. Most of the things in life are neither because they have good side effects, and bad side effects to them. So, I think looking for a “good only” solution is a loosing strategy.
You say we need tariffs to bring manufacturing back. Then you turn around and say the tariffs aren't the point, it's the deal. You even said it was silly to bet on announced tariffs elsewhere.
If the tariffs are necessary to bring manufacturing back full stop, then you don't need to "make a deal". If it's just a tool to make a deal, then they're not necessary!
You just keep moving those goalposts.
"Review the top-most commit. Did I make any mistakes? Did I leave anything out of the commit message?"
Sometimes I let it write the message for me:
"Write a new commit message for the current commit."
I've had to tell it how to write commit messages though. It likes to offer subjective opinions, use superlatives and guess at why something was done. I've had to tell it to cut that out: "Summarize what has changes. Be concise but thorough. Avoid adjective and superlatives. Use imperative mood."
Review your own code. Understand why you made the changes. And then clearly describe why you made them. If you can't do that yourself, I think that's a huge gap in your own skills.
Making something else do it means you don't internalize the changes that you made.