resolving-merge-conflicts

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (high risk: 0.70). The workflow requires reading git history/commit messages and PRs/issues/tickets for the merge, which are typically outsider-authored free text (e.g., PR/issue discussion bodies) that can be ingested into the agent’s LLM context via the git/PR/issue lookup steps at runtime.