fix: allow claims without appointment + support post/core multi-tooth input

- Make appointmentId nullable/optional in Prisma Zod schema via @zod rich
  comment so claims can be submitted without an existing appointment
- Convert undefined appointmentId to null in all claim form handlers and
  the backend claim creation endpoint
- Add AI classifier rule for expanding one procedure across multiple
  comma-separated tooth numbers (e.g. "post/core on #23, 24, 25, 26")
- Add "post/core" (slash) alias to CDT lookup maps

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

packages/db/shared/schemas/results/ClaimAggregateResult.schema.js

@@ -53,6 +53,7 @@ exports.ClaimAggregateResultSchema = z.object({ _count: z.object({
         updatedAt: z.number(),
         status: z.number(),
         claimNumber: z.number(),
+        preAuthNumber: z.number(),
         npiProviderId: z.number(),
         patient: z.number(),
         appointment: z.number(),
@@ -94,6 +95,7 @@ exports.ClaimAggregateResultSchema = z.object({ _count: z.object({
         createdAt: z.date().nullable(),
         updatedAt: z.date().nullable(),
         claimNumber: z.string().nullable(),
+        preAuthNumber: z.string().nullable(),
         npiProviderId: z.number().int().nullable()
     }).nullable().optional(),
     _max: z.object({
@@ -111,5 +113,6 @@ exports.ClaimAggregateResultSchema = z.object({ _count: z.object({
         createdAt: z.date().nullable(),
         updatedAt: z.date().nullable(),
         claimNumber: z.string().nullable(),
+        preAuthNumber: z.string().nullable(),
         npiProviderId: z.number().int().nullable()
     }).nullable().optional() });