[zellwk]

Problem

parse_status_line locates the chrome separator, then checks the first non-blank line above it. If that line doesn't start with a spinner glyph it returns None immediately.

Claude Code now renders a tip block between the status line and the chrome:

✳ Gitifying… (2m 1s · ↓ 6.5k tokens)
  ⎿ Tip: Use /btw to ask a quick side question without interrupting
     current work
────────────────────────────────────────
❯
────────────────────────────────────────
  ⏸ manual mode on · esc to interrupt · ← for agents

The scan stops on current work and reports no status. Whenever a tip is showing, the topic's status message goes stale — it keeps displaying whatever was last parsed until the tip disappears.

Fix

Keep scanning upward instead of bailing on the first non-spinner line.

The line directly above the separator is still accepted on the spinner glyph alone, so current behaviour is unchanged. Past that, a line must also carry the … of a live status line. That preserves the guard the original was written for — · bullets in Claude's prose output — and additionally keeps out the finished marker (✻ Sautéed for 7s), which has no ellipsis.

Every status line variant carries the ellipsis, including the ones quoted in #52:

✻ Thinking… 5s
✶ Coalescing… (25m 8s · ↓ 5.8k tokens · thought for 6s)
✢ Drizzling… (54s · ↓ 776 tokens)

Tests

Two added, and all existing parse_status_line tests pass unchanged:

• the tip-block layout parses correctly
• the finished ✻ Sautéed for 7s marker is not mistaken for a live status