What problem does it solve? Moving dlt pipelines from local development to the dltHub Platform requires separating dev and production credentials, configuring a production destination, and declaring deployable jobs — a process that is error-prone when done manually. ## Core Features & Use Cases - Profile-Scoped Secrets: Splits workspace secrets into dev and prod profile TOML files so each environment uses the right credentials. - Production Destination Setup: Configures named destinations (e.g., Motherduck instead of ephemeral duckdb) per profile, with a connectivity check script to verify access. - Deployment Manifest Creation: Builds __deployment__.py with @run.pipeline decorated functions and __all__ exports so the Runtime can discover jobs. - Use Case: You have a working dlt pipeline using local duckdb and want to deploy it to dltHub Runtime with Motherduck as the production warehouse while keeping local development unchanged. ## Quick Start Ask the assistant to prepare this dlt workspace for production deployment by splitting dev and prod secrets and configuring a Motherduck destination.