File a person under the name this event gave them

[EllAchE]

sbek CNT-S3, run 2026-08-17T05-46-05 (major):

Speaker attribution is wrong throughout the content surfaces. A file uploaded and a comment posted while authenticated as Priya Raman (vitruvius@example.com) render under the name "Marcus Vitruvius Pollio" on the file detail thread, in the version list, and in the organizer files library speaker column. The same misattribution appears on three submission rows in the final submissions grid. An organizer reading a comment thread or a file library cannot tell which speaker produced which artefact, which defeats the purpose of per-speaker deliverable tracking.

What was actually happening

There are two names for one person, and they are both correct. participant.display_name is what this event calls them; user.name is the account. Renaming a speaker for one conference writes the first and deliberately leaves the second alone — that is the point of a per-event name.

Every surface named in the finding read the account. lib/services/content.ts already resolved this properly (displayName ?? userName ?? email); the files library, the version history, the comment thread and the submissions grid did not.

The fix

eventPersonName in lib/person-name.ts is now the single place that decides the precedence, so the surfaces cannot drift apart again.

• lib/services/files.ts — the file index carries ownerDisplayName alongside the account name; both uploader lookups go through a shared eventPeople join.
• listFileComments re-resolves the author from author_user_id at read time. file_comment.author_name is written at post time, so comments already posted carry the stale string in the row; re-resolving fixes them without a backfill. The stored copy stays as the fallback for an author whose account is gone, so deleting an account does not blank the thread it posted in.
• lib/services/review.ts — the submissions grid, the reviewer queue and the submission detail all prefer the event's name for the submitter.

The joins are left, not inner: an organizer who uploaded on a speaker's behalf may hold their role through membership and have no participant row, and dropping their name off the version history would be a worse answer than their account name. participant_event_user is unique on (event_id, user_id), so nothing fans out.

Tests

lib/event-person-name.test.ts, 10 cases: the event's name beats the account; whitespace in either is not a name; the address is the last resort; commentAuthorName re-resolves a comment posted before a rename, and keeps the stored name for an author who no longer resolves or was never recorded.

lib/services/file-index.test.ts gains a case asserting a renamed speaker's headshot is filed under the event's name in both the owner and uploader columns.

lint, typecheck, test (2044 in 190 files), build, docs:openapi, docs:mcp all clean.

Not merged and not deployed.