Add WebSite schema structured data to improve how Google displays
the site name in search results.

Changes:
- Add JSON-LD WebSite schema to root layout with site name "Inkeep Agents"
- Include alternateName "Inkeep" as fallback
- Apply XSS protection by escaping < characters
- Simplify page titles from "Page - Inkeep Docs ~ Open Source Agent Builder"
  to "Page - Inkeep Docs" for cleaner branding

This provides stronger signals to Google for displaying "Inkeep Agents"
as the site name in search results for the docs.inkeep.com subdomain.

The implementation follows Google's site-name guidelines and Next.js 15
best practices for JSON-LD structured data.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Install schema-dts for type-safe schema.org definitions and update
the WebSite schema in layout.tsx to use proper TypeScript types.

Changes:
- Install schema-dts dev dependency
- Import WebSite and WithContext types from schema-dts
- Add type annotation to jsonLd: WithContext<WebSite>
- Rename site from "Inkeep Agents" to "Inkeep Docs"

This provides compile-time type checking for the structured data
and prevents potential errors in the schema definition.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

- Regenerated pnpm-lock.yaml to fix patchedDependencies mismatch
- Removes overly restrictive CPU constraint from libsql package
- Resolves ERR_PNPM_LOCKFILE_CONFIG_MISMATCH error on Vercel

- Pin fumadocs-openapi to 9.4.0 to prevent version conflicts
- Add custom not-found.tsx and error.tsx to avoid fumadocs-ui compatibility issues
- Update pnpm-lock.yaml to resolve ERR_PNPM_LOCKFILE_CONFIG_MISMATCH

These changes ensure consistent builds across local and CI/CD environments.

- Rename Error to ErrorPage to avoid shadowing global
- Add type="button" to button element

- Set NODE_ENV=production in agents-docs build script
- Resolves 'Html should not be imported outside pages/_document' error
- Ensures consistent builds regardless of local NODE_ENV setting

- Apply same NODE_ENV=production fix to agents-manage-ui
- Resolves Html import error in agents-manage-ui build

- Remove custom error pages (not-found.tsx, error.tsx) - not needed with NODE_ENV=production
- Revert fumadocs-openapi to ^9.4.0 (unpinned) - pinning was unnecessary
- Update pnpm-lock.yaml to reflect changes

The actual fix for Vercel deployment was only:
1. Regenerating pnpm-lock.yaml to fix patch hash mismatch
2. Setting NODE_ENV=production in build scripts

Add permanent redirect from /typescript-sdk/request-context to
/typescript-sdk/headers for backward compatibility.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

The lockfile was previously generated with pnpm 9.8.0, which uses base32
hash format (4o4xvnq62nkojrm2vwqdgdti6i), but CI uses pnpm 10.10.0 which
expects SHA256 format (57c6f1f9835fc6413b1565f909243d713314fac7b3e5fc8ccb3963a4c8b8d9a1).

This was causing ERR_PNPM_LOCKFILE_CONFIG_MISMATCH errors in CI for
agents-manage-api, agents-manage-ui, and agents-run-api builds.

Changes:
- Switched local pnpm version to 10.10.0 to match project specification
- Regenerated pnpm-lock.yaml with correct hash format
- Added fast-glob and updated next-validate-link in agents-docs

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>