@cubis/foundry 0.3.10 → 0.3.12

package/Ai Agent Workflow/powers/vercel-functions/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: vercel-functions
+description: "Vercel Serverless and Edge Functions: core patterns, Node.js and Python runtimes, edge runtime, Fluid Compute for long-running tasks, and function configuration."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, serverless, functions, edge function, nodejs runtime, python runtime, fluid compute, function config, api route, edge runtime
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nodejs-best-practices, fastapi-expert, vercel-routing, vercel-caching
+  consolidates: vercel-functions-core, vercel-functions-edge-runtime, vercel-functions-nodejs, vercel-functions-python, vercel-function-config, vercel-fluid-compute
+---
+
+# Vercel Functions
+
+## Purpose
+
+Design and implement Vercel Serverless and Edge Functions with the correct runtime selection, configuration, and compute strategy for each use case.
+
+## When To Use
+
+- Writing Vercel API routes or serverless function handlers.
+- Choosing between Edge Runtime and Node.js runtime.
+- Configuring Python serverless functions on Vercel.
+- Implementing long-running tasks or streaming with Fluid Compute.
+- Tuning function memory, regions, timeout, and concurrency config.
+
+## Domain Areas
+
+### Core Patterns
+
+- Request/response handler structure for Vercel functions.
+- Environment-aware error handling and status codes.
+- Cold start mitigation strategies.
+
+### Node.js Runtime
+
+- Use `@vercel/node` and standard Node.js APIs.
+- Streaming responses with `Response` and `ReadableStream`.
+
+### Python Runtime
+
+- Configure `requirements.txt` and handler conventions.
+- Use WSGI/ASGI adapters where needed.
+
+### Edge Runtime
+
+- Use Web Standard APIs only (no Node.js built-ins).
+- Optimize for global low-latency execution at the edge.
+- Middleware-friendly patterns.
+
+### Fluid Compute
+
+- Enable for long-running tasks exceeding standard limits.
+- Stream output progressively for large responses.
+- Configure max duration and concurrency appropriately.
+
+### Function Config (`vercel.json`)
+
+- Set `runtime`, `regions`, `maxDuration`, `memory` per function.
+- Use `rewrites` to map routes to specific functions.
+
+## Operating Checklist
+
+1. Choose runtime (Edge vs Node.js vs Python) based on latency, API, and duration needs.
+2. Set explicit `maxDuration` and `memory` for non-default requirements.
+3. Implement structured error responses with proper HTTP status codes.
+4. Test cold-start behavior and streaming in staging environment.
+5. Validate regional deployment targets match latency requirements.
+6. Run regression checks before promoting to production.
+
+## Output Contract
+
+- Runtime selection rationale and tradeoffs
+- Handler implementation with error handling and streaming
+- `vercel.json` function config section
+- Performance validation (cold start, p99 latency targets)
+- Residual risks and follow-up actions

package/Ai Agent Workflow/powers/vercel-observability/POWER.md

