fix: correct image relative paths for GitHub Pages rendering

Lab markdown files are at labs/lab-XX/README.md (2 levels deep).
Image references used ../images/ which resolved to labs/images/ (404).
Changed to ../../images/ to correctly resolve to the root images/ directory.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: emmanuelknafo

CONTRIBUTING.md

@@ -77,7 +77,7 @@ Examples:
 Place screenshot references after the step that produces visible output:
 
 ```markdown
-![ESLint results showing 12 warnings](../images/lab-02/lab-02-eslint-output.png)
+![ESLint results showing 12 warnings](../../images/lab-02/lab-02-eslint-output.png)
 ```
 
 ### Adding New Screenshots

labs/lab-00-prerequisites/README.md

@@ -41,7 +41,7 @@ npm --version
 
 You should see Node.js version 20.x or higher.
 
-![Node.js version verification](../images/lab-00/lab-00-node-version.png)
+![Node.js version verification](../../images/lab-00/lab-00-node-version.png)
 
 ### Exercise 2: Install Python 3.12+
 
@@ -56,7 +56,7 @@ pip --version
 
 You should see Python version 3.12.x or higher.
 
-![Python version verification](../images/lab-00/lab-00-python-version.png)
+![Python version verification](../../images/lab-00/lab-00-python-version.png)
 
 ### Exercise 3: Install .NET 8 SDK
 
@@ -70,7 +70,7 @@ dotnet --version
 
 You should see version 8.0.x or higher.
 
-![.NET SDK version verification](../images/lab-00/lab-00-dotnet-version.png)
+![.NET SDK version verification](../../images/lab-00/lab-00-dotnet-version.png)
 
 ### Exercise 4: Install Java 21+
 
@@ -85,7 +85,7 @@ mvn --version
 
 You should see Java version 21.x or higher.
 
-![Java version verification](../images/lab-00/lab-00-java-version.png)
+![Java version verification](../../images/lab-00/lab-00-java-version.png)
 
 ### Exercise 5: Install Go 1.22+
 
@@ -99,7 +99,7 @@ go version
 
 You should see Go version 1.22.x or higher.
 
-![Go version verification](../images/lab-00/lab-00-go-version.png)
+![Go version verification](../../images/lab-00/lab-00-go-version.png)
 
 ### Exercise 6: Install Docker
 
@@ -114,7 +114,7 @@ docker --version
 docker run hello-world
 ```
 
-![Docker version verification](../images/lab-00/lab-00-docker-version.png)
+![Docker version verification](../../images/lab-00/lab-00-docker-version.png)
 
 ### Exercise 7: Install Scanning Tools
 
@@ -176,7 +176,7 @@ Write-Host "Lizard:        $(lizard --version)"
 Write-Host "golangci-lint: $(golangci-lint --version)"
 ```
 
-![All scanning tools verified](../images/lab-00/lab-00-tools-installed.png)
+![All scanning tools verified](../../images/lab-00/lab-00-tools-installed.png)
 
 ### Exercise 8: Fork and Clone the Demo App Repository
 
