fix(docs): Correct relative path to 05-API-REFERENCE.md in integration.md

[doublegate]

Summary

This PR fixes a broken markdown link in docs/src/advanced/integration.md that was causing the GitHub Actions 'Check Markdown Links' workflow to fail.

Problem

The workflow failed with:

FILE: docs/src/advanced/integration.md
  [✖] ../05-API-REFERENCE.md → Status: 400
 
ERROR: 1 dead link found!

Root Cause

Incorrect relative path depth from docs/src/advanced/ to docs/:

• ❌ Wrong: ../05-API-REFERENCE.md (goes up 1 level → docs/src/05-API-REFERENCE.md - doesn't exist)
• ✅ Correct: ../../05-API-REFERENCE.md (goes up 2 levels → docs/05-API-REFERENCE.md - exists)

Path Analysis:

• Source: docs/src/advanced/integration.md (3 levels deep from root)
• Target: docs/05-API-REFERENCE.md (2 levels deep from root)
• Solution: Need ../../ to go up 2 levels

Changes Made

File: docs/src/advanced/integration.md (line 1302)

Before:

- **[API Reference](../05-API-REFERENCE.md)** - Complete Rust API documentation

After:

- **[API Reference](../../05-API-REFERENCE.md)** - Complete Rust API documentation

Verification

✅ Validated with markdown-link-check:

markdown-link-check docs/src/advanced/integration.md --config mlc_config.json
[✓] ../../05-API-REFERENCE.md

✅ Target file exists:

ls -la docs/05-API-REFERENCE.md
-rw-r--r-- 1 root root 20049 Nov 18 00:23 docs/05-API-REFERENCE.md

Impact

• ✅ GitHub Actions 'Check Markdown Links' workflow will pass
• ✅ API Reference link properly accessible from Integration guide
• ✅ Documentation navigation improved
• ✅ Minimal change: 1 file, 1 line

Quality Assurance

• ✅ Link verified with markdown-link-check
• ✅ Target file confirmed to exist
• ✅ No other broken links in integration.md
• ✅ Follows established relative path patterns from previous fixes

Related

• Follows the same pattern as the previous 60+ link fixes in PR (commits 7697f54, 9ebcdf7)
• Consistent with relative path depth corrections across the project

---

Ready for Review ✅

[github-actions]

🤖 Hi @doublegate, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[gemini-code-assist]

Summary of Changes

Hello @doublegate, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical documentation issue by correcting an improperly formed relative path within the integration.md file. The fix ensures that the 'API Reference' link correctly points to its target, thereby restoring proper navigation for users and eliminating a recurring failure in the automated markdown link checking workflow.

Highlights

• Broken Markdown Link Fix: Corrected a broken markdown link in docs/src/advanced/integration.md that was causing the GitHub Actions 'Check Markdown Links' workflow to fail.
• Path Correction: The relative path for the 'API Reference' link was updated from ../05-API-REFERENCE.md to ../../05-API-REFERENCE.md to correctly point to docs/05-API-REFERENCE.md.
• CI/CD Workflow Resolution: This fix ensures the GitHub Actions 'Check Markdown Links' workflow will now pass, improving the stability of the documentation build process and ensuring correct navigation.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly identifies and fixes a broken link in the documentation, which resolves the failing 'Check Markdown Links' workflow. The analysis in the PR description is thorough.

I've added one suggestion to point the link to what appears to be a more current version of the API reference documentation. This would improve consistency with other links in the file and ensure users are directed to the latest information.

[Copilot]

Pull Request Overview

This PR fixes a broken markdown link in the integration guide by correcting the relative path depth to the API Reference document. The path was pointing one level too shallow, causing the link checker to fail.

• Corrects relative path from ../05-API-REFERENCE.md to ../../05-API-REFERENCE.md

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.