@@ -0,0 +1,103 @@
+````markdown
+---
+inclusion: manual
+name: vercel-observability
+description: "Vercel observability stack: logs, tracing (OTel), session tracing, speed insights, web analytics, alerts, custom events, log drains, audit logs, and structured monitoring."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, observability, runtime logs, tracing, opentelemetry, session tracing, speed insights, web analytics, alerts, log drain, audit log, custom events, monitoring
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: monitoring-expert, sre-engineer, vercel-functions, vercel-firewall
+  consolidates: vercel-observability-overview, vercel-alerts-monitoring, vercel-runtime-logs, vercel-log-drain-reference, vercel-log-trace-correlation, vercel-session-tracing, vercel-tracing-otel, vercel-speed-insights, vercel-web-analytics, vercel-custom-events, vercel-audit-logs, vercel-drains-setup
+---
+
+# Vercel Observability
+
+## Purpose
+
+Instrument, collect, and act on observability signals from Vercel deployments: structured runtime logs, distributed traces, session tracing, performance metrics, analytics, and audit events.
+
+## When To Use
+
+- Setting up runtime log viewing and structured log queries.
+- Configuring log drains to export to external systems (Datadog, Baselime, etc.).
+- Implementing OpenTelemetry (OTel) tracing in Vercel functions.
+- Correlating logs with traces and requests via trace IDs.
+- Monitoring Core Web Vitals with Speed Insights.
+- Collecting custom business events for product analytics.
+- Tracking user sessions for debugging with Session Tracing.
+- Reviewing audit logs for security and compliance.
+- Setting up threshold alerts on function errors, p99 latency, etc.
+
+## Domain Areas
+
+### Runtime Logs
+
+- View and filter logs in Vercel dashboard or CLI.
+- Structure logs with consistent fields (level, traceId, userId).
+
+### Log Drains
+
+- Configure HTTP or HTTPS log drain endpoints.
+- Filter by source (functions, edge, build) and log level.
+- Validate drain delivery and handle backpressure.
+
+### OpenTelemetry Tracing
+
+- Instrument functions with `@vercel/otel` or standard OTel SDK.
+- Export spans to Vercel or external OTLP endpoints.
+- Correlate log entries with trace IDs for unified debugging.
+
+### Session Tracing
+
+- Enable session capture for replay-based debugging.
+- Scope to error sessions or specific user segments.
+
+### Speed Insights
+
+- Install `@vercel/speed-insights` in Next.js or other frameworks.
+- Monitor LCP, FID/INP, CLS per route.
+- Set performance budgets and track regressions.
+
+### Web Analytics
+
+- Enable Vercel Web Analytics for privacy-first traffic data.
+- Track page views, referrers, and custom events.
+
+### Custom Events
+
+- Emit custom events via `@vercel/analytics/react` or REST API.
+- Use for funnel tracking, feature adoption, and error reporting.
+
+### Alerts & Monitoring
+
+- Configure threshold alerts on error rate, latency, and availability.
+- Route alerts to Slack, PagerDuty, or webhooks.
+
+### Audit Logs
+
+- Review deployment, permission, and configuration changes.
+- Export audit logs for compliance reporting.
+
+## Operating Checklist
+
+1. Enable runtime logs and configure structured log format.
+2. Set up log drain to external system if needed.
+3. Instrument functions with OTel and validate trace export.
+4. Install Speed Insights and establish performance budgets.
+5. Configure alerts with non-noisy thresholds and on-call routing.
+6. Schedule audit log review cadence for security compliance.
+
+## Output Contract
+
+- Observability architecture diagram (logs → traces → metrics → alerts)
+- Log structure schema and drain configuration
+- OTel instrumentation code and exporter config
+- Speed Insights dashboard and performance budget definition
+- Alert policy with thresholds and escalation routing
+````

