Refactor an existing product fast with Claude Fable 5 and GPT-5.6 Sol first

The previous post's lesson was one I wrote after paying for it. I turned Loop Engineering on for an existing product, and two weeks in, debt really had piled up at ten times the usual speed underneath gates that kept passing. This post is about that regret and the human-driven, high-throughput refactor I went back to run instead, with Claude Fable 5 planning and GPT-5.6 Sol implementing, both on their light settings.

I Missed a More Popular Same-Name OSS, So I Renamed Mine to hermes-talaria

I later realized my OSS oh-my-hermes shared a name with a repository sitting at about 1.3k stars. It was just confusing, so I renamed mine to hermes-talaria and flipped the extension namespace prefix from omh- to ht- along the way. Since I am currently the only user, the breaking change is fine. For the new name I checked GitHub search first.

Dropping Loop Engineering onto an existing product piles up technical debt at high speed — rebuild the verification substrate with refactoring first

The previous post argued that a solopreneur-style new product is where Loop Engineering just works. The inverse is that an existing product is where it just does not. Worse, if you turn it on before the verification substrate is real, technical debt piles up underneath gates that keep passing. This post is about the refactoring you have to do first to avoid that.