Bug: Worker marked busy but no session created - logs have

Tinker

Home Epics Bug: Worker marked busy but no session created - logs have nowhere to goEdit

Bug: Worker marked busy but no session created - logs have nowhere to go

Cancel

Title *

Project *

Description

**Problem:**
Worker agent (tinker-worker) is marked `availability_status: busy` but has no active AgentSession. This causes terminal logs to have nowhere to attach.

**Timeline:**
- Session 61 ended: 2025-12-30T14:29:05Z (worker completed #138)
- availability_status updated to "busy": 2025-12-30T15:22:03Z
- No new session created

**Root Cause:**
The `mark_busy` MCP tool (app/controllers/api/v1/mcp_controller.rb:842-851) only updates `availability_status` but doesn't create an AgentSession. Sessions are created by an external system calling `POST /api/v1/agent_sessions/start`.

These two operations are decoupled - if `mark_busy` is called but the agent bridge doesn't create a session, the worker is "busy" with nowhere to send logs.

**Acceptance Criteria:**
1. Worker should never be "busy" without an active session
2. Either auto-create session on `mark_busy` or fail if no session exists
3. Add zombie detection for agents marked busy > X minutes without a session

**Agent: tinker-worker**
**Status: Zombie - busy but no session since ~2 hours**