Notification log for triggered rule events

[bracyw]

Changes

Captures rule_notify socket events on the frontend and surfaces them across the nav, Rules page, and a dedicated log page — all backed by a single signal-based NotificationLogService (session-only, 500-entry cap).

• NotificationLogService accumulates notifications with unread tracking, per-entry dismiss, and clear-all; public methods documented with JSDoc
• Nav bar bell icon with popover dropdown showing the 10 most recent entries and an unread badge count
• Collapsible notification stream rail on the Rules page (always expanded on mobile)
• Red "View Log" button on the Rules page navigates to the full log
• /notification-log page with a scrollable PrimeNG table (Rule ID, Topic, Values, Time, per-row dismiss, Clear All)
• Shared NotificationListComponent renders both the nav popover and Rules page stream rail from one code path
• Socket connection sends clientId query param (persisted in localStorage) for rule subscription identity
• Removed accidentally committed .claude/settings.json symlink and added .claude/ to .gitignore

Notes

• Includes the 535-rules-table branch merge for integration testing — those changes will land via their own PR
• rule_notify payload arrives as a pre-parsed object from socketioxide, unlike data/faults/timers which arrive as JSON strings, so the handler accepts RuleNotification directly instead of calling JSON.parse
• Signal updates from socket callbacks are wrapped in NgZone.run() to ensure change detection runs
• No toast popup — notifications surface only via the bell badge, stream rail, and log page

Test Cases

• Receiving a rule_notify socket event adds a notification to the nav popover, Rules stream rail, and log page
• Badge count increments per event and clears when the dropdown opens
• Individual dismiss removes only that entry; Clear All empties everything
• Empty state renders correctly when no notifications exist
• Navigation between pages preserves the log within a session
• Log is capped at 500 entries — oldest are dropped
• View Log button on Rules page navigates to /notification-log
• Stream rail toggles open/closed on desktop; always visible on mobile

Screenshots

screenshot pending

Checklist

• All commits are tagged with the ticket number
• No linting errors / newline at end of file warnings
• All code follows repository-configured prettier formatting
• No merge conflicts
• All checks passing
• Assign the PR to yourself
• PR is linked to the ticket
• Screenshots of UI changes (see Screenshots section)
• Request reviewers & ping on Slack

Closes #544

[bracyw]

Claude folder should be ignored

[bracyw]

This should be made it's own component and abstracted to be able to be used again.

[bracyw]

We should create another ticket to generalize the Notification Center to have different sections and be customizable.

[bracyw]

We should use a primeng component for this if possible. Oriented towards notifications or data of this type.

[bracyw]

Review if this is needed yet and add docs on how it is currently used