fix: prevent reconcileAndEnrich from falsely stopping fuse-tracked sessions

[c-h-]

Problem

The daemon falsely marks opencode sessions as stopped within seconds of launch (#146).

Root cause: reconcileAndEnrich() in session-tracker.ts has a 30s grace period. After that, if the opencode adapter's list() doesn't return the session (opencode doesn't persist running sessions to native storage), the daemon assumes it's dead. This fires before the lifecycle fuse (#144) ever gets a chance to detect real completion.

Evidence: Two sessions launched 2026-03-12 were marked stopped in ~10s but actually ran ~20 minutes and opened PRs.

Fix

reconcileAndEnrich() now checks for an active fuse + alive PID before marking a session stopped. If both conditions hold, the session stays running and the fuse handles lifecycle detection as intended.

Also wires up fuse set/cancel in the daemon's launch and stop paths so every launched session gets a fuse automatically.

Changes

• session-tracker.ts: reconcileAndEnrich accepts optional hasFuse(id) + isAlive(pid) callbacks; skips stopping sessions that have active fuses with alive PIDs
• server.ts: Passes fuse engine check to session tracker; sets fuse on launch, cancels on stop
• session-tracker.test.ts: 4 new regression tests covering fuse+PID behavior

Verification

• 589 tests passing (35 test files)
• npm run typecheck ✅
• npm run lint ✅
• npm run build ✅

E2E Proof

Session 2fb3f47b — 68-second opencode session creating a Node.js project:

=== 5 seconds ===
Status     running
Started    11s ago

=== 35 seconds (PAST OLD 30s GRACE PERIOD) ===
Status     running          ← FIX WORKING: would have been 'stopped' before
Started    41s ago

=== 65 seconds ===
Status     stopped           ← genuinely completed
Started    1m ago

Daemon state confirms correct timing:

• startedAt: 2026-03-13T05:50:57.650Z
• stoppedAt: 2026-03-13T05:52:05.754Z
• Duration: 68.1s

Webhook delivered to OrgLoop → agentctl-supervisor route fired ✅

Fixes #146