Automations list: operator roster follow-ups after Task

Seen on /automations (operator, ~49 system rows) at 1024px and 1440px on a local stack while doing Task 6727. 1. A frequent row's Last cell now reads "○ now" (nothing to do), which says the schedule is alive but not when it last did work. Serve the newest `acted` run's time on the automation object and add it to the Last cell's hover ("Nothing to do now · last did work 3h ago"), without changing the cell itself. 2. When an operator's own automations sit beside ~45 system rows, the ⚙ marker is the only way to separate them. Add a System / Mine choice to the list's filters so an operator can hide the platform rows. 3. System descriptions are still cut off in the Target · Action column at 1024px (≈216px). Consider wrapping the description to two lines on an all-system roster, or showing it under the name, so it can be read without hovering. 4. On a fresh stack about half the daily system rows read "never". Hover could say when it first runs ("Never run · first run in 6h"), as the When cell's hover already knows the next run. Out of scope: the phone layout, the row menu, the run ledger and retention behaviour. Done means: - Each item is either shipped or recorded as declined with a reason. - `./dc check full` green.

Shipped all 4: last-did-work hover, operator Owner filter (System/Org), two-line system descriptions, first-run hover; also fixed a pre-existing /api/automations 500 in _missed_gap. Quick gate + tests green; visual check passed at 1024/1440. PR #5696 merged (269115ccf); its deploy was superseded. Follow-up draft 6912.