package/Ai Agent Workflow/powers/vercel-observability/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: vercel-observability
+description: "Vercel observability stack: logs, tracing (OTel), session tracing, speed insights, web analytics, alerts, custom events, log drains, audit logs, and structured monitoring."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, observability, runtime logs, tracing, opentelemetry, session tracing, speed insights, web analytics, alerts, log drain, audit log, custom events, monitoring
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: monitoring-expert, sre-engineer, vercel-functions, vercel-firewall
+  consolidates: vercel-observability-overview, vercel-alerts-monitoring, vercel-runtime-logs, vercel-log-drain-reference, vercel-log-trace-correlation, vercel-session-tracing, vercel-tracing-otel, vercel-speed-insights, vercel-web-analytics, vercel-custom-events, vercel-audit-logs, vercel-drains-setup
+---
+
+# Vercel Observability
+
+## Purpose
+
+Instrument, collect, and act on observability signals from Vercel deployments: structured runtime logs, distributed traces, session tracing, performance metrics, analytics, and audit events.
+
+## When To Use
+
+- Setting up runtime log viewing and structured log queries.
+- Configuring log drains to export to external systems (Datadog, Baselime, etc.).
+- Implementing OpenTelemetry (OTel) tracing in Vercel functions.
+- Correlating logs with traces and requests via trace IDs.
+- Monitoring Core Web Vitals with Speed Insights.
+- Collecting custom business events for product analytics.
+- Tracking user sessions for debugging with Session Tracing.
+- Reviewing audit logs for security and compliance.
+- Setting up threshold alerts on function errors, p99 latency, etc.
+
+## Domain Areas
+
+### Runtime Logs
+
+- View and filter logs in Vercel dashboard or CLI.
+- Structure logs with consistent fields (level, traceId, userId).
+
+### Log Drains
+
+- Configure HTTP or HTTPS log drain endpoints.
+- Filter by source (functions, edge, build) and log level.
+- Validate drain delivery and handle backpressure.
+
+### OpenTelemetry Tracing
+
+- Instrument functions with `@vercel/otel` or standard OTel SDK.
+- Export spans to Vercel or external OTLP endpoints.
+- Correlate log entries with trace IDs for unified debugging.
+
+### Session Tracing
+
+- Enable session capture for replay-based debugging.
+- Scope to error sessions or specific user segments.
+
+### Speed Insights
+
+- Install `@vercel/speed-insights` in Next.js or other frameworks.
+- Monitor LCP, FID/INP, CLS per route.
+- Set performance budgets and track regressions.
+
+### Web Analytics
+
+- Enable Vercel Web Analytics for privacy-first traffic data.
+- Track page views, referrers, and custom events.
+
+### Custom Events
+
+- Emit custom events via `@vercel/analytics/react` or REST API.
+- Use for funnel tracking, feature adoption, and error reporting.
+
+### Alerts & Monitoring
+
+- Configure threshold alerts on error rate, latency, and availability.
+- Route alerts to Slack, PagerDuty, or webhooks.
+
+### Audit Logs
+
+- Review deployment, permission, and configuration changes.
+- Export audit logs for compliance reporting.
+
+## Operating Checklist
+
+1. Enable runtime logs and configure structured log format.
+2. Set up log drain to external system if needed.
+3. Instrument functions with OTel and validate trace export.
+4. Install Speed Insights and establish performance budgets.
+5. Configure alerts with non-noisy thresholds and on-call routing.
+6. Schedule audit log review cadence for security compliance.
+
+## Output Contract
+
+- Observability architecture diagram (logs → traces → metrics → alerts)
+- Log structure schema and drain configuration
+- OTel instrumentation code and exporter config
+- Speed Insights dashboard and performance budget definition
+- Alert policy with thresholds and escalation routing

package/Ai Agent Workflow/powers/vercel-platform/POWER.md

