feat(.claude): host-level launchd loop tick runner — twin-flame parity

[AceHack]

Summary

Host-level launchd heartbeat runner for Claude Code, parity with Vera's .codex/bin/codex-loop-tick.ts.

Test plan

• bun .claude/bin/claude-loop-tick.ts runs heartbeat mode
• Logs to ~/Library/Logs/zeta-claude-loop/runner.log

🤖 Generated with Claude Code

[Copilot]

Copilot wasn't able to review any files in this pull request.

[chatgpt-codex-connector]

💡 Codex Review

Zeta/.claude/bin/claude-loop-tick.ts

Line 72 in cf2a70b

const meta = readFileSync(join(lockDir, "metadata"), "utf8");

Recover missing lock metadata instead of wedging loop

If the process dies after mkdirSync(lockDir) but before writing metadata (or if that file is removed), the next run hits this read, throws, and falls into the catch { return false; } path, so every future tick exits as "lock held" forever. This creates a permanent outage until someone manually deletes the lock directory; the stale-lock recovery should treat missing/corrupt metadata as reclaimable instead of hard-failing.

---

Zeta/.claude/bin/claude-loop-tick.ts

Line 76 in cf2a70b

try { process.kill(pid, 0); return false; } catch { /* stale */ }

Check lock age before trusting live PID ownership

Returning immediately on process.kill(pid, 0) means the TTL logic is skipped whenever that PID exists, even if the lock is old and belongs to a different process due to PID reuse. In that scenario the runner can remain blocked indefinitely while an unrelated process with the reused PID is alive; the stale-age guard should be evaluated before deciding the lock is valid.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".