Every session has a paper trail the client can read

When I finish a mixing session, a software sprint call, or an accessibility audit walkthrough, I write session notes in the admin panel. Those notes appear in the client's portal immediately. The SessionCard component renders each session with four pieces of context — the date formatted in UK English using Intl.DateTimeFormat, the duration in minutes, the comment count, and a link to the parent project. The notes themselves are line-clamped to three lines on the session list so every card has a consistent height, but the full text is available when you tap through to the project. The date uses a semantic time element with an ISO datetime attribute so machines can parse it and humans can read it. The comment count appears with proper pluralisation — 1 comment or 3 comments — using a single ternary. If there are no comments, that metadata disappears entirely rather than showing zero comments. The project name links back to the full project view using the accent colour so it visually connects to the navigation. The card itself is a glass container with the same border and blur treatment as every other portal component. One component handles every session type. A ninety-minute mixing session and a thirty-minute software standup use the same card, the same date format, the same comment indicator. The client has a complete record of every interaction without me sending a single follow-up email.