Fix formatting in resume file

.agents/resume

@@ -0,0 +1,9 @@
+#!/usr/bin/env bash
+# Runs on every orb wake. Nothing to authenticate or reconnect; just confirm the
+# toolchain from .agents/setup still resolves so a broken snapshot fails loudly.
+set -euo pipefail
+
+repo_root="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+eval "$("$HOME/.local/bin/mise" -C "$repo_root" env -s bash)"
+node --version
+pnpm --version 

.agents/setup

@@ -0,0 +1,46 @@
+#!/usr/bin/env bash
+# Prepares a fresh Amp orb: the Node and pnpm versions pinned in .tool-versions,
+# then the pnpm dependencies. Idempotent: Amp reruns it on stale snapshots.
+set -euo pipefail
+
+repo_root="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+cd "$repo_root"
+
+step() { printf '\n==> %s (%s)\n' "$1" "$(date +%T)"; }
+
+mise_bin="$HOME/.local/bin/mise"
+step "Install mise"
+if [ ! -x "$mise_bin" ]; then
+	curl -fsSL https://mise.run | sh
+fi
+
+step "Install pinned toolchain from .tool-versions"
+"$mise_bin" install --yes
+# The installer cannot change this running script's environment.
+eval "$("$mise_bin" env -s bash)"
+
+step "Expose the toolchain to login shells"
+profile_marker="# sourcegraph/docs: pinned Node and pnpm from mise"
+if ! grep -Fqx "$profile_marker" "$HOME/.bash_profile" 2>/dev/null; then
+	cat >>"$HOME/.bash_profile" <<EOF
+
+$profile_marker
+[ -d "$repo_root" ] && eval "\$("$mise_bin" -C "$repo_root" env -s bash)"
+EOF
+fi
+
+step "Install dependencies"
+# CI=true: without a TTY, pnpm otherwise aborts if a stale snapshot's
+# node_modules was built by a different pnpm version and must be recreated.
+CI=true pnpm install --frozen-lockfile
+
+step "Write orb agent guidance"
+mkdir -p "$HOME/.config/amp"
+cat >"$HOME/.config/amp/AGENTS.md" <<'EOF'
+# Inside the Orb
+
+- Node and pnpm come from mise (`.tool-versions`); `.agents/setup` puts them on PATH for login shells. Use `pnpm`, not `npm`.
+- Dev server: `amp orb services ensure` starts `pnpm dev` from `.amp/services.yaml` and returns a portal link.
+EOF
+
+step "Done: node $(node --version), pnpm $(pnpm --version)"

