Weekly Changelog #5
Originally published on Substack.
Foreword
I’ve been thinking AI is a lot like a golem. There’s undeniably some magic involved, but it also isn’t full on soft fantasy magic either. And it almost always ends up being a parable.

Changelog
lowly-writing-framework
A handful of small iterations, mostly fixing behaviors I wasn’t happy with.
v4.8.1: nitpick review comments now carry suggested edits.
v4.9.0: added PowerShell argument mechanics for
ghtoreferences/gh-cli.md.v4.10.0: review threads can be resolved with
resolutionReason(ADDRESSED,WONT_FIX,INVALID).v4.11.0: new separation-of-concerns check, plus three evals.
v4.11.1: the separation-of-concerns guidance now applies only when design feedback is requested or already in scope.
tofu-garnish
The docs feature received some love this week - with added ability to render/deploy images in your markdown documentation. It also can show pills indicating which resources were created/modified/destroyed since the last publishing of Tofu Garnish.
These quality of life enhancements hopefully help to further demystify the “state” of Tofu for engineering teams.
lowlysre/icd-10-cdm

The latest release adds hasICD10Code(code), which returns a boolean. Lookups now return undefined and normalizeICD10Code returns "" for non-string input, where both used to throw TypeError.
These changes are aimed at making the lookup tool more helpful for agentic use cases, where these types of adjustments can make it easier to build and test models for ground-truth in medical use cases.
mwaa-get-env-action and mwaa-update-env-action

The inaugural release of these two actions is here! I’ve written variations of MWAA (AWS Managed Apache Airflow) actions to do maintenance and deploy workflows multiple times for different organizations, and boss…I’m tired.
These two actions are complementary and aim to provide a super easy, well logged, well documented experience for deploying to MWAA via GitHub Actions. These use very few dependencies, and leverage the AWS SDK to avoid version mismatch issues that defaulting to a GitHub Runner’s AWS CLI version may lead to.
third-party-notices

Another new project! This came from frustration building the two MWAA GitHub Actions above: I couldn’t find a simple, maintained, non-ecosystem CLI to generate my third-party-notices.txt for those actions.
So, I borrowed from a few tools worth admiring and wrote my own. This npm package is meant to be a CI/CD tool, so its only a CLI and has 0 dependencies.