When an operator types a repository path and the system disagrees about spelling, the visible bug looks like a casing or formatting problem. It usually is not. The durable fix is to reconcile Git's registered worktree identity against the filesystem object identity at the shared authority boundary —...

A long-running automated workflow that goes silent looks identical to one that has hung. The fix sounds trivial — "show more progress" — but the interesting decisions are about where the liveness signal lives, how honest it is, and whether your test actually exercises the path a real user hits.

The...

A human gate is not finished when the system prints instructions. It is finished when the operator can make the decision, the workflow records that decision through the authoritative surface, and the next legal path resumes without forcing the operator to become the lifecycle engine.

The Surface Pr...

Some engineering tasks look like polish until they touch a contract.

"Add progress logs" sounds small. A long-running controller is hard to watch, and an operator needs to know whether the system is dispatching work, waiting at a gate, retrying, or failing. Human-visible progress is a reasonable re...

A wrapper command should make the right workflow path easier to run without becoming a second source of lifecycle truth. The safer pattern is to compose existing authority surfaces, capture explicit handoff signals, validate them, and stop at the next legitimate boundary.

Opening

Convenience code ...