orca/mobile/src/notifications/push-payload.ts

// Why two shapes: APNs nests Orca's fields under `orca` beside `aps`, while FCM
// carries them flat in `data` as strings. Both reach JS as the notification's
// `content.data`, so the reader accepts either and coerces the numeric fields.
export type OrcaPushPayload = {
  readonly kind?: 'alert' | 'dismiss'
  readonly hostFingerprint: string
  readonly notificationId?: string
  readonly notificationSeq?: number
  readonly notificationEpoch?: string
  readonly paneKey?: string
  readonly worktreeId?: string
}

function readString(value: unknown): string | undefined {
  return typeof value === 'string' && value.length > 0 ? value : undefined
}

function readSeq(value: unknown): number | undefined {
  const raw = typeof value === 'number' ? value : Number(readString(value))
  return Number.isFinite(raw) ? raw : undefined
}

export function readOrcaPushPayload(data: unknown): OrcaPushPayload | null {
  if (!data || typeof data !== 'object') {
    return null
  }
  const nested = (data as { orca?: unknown }).orca
  const record = (nested && typeof nested === 'object' ? nested : data) as Record<string, unknown>
  // The fingerprint is what makes this a gateway push; locally scheduled data never has one.
  const hostFingerprint = readString(record.hostFingerprint)
  if (!hostFingerprint) {
    return null
  }
  return {
    hostFingerprint,
    ...(record.kind === 'dismiss' || record.kind === 'alert' ? { kind: record.kind } : {}),
    notificationId: readString(record.notificationId),
    notificationSeq: readSeq(record.notificationSeq),
    notificationEpoch: readString(record.notificationEpoch),
    paneKey: readString(record.paneKey),
    worktreeId: readString(record.worktreeId)
  }
}