docs: synchronizing help from snyk/user-docs

[team-cli-bot]

Automatic PR controlled by GitHub Action

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

	Warnings
⚠️	Please make changes to snyk help text in Gitbook. Changes will be automatically synchronised to Snyk CLI as a scheduled PR. For more information, see: help/README.md.

Generated by 🚫 dangerJS against 17fa676

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Broken Link 🟠 [major] The documentation for the snyk monitor command has been updated with a broken link for Runtime Resolution Scanning (pointing to /broken/pages/PvXOZ1NqIqQz46Zk799z). This placeholder path indicates a failure in the documentation synchronization or generation process. Since this flag is described as "Required" for .NET Runtime Resolution Scanning, the broken link prevents users from accessing essential setup instructions. Required. You must use this option when you test .NET projects using [Runtime Resolution Scanning](/broken/pages/PvXOZ1NqIqQz46Zk799z) Documentation Inconsistency 🟠 [major] Documentation for the --dotnet-runtime-resolution flag has been entirely removed from the snyk test command help file, yet it remains present and was even updated with a new (albeit broken) link in the snyk monitor command help file (see monitor.md:334). This discrepancy is confusing for users, as it is unclear if the flag is still supported across different CLI commands. If the flag has been deprecated or its functionality integrated into default behavior, it should be removed from all relevant command documentation to ensure consistency. ### `--dotnet-target-framework`

📚 Repository Context Analyzed This review considered 8 relevant code sections from 5 files (average relevance: 0.93) help/cli-commands/test.md (lines 301-400) help/cli-commands/container-sbom.md (2 segments, lines 1-100) help/cli-commands/monitor.md (3 segments, lines 301-400) help/cli-commands/redteam.md (lines 1-100) help/cli-commands/container.md (lines 1-16)