Isn't this effectively what code commits are for? If you've done something worth noting, it should probably be in a commit anyway.
No reason you couldn't have a text file with setup notes on a system and have commit any updates so you have a trackable log.
In fact for any employee it’s useful to keep track of stuff like this, come PR time.
I started using the did file while learning a new language, don’t remember which. I’d have 15 tabs open with different docs and tutorials but very very little actual code written or way to mark where I was. I settled on a single text file and It was super helpful to just look back a week and notice there was some measurable progress.