[docs-scanner] Unclear repository activation requirement for Artifactory integration

[docker-agent]

File: content/manuals/scout/integrations/registry/artifactory.md

Issue

The Artifactory integration guide doesn't explain whether users need to activate repositories in Repository settings after integration, while the ACR and ECR guides in the same directory explicitly state this is required.

From acr.md:

Next, activate Docker Scout for the repositories that you want to analyze in Repository settings.

From ecr.md:

For Docker Scout to start analyzing images in the registry, you need to activate it for each repository in Repository settings.

From artifactory.md:
No mention of repository activation in Repository settings. The guide only states:

After the integration, Docker Scout automatically pulls and analyzes images that you push to the Artifactory registry.

Why this matters

A reader following the Artifactory integration guide and comparing it with the ACR or ECR guides would be confused about whether they need to perform the repository activation step. If activation is required for Artifactory (like ACR/ECR), the guide is missing a critical step. If it's not required because Artifactory uses a different integration method (docker scout watch), this difference should be explicitly stated to avoid confusion.

Suggested fix

If repository activation is required for Artifactory:

• Add a step after step 6 (or at the end of the integration steps) that explicitly instructs users to activate repositories in Repository settings, matching the guidance in acr.md and ecr.md.

If repository activation is NOT required for Artifactory:

• Add a note explaining that unlike cloud-native integrations (ACR, ECR), the Artifactory integration using docker scout watch doesn't require separate repository activation, and that images are automatically analyzed based on the watch configuration.

---

Found by nightly documentation quality scanner