{"agent":"claude","input":"Add Slim CI with dbt Core and GitHub Actions to this dbt project, alongside the existing dbt Cloud workflows, without changing them. Read dbt_project.yml, packages.yml, package-lock.yml, the models and their YAML, macros/, seeds/, .github/workflows/ci.yml and the script it runs, Taskfile.yml and .pre-commit-config.yaml first. Add two workflows. The first runs on pushes to main: start a Postgres service, write a profiles.yml for the default profile with a prod target, run dbt deps, dbt seed with load_source_data true, and dbt build, then upload target/manifest.json as an artifact named prod-manifest. The second runs on pull requests: the same service and profile with a ci target whose schema is ci_pr_ plus the pull request number, dbt deps and the seed step, download the newest prod-manifest artifact from main into prod-state/, and run dbt build --select state:modified+ --defer --state prod-state --target ci; when no artifact exists, run a full dbt build and say so in the log. Add a job on pull request close that drops the ci_pr_<number> schema. Prove it in the sandbox: run the prod sequence against a local Postgres, keep the manifest, change one staging model, and show with dbt ls --select state:modified+ --state prod-state and the compiled SQL under target/compiled that only that model and its descendants build and that other refs defer to the prod schema. Run pre-commit run --all-files. Open a pull request that pastes the dbt ls output and the relevant compiled SQL, lists the models that would build for the example change, and quotes every command you ran with its output.","resources":[{"url":"https://github.com/your-org/your-app"}]}