.agents/skills/publishing-docs-versions/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: publishing-docs-versions
+description: "Archives Sourcegraph docs release branches and updates latest-version metadata. Use when a new Sourcegraph docs version is released, when creating docs legacy branches, or when updating DOCS_LATEST_VERSION and previous-version lists."
+---
+
+# Publishing Sourcegraph Docs Versions
+
+Use this skill for the Sourcegraph docs repo release-version workflow: cutting legacy branches in the `legacy` remote and updating `origin` so the newest version becomes `latest`.
+
+## Repository conventions
+
+- Remotes:
+  - `origin` = `sourcegraph/docs`
+  - `legacy` = `sourcegraph/docs-legacy-versions`
+- 7.x legacy branches use underscores: `v7_0`, `v7_1`, `v7_2`, etc.
+- Legacy branches are pushed directly to the `legacy` remote.
+- `origin/main` is protected; direct pushes are rejected. Make a branch on `origin` and open a PR.
+- The files that control latest/previous versions are:
+  - `docs.config.js`
+  - `src/data/versions.ts`
+  - `docs/legacy.mdx`
+- `src/data/versions.ts` on `origin/main` is the canonical dropdown list. The
+  current site exposes it through `/docs/api/versions`, and legacy selectors
+  load that manifest at runtime.
+- A legacy branch's bundled `src/data/versions.ts` is only a fallback. Its first
+  entry identifies the archived site and must not have the `latest` label.
+
+## Standard workflow for a new release
+
+For a new release `X.Y`:
+
+1. Archive the previous docs version `P.Q` in the `legacy` remote.
+2. Ensure the legacy branch’s own config says it is version `P.Q`, marks it as
+   selected rather than latest, and lists older fallback versions only.
+3. Update `origin` so `X.Y` is latest and `P.Q` appears as a previous version.
+
+Example: when 7.4 is released, archive 7.3 as `legacy/v7_3`, then update `origin` with `DOCS_LATEST_VERSION: '7.4'` and add 7.3 to previous-version lists.
+
+## Finding the cut point for a legacy branch
+
+Always inspect history instead of guessing:
+
+```bash
+git fetch --all --prune
+git log --date=short --pretty=format:'%h %ad %s' origin/main --since='<release date - 1 week>' --until='<release date + 2 weeks>' --reverse
+git for-each-ref refs/remotes/legacy --format='%(refname:short) %(objectname:short) %(committerdate:short) %(subject)' | sort -V | tail -50
+```
+
+Pick the commit the user considers the correct snapshot for the previous version. If the user gives a release date but not a commit, use the repo’s existing pattern:
+
+- Choose a hand-picked `origin/main` commit near the release cut.
+- Prefer the last relevant docs commit on the release date when obvious.
+- If no version-bump commit exists yet and the user wants the just-current docs archived, use the current `origin/main` tip.
+
+For reference, recent historical decisions:
+
+- `legacy/v7_0` was cut from `a5d80e5e` and then got empty no-op marker commits.
+- `legacy/v7_1` was cut from `6b8ae421` for the Apr 24 release-date snapshot.
+- `legacy/v7_2` was cut from `fccceac6`, then updated with a version metadata commit.
+
+## Creating and pushing the legacy branch
+
+Create the branch from the selected cut commit, add an empty marker commit, and push to `legacy`:
+
+```bash
+git switch --detach <cut-commit>
+git switch -c vX_Y
+git commit --allow-empty -m "Branch for docs version X.Y"
+git push -u legacy vX_Y
+```
+
+Then update the legacy branch so it identifies itself as `X.Y` and lists only
+older fallback versions. The runtime manifest supplies the current canonical
+list when the current docs site is available.
+
+For `v7_3`, for example:
+
+- `docs.config.js`: `DOCS_LATEST_VERSION: '7.3'`
+- `src/data/versions.ts`: first entry identifies `v7.3` without a `latest`
+  label; fallback entries should include `v7.2`, `v7.1`, `v7.0`, then 6.x.
+- `docs/legacy.mdx`: `Sourcegraph 7.X` should include `7.2`, `7.1`, `7.0` (not 7.3 itself).
+
+Commit and push:
+
+```bash
+git add docs.config.js src/data/versions.ts docs/legacy.mdx
+git commit -m "Update docs latest version to X.Y"
+git push legacy vX_Y
+```
+
+## Updating origin for the newly released version
+
+Work on a branch from `origin/main`:
+
+```bash
+git switch main
+git pull --ff-only origin main
+git switch -c eg-update-docs-to-X-Y
+```
+
+Apply the same version metadata pattern, but for the new latest version.
+
+For `7.4`, for example:
+
+- `docs.config.js`: `DOCS_LATEST_VERSION: '7.4'`
+- `src/data/versions.ts`: add previous versions in descending order: `v7.3`, `v7.2`, `v7.1`, `v7.0`, then 6.x.
+- `docs/legacy.mdx`: add/update `Sourcegraph 7.X` with `7.3`, `7.2`, `7.1`, `7.0`.
+
+Commit, push the branch, and open a PR:
+
+```bash
+git add docs.config.js src/data/versions.ts docs/legacy.mdx
+git commit -m "Update docs latest version to X.Y"
+git push -u origin eg-update-docs-to-X-Y
+gh pr create --base main --head eg-update-docs-to-X-Y --title "Update docs latest version to X.Y" --body "## Summary
+- Set DOCS_LATEST_VERSION to X.Y
+- Add previous 7.x versions to the version selector
+- Update the legacy versions page
+
+## Test plan
+- Not run (config/navigation content change only)"
+```
+
+## Verification
+
+Use lightweight verification for this content/config change:
+
+```bash
+git diff -- docs.config.js src/data/versions.ts docs/legacy.mdx
+git status --short --branch
+git ls-remote --heads legacy 'v7_*'
+```
+
+Confirm:
+
+- The legacy branch points to the pushed commit.
+- The legacy branch identifies itself without claiming to be latest and lists
+  only older fallback versions.
+- The origin PR branch sets the new latest version and includes the archived version in previous-version lists.
+- The current manifest lists the new latest version first, and its URL points to
+  `https://sourcegraph.com/docs`.
+- Return the local workspace to clean `main` unless the user asked to stay on a release branch.

.amp/services.yaml

@@ -0,0 +1,10 @@
+services:
+    docs:
+        command: pnpm dev --hostname 0.0.0.0
+        port: 31420
+        env:
+            NODE_OPTIONS: --max-old-space-size=3072
+        health: /agentic-batch-changes
+        portal:
+            url: /agentic-batch-changes
+            title: Sourcegraph Docs

.github/workflows/check-links.yml

