{"agent":"claude","input":"Review this pull request to our Dagster workspace. Read dg.toml, dagster_cloud.yaml, the Makefile, .github/workflows/deploy-dagster-cloud.yml, dbt_project/profiles.yml and the pyproject.toml, definitions.py and utils of every project the diff touches first. In each changed project run uv sync --extra dev from its own uv.lock. For a project that loads dbt, run dbt deps and dbt parse against the LOCAL target so no warehouse credentials are needed. Set DAGSTER_IS_DEV_CLI so the code resolves its LOCAL resources, run dg check defs, ruff check without --fix, ruff format --check, and pytest, and quote every error with file and line. Run pytest on the base branch too and report failures that exist there separately from failures the pull request introduces. Then read the diff: every resource must exist under the LOCAL, BRANCH and PROD keys of its resource_def; a changed partitions definition must match every other definition of the same partitions; a renamed asset key, key_prefix, job, schedule or sensor must be updated everywhere it is referred to by string, including asset sensors, AssetIn, asset selections and component YAML; a changed cron or automation condition is stated in plain words; a new code location must be added to dg.toml, dagster_cloud.yaml and the workflow's file filter, location list and image build. Do not materialize assets against a warehouse. Post one review on the pull request with file and line for every finding and the command output quoted. Do not push commits.","resources":[{"url":"https://github.com/your-org/your-app/pull/42"}]}