Notion-triggered social ops

Cloud control plane for the dedicated posting runner.

Railway owns queueing, approvals, Telegram previews, and run history. The actual browser automation now lives on a long-lived cloud desktop with persistent profiles.

Mode

TEST

Awaiting

Runners online

Ready

Database setup still missing

Invalid `prisma.runner.findMany()` invocation: The table `public.Runner` does not exist in the current database.

Controls

Runtime settings

Switch TEST/LIVE, configure Telegram and destination URLs, and publish the remote desktop entry point for operators.

Runner

Cloud desktop health

Monitor the VM-side daemon, profile readiness, and the remote desktop handoff if a checkpoint needs manual recovery.

No runner has checked in yet. Start the VM daemon with `APP_RUNTIME=runner` and the control-plane URL.

Approval queue

Telegram-driven preview holds

TEST mode composes on the cloud desktop, sends a screenshot to Telegram, and waits here for backup operator control.

No approvals are pending right now.

Signals

Recent activity

Review webhooks, runner presence, and the last execution attempts across both platforms.

Webhook secret

Configured

Runner auth

Locked

Review the hidden style guide

Pipeline

Jobs

See the next scheduled posts, live claim ownership, and the current queue state across the control plane.

Platform	Caption	When	Runner	State