Update execution model trigger conditions

[vim-zz]

Standardize condition descriptions to consistently reference context usage rather than specific properties. Move GitHub icons to the end of trigger names for better readability.

✨ PR Description

Purpose: Update PR trigger condition descriptions to use consistent "pr context" terminology and improve clarity of event handling rules.

Main changes:

• Standardized condition descriptions to use "when pr context is used in .cm" format
• Updated approval trigger conditions to include specific action dependencies
• Fixed text formatting for GitHub-specific events for better visual consistency

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how}

[orca-security-us]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[gitstream-cm]

✨ PR Review

The PR standardizes trigger condition descriptions and improves formatting, but introduces a significant loss of precision in the technical documentation that could mislead users.

1 issues detected:

🧾 Readability - Generic condition descriptions lose important specificity about trigger activation requirements.

Details: The standardization from specific property references (pr.comment, pr.description, pr.label, pr.title) to generic "pr context is used in .cm" removes critical technical details about exactly which context properties trigger these events. This could mislead users about when their automations will actually execute.
File: docs/execution-model.md

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Review using Guidelines Learn how}

Review dismissed