@@ -210,7 +210,7 @@ cq-demo-app-004
 cq-demo-app-005
 ```
 
-![Cloning the demo-app repository](../images/lab-00/lab-00-clone-repo.png)
+![Cloning the demo-app repository](../../images/lab-00/lab-00-clone-repo.png)
 
 ### Exercise 9: Verify Docker Builds
 

labs/lab-01-explore-demo-apps/README.md

@@ -46,7 +46,7 @@ You should see the following key directories:
 
 Additional directories include `src/converters/` (SARIF converters), `src/config/` (tool configurations), `scripts/` (bootstrap and data pipeline), and `power-bi/` (PBIP dashboard).
 
-![Repository directory structure](../images/lab-01/lab-01-repo-structure.png)
+![Repository directory structure](../../images/lab-01/lab-01-repo-structure.png)
 
 ### Exercise 2: Explore cq-demo-app-001 (TypeScript / Express)
 
@@ -84,7 +84,7 @@ docker run -d -p 3000:3000 --name app001 cq-demo-app-001
 
 Open [http://localhost:3000](http://localhost:3000) to see the running app.
 
-![TypeScript Express app running](../images/lab-01/lab-01-app-001-running.png)
+![TypeScript Express app running](../../images/lab-01/lab-01-app-001-running.png)
 
 Clean up:
 
@@ -128,7 +128,7 @@ docker run -d -p 5000:5000 --name app002 cq-demo-app-002
 
 Open [http://localhost:5000](http://localhost:5000) to verify.
 
-![Python Flask app running](../images/lab-01/lab-01-app-002-running.png)
+![Python Flask app running](../../images/lab-01/lab-01-app-002-running.png)
 
 Clean up:
 
@@ -172,7 +172,7 @@ docker run -d -p 8080:8080 --name app003 cq-demo-app-003
 
 Open [http://localhost:8080](http://localhost:8080) to verify.
 
-![C# ASP.NET Core app running](../images/lab-01/lab-01-app-003-running.png)
+![C# ASP.NET Core app running](../../images/lab-01/lab-01-app-003-running.png)
 
 Clean up:
 
@@ -216,7 +216,7 @@ docker run -d -p 8080:8080 --name app004 cq-demo-app-004
 
 Open [http://localhost:8080](http://localhost:8080) to verify.
 
-![Java Spring Boot app running](../images/lab-01/lab-01-app-004-running.png)
+![Java Spring Boot app running](../../images/lab-01/lab-01-app-004-running.png)
 
 Clean up:
 
@@ -260,7 +260,7 @@ docker run -d -p 8080:8080 --name app005 cq-demo-app-005
 
 Open [http://localhost:8080](http://localhost:8080) to verify.
 
-![Go net/http app running](../images/lab-01/lab-01-app-005-running.png)
+![Go net/http app running](../../images/lab-01/lab-01-app-005-running.png)
 
 Clean up:
 
@@ -285,7 +285,7 @@ Look for these patterns:
 4. **Copy-pasted blocks**: Similar code blocks in different files
 5. **Missing tests**: Source files without corresponding test files
 
-![Sample code with intentional violations](../images/lab-01/lab-01-violations-preview.png)
+![Sample code with intentional violations](../../images/lab-01/lab-01-violations-preview.png)
 
 ## Verification Checkpoint
 

labs/lab-02-linting/README.md

@@ -49,7 +49,7 @@ You should see violations such as:
 - `@typescript-eslint/no-unused-vars` — declared but unused variables
 - `@typescript-eslint/no-explicit-any` — use of `any` type instead of specific types
 
-![ESLint output showing TypeScript violations](../images/lab-02/lab-02-eslint-output.png)
+![ESLint output showing TypeScript violations](../../images/lab-02/lab-02-eslint-output.png)
 
 Now run ESLint with SARIF output to see the machine-readable format:
 
@@ -68,7 +68,7 @@ Examine the SARIF output:
 Get-Content eslint-results.sarif | ConvertFrom-Json | ConvertTo-Json -Depth 10 | Select-Object -First 60
 ```
 
-![ESLint SARIF output](../images/lab-02/lab-02-eslint-sarif.png)
+![ESLint SARIF output](../../images/lab-02/lab-02-eslint-sarif.png)
 
 ```powershell
 cd ..
@@ -93,7 +93,7 @@ Ruff organizes rules by category prefix:
 | `I` | isort — import ordering | I001 (unsorted imports) |
 | `N` | pep8-naming — naming conventions | N802 (function name should be lowercase) |
 
-![Ruff output showing Python violations](../images/lab-02/lab-02-ruff-output.png)
+![Ruff output showing Python violations](../../images/lab-02/lab-02-ruff-output.png)
 
 Run Ruff with SARIF output:
 
@@ -124,7 +124,7 @@ Common .NET Analyzer findings include:
 | CA1031 | Do not catch general exception types |
 | IDE0060 | Remove unused parameter |
 
-![.NET Analyzers output](../images/lab-02/lab-02-dotnet-analyzers.png)
+![.NET Analyzers output](../../images/lab-02/lab-02-dotnet-analyzers.png)
 
 To generate SARIF output from the .NET build:
 
@@ -157,7 +157,7 @@ Common Checkstyle findings:
 | `JavadocMethod` | Missing Javadoc on public methods |
 | `CyclomaticComplexity` | Methods with complexity > 10 |
 
-![Checkstyle output for Java](../images/lab-02/lab-02-checkstyle-output.png)
+![Checkstyle output for Java](../../images/lab-02/lab-02-checkstyle-output.png)
 
 ```powershell
 cd ..
@@ -182,7 +182,7 @@ Common golangci-lint findings:
 | `govet` | Reports suspicious constructs |
 | `unused` | Unused variables, functions, or types |
 
-![golangci-lint output for Go](../images/lab-02/lab-02-golangci-lint-output.png)
+![golangci-lint output for Go](../../images/lab-02/lab-02-golangci-lint-output.png)
 
 Run with SARIF output (golangci-lint does not natively output SARIF, but you can use JSON and convert):
 
@@ -247,7 +247,7 @@ Key SARIF concepts:
 | `results[].locations` | File path, line number, and column |
 | `results[].message` | Human-readable description of the finding |
 
-![SARIF JSON structure](../images/lab-02/lab-02-sarif-structure.png)
+![SARIF JSON structure](../../images/lab-02/lab-02-sarif-structure.png)
 
 ## Verification Checkpoint
 

labs/lab-03-complexity/README.md

