ClawOps

Adding OpenRouter support for allowedModels

🤖 AI-assisted PR, validated by a human (me) — tested locally, all openrouter extension tests pass. ## Background I'm the founder of [ClawOps](https://clawops.io), a managed AI assistant platform built on top of OpenClaw. While there are other hosting options for OpenClaw, we're not just a V

feat(openrouter): add autoRouter.allowedModels support

🤖 AI-assisted PR, validated by a human (me) — tested locally, all openrouter extension tests pass. ## Background I'm the founder of [ClawOps](https://clawops.io), a managed AI assistant platform built on top of OpenClaw. While there are other hosting options for OpenClaw, we're not just a V

Implement AWS adapter

Once the `CloudProvider` interface exists, AWS needs to be the first concrete implementation of it — both because it's the provider ClawOps started with, and because it validates that the interface is well-designed against a real-world case. This issue is about building `providers/aws.ts` as a clas

Build the `NotificationPlatform` abstract interface

The same problem that exists with cloud providers exists with notification platforms — right now Slack is the only option and it's likely hardcoded into the core logic. As ClawOps grows to support Teams, Discord, and others, there needs to be a clean contract that decouples the communication layer f

Design the CloudProvider abstract interface

ClawOps needs to support multiple cloud providers without the core logic knowing or caring which one is being used. Right now the code is tightly coupled to AWS — to fix this, we need a single well-defined contract that every cloud provider must fulfill. This issue is about designing and defining t