feat(flows): trigger execution + run history

[xuyushun441-sys]

Summary

Makes flows runnable from the app and surfaces their execution log — the last read-only piece of the Flows feature (completes: list ✅, diagram ✅, run ✅, history ✅).

Client / UI

• useFlowRuns / useFlowRun / useTriggerFlow wrap the automation API (GET /automation/{name}/runs, GET .../runs/{id}, POST .../trigger). The trigger endpoint wraps the handler result, so a 200 can still carry { success: false, error } — useTriggerFlow detects that and reports a real failure instead of a false success (the same envelope trap as object actions).
• Flow detail gains a Run header button: confirm (cross-platform dialog) → trigger → success/error toast → run history auto-refetches.
• Run History section (status badge, trigger, time, duration); tapping a run opens a new run-detail screen with the per-node step log. Route restructured: flows/[name].tsx → flows/[name]/index.tsx + flows/[name]/runs/[runId].tsx.
• i18n: workflow.{runFlow,runConfirm,runStarted,runFailed,runHistory,noRuns,steps,runLabel} in en/zh/ar.

Server (apps/server)

• Add @objectstack/service-automation (+ trigger plugins) and register AutomationServicePlugin, so the local dev server actually exposes the automation routes (previously reported automation: unavailable). The plugin seeds built-in node executors itself (ADR-0018).

Verification

• ✅ In-browser against the local 7.5.0 server: Run opens the confirm dialog, POST /automation/lead_conversion/trigger fires (200), the inner {success:false,error:"Flow 'lead_conversion' not found"} (template flows ship as draft, so the engine won't run them) is surfaced as an error toast, and Run History renders + auto-refetches.
• ✅ New useFlowRuns tests incl. the inner-envelope failure case; tsc (mobile + server) + objectstack validate clean; full suite 1135 pass (20 pre-existing snapshot failures, unrelated).

Note

A successful run + populated history/step-log couldn't be shown locally because the bundled template flows are status: draft (you don't run drafts). The run-detail screen is built against the documented ExecutionLogEntry shape and renders defensively; it'll populate against any active flow.

🤖 Generated with Claude Code