@@ -59,7 +59,7 @@ Lizard outputs a table with these columns:
 | Length | Total function length in lines |
 | Location | File path and function name |
 
-![Lizard output showing complexity metrics](../images/lab-03/lab-03-lizard-output.png)
+![Lizard output showing complexity metrics](../../images/lab-03/lab-03-lizard-output.png)
 
 ### Exercise 3: Generate CSV Output
 
@@ -77,7 +77,7 @@ Get-Content lizard-output.csv | Select-Object -First 15
 
 The CSV contains one row per function with columns: NLOC, CCN, Token, PARAM, Length, Location, File, Function, Start, End.
 
-![Lizard CSV output](../images/lab-03/lab-03-lizard-csv.png)
+![Lizard CSV output](../../images/lab-03/lab-03-lizard-csv.png)
 
 ### Exercise 4: Convert to SARIF Format
 
@@ -98,7 +98,7 @@ Examine the generated SARIF:
 Get-Content complexity.sarif | ConvertFrom-Json | Select-Object -ExpandProperty runs | Select-Object -ExpandProperty results | Select-Object ruleId, level, @{N='function';E={$_.locations[0].physicalLocation.artifactLocation.uri}} | Format-Table
 ```
 
-![lizard-to-sarif.py conversion output](../images/lab-03/lab-03-sarif-conversion.png)
+![lizard-to-sarif.py conversion output](../../images/lab-03/lab-03-sarif-conversion.png)
 
 ### Exercise 5: Identify High-Complexity Functions
 
@@ -114,7 +114,7 @@ For each flagged function, note:
 2. **What causes it** — nested `if/else`, `switch` statements, loops within loops
 3. **How to fix it** — extract helper functions, use early returns, replace conditionals with lookup tables
 
-![Functions exceeding CCN threshold](../images/lab-03/lab-03-high-ccn-functions.png)
+![Functions exceeding CCN threshold](../../images/lab-03/lab-03-high-ccn-functions.png)
 
 ### Exercise 6: Analyze Nesting Depth
 

labs/lab-04-duplication/README.md

@@ -41,7 +41,7 @@ jscpd scans for blocks of duplicated code (clones) across files and languages. T
 - **Lines** of duplicated code
 - **Percentage** of duplication in the codebase
 
-![jscpd output showing duplicates](../images/lab-04/lab-04-jscpd-output.png)
+![jscpd output showing duplicates](../../images/lab-04/lab-04-jscpd-output.png)
 
 ### Exercise 2: Generate an HTML Report
 
@@ -65,7 +65,7 @@ The HTML report provides:
 - Side-by-side comparison of duplicated blocks
 - File-level and project-level duplication metrics
 
-![jscpd HTML report](../images/lab-04/lab-04-duplication-report.png)
+![jscpd HTML report](../../images/lab-04/lab-04-duplication-report.png)
 
 ### Exercise 3: Understand Clone Types
 
@@ -83,7 +83,7 @@ Review a detected clone in detail:
 jscpd cq-demo-app-001/src cq-demo-app-002/src --min-lines 5 --reporters consoleFull
 ```
 
-![Clone detail view](../images/lab-04/lab-04-clone-details.png)
+![Clone detail view](../../images/lab-04/lab-04-clone-details.png)
 
 ### Exercise 4: Configure Detection Thresholds
 
@@ -123,7 +123,7 @@ Key configuration options:
 | `ignore` | `[]` | Glob patterns for files/directories to exclude |
 | `reporters` | `["consoleFull"]` | Output formats: `console`, `consoleFull`, `json`, `html`, `sarif` |
 
-![.jscpd.json configuration](../images/lab-04/lab-04-jscpd-config.png)
+![.jscpd.json configuration](../../images/lab-04/lab-04-jscpd-config.png)
 
 ### Exercise 5: Generate SARIF Output
 

labs/lab-05-coverage/README.md

@@ -43,7 +43,7 @@ Jest outputs a coverage summary table:
 | **Functions** | Percentage of functions called |
 | **Lines** | Percentage of lines executed |
 
-![Jest coverage output](../images/lab-05/lab-05-jest-coverage.png)
+![Jest coverage output](../../images/lab-05/lab-05-jest-coverage.png)
 
 The coverage summary JSON is saved to `coverage/coverage-summary.json`. Note the intentionally low coverage — many utility functions have no tests.
 
@@ -60,7 +60,7 @@ python -m pytest tests/ --cov=src --cov-report=term --cov-report=xml:coverage.xm
 
 pytest-cov generates a Cobertura XML report at `coverage.xml` and prints a terminal summary.
 
-![pytest-cov coverage output](../images/lab-05/lab-05-pytest-coverage.png)
+![pytest-cov coverage output](../../images/lab-05/lab-05-pytest-coverage.png)
 
 Note which modules have low coverage — the service layer typically has the least coverage in this demo app because error-handling paths are untested.
 
