What

Treat Sentry-authored GitHub content as internal-equivalent across nexu-pal workflows, and fix the actor match to use the real GitHub login sentry[bot].

Why

Recent Sentry issues were still receiving needs-information and Feishu notifications because the automation matched app/sentry, while the real GitHub actor is sentry[bot]. Sentry content should be handled like internal authors everywhere.

How

• add a shared helper for internal-equivalent author detection
• switch nexu-pal triage to detect sentry[bot] instead of app/sentry
• skip Feishu notifications for Sentry-authored issues/discussions/PRs the same way we skip internal authors
• update tests and nexu-pal spec notes to reflect the real actor and behavior

Affected areas

• Desktop app (Electron shell)
• Controller (backend / API)
• Web dashboard (React UI)
• OpenClaw runtime
• Skills
• Shared schemas / packages
• Build / CI / Tooling

Checklist

• pnpm typecheck passes
• pnpm lint passes
• pnpm test passes
• pnpm generate-types run (if API routes/schemas changed)
• No credentials or tokens in code or logs
• No any types introduced (use unknown with narrowing)

Notes for reviewers

Repo-wide checks still have pre-existing unrelated failures/warnings:

• pnpm lint reports existing warnings in tests/desktop/launchd-startup-scenarios.test.ts
• pnpm test still has an existing failure in tests/desktop/skill-dir-watcher-workspace.test.ts