Rescuing a Long-Running Job with 'Sub-Step Idempotency' — How vault-auto-ingest

<p>Every night my Mac quietly rewrites my long-term memory. Not metaphorically — a shell script drains that day's Claude Code conversation logs into an Obsidian vault, commits

<p>Your Claude Code setup doesn't break in one dramatic moment — it degrades a few bytes at a time, and by the time you notice, you've been paying a context tax for weeks. In a <a

<p>The fix had comments. It had logs. It even had an audit note saying "measured 4m00s, exit 0." It still failed every Sunday for three weeks straight, and nobody noticed.</p>

<p>This is a follow-up to my <a href="https://zenn.dev/bokuwalily/articles/claude-autopilot" rel="noopener noreferrer">previous post</a> on getting Claude Code to improve itself