@@ -89,7 +89,7 @@ reportgenerator -reports:TestResults/**/coverage.cobertura.xml -targetdir:Covera
 Get-Content CoverageReport/Summary.txt
 ```
 
-![Coverlet coverage output](../images/lab-05/lab-05-coverlet-output.png)
+![Coverlet coverage output](../../images/lab-05/lab-05-coverlet-output.png)
 
 ```powershell
 cd ..
@@ -112,7 +112,7 @@ View the summary:
 Get-Content target/site/jacoco/jacoco.xml | Select-String "counter type" | Select-Object -First 10
 ```
 
-![JaCoCo coverage output](../images/lab-05/lab-05-jacoco-output.png)
+![JaCoCo coverage output](../../images/lab-05/lab-05-jacoco-output.png)
 
 ```powershell
 cd ..
@@ -128,7 +128,7 @@ go tool cover -func=coverage.out
 
 The `-func` flag shows per-function coverage. The Go demo app intentionally has minimal test files, resulting in very low coverage.
 
-![Go test coverage output](../images/lab-05/lab-05-go-coverage.png)
+![Go test coverage output](../../images/lab-05/lab-05-go-coverage.png)
 
 To generate an HTML coverage report:
 
@@ -175,7 +175,7 @@ python src/converters/coverage-to-sarif.py --input cq-demo-app-004/target/site/j
 python src/converters/coverage-to-sarif.py --input cq-demo-app-005/coverage.out --format gocover --output cq-005-coverage.sarif --threshold 80
 ```
 
-![coverage-to-sarif.py conversion](../images/lab-05/lab-05-sarif-conversion.png)
+![coverage-to-sarif.py conversion](../../images/lab-05/lab-05-sarif-conversion.png)
 
 ### Exercise 7: Compare Coverage Across Apps
 
@@ -200,7 +200,7 @@ Write-Host "App 005 (Go):"
 Get-Content cq-005-coverage.sarif | ConvertFrom-Json | Select-Object -ExpandProperty runs | Select-Object -ExpandProperty results | Measure-Object | Select-Object -ExpandProperty Count | ForEach-Object { Write-Host "  Files below threshold: $_" }
 ```
 
-![Coverage comparison across apps](../images/lab-05/lab-05-coverage-comparison.png)
+![Coverage comparison across apps](../../images/lab-05/lab-05-coverage-comparison.png)
 
 The 80% threshold is the CI quality gate standard. Any file below this threshold generates a SARIF finding that would block a merge in a production CI pipeline.
 

labs/lab-06-ado-pipelines/README.md

@@ -35,7 +35,7 @@ If the repository has not been imported to ADO yet, use the bootstrap script or
 
 Alternatively, use the `bootstrap-demo-apps-ado.ps1` script which automates this process.
 
-![Importing repository into ADO](../images/lab-06-ado/lab-06-ado-pipeline-import.png)
+![Importing repository into ADO](../../images/lab-06-ado/lab-06-ado-pipeline-import.png)
 
 ### Exercise 2: Create the Pipeline
 
@@ -89,11 +89,11 @@ steps:
 2. Click on the running pipeline to see job progress.
 3. Each matrix job runs independently and produces its own SARIF output.
 
-![ADO pipeline running](../images/lab-06-ado/lab-06-ado-pipeline-run.png)
+![ADO pipeline running](../../images/lab-06-ado/lab-06-ado-pipeline-run.png)
 
 Wait for all 5 matrix jobs to complete:
 
-![ADO pipeline completed](../images/lab-06-ado/lab-06-ado-pipeline-complete.png)
+![ADO pipeline completed](../../images/lab-06-ado/lab-06-ado-pipeline-complete.png)
 
 ### Exercise 4: View Results in ADO Advanced Security
 
@@ -104,7 +104,7 @@ Wait for all 5 matrix jobs to complete:
    - **Tool**: The scanner name from the SARIF `tool.driver.name` field
    - **Rule**: Individual rule IDs
 
-![ADO Advanced Security findings](../images/lab-06-ado/lab-06-ado-advanced-security.png)
+![ADO Advanced Security findings](../../images/lab-06-ado/lab-06-ado-advanced-security.png)
 
 ### Exercise 5: Examine a Finding
 
@@ -115,7 +115,7 @@ Click on any finding to see its detail view:
 - **Severity** mapped from the SARIF level
 - **Remediation guidance** from the SARIF `help.markdown` field
 
-![ADO finding detail](../images/lab-06-ado/lab-06-ado-finding-detail.png)
+![ADO finding detail](../../images/lab-06-ado/lab-06-ado-finding-detail.png)
 
 ### Exercise 6: Compare GitHub vs. ADO Integration