notify-bridge: let a gate supply its own notification headline and summary

[m4ttheweric]

Gate notifications read {label} / {question} today, and on a respond gate the first question is a file:line, so the banner ends up full of paths. This lets the thing that opens a gate hand over its own friendlier copy.

• {headline} and {summary} in an rt.notify.eventBridges template now fall back to meta.headline / meta.summary when the event payload has no field of that name
• without those they fall back to label / the first question label, so a rule can switch to the new fields before every opener sets them
• a payload's own headline / summary still wins, so the herd-watchdog rule works as before
• the registry description for the setting documents the new fields

The board side (sets the meta copy, switches its rule, and gives triage notifications a click target) is a separate PR in the apps repo.

Tests: lib/__tests__/notify-bridge.test.ts 46/46, rt-client settings suites green, tsc clean.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 3 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available. Your 85 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: b7ab59d0-d2a1-4d18-bbf8-d8bbb96cf3b0

📥 Commits

Reviewing files that changed from the base of the PR and between caad15b and e053ba5.

📒 Files selected for processing (3)

• lib/__tests__/notify-bridge.test.ts
• lib/notify-bridge.ts
• packages/rt-client/src/settings/registry-defs.ts

---

_{Comment @coderabbitai help to get the list of available commands.}