update link_map for js

.github/CODEOWNERS

@@ -4,3 +4,16 @@
 # These owners will be the default owners for everything in
 # the repo. Unless a later match takes precedence, they will be requested for review when someone opens a pull request.
 *       @lnhsingh @katmayb
+
+# Any file in the `/src/oss`
+# and any of its subdirectories.
+/src/oss/ @lnhsingh
+
+# Any file in the `/src/oss/python/integrations`
+# and any of its subdirectories.
+/src/oss/python/integrations/ @mdrxy
+
+# Any file in the `/src/langsmith`
+# and any of its subdirectories.
+/src/langsmith/ @katmayb
+

.github/copilot-instructions.md

@@ -59,6 +59,12 @@ If any code fences like this exist on the code page, then two outputs (one for e
 
 For implementation details, see `pipeline/preprocessors/markdown_preprocessor.py`.
 
+## Snippets
+
+Snippet files in `src/snippets/` are reusable MDX content that can be imported into multiple pages. These snippets undergo special link preprocessing during the build process that converts absolute `/oss/` links to relative paths.
+
+**Important:** When writing links in snippets, be careful about path segments. Read the docstrings and comments in `pipeline/core/builder.py` method `_process_snippet_markdown_file` (lines 807-872) to understand how snippet link preprocessing works and why certain path structures are required.
+
 ## Style guide
 
 In general, follow the [Google Developer Documentation Style Guide](https://developers.google.com/style). You can also access this style guide through the [Vale-compatible implementation](https://github.com/errata-ai/Google).

.github/labeler.yml

@@ -33,13 +33,6 @@ oss:
       - src/oss/**
       - src/oss/**/*
 
-# Label for Labs documentation changes
-labs:
-  - changed-files:
-    - any-glob-to-any-file:
-      - src/labs/**
-      - src/labs/**/*
-
 # Label for Python-specific documentation
 python:
   - changed-files:

.github/pull_request_template.md

@@ -6,7 +6,7 @@
 **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other]
 
 ## Related issues/PRs
-<!-- 
+<!--
 Link to related issues, feature PRs, or discussions (if applicable)
 
 To automatically close an issue when this PR is merged, use closing keywords:
@@ -33,8 +33,8 @@ Examples:
 - [ ] All code examples have been tested and work correctly
 - [ ] I have used **root relative** paths for internal links
 - [ ] I have updated navigation in `src/docs.json` if needed
-- I have gotten approval from the relevant reviewers
-- (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)
+
+(Internal team members only / optional): Create a preview deployment as necessary using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)
 
 ## Additional notes
 <!-- Any other information that would be helpful for reviewers -->

.github/workflows/create-preview-branch.yml

@@ -4,7 +4,7 @@ run-name: Preview by @${{ github.actor }}
 
 on:
   pull_request:
-    types: [opened, synchronize, reopened]
+    types: [opened, synchronize, reopened, closed]
   workflow_dispatch:
 
 concurrency:
@@ -17,14 +17,72 @@ permissions:
   actions: read
 
 jobs:
+  cleanup-preview-branches:
+    # Run only when PR is closed or merged
+    if: github.event.action == 'closed'
+    permissions:
+      contents: write
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Delete preview branches for this PR
+        run: |
+          set -euo pipefail
+
+          PR_STATE="${{ github.event.pull_request.merged && 'merged' || 'closed' }}"
+          echo "[INFO] Cleaning up preview branches for $PR_STATE PR #${{ github.event.pull_request.number }}"
+
+          # Get the source branch name
+          SOURCE_BRANCH="${{ github.event.pull_request.head.ref }}"
+          echo "[INFO] Source branch: $SOURCE_BRANCH"
+
+          # Generate the safe prefix that would have been used for this branch
+          # This transforms the branch name to match the preview branch naming convention:
+          # 1. Remove all non-alphanumeric characters (tr -cd '[:alnum:]')
+          # 2. Take only the first 6 characters (cut -c1-6)
+          # Example: "feature/my-branch-123" -> "featur"
+          safe_prefix=$(echo "$SOURCE_BRANCH" | tr -cd '[:alnum:]' | cut -c1-6)
+          echo "[INFO] Looking for preview branches matching pattern: preview-${safe_prefix}-*"
+
+          # Find and delete all preview branches with this prefix
+          git fetch origin
+          BRANCHES=$(git branch -r | grep "origin/preview-${safe_prefix}-" | sed 's|origin/||' || true)
+
+          if [ -z "$BRANCHES" ]; then
+            echo "[INFO] No preview branches found for this PR"
+          else
+            echo "[INFO] Found preview branches to delete:"
+            echo "$BRANCHES"
+
+            for branch in $BRANCHES; do
+              # Safety check: ensure branch starts with 'preview-'
+              if [[ ! "$branch" =~ ^preview- ]]; then
+                echo "[ERROR] Branch '$branch' does not start with 'preview-'"
+                echo "[ERROR] Refusing to delete non-preview branch for safety"
+                exit 1
+              fi
+
+              echo "[INFO] Deleting branch: $branch"
+              git push origin --delete "$branch" || echo "[WARN] Failed to delete $branch (may already be deleted)"
+            done
+
+            echo "[SUCCESS] Cleanup complete"
+          fi
+
   create-preview:
     # This job needs to push a branch, so contents: write here only.
     permissions:
       contents: write
     runs-on: ubuntu-latest
 
     # Skip for PRs from forks - they don't have write access
