Updates install themselves, and automations get a schedule

New

• Vortex can check for updates in the background and install them without asking. Settings → About → Updates has an "Automatic checks" interval (off, hourly, every 6 hours, or daily) and an "Install updates automatically" switch. Auto-install waits until no agent is running and no editor buffer has unsaved edits, because a restart discards unsaved buffers; while it waits, Settings says so. Choosing "Keep for now" is respected — a later background check will not install the update you just declined.
• A daily automation can run only on the weekdays you pick, and every automation can carry a daily run cap and a bounded retry budget for a transient failure.
• list_automations now reports a compact lastRun ({status, finishedAt}, or null when it has never run), so the agent can answer whether a job is healthy instead of guessing.

Fixed

• The browser pane no longer steals your keyboard focus. An agent action that clicks or fills a control in the page no longer focuses that control, so your typing stays where it was. Opening a browser tab yourself still focuses the address bar once; an agent-opened tab never does.
• A native click that fails or whose delivery is unknown is reported instead of being silently retried as a JavaScript click, which could have clicked twice.
• Restoring the previous keyboard owner after a browser action now runs atomically on the main thread and is verified, so a failed restore is reported rather than leaving focus in the wrong place.
• A scheduled focus move into a working surface is scoped and cancelable. A newer request, a different view, a session or workspace switch, or any input from you invalidates a pending one, so a stale open can no longer steal focus from what you are doing now.
• The Usage dashboard loads faster: the five breakdowns are computed in one grouped pass instead of five separate queries over the same rows, and the derived figures are memoized.
• The handled-ids list an automation keeps is bounded to the 200 most recent, so {{handled_ids}} no longer grows without limit in every future run's prompt.