Workers don't properly report completion status to system

Problem

Workers that complete successfully are not being marked as "done" by the system, causing them to appear as "running" indefinitely in the status block.

Observed Behavior

• Worker completes task and sends final set_status with kind: "outcome"
• System shows worker as still running despite completion
• Worker transcript shows successful execution
• No timeout occurred (completed well within 600s limit)

Example

Worker ID: a01b324b-3c38-422f-8c04-31bc62dcc52f

• Started: 2026-03-20T21:08:37+00:00
• Final outcome status: 2026-03-20T21:09:43+00:00 (1 minute duration)
• Timeout configured: 600 seconds
• Result: Still showing as "running" in system

Expected Behavior

When a worker sends set_status with kind: "outcome" indicating successful completion, the system should:

1. Mark the worker as "done" or "completed"
2. Remove from active worker list
3. Update status block accordingly

Additional Issue: Worker Timeout Not Firing

Worker 21039cb8-436e-4c4f-8c46-0cb85f8676e6:

• Status: running for 12+ minutes
• Timeout configured: 600 seconds (10 min)
• Expected: Should auto-fail after 10 min idle
• Actual: Timeout never triggered

Context

This is affecting automated workflows that delegate to workers. Even when workers complete successfully, the system doesn't recognize completion, making it unclear whether tasks finished.

Version

Spacebot v0.3.3

Start by tracing the worker set_status handler for kind: "outcome" and the status block's active-worker tracking. Reproduce both a successful completion and the 600-second timeout case, then verify that completed workers leave the active list and idle workers transition out of running.