-    if: github.event.pull_request.head.repo.full_name == github.repository || github.event_name == 'workflow_dispatch'
+    # Skip when PR is closed
+    if: (github.event.pull_request.head.repo.full_name == github.repository || github.event_name == 'workflow_dispatch') && github.event.action != 'closed'
 
     # Expose the generated preview branch name for the next job
     outputs:
@@ -175,5 +233,5 @@ jobs:
               owner: context.repo.owner,
               repo: context.repo.repo,
               issue_number: context.issue.number,
-              body: `Preview ID generated: ${preview}`
+              body: `Mintlify preview ID generated: ${preview}`
             });

.github/workflows/update-package-downloads.yml

@@ -28,13 +28,23 @@ jobs:
 
       - name: Update download counts
         run: |
-          uv run .github/scripts/packages_yml_get_downloads.py
+          # Note: Script only updates packages if their downloads_updated_at
+          # timestamp is older than 24 hours to avoid hammering pepy.tech.
+          # If run manually within 24 hours of a previous update, no changes
+          # will be detected and the workflow will exit early.
+          uv run scripts/packages_yml_get_downloads.py
 
-      - name: Upload updated packages.yml as artifact
+      - name: Generate partner package table
+        run: |
+          uv run python pipeline/tools/partner_pkg_table.py
+
+      - name: Upload updated files as artifact
         uses: actions/upload-artifact@v4
         with:
           name: packages-yml
-          path: reference/packages.yml
+          path: |
+            reference/packages.yml
+            src/oss/python/integrations/providers/overview.mdx
           retention-days: 1
 
   commit-downloads:
@@ -47,11 +57,11 @@ jobs:
     steps:
       - uses: actions/checkout@v5
 
-      - name: Download updated packages.yml
+      - name: Download updated files
         uses: actions/download-artifact@v4
         with:
           name: packages-yml
-          path: reference/
+          path: .
 
       - name: Create PR with changes
         env:
@@ -61,7 +71,7 @@ jobs:
           git config --global user.email "github-actions[bot]@users.noreply.github.com"
 
           # Check if there are changes
-          if git diff --quiet reference/packages.yml; then
+          if git diff --quiet reference/packages.yml src/oss/python/integrations/providers/overview.mdx; then
             echo "No changes to commit"
             exit 0
           fi
@@ -71,11 +81,12 @@ jobs:
           git checkout -b "$BRANCH_NAME"
 
           # Commit changes
-          git add reference/packages.yml
+          git add reference/packages.yml src/oss/python/integrations/providers/overview.mdx
           git commit -m "$(cat <<'EOF'
           chore: update package download counts
 
           🤖 Automated update of package download statistics from pepy.tech
+          and regenerated provider overview page
 
           Generated with GitHub Actions workflow update-package-downloads.yml
           EOF
@@ -93,6 +104,7 @@ jobs:
 
           ## Details
           - Updates download counts in `reference/packages.yml`
+          - Regenerates provider overview page at `src/oss/python/integrations/providers/overview.mdx`
           - Generated by GitHub Actions workflow `update-package-downloads.yml`
           - Scheduled to run every Sunday at 11:59 PM UTC
 

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "reference/external/html-docs"]
+	path = reference/external/html-docs
+	url = https://github.com/langchain-ai/langchain-api-docs-html.git

.markdownlint.json

@@ -4,5 +4,6 @@
   "MD013": false,
   "MD025": false,
   "MD033": false,
