Fix a bunch of docs build errors and warnings

cosmos/profiles/__init__.py

@@ -39,7 +39,6 @@
     DatabricksOauthProfileMapping,
     DuckDBUserPasswordProfileMapping,
     OracleUserPasswordProfileMapping,
-    DuckDBUserPasswordProfileMapping,
     PostgresUserPasswordProfileMapping,
     RedshiftUserPasswordProfileMapping,
     SnowflakeUserPasswordProfileMapping,

docs/configuration/caching.rst

@@ -111,7 +111,7 @@ The cache values contain a few properties:
 
 
 Caching the partial parse file
-~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 (Introduced in Cosmos 1.4)
 

docs/configuration/callbacks.rst

@@ -105,6 +105,7 @@ Below, find an example of a callback method that raises an exception if the quer
 Users can use the same approach to call the data observability platform `montecarlo <https://docs.getmontecarlo.com/docs/dbt-core>`_ or other services.
 
 .. code-block:: python
+
     def montecarlo_import_artifacts(
         project_dir: str,
         mcd_id: str,

docs/configuration/dag-customization.rst

@@ -1,7 +1,7 @@
 .. _dag_customization:
 
 Post-rendering DAG customization
-================
+================================
 
 .. note::
     The DbtToAirflowConverter.tasks_map property is only available for cosmos >= 1.8.0
@@ -13,7 +13,7 @@ An example use case you can think of is implementing sensor tasks that wait for
 running a source node task (or task group, if the source contains a test).
 
 Mapping from dbt nodes to Airflow tasks
-----------------------
+---------------------------------------
 
 To interact with Airflow tasks created by Cosmos,
 you can iterate over the dag.dbt_graph.filtered_nodes property like so:

docs/configuration/dbt-fusion.rst

@@ -14,9 +14,10 @@ It is a unified approach that aims to merge dbt Core and dbt Cloud features via
 implemented in a different programming language (Rust, as opposed to Python).
 As part of this, dbt Labs are `rewriting all dbt adapters <https://github.com/dbt-labs/dbt-fusion/tree/main/crates/dbt-fusion-adapter/src/adapters>`_ (equivalent to Airflow providers) in Rust, starting from Snowflake.
 They are also changing the `licensing model <https://github.com/dbt-labs/dbt-fusion/blob/main/LICENSES.md>`_ to a hybrid Open-Source and commercial license. We're supporting dbt Fusion with a license-complaint integration. This integration enables teams to:
- - Use dbt Fusion locally for enhanced development experience with real-time validation
- - Deploy dbt Fusion on Astro for production compliance with ELv2 licensing restrictions
- - Maintain consistent workflows across development and production environments
+
+- Use dbt Fusion locally for enhanced development experience with real-time validation
+- Deploy dbt Fusion on Astro for production compliance with ELv2 licensing restrictions
+- Maintain consistent workflows across development and production environments
 
 Some reported dbt Fusion features include:
  - **Lightning-fast performance:** Up to 30× faster parsing speeds
@@ -74,4 +75,5 @@ Limitations
 - Currently (23 June 2025) dbt Fusion is still in beta
 - dbt Fusion only supports Snowflake
 - Cosmos does not support dbt Fusion when using ``ExecutionMode.AIRFLOW_ASYNC``
+
 To support dbt Fusion, Cosmos modified its interaction with dbt. This works with the latest versions of dbt-core, but may not work with older versions. If you want to continue using dbt-core and was affected, set the environment variable ``AIRFLOW__COSMOS__PRE_DBT_FUSION=1`` and Cosmos interaction with dbt-core will work as previous versions.

docs/configuration/source-nodes-rendering.rst

@@ -1,7 +1,7 @@
 .. _source-nodes-rendering:
 
 Source Nodes Rendering
-================
+======================
 
 .. note::
     This feature is only available for dbt-core >= 1.5 and cosmos >= 1.6.0.
@@ -11,6 +11,7 @@ You can control this behavior using the ``source_rendering_behavior`` field in t
 
 - **all**:
   When set to ``all``, Cosmos renders all sources in the dbt project. It uses three different node types for this:
+
     - ``EmptyOperator``: For sources that do not have tests or freshness checks.
     - ``DbtSourceOperator``: For sources that have freshness checks.
     - ``DbtTestOperator``: For sources that have tests.

docs/contributors-roles.rst

@@ -1,3 +1,5 @@
+:orphan:
+
 .. _contributors-roles:
 
 Contributor roles
@@ -52,5 +54,6 @@ General prerequisites that we look for in all candidates:
 2. Visibility on discussions on the Slack channel or GitHub issues/discussions
 3. Contributions to community health and project's sustainability for the long-term
 4. Understands the project's contributors guidelines :ref:`contributing`.
+
 Astronomer is responsible and accountable for releasing new versions of Cosmos in PyPI <https://pypi.org/project/astronomer-cosmos/>, following the milestones <https://github.com/astronomer/astronomer-cosmos/milestones>.
 Astronomer has the right to grant and revoke write access permissions to the project's official repository for any reason it sees fit.

docs/contributors.rst

@@ -1,4 +1,7 @@
+:orphan:
+
 .. _contributors:
+
 Contributors
 ============
 

docs/getting_started/aws-container-run-job.rst

@@ -1,3 +1,5 @@
+.. _aws-container-run-job:
+
 .. title:: Getting Started with Astronomer Cosmos on AWS ECS
 
 Getting Started with Astronomer Cosmos on AWS ECS

docs/getting_started/execution-modes-local-conflicts.rst

@@ -1,3 +1,5 @@
+:orphan:
+
 .. _execution-modes-local-conflicts:
 
 Airflow and dbt dependencies conflicts

docs/getting_started/index.rst

@@ -12,6 +12,7 @@
    Docker Execution Mode <docker>
    Kubernetes Execution Mode <kubernetes>
    Azure Container Instance Execution Mode <azure-container-instance>
+   AWS Container Run Job Execution Mode <aws-container-run-job>
    GCP Cloud Run Job Execution Mode <gcp-cloud-run-job>
    dbt and Airflow Similar Concepts <dbt-airflow-concepts>
    Operators <operators>