Why extract the tools
Agent workflows kept running into ordinary systems problems: repeated tests, concurrent writers, lost messages, and evidence that went stale after an edit. The original mechanisms developed in July and August 2026. In September I separated eleven standalone projects containing thirteen tools, plus a twelfth repository of demos and case studies. The extraction replaced machine assumptions with explicit inputs and synthetic fixtures.
State that outlives a process
Durable Mailbox, Session Ledger, Job Heartbeat, and Decision Ledger preserve messages, lifecycle reports, generations, and original decision wording. Each tool makes a narrower promise than a workflow platform, and records what a caller reported without pretending that a local record proves outside reality.
Safer local change
Gate Runner, Worktree Guard, Shell Lock, and three Agent File Guards handle repeated checks, dangerous Git operations, cooperating writers, unfamiliar instruction surfaces, accidental document shrinkage, and hidden NUL bytes. They are designed to refuse ambiguous work and leave the final mutation explicit.
Evidence with boundaries
Repo Health separates a clean observation from a failed inspection. Config Baseline records bounded configuration drift. Review Receipts binds review words to exact selected bytes without claiming that a current review is an approval. Together, the tools make missing evidence visible instead of turning it into a reassuring default.
What the verification establishes
The September 22 extraction revisions passed fresh private-remote clone checks on macOS and suites in an isolated Linux container. Four filesystem case-equivalence tests were skipped on Linux and exercised on macOS. The extracted histories passed Gitleaks with zero findings. These are bounded test and scanner results, not proof that every failure or secret is detectable.
Knowing when to retire an integration
My July session-messaging work preceded Claude Code’s August cross-session messaging release. I adopted native live-session transport in August while retaining the disk queue’s separate durability contract. In September I marked this entire collection deprecated for new Claude Code integrations. The implementations and lessons remain useful as references; that maintenance decision does not mean native features replace every tool.
Release status
All twelve repositories have Apache-2.0 licensing and remain private. Public launch is deferred. They are deprecated reference projects, with no promise of ongoing feature work or support. The larger original agent runtime is separate and has not been released.