Update dependabot and labeling automation docs

[vim-zz]

Update documentation with new dependabot auto-approve logic and rename

✨ PR Description

Purpose: Update documentation for dependabot automation and rename smart labeling section to accurately reflect its functionality.

Main changes:

• Renamed smart labeling section from "Claude Code Detection" to "Agent Coding Detection" for broader applicability
• Split dependabot automation documentation into separate "Minor Bump" and "Patch Bump" sections
• Removed unnecessary manifest version declaration from dependabot configuration example
• Added missing dependabot_bump template variable to the configuration example

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀}

[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 updates documentation for managed automation workflows with renamed sections and new configuration examples. The changes improve clarity in most areas, but there's a structural issue with YAML example placement.

1 issues detected:

🧾 Readability - The configuration line is placed without clear structural context, potentially confusing readers about proper YAML hierarchy.

Details: A YAML configuration line is added outside of clear structural context, making it ambiguous where this configuration should be placed in actual implementation. The line appears to be inserted at an inappropriate level in the documentation example.
File: docs/managed-mode.md (135-135)

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀}

[gitstream-cm]

🧾 Readability - Unclear Configuration Placement: Either properly nest the dependabot_bump configuration under an appropriate parent section (like automations) or clearly document where this configuration belongs in the overall YAML structure.

Suggested change

	dependabot_bump: {{ pr.description | checkDependabot | checkSemver }}
	automations:
	dependabot_bump:
	on:
	- pr_created
	if:
	- dependabot_bump: {{ pr.description | checkDependabot | checkSemver }}

[claude]

Code Review - PR #791: Update dependabot and labeling automation docs

✅ Overall Assessment

This is a well-structured documentation update that improves clarity and organization. The changes are focused and improve user understanding of the automation configurations.

📝 Code Quality & Best Practices

Strengths:

• Clear naming improvement: Changing "Claude Code Detection" to "Agent Coding Detection" better reflects the multi-agent nature of the automation
• Better organization: Splitting Dependabot automations into separate sections for minor vs patch bumps improves readability
• Consistent YAML structure: The automation configurations follow gitStream conventions properly

Suggestions:

• Consider adding a brief explanation of the difference between minor and patch version bumps for users unfamiliar with semantic versioning

🐛 Potential Issues

Minor concerns:

• The dependabot_bump variable definition appears twice (lines 135 and 156). While this works, it could be defined once at the document level to follow DRY principles
• Missing manifest: section in the second Dependabot automation block - while this may work in context, consistency would improve maintainability

⚡ Performance Considerations

• No performance impact - this is documentation only
• The automation logic itself is efficient with appropriate filtering conditions

🔒 Security Concerns

• No security issues identified
• The automation correctly validates Dependabot authorship before auto-approving
• Proper scoping to only minor/patch updates maintains security posture

🧪 Test Coverage

• Documentation changes don't require test coverage
• The YAML configurations follow established patterns that are presumably tested elsewhere in the system

💡 Recommendations

1. DRY improvement: Consider consolidating the dependabot_bump definition at document level
2. Consistency: Add manifest section to the patch bump automation or document why it's omitted
3. Documentation enhancement: Consider adding a note about semantic versioning for users unfamiliar with the minor/patch distinction

✨ Summary

This PR effectively improves the documentation structure and clarity. The changes align well with gitStream conventions and maintain security best practices. The split between minor and patch bump automations will help users better understand and configure their dependency management workflows.

Recommendation: ✅ Approve - Minor suggestions above are optional improvements that don't block merging.