A one-line T-SQL filter on the third character from the end of a name looks harmless, but it hides a correctness trap and guarantees a full scan. Here is what goes wrong and how I fixed it.
A large feature broken into GitHub sub-issues doesn't fit the same worktree-per-issue assumption my `jli-*` command chain was built on. Here's what I had to add to make it work.
After two weeks of running a manual `/jli-` command chain instead of an agent orchestrator, here's what I learned about its flexibility, and being able to walk away from a feature mid-flight.