feat(mentions): mentioning a person finally tells them

[catomean]

The mention notification type has existed since the notification config was written — copy, an icon case in NotificationItem.tsx, a place in the type union. Nothing has ever created one.

You could write @alice and she would never know. That makes the mention syntax decorative rather than social, and it has been that way the whole time.

Widening the pipeline instead of building a second one

Fixing it needs exactly what the Cat already uses: notice a mention on a post, resolve it properly, act, retry on failure. So the existing pipeline widens by one word.

before	after
cat_mention_queue	mention_queue
claim_cat_mentions	claim_mentions
prefilter ~* '@cat'	prefilter '@'

The Cat is one mentioned account among many, and the name should say so.

It is still a prefilter and still deliberately dumb. domain/mentions/parse.ts + services/mentions/resolve.ts remain the single authority on what counts as a mention. The worker discards what the trigger over-selects and marks it done, not failed — retrying a post that named nobody three times and then logging an error is noise about nothing.

One resolve now produces both outcomes: reply if the Cat was named, and tell the people who were. Two features, one query, one definition of what a mention is.

Mentions in private messages are deliberately not notified

This is a privacy decision, not an omission:

• a participant already gets a new_message notification, so a second one for being named is noise
• a non-participant must never be told at all — the notification would disclose that a conversation exists, who is in it, and through the preview part of what was said

Typing a friend's handle in a private chat is not publishing to them.

Details that decide whether it's welcome or noise

• quotes the post rather than sending a bare "you were mentioned"
• skips the author naming themselves
• skips the Cat — it has no inbox
• never throws: the post is already written by then, and losing a notification must not cost the Cat's reply

Verification

• npm run verify — exit 0 (2384 tests)
• 6 new notifier tests + 1 new worker test covering a post that names only people
• migration dry-run on production inside BEGIN … ROLLBACK — table, function and trigger present in-transaction, old table restored after rollback

🤖 Generated with Claude Code