An event is not a message, and a notice is not either (GRYT-896)

[sivert-io]

Client half. Server half is Gryt-chat/server#130 — merge that one first, or this listens for an event nothing sends.

Two changes, one mistake behind both: everything a server said became a chat message shaped like somebody talking.

Events become one quiet row

A join filled a whole message slot — the word "System" where a nickname goes, in the same weight and size, a 51px avatar column held empty so the absence read as a missing avatar rather than a different kind of thing, a timestamp on its own line, plus reactions and a hover toolbar. You could react to somebody joining. Two people arriving cost two full rows.

Now: the avatar column carries a small arrow — in for joined, out for left — so the space is doing something and the row is unmistakably not somebody talking. No name line, because there is no author. The time trails the text. One 34px line.

The left edge every message shares stays where it is. A centred rule would say "not a message" more loudly and break that edge, and a channel where people come and go is exactly where a run of rules chops the conversation into fragments.

Which arrow is read off the text rather than a new column — the server sends these as ordinary message rows and two verbs are not worth a migration. Anything unrecognised draws the "in" arrow, the right guess for anything that is not a departure.

A directed notice is not in chat at all

The server sends { kind, version } and this side owns every word. That is the security property: text a server chose, in app furniture, addressed to one person, is a phishing message. Taking the text away is the only version that cannot be turned into one.

parseServerNotice re-checks the shape rather than trusting it. The server validating its own output guards against a bug in the server; this guards against the server, which is somebody else's machine and need not be running our code. Unknown kinds, malformed values and smuggled extra fields are dropped in silence — a malformed notice is a server bug or a server trying something, and neither is worth interrupting somebody with.

The panel sits below the channel header, above the messages, and says "From <server>, only to you" in the frame. Inside the server's area, never in Gryt's own chrome — anything painted there should only ever be Gryt. Its two links are constants in the file; a server cannot reach them.

Dismissal is per device and permanent, and the server is not told. A server learning which of its notices somebody has silenced is the beginning of working around it.

Tests

check-server-notice.mjs, wired into CI. Five mutations, each caught:

mutation	caught
version pattern widened	✓
payload spread through the parse, carrying extra fields	✓
the switch's default: return null removed	✓
panel reads a URL off the notice	✓
panel's own link points at a host we do not own	✓

The last two are source checks. A panel that interpolated a notice field into an href would typecheck and look reasonable in review.

Verified against a running server

Real emit, real listener, real render:

• "From Rig, only to you", the title, the version interpolated into client-owned copy, the download button
• three event rows at 34px each, @name joined the server 23:41 on one line, no "System" anywhere

Two things the rig caught that nothing else would

• chatView became a fragment, and both places that render it drop it into a flex row — so the chat stopped being the thing that grows and collapsed to a column one character wide. It is a filling flex column now.
• The timestamp dropped to its own line, because MarkdownRenderer emits a block. A second line for four words is the thing this treatment exists to stop. Baseline-aligned flex row instead.

tsc -b and eslint clean.

🤖 Generated with Claude Code