cursor-triage-issue-reports
Native Codex execution boundary
Use only an explicitly configured, authorized Benny workflow. Source distribution does not install or activate it. Resolve actual native connector schemas, permissions and control capabilities; missing event delivery remains incomplete and is never silently converted to scheduled polling. No source-repository or cache path is needed at runtime. Read configuration from the project-owned path supplied by setup.
Normalize a new top-level trigger once: source_channel_id, message_ts (or upstream ts only when supplied aliases agree), and empty thread_ts. Reject conflicting timestamps and child events before any external write. Freeze the root as SOURCE_THREAD_TS; subsequent reads/posts revalidate that original parent. Local supplied-event fixtures cannot prove the live parent or external writes.
Triage issue reports
Classify one Slack report and post one useful verdict in its source thread. Create a tracker issue only for a clear, new bug. Do not reproduce or fix it here.
Load the external Benny configuration supplied by the automation. If the config is missing, malformed, or incomplete, stop without posting or writing to the tracker.