server.ts swallows cookie-write failures on a safety condition (middleware) that does not exist in terra

src/lib/supabase/server.ts setAll wraps cookie writes in catch {} justified by the comment "safe to ignore when middleware refreshes the session". Terra has NO middleware: coder-terra-cc verified with a must-fail control - find over the repo excluding node_modules for middleware.* any extension returns zero, while the same finder returns layout.tsx, so the finder works; venus by contrast ships one. The swallow may still be structurally necessary (Next.js Server Components cannot set cookies at all, which is why the upstream Supabase pattern has the try/catch), so the defect is NOT simply "remove the catch" - it is that the stated safety condition names a component that does not exist, leaving open what actually refreshes the session on the Server-Component path, if anything. Shape the answer to that question before any diff. Not the cause of the 2026-08-14 Puia sign-in failures: the callback is a Route Handler where setAll works. Found by coder-terra-cc while diagnosing TERRA-18.