askcc develop repeatedly dies before first commit, leaving uncommitted work stranded in worktree #114

Summary

Across at least 3 separate repos (weyucou/nemawashi-backend#3, weyucou/ibuki-backend#13, weyucou/mther-infra#42), askcc develop sessions have died before making any git commit — sometimes after writing substantial working code+tests, sometimes with a clean worktree. The issue stays labeled action:develop, remains assigned, and no PR is ever opened, so it silently looks "in progress" to org-scan tooling when nothing is actually happening.

Evidence

• weyucou/nemawashi-backend#3: 4+ separate feature/3-* branches all sitting at the exact same commit SHA as main (zero commits), but the associated .claude/worktrees/* directories contain uncommitted working code + passing tests from multiple independent attempts. The most complete attempt (jaunty-inventing-pony worktree) has a full webhook feature implementation with 11/11 tests passing that was simply never committed.
• weyucou/ibuki-backend#13: two worktrees (humming-greeting-gem, reactive-knitting-sonnet) both stalled with real uncommitted infra work (Dockerfile, CloudFormation template, dependency bumps) but no commits.
• weyucou/mther-infra#42: worktree found completely clean (no uncommitted changes either) — this attempt appears to have died even earlier, before writing any code.
• Stale ellen:processing labels have had to be auto-recovered on nemawashi-backend#3 multiple times (2026-07-02, twice) with no active process found, suggesting this crash pattern predates a single incident and recurs.

Impact

• Real engineering work is silently lost/stranded unless a human (or another agent) happens to inspect the worktree directory before it's cleaned up.
• Issues appear stuck "in development" indefinitely with no visible error, misleading project-board scans into thinking a job is in-flight when it has actually died.

Ask

• Investigate what's causing askcc develop to exit before its first commit (timeout? unhandled API error? OOM?) — logs from the detached launcher (nohup/setsid wrapper) may have more detail if available.
• Consider having askcc commit early/incrementally (e.g. after each file write, or at least once tests pass) rather than only at the very end of a session, so partial progress survives a crash.
• Consider surfacing a clearer failure signal (e.g. a PR comment or issue comment noting "session terminated before commit") instead of leaving the issue silently labeled action:develop with no trace.