Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/web/app/`(ee)/api/partners/applications/route.ts:
- Line 59: The createdAt field for partner applications is taken from
programEnrollment (createdAt: programEnrollment.createdAt) which differs from
the webhook convention (application.createdAt) and causes inconsistent ordering;
update the listing code in route.ts to use application.createdAt for the
createdAt property and change the query/orderBy to order by
application.createdAt descending so it matches partnerApplicationWebhookSchema /
partnerApplicationSchema and the webhook handler
(apps/web/lib/partners/complete-program-applications.ts).
- Around line 44-71: The mapped "result" can contain nulls due to the `if
(!application) return null` branch inside `applications.map(...)`, which will
make `z.array(partnerApplicationSchema).parse(result)` throw; to fix, either
remove the unreachable null-return branch in the `applications.map` callback
(remove the `if (!application) ...` and assume `application` exists) or ensure
you filter out nulls before parsing (e.g., filter the `result` from
`applications.map` to remove null/undefined entries) so that the value passed to
`NextResponse.json(z.array(partnerApplicationSchema).parse(...))` contains only
valid partner application objects; update code paths that reference
`applications.map`, `formatApplicationFormData`, `polyfillSocialMediaFields`,
and the final `NextResponse.json(...)` call accordingly.

---

Nitpick comments:
In `@apps/web/lib/zod/schemas/program-application.ts`:
- Around line 50-54: Replace the redundant z.object({}).extend(...) pattern by
building the schema directly from the pagination shape: call
getPaginationQuerySchema({ pageSize: PARTNERS_MAX_PAGE_SIZE }) and pass its
returned shape into z.object to create getPartnerApplicationsQuerySchema
(referencing getPartnerApplicationsQuerySchema, getPaginationQuerySchema, and
PARTNERS_MAX_PAGE_SIZE).

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/web/app/`(ee)/api/partners/applications/route.ts:
- Around line 16-41: The pagination schema lets non-integer numbers through,
causing Prisma take/skip to receive floats; update the Zod schema that defines
page and pageSize (the getPaginationQuerySchema used by
getPartnerApplicationsQuerySchema) to add .int() to both page and pageSize so
only integer values pass validation before hitting
prisma.programEnrollment.findMany (which uses take and skip).

---

Duplicate comments:
In `@apps/web/app/`(ee)/api/partners/applications/route.ts:
- Around line 37-38: The pagination sort uses programEnrollment.createdAt but
the response exposes application.createdAt, so update the query in route handler
to order by the application's createdAt instead of programEnrollment.createdAt
(or add a secondary orderBy on application.createdAt) so that the returned list
is ordered by the same timestamp shown to clients; locate the query referencing
orderBy and programEnrollment.createdAt in
apps/web/app/(ee)/api/partners/applications/route.ts (the block constructing the
DB query and the orderBy clause) and replace or augment it to use
application.createdAt as the primary sort key.