@@ -0,0 +1,127 @@
+````markdown
+---
+inclusion: manual
+name: vercel-platform
+description: "Vercel platform operations: project configuration, RBAC, 2FA/OIDC/SSO, secure compute, REST API, SDK, webhooks, integrations, MCP for agents, image optimization, OG images, cron jobs, monorepos, microfrontends, and multi-tenant architecture."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, project config, rbac, 2fa, oidc, sso, secure compute, rest api, vercel sdk, webhooks, integrations marketplace, mcp for agents, image optimization, og image, cron jobs, monorepo, microfrontends, multi-tenant, automation, audit
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: devops-engineer, secure-code-guardian, monitoring-expert, vercel-deployments, vercel-observability
+  consolidates: vercel-automation, vercel-project-configuration, vercel-rbac-access-groups, vercel-2fa-enforcement, vercel-oidc-federation, vercel-secure-compute, vercel-rest-api, vercel-sdk, vercel-webhooks-and-checks, vercel-integrations-native, vercel-marketplace-partner-api, vercel-mcp-for-agents, vercel-agent-workflows, vercel-image-optimization, vercel-og-image-generation, vercel-cron-jobs, vercel-microfrontends, vercel-monorepos, vercel-multi-tenant
+---
+
+# Vercel Platform
+
+## Purpose
+
+Administer Vercel at the platform level — project configuration, team access control, identity/SSO, secure networking, REST API automation, webhooks, native integrations, architecture patterns (monorepos, microfrontends, multi-tenant), and platform-level features like image optimization, OG image generation, and cron jobs.
+
+## When To Use
+
+- Configuring project-level settings in `vercel.json`.
+- Managing team RBAC roles and access groups.
+- Enforcing 2FA or configuring OIDC/SSO federation.
+- Using Secure Compute for private networking (VPC-like).
+- Automating Vercel operations via REST API or SDK.
+- Registering webhooks for deployment events.
+- Installing and building native integrations or marketplace partners.
+- Configuring Vercel MCP for agent-driven platform automation.
+- Optimizing images via `next/image` or Vercel's Image Optimization API.
+- Generating Open Graph images with `@vercel/og`.
+- Scheduling background jobs with Vercel Cron.
+- Structuring monorepo builds and microfrontend app groups.
+- Implementing multi-tenant SaaS on Vercel.
+
+## Domain Areas
+
+### Project Configuration
+
+- `vercel.json` schema: functions, headers, redirects, rewrites, regions.
+- Framework detection and override settings.
+
+### RBAC & Access Groups
+
+- Assign Owner, Member, Viewer roles per project or team.
+- Access groups for project-level permission scoping.
+
+### Identity & Security (2FA / OIDC / Secure Compute)
+
+- Enforce 2FA for all team members.
+- Configure OIDC federation for CI/CD token-based auth.
+- Use Secure Compute for private egress to internal services.
+
+### REST API & SDK
+
+- Authenticate with `VERCEL_TOKEN`; respect rate limits.
+- Use `@vercel/sdk` (TypeScript) for typed API access.
+- Common endpoints: deployments, env vars, domains, projects.
+
+### Webhooks & Checks
+
+- Register webhooks for `deployment.created`, `deployment.succeeded`, etc.
+- Implement deployment checks (CI gates) via the Checks API.
+
+### Integrations & Marketplace
+
+- Install native integrations (e.g., observability, storage).
+- Build marketplace partner integrations with OAuth and webhooks.
+
+### MCP for Agents
+
+- Run Vercel MCP server locally or in CI for agent workflows.
+- Use for automated deployment queries, log retrieval, and config changes.
+
+### Image Optimization & OG Images
+
+- Use `next/image` for automatic format conversion and resizing.
+- Generate OG images on the fly with `@vercel/og` (ImageResponse).
+- Cache OG images appropriately.
+
+### Cron Jobs
+
+- Define cron schedules in `vercel.json` under `crons`.
+- Secure cron handler endpoints with `CRON_SECRET`.
+- Monitor cron execution logs in Vercel dashboard.
+
+### Monorepos
+
+- Configure `rootDirectory` per project for monorepo packages.
+- Use Turborepo + Vercel Remote Cache for fast incremental builds.
+
+### Microfrontends
+
+- Define app groups and routing in Vercel Microfrontends config.
+- Route per-path segments to independent Next.js apps.
+
+### Multi-Tenant Architecture
+
+- Use hostname-based routing in middleware for tenant resolution.
+- Scope environment variables and storage per tenant.
+- Combine with Edge Config for real-time tenant config.
+
+## Operating Checklist
+
+1. Audit and lock project configuration in `vercel.json`.
+2. Review and tighten RBAC roles; remove over-privileged members.
+3. Enforce 2FA for all team members; configure OIDC for CI.
+4. Validate REST API token scopes; rotate stale tokens.
+5. Test webhook delivery with replay; implement idempotent handlers.
+6. Verify cron endpoint security with `CRON_SECRET` validation.
+7. Validate monorepo build filtering and Turborepo cache hit rates.
+
+## Output Contract
+
+- `vercel.json` configuration with annotated sections
+- RBAC role matrix and access group definitions
+- Identity/SSO configuration steps and validation evidence
+- REST API and SDK integration patterns
+- Webhook handler implementation with idempotency
+- Architecture diagram for monorepo/microfrontend/multi-tenant setup
+- Residual risks and follow-up actions
+````

