[comp] Production Deploy

[github-actions]

This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
app (staging)	Building		Mar 1, 2026 9:57pm
portal (staging)	Building		Mar 1, 2026 9:57pm

[cursor]

PR Summary

Medium Risk
Changes device registration behavior when serial numbers collide across members, which can affect device identity/deduplication and data integrity within an org. UI also masks fallback serials, reducing visibility into the underlying identifier used.

Overview
Device registration no longer hard-fails when a serial number is already registered to a different member in the same org. Instead, the API generates (or reuses) a unique fallback:<originalSerial>:<uuid> serial for that member/hostname and returns the created/updated device.

The device details UI now detects fallback: serials and displays “Generic serial number” instead of the raw fallback value.

^{Written by Cursor Bugbot for commit 5e6a5ca. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Fallback serial lookup has prefix collision risk

Low Severity

The startsWith query fallback:${serialNumber}: can match fallback records for a different original serial when one serial is a string prefix of another up to a colon. For instance, if a member already has a fallback device for serial ABC:DEF (stored as fallback:ABC:DEF:<uuid>), a new registration with serial ABC would search with startsWith: 'fallback:ABC:' and incorrectly match that record, potentially overwriting it with unrelated device data.