@@ -0,0 +1,110 @@
+name: Check links
+
+# Reports internal links and #anchors that this PR breaks, compared with the
+# merge base, absolute links to this site, and external links on added lines
+# that 404. Pre-existing broken links on the base branch are ignored.
+
+on:
+    pull_request:
+
+# A new push supersedes the run for the previous one
+concurrency:
+    group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
+    cancel-in-progress: true
+
+permissions:
+    contents: read
+    pull-requests: write
+
+jobs:
+    check-links:
+        name: Broken links introduced by this PR
+        runs-on: ubuntu-latest
+        steps:
+            - name: Check out pull request head
+              uses: actions/checkout@v4
+              with:
+                  ref: ${{ github.event.pull_request.head.sha }}
+                  fetch-depth: 0
+
+            - name: Install github-slugger, the only dependency of dev/check-links.mjs
+              # Into a scratch prefix, not the repo: `npm install <pkg>` next to
+              # package.json would install every dependency of the site
+              run: |
+                  npm install --prefix "$RUNNER_TEMP/deps" --no-package-lock --no-audit --no-fund \
+                      "github-slugger@$(node -p 'require("./package.json").dependencies["github-slugger"]')"
+                  ln -s "$RUNNER_TEMP/deps/node_modules" node_modules
+
+            - name: Check out merge base
+              env:
+                  BASE_SHA: ${{ github.event.pull_request.base.sha }}
+              run: |
+                  merge_base=$(git merge-base "$BASE_SHA" HEAD)
+                  git worktree add "$RUNNER_TEMP/base" "$merge_base"
+                  git diff -U0 "$merge_base" HEAD > "$RUNNER_TEMP/changes.diff"
+
+            - name: Record broken links already present on the base branch
+              # Exit 1 means findings, which is expected here
+              run: |
+                  node dev/check-links.mjs --check-anchors --check-self-links --format json \
+                      --root "$RUNNER_TEMP/base" > "$RUNNER_TEMP/base-links.json" \
+                      || [ $? -eq 1 ]
+
+            - name: Find broken links introduced by this PR
+              id: check
+              env:
+                  # File links in the report open the file on the PR branch
+                  LINK_BASE: ${{ github.event.pull_request.head.repo.html_url }}/blob/${{ github.event.pull_request.head.ref }}
+              run: |
+                  if node dev/check-links.mjs --check-anchors --check-self-links --check-external --format markdown \
+                      --baseline "$RUNNER_TEMP/base-links.json" \
+                      --diff "$RUNNER_TEMP/changes.diff" \
+                      --review "$RUNNER_TEMP/review.json" \
+                      --link-base "$LINK_BASE" > "$RUNNER_TEMP/report.md"; then
+                      echo "broken=false" >> "$GITHUB_OUTPUT"
+                  else
+                      echo "broken=true" >> "$GITHUB_OUTPUT"
+                  fi
+                  cat "$RUNNER_TEMP/report.md"
+
+            - name: Comment on the pull request
+              # Fork PRs get a read-only token; the report is still in the job log
+              if: github.event.pull_request.head.repo.full_name == github.repository
+              env:
+                  GH_TOKEN: ${{ github.token }}
+                  PR_NUMBER: ${{ github.event.pull_request.number }}
+                  BROKEN: ${{ steps.check.outputs.broken }}
+              run: |
+                  marker='<!-- check-links-report -->'
+                  existing_comment=$(gh api "repos/$GITHUB_REPOSITORY/issues/$PR_NUMBER/comments" \
+                      --paginate --jq ".[] | select(.body | startswith(\"$marker\")) | .id" | head -n 1)
+
+                  # Comment only when there is something to report, or an earlier report to resolve
+                  if [ "$BROKEN" = true ]; then
+                      { echo "$marker"; cat "$RUNNER_TEMP/report.md"; } > "$RUNNER_TEMP/comment.md"
+                  elif [ -n "$existing_comment" ]; then
+                      printf '%s\n### ✅ The broken links an earlier revision of this PR introduced are fixed\n' \
+                          "$marker" > "$RUNNER_TEMP/comment.md"
+                  else
+                      exit 0
+                  fi
+
+                  if [ -n "$existing_comment" ]; then
+                      gh api --method PATCH "repos/$GITHUB_REPOSITORY/issues/comments/$existing_comment" \
+                          --field body=@"$RUNNER_TEMP/comment.md"
+                  else
+                      gh pr comment "$PR_NUMBER" --body-file "$RUNNER_TEMP/comment.md"
+                  fi
+
+            - name: Suggest fixes as review comments
+              # One suggested change per finding with a fix, kept in sync with the
+              # findings; see dev/sync-review-comments.sh
+              if: github.event.pull_request.head.repo.full_name == github.repository
+              env:
+                  GH_TOKEN: ${{ github.token }}
+                  PR_NUMBER: ${{ github.event.pull_request.number }}
+              run: dev/sync-review-comments.sh '<!-- check-links-finding:' "$RUNNER_TEMP/review.json"
+
+            - name: Fail when this PR introduces broken links
+              if: steps.check.outputs.broken == 'true'
+              run: exit 1