refactor: rename Hono context variable from supabase to supabaseContext

Avoids naming clash with the supabase client inside SupabaseContext,
following Hono conventions for descriptive variable names (jwtPayload,
requestId, etc.).

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

Author: tomaspozo

src/adapters/hono/middleware.test.ts

@@ -4,7 +4,7 @@ import { describe, expect, it } from 'vitest'
 import type { SupabaseContext } from '../../types.js'
 import { supabase } from './middleware.js'
 
-type Env = { Variables: { supabase: SupabaseContext } }
+type Env = { Variables: { supabaseContext: SupabaseContext } }
 
 describe('hono supabase middleware', () => {
   const env = {
@@ -18,7 +18,7 @@ describe('hono supabase middleware', () => {
     const app = new Hono<Env>()
     app.use('*', supabase({ allow: 'always', env }))
     app.get('/', (c) => {
-      const ctx = c.get('supabase')
+      const ctx = c.get('supabaseContext')
       return c.json({
         authType: ctx.authType,
         hasSupabase: !!ctx.supabase,

src/adapters/hono/middleware.ts

@@ -6,13 +6,13 @@ import type { SupabaseContext, WithSupabaseConfig } from '../../types.js'
 
 export function supabase(config?: Omit<WithSupabaseConfig, 'cors'>) {
   return createMiddleware<{
-    Variables: { supabase: SupabaseContext }
+    Variables: { supabaseContext: SupabaseContext }
   }>(async (c, next) => {
     // Skip if a previous middleware already set the context.
     // This allows route-level overrides: a route can use supabase({ allow: 'secret' })
     // while the app-wide middleware uses supabase({ allow: 'user' }), without the
     // app-wide one overwriting the stricter context already established.
-    if (c.var.supabase) {
+    if (c.var.supabaseContext) {
       await next()
       return
     }
@@ -25,7 +25,7 @@ export function supabase(config?: Omit<WithSupabaseConfig, 'cors'>) {
       })
     }
 
-    c.set('supabase', ctx)
+    c.set('supabaseContext', ctx)
     await next()
   })
 }