Customer Messaging has no backend: /api/messaging/pending always returns an empty inbox

The Customer Messaging dashboard at /messaging renders from /api/messaging/pending, which is hardcoded to return nothing:

/**
 * Note: There is no Prisma model for pending messages yet (Slack/Teams
 * messages are handled by their respective bots). This endpoint returns
 * an empty list until a messaging model is added to the schema.
 */
export async function GET() {
    ...
    return NextResponse.json({ messages: [], count: 0 });
}

Why it matters

The page is in the shipped navigation and always shows an empty inbox. To a user that reads as "no pending customer messages", not "this feature has no backend" — the UI states something false rather than being visibly unbuilt.

Fix

Either add the PendingMessage Prisma model and have the Slack/Teams bots write to it, or hide the route until it has a backend. The interim option — an explicit "not yet available" empty state — is cheap and stops the page from lying.

Start at /api/messaging/pending and /messaging; inspect the current empty response and the shipped navigation entry. Decide with maintainers whether to add a PendingMessage Prisma model and bot writes or use an explicit not-yet-available state. Done means the inbox no longer presents an unsupported empty inbox.