-  "MD041": false
+  "MD041": false,
+  "MD051": false
 }

AGENTS.md

@@ -59,6 +59,12 @@ If any code fences like this exist on the code page, then two outputs (one for e
 
 For implementation details, see `pipeline/preprocessors/markdown_preprocessor.py`.
 
+## Snippets
+
+Snippet files in `src/snippets/` are reusable MDX content that can be imported into multiple pages. These snippets undergo special link preprocessing during the build process that converts absolute `/oss/` links to relative paths.
+
+**Important:** When writing links in snippets, be careful about path segments. Read the docstrings and comments in `pipeline/core/builder.py` method `_process_snippet_markdown_file` (lines 807-872) to understand how snippet link preprocessing works and why certain path structures are required.
+
 ## Style guide
 
 In general, follow the [Google Developer Documentation Style Guide](https://developers.google.com/style). You can also access this style guide through the [Vale-compatible implementation](https://github.com/errata-ai/Google).

CLAUDE.md

@@ -1,88 +1 @@
-# LangChain's unified documentation overview
-
-This repository encompasses the comprehensive documentation for LangChain's products and services, hosted on the Mintlify platform. The documentation is divided into sections for each product. This is a shared set of guidelines to ensure consistency and quality across all content.
-
-## Scope
-
-**These instructions apply to manually authored documentation only. They do NOT apply to:**
-
-- Files in `**/reference/**` directories (auto-generated API reference documentation)
-- Build artifacts and generated files
-
-For reference documentation, see `.github/instructions/reference-docs.instructions.md`.
-
-## Working relationship
-
-- You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
-- ALWAYS ask for clarification rather than making assumptions
-- NEVER lie, guess, or make up information
-
-## Project context
-
-- Format: MDX files with YAML frontmatter. Mintlify syntax.
-- Config: docs.json for navigation, theme, settings
-- Components: Mintlify components
-
-## Content strategy
-
-- Document just enough for user success - not too much, not too little
-- Prioritize accuracy and usability of information
-- Make content evergreen when possible
-- Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason. Reference existing content when possible
-- Check existing patterns for consistency
-- Start by making the smallest reasonable changes
-
-## docs.json
-
-- Refer to the [docs.json schema](https://mintlify.com/docs.json) when building the docs.json file and site navigation
-- If adding a new group, ensure the root `index.mdx` is included in the `pages` array like:
-
-```json
-{
-  "group": "New group",
-  "pages": ["new-group/index", "new-group/other-page"]
-}
-```
-
-If the trailing `/index` (no extension included) is omitted, the Mintlify parser will raise a warning even though the site will still build.
-
-## Frontmatter requirements for pages
-
-- title: Clear, descriptive, concise page title
-- description: Concise summary for SEO/navigation
-
-## Custom code language fences
-
-We have implemented custom code language fences for Python and JavaScript/TypeScript. They are used to tag content that is specific to that language. Use either `:::python` or `:::js` to tag content that is specific to that language. Both are closed with the `:::` fence.
-
-If any code fences like this exist on the code page, then two outputs (one for each language) will be created. For example, if this syntax is on the page in `/concepts/foo.mdx`, two pages will be created at `/python/concepts/foo.mdx` and `/javascript/concepts/foo.mdx`.
-
-For implementation details, see `pipeline/preprocessors/markdown_preprocessor.py`.
-
-## Style guide
-
-In general, follow the [Google Developer Documentation Style Guide](https://developers.google.com/style). You can also access this style guide through the [Vale-compatible implementation](https://github.com/errata-ai/Google).
-
-- Second-person voice ("you")
-- Prerequisites at start of procedural content
-- Test all code examples before publishing
-- Match style and formatting of existing pages
-- Include both basic and advanced use cases
-- Language tags on all code blocks
-- Alt text on all images
-- Root relative paths for internal links
-- Correct spelling
-- Correct grammar
-- Sentence-case for headings
-- Ensure American English spelling
-
-## Do not
-
-- Do not skip frontmatter on any MDX file
-- Do not use absolute URLs for internal links
-- Do not review code blocks (denoted by ```), as they are often not full snippets
-- Do not include untested code examples
-- Do not make assumptions - always ask for clarification
-- Do not include localization in relative links (e.g., `/python/` or `/javascript/`) - these are resolved automatically by the build pipeline
-
-For questions, refer to the Mintlify docs (either via MCP, if available), or at the [Mintlify documentation](https://docs.mintlify.com/docs/introduction).
+AGENTS.md