What problem does it solve? It centralizes the operational knowledge for running Hub Pro cloud tasks—proceeding cloud Forge Run batches on Railway, calling the founder-ops API, and using the API Station—without running a local FORGE motor on the Mac founder session. ## Core Features & Use Cases - Cloud Proceed Control: Trigger full-pack cloud task proceeds through the Cloud Workers API on port 13027 with receipts and logs for verification. - Founder Ops API: Query and execute founder operations such as dual_heal and cloud worker status checks via the Worker Hub on port 13020. - Deploy & Queue Verification: Deploy to Railway with the founder deploy script and verify queue state through the cloud-forge-run queue endpoint, including stale pointer repair. - Use Case: After a Railway deploy shows healthy but the queue still references an old batch, use the documented sync_pointer_from_image repair flow to realign the persistent volume pointer and confirm the new batch. ## Quick Start Ask the assistant to proceed the next cloud task using the Cloud Workers API and show the receipt and queue proof.