Enable Next.js to execute auth middleware by adding src/middleware.ts entrypoint

[Copilot]

The unresolved review comment identified that authentication middleware was never executed because the implementation lived in src/proxy.ts, which Next.js does not treat as middleware. This PR wires the existing logic into the framework-recognized middleware entrypoint without changing behavior inside the auth flow.

• Problem addressed

  • Next.js only loads middleware from middleware.ts or src/middleware.ts; src/proxy.ts was ignored, so config.matcher and auth redirects were effectively inactive.

• Minimal fix

  • Added src/middleware.ts to re-export the existing middleware function and matcher config from src/proxy.ts.
  • No logic changes were made to route matching, Supabase auth checks, or redirect rules.

• Implementation

  // src/middleware.ts
  export { proxy as middleware, config } from "./proxy";

[Copilot]

Pull request overview

This PR wires Next.js’ middleware entrypoint (src/middleware.ts) to the existing auth-aware proxy logic so that the authentication/redirect behavior implemented in src/proxy.ts actually executes at runtime.

Changes:

• Add src/middleware.ts that re-exports proxy as the Next.js middleware function.
• Re-export the existing config.matcher so route matching continues to be controlled from the proxy module.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.