feat: add remote cloud deployment infrastructure

.cargo/config.toml

@@ -1,9 +1,9 @@
-[target.aarch64-apple-darwin]
-linker = "clang++"
-
-[env]
-CXXFLAGS = "-include cstdint"
-
 [build]
-# For access to tokio metrics
-rustflags = ["--cfg", "tokio_unstable"]
+# Configuration for macOS development
+
+[alias]
+# Convenient aliases for macOS development
+check-mac = "check --no-default-features --features macos-dev"
+build-mac = "build --no-default-features --features macos-dev"  
+test-mac = "test --no-default-features --features macos-dev"
+run-mac = "run --no-default-features --features macos-dev"

.github/workflows/remote-providers-tests.yml

@@ -0,0 +1,103 @@
+name: CI
+
+on:
+  pull_request:
+    paths:
+      - 'crates/blueprint-remote-providers/**'
+      - '.github/workflows/remote-providers-tests.yml'
+  push:
+    branches: [main]
+    paths:
+      - 'crates/blueprint-remote-providers/**'
+      - '.github/workflows/remote-providers-tests.yml'
+
+jobs:
+  test-remote-providers:
+    name: cargo test (blueprint-remote-providers)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Run unit tests
+        run: cargo test -p blueprint-remote-providers --lib
+
+      - name: Run pricing tests
+        run: cargo test -p blueprint-remote-providers test_pricing
+
+  test-remote-providers-kubernetes:
+    name: cargo test (blueprint-remote-providers-kubernetes)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Setup Kind
+        uses: helm/[email protected]
+        with:
+          cluster_name: blueprint-test
+          wait: 120s
+
+      - name: Verify cluster
+        run: |
+          kubectl cluster-info
+          kubectl get nodes
+
+      - name: Run Kubernetes tests
+        run: cargo test -p blueprint-remote-providers --test managed_kubernetes_e2e --features kubernetes
+
+  test-remote-providers-ssh:
+    name: cargo test (blueprint-remote-providers-ssh)
+    runs-on: ubuntu-latest
+    services:
+      ssh:
+        image: linuxserver/openssh-server:latest
+        env:
+          PUID: 1000
+          PGID: 1000
+          TZ: UTC
+          PASSWORD_ACCESS: true
+          USER_PASSWORD: testpass
+          USER_NAME: blueprint
+        ports:
+          - 2222:2222
+        options: >-
+          --health-cmd "nc -z localhost 2222"
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Install sshpass
+        run: sudo apt-get update && sudo apt-get install -y sshpass
+
+      - name: Test SSH connection
+        run: |
+          sshpass -p testpass ssh -o StrictHostKeyChecking=no -p 2222 blueprint@localhost echo "SSH works"
+
+      - name: Run SSH deployment tests
+        run: echo "SSH deployment tests moved to lib tests" && cargo test -p blueprint-remote-providers --lib test_ssh
+
+  test-remote-providers-integration:
+    name: cargo test (blueprint-remote-providers-integration)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Run integration tests
+        run: cargo test -p blueprint-remote-providers --lib
+
+      - name: Run property tests
+        run: cargo test -p blueprint-remote-providers --test property_tests

AGENTS.md

@@ -0,0 +1,20 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+The workspace is anchored by the root `Cargo.toml`, `dist-workspace.toml`, and `workspace-hack/` helper crate. Core runtime crates live in `crates/`, grouped by capability (`core/`, `networking/`, `manager/`, `stores/`, `testing-utils/`, etc.), and should keep public APIs surfaced through `crates/sdk/`. The `cli/` directory hosts the `cargo-tangle` binary with integration coverage in `cli/tests/`. Starter blueprints live in `examples/` and must remain buildable against the latest SDK. Long-form specifications and operator guides are under `docs/`. Use `docker-compose.yml` only when you need optional external services; it is not exercised in CI.
+
+## Build, Test, and Development Commands
+- `cargo fmt --all`: Format Rust sources using the shared `rustfmt.toml` rules.
+- `cargo clippy --workspace --all-targets --all-features -D warnings`: Enforce lint cleanliness across every crate.
+- `cargo test --workspace --all-features`: Run unit, doc, and integration tests; prefer `cargo test -p <crate>` for focused runs.
+- `cargo build --workspace --all-features`: Compile everything locally before publishing a crate or tagging a release.
+- `cargo run -p blueprint-manager -- --help`: Smoke-check runtime binaries after changes to orchestration crates.
+
+## Coding Style & Naming Conventions
+Rust files use the pinned stable toolchain 1.88 (managed via `rust-toolchain.toml`) with 4-space indentation. Follow idiomatic naming: modules and functions in `snake_case`, types and traits in `PascalCase`, constants in `SCREAMING_SNAKE_CASE`. Keep public exports centralized in each crate’s `lib.rs`, re-exporting from submodules instead of deep relative paths. Format documentation comments thoughtfully—`rustfmt` is configured to wrap doc examples—and order imports with standard/prelude/external grouping. For manifest updates, run `taplo fmt` to honor `taplo.toml`.
+
+## Testing Guidelines
+Write async tests with `tokio::test` where network or time-based behavior is exercised, and mirror fixtures in `crates/testing-utils/` when possible. Place integration suites in each crate’s `tests/` directory or under `cli/tests/` for CLI flows, naming files with the feature under test (`manager_failover.rs`, `router_happy_path.rs`). Maintain edge-case coverage for multi-node scenarios and include negative-path assertions. Before opening a PR, run `cargo test --workspace --all-features` and document any intentionally skipped targets.
+
+## Commit & Pull Request Guidelines
+Adopt Conventional Commits (`feat(router):`, `fix(cli):`, etc.) and align branches with the `feature/`, `fix/`, or `docs/` prefixes already in use. Each PR description should summarize behavior changes, list the verification commands you ran, and link any tracked issues. Attach logs or terminal snippets when altering CLI UX, and update `docs/` or examples when interfaces shift. Ensure CI is green, request a maintainer review, and keep PRs scoped to a single logical change set.