package/Ai Agent Workflow/powers/vercel-platform/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: vercel-platform
+description: "Vercel platform operations: project configuration, RBAC, 2FA/OIDC/SSO, secure compute, REST API, SDK, webhooks, integrations, MCP for agents, image optimization, OG images, cron jobs, monorepos, microfrontends, and multi-tenant architecture."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, project config, rbac, 2fa, oidc, sso, secure compute, rest api, vercel sdk, webhooks, integrations marketplace, mcp for agents, image optimization, og image, cron jobs, monorepo, microfrontends, multi-tenant, automation, audit
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: devops-engineer, secure-code-guardian, monitoring-expert, vercel-deployments, vercel-observability
+  consolidates: vercel-automation, vercel-project-configuration, vercel-rbac-access-groups, vercel-2fa-enforcement, vercel-oidc-federation, vercel-secure-compute, vercel-rest-api, vercel-sdk, vercel-webhooks-and-checks, vercel-integrations-native, vercel-marketplace-partner-api, vercel-mcp-for-agents, vercel-agent-workflows, vercel-image-optimization, vercel-og-image-generation, vercel-cron-jobs, vercel-microfrontends, vercel-monorepos, vercel-multi-tenant
+---
+
+# Vercel Platform
+
+## Purpose
+
+Administer Vercel at the platform level — project configuration, team access control, identity/SSO, secure networking, REST API automation, webhooks, native integrations, architecture patterns (monorepos, microfrontends, multi-tenant), and platform-level features like image optimization, OG image generation, and cron jobs.
+
+## When To Use
+
+- Configuring project-level settings in `vercel.json`.
+- Managing team RBAC roles and access groups.
+- Enforcing 2FA or configuring OIDC/SSO federation.
+- Using Secure Compute for private networking (VPC-like).
+- Automating Vercel operations via REST API or SDK.
+- Registering webhooks for deployment events.
+- Installing and building native integrations or marketplace partners.
+- Configuring Vercel MCP for agent-driven platform automation.
+- Optimizing images via `next/image` or Vercel's Image Optimization API.
+- Generating Open Graph images with `@vercel/og`.
+- Scheduling background jobs with Vercel Cron.
+- Structuring monorepo builds and microfrontend app groups.
+- Implementing multi-tenant SaaS on Vercel.
+
+## Domain Areas
+
+### Project Configuration
+
+- `vercel.json` schema: functions, headers, redirects, rewrites, regions.
+- Framework detection and override settings.
+
+### RBAC & Access Groups
+
+- Assign Owner, Member, Viewer roles per project or team.
+- Access groups for project-level permission scoping.
+
+### Identity & Security (2FA / OIDC / Secure Compute)
+
+- Enforce 2FA for all team members.
+- Configure OIDC federation for CI/CD token-based auth.
+- Use Secure Compute for private egress to internal services.
+
+### REST API & SDK
+
+- Authenticate with `VERCEL_TOKEN`; respect rate limits.
+- Use `@vercel/sdk` (TypeScript) for typed API access.
+- Common endpoints: deployments, env vars, domains, projects.
+
+### Webhooks & Checks
+
+- Register webhooks for `deployment.created`, `deployment.succeeded`, etc.
+- Implement deployment checks (CI gates) via the Checks API.
+
+### Integrations & Marketplace
+
+- Install native integrations (e.g., observability, storage).
+- Build marketplace partner integrations with OAuth and webhooks.
+
+### MCP for Agents
+
+- Run Vercel MCP server locally or in CI for agent workflows.
+- Use for automated deployment queries, log retrieval, and config changes.
+
+### Image Optimization & OG Images
+
+- Use `next/image` for automatic format conversion and resizing.
+- Generate OG images on the fly with `@vercel/og` (ImageResponse).
+- Cache OG images appropriately.
+
+### Cron Jobs
+
+- Define cron schedules in `vercel.json` under `crons`.
+- Secure cron handler endpoints with `CRON_SECRET`.
+- Monitor cron execution logs in Vercel dashboard.
+
+### Monorepos
+
+- Configure `rootDirectory` per project for monorepo packages.
+- Use Turborepo + Vercel Remote Cache for fast incremental builds.
+
+### Microfrontends
+
+- Define app groups and routing in Vercel Microfrontends config.
+- Route per-path segments to independent Next.js apps.
+
+### Multi-Tenant Architecture
+
+- Use hostname-based routing in middleware for tenant resolution.
+- Scope environment variables and storage per tenant.
+- Combine with Edge Config for real-time tenant config.
+
+## Operating Checklist
+
+1. Audit and lock project configuration in `vercel.json`.
+2. Review and tighten RBAC roles; remove over-privileged members.
+3. Enforce 2FA for all team members; configure OIDC for CI.
+4. Validate REST API token scopes; rotate stale tokens.
+5. Test webhook delivery with replay; implement idempotent handlers.
+6. Verify cron endpoint security with `CRON_SECRET` validation.
+7. Validate monorepo build filtering and Turborepo cache hit rates.
+
+## Output Contract
+
+- `vercel.json` configuration with annotated sections
+- RBAC role matrix and access group definitions
+- Identity/SSO configuration steps and validation evidence
+- REST API and SDK integration patterns
+- Webhook handler implementation with idempotency
+- Architecture diagram for monorepo/microfrontend/multi-tenant setup
+- Residual risks and follow-up actions

