ux-patterns-for-developers

What changed adds equivalent routed production workflows for GitHub Actions and Gitea Actions centralizes validation and prebuilt Vercel deployment in shared scripts disables Vercel Git-triggered deployments to prevent duplicate builds keeps manual runs validation-only unless that provider is selected Why This lets production builds move between GitHub and the homelab Gitea runner without changing deployment behavior or spending GitHub Actions minutes when Gitea is selected. Validation full completed successfully without deployment on both routed workflows and on both shared scripts Summary by CodeRabbit Chores** Added automated validation for dependency installation and TypeScript checks. Added a deployment workflow that verifies credentials, builds the web app, and publishes it. Disabled automatic Vercel deployments from the repository configuration.

Why The "X views" badge on pattern pages fetched (OpenPanel) client-side on every page view — a function invocation per view with no real value, and the upstream call was failing auth () so it always showed 0 anyway. Changes : drop the view count, the fetch, and the React hooks. It's now a plain (non-client) component that renders only the frontmatter-driven popularity badge. Delete the now-unused route and its function entry. Effect Removes the per-view invocations entirely (further GB-Hrs reduction). Makes the OpenPanel "enable Export" todo moot. 🤖 Generated with Claude Code Summary by CodeRabbit Refactor Simplified pattern stats display to focus on popularity badges only. Removed view-count loading and formatting from the stats UI. Bug Fixes Removed the page stats endpoint, eliminating an extra stats fetch and related error states for missing page data. Chores** Streamlined serverless configuration by removing the dedicated stats function settings.

Why PR #256 added bad-bot blocking on , but it reused the general bad-bot list which matches generic HTTP clients (, , , ) — exactly what legitimate MCP callers use. That would 403 real programmatic clients. Fix Add (matches ) to . On the MCP host, hard-block only those scanners; rely on the existing per-IP rate limit (30/window) to contain abuse from everything else. Main-site (non-MCP) traffic still uses the full bad-bot list unchanged. 🤖 Generated with Claude Code