Prateek e0f4a9dc27 fix: prevent merged PRs from showing "Merge conflicts" status ... GitHub returns `mergeable: null` for merged/closed PRs. The SCM plugin was misinterpreting this as unknown/problematic status, leading to false "Merge conflicts" warnings in the dashboard. Fixed in two layers: 1. SCM plugin: Check PR state first in getMergeability(). Return clean result immediately for merged/closed PRs without querying mergeable. 2. Dashboard: Skip merge conflict display for non-open PRs in SessionDetail component. SessionCard already had protection via early return in getAlerts(). Closes: bug described in task description Tests: Added tests for merged/closed PR cases, all 54 tests passing Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>		2026-02-16 08:56:43 +05:30
..
agent-orchestrator	feat: publish to npm under @composio scope (#32)	2026-02-15 04:28:57 +05:30
cli	fix: unset CLAUDECODE in spawned sessions to prevent nested session errors	2026-02-16 05:51:05 +05:30
core	refactor: replace magic strings with constants for status enums (#64)	2026-02-16 08:53:17 +05:30
integration-tests	feat: wire up live activity detection for agent sessions (#45)	2026-02-16 05:31:02 +05:30
plugins	fix: prevent merged PRs from showing "Merge conflicts" status	2026-02-16 08:56:43 +05:30
web	fix: prevent merged PRs from showing "Merge conflicts" status	2026-02-16 08:56:43 +05:30