Fresh jobs can be enqueued without trigger actor

[pilipilisbot]

Recent jobs can be created with trigger_actor = NULL, so the dashboard shows unknown actor for fresh queue entries.

Observed on the live DB after jobs #378-#383 were enqueued on 2026-05-25:

• #378 pilipilisbot/github-agent-bridge#35 sync_after_merge: trigger_actor = NULL
• #379 pilipilisbot/github-agent-bridge#33 open_issue: trigger_actor = NULL
• #380 pilipilisbot/github-agent-bridge#36 sync_after_merge: trigger_actor = NULL
• #381 gisce/webclient#3524 reply_comment: trigger_actor = NULL
• #382 pilipilisbot/github-agent-bridge#32 open_issue: trigger_actor = NULL
• #383 pilipilisbot/github-agent-bridge#34 sync_after_merge: trigger_actor = NULL

Diagnosis:

• The local service install is currently stale: the checkout is v0.18.1 / 23eb2b9, but the editable package reported by the service venv is still github-agent-bridge 0.17.0.
• This is not only an install drift issue. Current main still computes the trigger actor during enqueue only via trigger_actor_details_from_notification(n), which depends on the GitHub notification From: display name.
• GitHub event notifications can arrive as GitHub <notifications@github.com> with useful context only in the URL/body, especially #event-... issue/PR event notifications. In that case the enqueue path stores NULL instead of falling back to GitHub API context lookup.
• Manual checks show github_actor_details_for_context(...) can resolve actors for the stored contexts, for example issue/comment contexts and some PR/issue contexts. The problem is that this resolution is only available via backfill, not during normal enqueue.

Expected behavior:

New jobs should store trigger_actor and trigger_actor_avatar_url at enqueue time whenever the actor can be resolved from either:

1. the GitHub notification sender display name, or
2. the parsed GitHub context via GitHub API fallback.

Suggested fix:

• Add an enqueue-time fallback in JobQueue.enqueue: if trigger_actor_details_from_notification(n) returns None, try resolving actor details from the parsed GitHubContext.
• Avoid making this fallback mandatory for shadow/dry-run or unauthenticated test paths; failures should leave actor null rather than blocking enqueue.
• Add tests for notifications with from_addr="GitHub <notifications@github.com>" and a resolvable issue/comment URL.
• Consider parsing/storing #event-... IDs separately if we need the event actor instead of issue/PR author for merge/assignment events.
• Operationally, add a deployment/version check so the service venv cannot silently lag behind the checked-out release.

Acceptance criteria:

• A new actionable notification whose From: is GitHub <notifications@github.com> gets a non-null actor when GitHub API context can resolve it.
• Existing From: ecarreras <notifications@github.com> behavior stays unchanged.
• backfill-trigger-actors remains useful for historical rows but is not required for fresh jobs.

[pilipilisbot]

Opened PR #38 for this: #38

What changed in be15b2b:

• JobQueue.enqueue now uses shared actor logic that first trusts the GitHub notification sender login, then falls back to the parsed GitHubContext via the existing GitHub API resolver.
• The fallback is fail-open: missing gh, API errors, or unresolved context leave actor fields null instead of blocking enqueue.
• gab monitor can now alert on install drift when GITHUB_AGENT_BRIDGE_EXPECTED_VERSION is set.

Validation: .venv/bin/python -m pytest -q passed with 148 tests, git diff --check passed locally, and GitHub Actions passed for Python 3.11 and 3.12.

[pilipilisbot]

PR #38 ja està fusionat i he fet el sync post-merge del checkout local.

Resum verificat:

• PR fix: resolve trigger actors during enqueue #38 fusionat a main amb merge commit 2bd3093.
• main va publicar v0.18.3 a 5bff57e.
• GitHub Actions post-merge passen: tests run 26396118834 i release run 26396118833.
• El checkout local /home/openclaw/.openclaw/workspace/github/github-agent-bridge queda net a main / v0.18.3.
• He eliminat la branca local obsoleta fix-enqueue-trigger-actor-fallback; la remota ja havia estat esborrada per GitHub.