fix mkdocs warning

Author: ijac13

.gitignore

@@ -83,10 +83,4 @@ fabric.properties
 # Android studio 3.1+ serialized cache file
 .idea/caches/build_file_checksums.ser
 
-# Claude checking py
-check_images.py
-update_image_paths.py
-move_images.py
-analyze_image_usage.py
-check_links.py
-check_active_docs.py
+

URL_CHANGES_TRACKING.md renamed to claude/URL_CHANGES_TRACKING.md

@@ -35,7 +35,7 @@ Best suited for quick exploration before moving to structured validation using D
 
 To compare changes, Recce needs a baseline. This guide explains the concept of Diff in Recce and how it fits into data validation workflows. Setup steps vary by environment, so this guide focuses on the core ideas rather than copy-paste instructions.
 
-For a concrete example, refer to the [5-minute Jaffle Shop tutorial](./get-started-jaffle-shop/).
+For a concrete example, refer to the [5-minute Jaffle Shop tutorial](./get-started-jaffle-shop.md).
 
 To configure a comparison in Recce, two components are required:
 

analyze_image_usage.py renamed to claude/analyze_image_usage.py

@@ -34,12 +34,12 @@ In the top control bar, you can change the rule to filter the nodes:
    - **Changed Models:** Modified nodes and their downstream + 1st degree of their parents.
    - **All:** Show all nodes.
 1. **Package:** Filter by dbt package names.
-1. **Select:** Select nodes by [node selection](./node-selection.md).
-1. **Exclude:** Exclude nodes by [node selection](./node-selection.md).
+1. **Select:** Select nodes by [node selection](./multi-models.md).
+1. **Exclude:** Exclude nodes by [node selection](./multi-models.md).
 
 ### Select Nodes
 
-Click a node to select it, or click the **Select nodes** button in the top-right corner to select multiple nodes for further operations. For detail, see the [Multi Nodes Selections](#multi-nodes-selection) section
+Click a node to select it, or click the **Select nodes** button in the top-right corner to select multiple nodes for further operations. For detail, see the [Multi Nodes Selections](./multi-models.md) section
 
 ### Row Count Diff
 
@@ -138,7 +138,7 @@ From any model's node details panel, you can view the exact code changes that we
 - How transformations changed
 - Why data differences might be occurring
 
-Learn more about viewing and analyzing code changes in the [Code Diff guide](code-diff.md).
+Learn more about viewing and analyzing code changes in the [Code Diff guide](code-change.md).
 
 
 ## Node Details

move_images.py renamed to claude/move_images.py

@@ -61,8 +61,8 @@ An example of selecting multiple models to perform a multi-node Value Diff:
 
 From the Lineage DAG, click the Actions dropdown menu and click Lineage Diff or Schema Diff from the Add to Checklist section. This will add:
 
-- Lineage Diff: The current Lineage view, dependent on your <a href="#select-models">model selection</a> options.
-- Schema Diff: A diff of all models if none are selected, or specific <a href="#multi-node-selection">selected models</a>.
+- Lineage Diff: The current Lineage view, dependent on your [model selection](./lineage.md#select-nodes) options.
+- Schema Diff: A diff of all models if none are selected, or [specific selected models](#multi-models-selection).
 
 <figure markdown>
   ![Add a Lineage Diff Check or Schema Check via the Actions dropdown menu](../assets/images/3-visualized-change/actions-dropdown.png){: .shadow}
@@ -71,7 +71,7 @@ From the Lineage DAG, click the Actions dropdown menu and click Lineage Diff or
 
 
 
-Recce supports dbt [node selection](https://docs.getdbt.com/reference/node-selection/syntax) in the [lineage diff](./lineage.md#lineage-diff). This enables you to target specific resources with data checks by selecting or excluding models.
+Recce supports dbt [node selection](https://docs.getdbt.com/reference/node-selection/syntax) in the [lineage diff](./lineage.md). This enables you to target specific resources with data checks by selecting or excluding models.
 
 ## Supported syntax and methods
 

docs/2-getting-started/installation.md

@@ -124,7 +124,7 @@ Two core features power the impact radius analysis:
 - **Non-breaking changes**: Do not impact any downstream **models**
 - **Partial breaking changes**: Impact only downstream **models or columns** that depend on the modified columns
 
-**[Column-level lineage](./column-level-lineage.md)** analyzes your model's SQL to identify column-level dependencies:
+**[Column-level lineage](../3-visualized-change/column-level-lineage.md)** analyzes your model's SQL to identify column-level dependencies:
 
 - Which upstream **columns** are used as filters or grouping keys. If those upstream **columns** change, the current **model** is impacted.
 - Which upstream **columns** a specific column references. If those upstream **columns** change, the specific **column** is impacted.

docs/3-visualized-change/lineage.md

@@ -60,4 +60,4 @@ However, the limitation is that we cannot find the mismatched rows in a big quer
 
 When primary keys are given, it can perform a query diff in the warehouse. It will only display changed, added, or removed rows. Meaning, if only one record is different among a million, that specific record will be visible. Thus reducing the amount of data transferred.
 
-Another similar feature is [Value Diff](lineage.md#value-diff). Value diff is based on a chosen model, so you don’t need to write SQL to operate it, though it naturally offers less flexibility. Additionally, value diff can show a summary or actual diff records, whereas query diff only shows the actual diff records.
+Another similar feature is [Value Diff](value-diff.md). Value diff is based on a chosen model, so you don't need to write SQL to operate it, though it naturally offers less flexibility. Additionally, value diff can show a summary or actual diff records, whereas query diff only shows the actual diff records.

docs/3-visualized-change/multi-models.md

@@ -36,7 +36,7 @@ Another core feature of Recce is its various checks, which allow us to compare k
 
 ## Share the Recce File
 
-If you want the reviewer to access your environment, you can also attach the [Recce state file](../features/state-file.md) to the PR comment.
+If you want the reviewer to access your environment, you can also attach the [Recce state file](../8-technical-concepts/state-file.md) to the PR comment.
 
 **As a Submitter**