package/Ai Agent Workflow/powers/vercel-routing/POWER.md

@@ -0,0 +1,82 @@
+````markdown
+---
+inclusion: manual
+name: vercel-routing
+description: "Vercel edge routing: middleware patterns, redirects/rewrites, Edge Config for real-time config without redeploys, Edge Config integrations, and Node.js migration paths."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0.0"
+  domain: vercel
+  triggers: vercel, routing, middleware, redirects, rewrites, edge config, edge config integrations, edge to node, a/b routing, geo routing, edge middleware
+  role: specialist
+  scope: implementation
+  output-format: checklist
+  related-skills: nextjs-developer, vercel-functions, vercel-caching, vercel-flags
+  consolidates: vercel-routing-middleware, vercel-redirects-rewrites, vercel-edge-config, vercel-edge-config-integrations, vercel-edge-to-node-migration
+---
+
+# Vercel Routing
+
+## Purpose
+
+Configure Vercel's edge routing layer with middleware patterns, redirect/rewrite rules, real-time Edge Config for runtime configuration, and migration paths away from the edge runtime.
+
+## When To Use
+
+- Writing Vercel Middleware for auth, geo-routing, A/B testing, or bot checks.
+- Configuring redirects and rewrites in `vercel.json` or Next.js config.
+- Using Edge Config for real-time feature toggling or config without redeploys.
+- Integrating Edge Config with third-party providers (LaunchDarkly, etc.).
+- Migrating edge-incompatible middleware to Node.js functions.
+
+## Domain Areas
+
+### Middleware
+
+- Author `middleware.ts` with `NextRequest`/`NextResponse` or Web APIs.
+- Apply auth checks, geo-redirects, A/B bucket assignment.
+- Use `matcher` config to scope execution precisely.
+- Mind cold start and bundle size constraints (1MB limit).
+
+### Redirects & Rewrites
+
+- Configure in `vercel.json` under `redirects` / `rewrites`.
+- Permanent (308) vs temporary (307) redirects.
+- Capture groups and dynamic path rewriting.
+- Header-based and query-based conditional rewrites.
+
+### Edge Config
+
+- Create and populate Edge Config stores via dashboard or CLI.
+- Read in middleware with `@vercel/edge-config` SDK.
+- Zero-redeploy config changes for feature flags and kill switches.
+
+### Edge Config Integrations
+
+- Connect Edge Config to third-party providers.
+- Sync external flag state into Edge Config automatically.
+
+### Edge-to-Node Migration
+
+- Identify middleware using Node.js-incompatible APIs.
+- Refactor to Node.js serverless functions or API routes.
+- Use `runtime: 'nodejs'` config override.
+
+## Operating Checklist
+
+1. Audit middleware bundle size and strip unnecessary dependencies.
+2. Validate matcher patterns cover only intended routes.
+3. Test redirect rules for cyclic redirect risk.
+4. Populate Edge Config with safe defaults before enabling reads.
+5. Document Edge Config keys and owners; restrict write access.
+6. Plan edge-to-node migration with regression test coverage.
+
+## Output Contract
+
+- Middleware implementation with matcher config
+- Redirect/rewrite rule set with conflict analysis
+- Edge Config schema, population scripts, and read integration
+- Edge-to-node migration plan with test strategy
+- Performance impact assessment (middleware execution time)
+````