On Vercel Hobby, a GET request to a dynamically rendered Next.js route /auth/confirm was unavailable in Runtime Logs when inspected within one hour. Deployment Protection was enabled. Under what conditions should this GET produce a searchable Runtime Logs record with Search Params? Which existing request-level surface can establish whether query parameter values are visible, masked, or omitted without changing configuration? I am not asking about retention length. I need clarification on request/query visibility and redaction behavior for Hobby. Please identify:

• whether Search Params should be available for this type of request,
• whether Deployment Protection affects whether the request appears,
• and whether any paid feature changes query-value visibility rather than merely extending retention.