adding state:modified

website/docs/reference/global-configs/behavior-changes.md

@@ -69,6 +69,7 @@ When we use dbt Cloud in the following table, we're referring to accounts that h
 | source_freshness_run_project_hooks                              | 2024.03.61       | TBD*                | 1.8.0           | 1.9.0             |
 | [Redshift] [restrict_direct_pg_catalog_access](#redshift-restrict_direct_pg_catalog_access)    | 2024.09.242      | TBD*                | dbt-redshift v1.9.0           | 1.9.0             |
 | skip_nodes_if_on_run_start_fails                                |                  | TBD*                | 1.9.0           | TBD*              |
+| state_modified_compare_more_unrendered                          |                  | TBD*                | 1.9.0           | TBD*              |
 
 When the dbt Cloud Maturity is "TBD," it means we have not yet determined the exact date when these flags' default values will change. Affected users will see deprecation warnings in the meantime, and they will receive emails providing advance warning ahead of the maturity date. In the meantime, if you are seeing a deprecation warning, you can either:
 - Migrate your project to support the new behavior, and then set the flag to `True` to stop seeing the warnings.
@@ -132,9 +133,17 @@ on-run-start:
 
 ### On-run-start hook
 
+The flag is `False` by default.
+
 Set the `skip_nodes_if_on_run_start_fails` flag to `True` to skip all selected resources from running if there is a failure on an `on-run-start` hook. 
 
-The flag is `False` by default.
+### Source definitions and variables for state:modified
+
+The flags are `False` by default.
+
+Set `state_modified_compare_more_unrendered` to `True` to start persisting `unrendered_database` and `unrendered_schema` configs during source parsing, and do comparison on unrendered values during `state:modified` checks. Setting the flag to `True` reduces false positives during `state:modified` checks when `prod` and `dev` environments have different configs.
+
+Set the `state_modified_compare_vars` to `True` if a model uses a `var` or `env_var` in its definition. dbt will be able to identify its lineage to include the model in `state:modified` because the `var` or `env_var` value has changed.
 
 ## Adapter-specific behavior changes
 Some adapters may show behavior changes when certain flags are enabled. Refer to the following sections for each respective adapter.