fix(scripts): add grouped link-lang console diagnostics and failure summary

[AhmedMustafa249]

Pull Request

Description

• print per-file and per-issue link-lang findings in terminal output
• add workflow JSON-based failure details while preserving exit behavior
• extend Pester assertions for issue and no-issue output paths

Related Issue(s)

Fixes #629

Type of Change

Select all that apply:

Code & Documentation:

• Bug fix (non-breaking change fixing an issue)
• New feature (non-breaking change adding functionality)
• Breaking change (fix or feature causing existing functionality to change)
• Documentation update

Infrastructure & Configuration:

• GitHub Actions workflow
• Linting configuration (markdown, PowerShell, etc.)
• Security configuration
• DevContainer configuration
• Dependency update

Other:

• Script/automation (.ps1, .sh, .py)
• Other (please describe):

Testing

• npm run lint:links (with planted language links in markdown files): Returns console output with details about the affected files, line numbers and URL information

• Test run shows:

🔍 Checking for URLs with language paths...
Found 4 URLs with 'en-us' language paths

📄 .github/CUSTOM-AGENTS.md
  ⚠️ Line 430: https://docs.microsoft.com/en-us/azure
📄 .github/PULL_REQUEST_TEMPLATE.md
  ⚠️ Line 43: https://docs.microsoft.com/en-us/azure
📄 CODE_OF_CONDUCT.md
  ⚠️ Line 28: https://docs.microsoft.com/en-us/azure
📄 SECURITY.md
  ⚠️ Line 106: https://docs.microsoft.com/en-us/azure
WARNING: WARNING [.github/CUSTOM-AGENTS.md:430] URL contains language path: https://docs.microsoft.com/en-us/azure
WARNING: WARNING [.github/PULL_REQUEST_TEMPLATE.md:43] URL contains language path: https://docs.microsoft.com/en-us/azure
WARNING: WARNING [CODE_OF_CONDUCT.md:28] URL contains language path: https://docs.microsoft.com/en-us/azure
WARNING: WARNING [SECURITY.md:106] URL contains language path: https://docs.microsoft.com/en-us/azure
❌ Link language check failed with 4 issue(s) in 4 file(s).

Checklist

Required Checks

• Documentation is updated (if applicable)
• Files follow existing naming conventions
• Changes are backwards compatible (if applicable)
• Tests added for new functionality (if applicable)

Required Automated Checks

The following validation commands must pass before merging:

• Markdown linting: npm run lint:md
• Spell checking: npm run spell-check
• Frontmatter validation: npm run lint:frontmatter
• Skill structure validation: npm run validate:skills
• Link validation: npm run lint:md-links
• PowerShell analysis: npm run lint:ps

Security Considerations

• This PR does not contain any sensitive or NDA information
• Any new dependencies have been reviewed for security issues
• Security-related scripts follow the principle of least privilege

[Copilot]

Pull request overview

This PR adds per-issue console diagnostics to the link-lang check script and enhances the workflow's failure step to display detailed violation information. Previously, when the link-lang check failed in GitHub Actions, contributors only saw a count summary with no details about which files, lines, or URLs were problematic. This change brings the link-lang check output in line with other linting scripts like PSScriptAnalyzer by adding grouped, per-file console output.

Changes:

• Added grouped per-file and per-issue console output to Invoke-LinkLanguageCheck.ps1 using Write-Host calls
• Enhanced the workflow's failure step to parse and display JSON results with file, line, and URL details
• Extended Pester tests to verify console output for both issue-found and no-issue code paths

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
scripts/linting/Invoke-LinkLanguageCheck.ps1	Added grouped Write-Host output showing file names and individual violations, following the PSScriptAnalyzer pattern; moved $uniqueFiles calculation earlier for reuse in JSON output
.github/workflows/link-lang-check.yml	Replaced generic failure message with JSON-based detailed output showing per-issue file/line/URL information, with defensive fallbacks for malformed data
scripts/tests/linting/Invoke-LinkLanguageCheck.Tests.ps1	Added Write-Host mock capturing and assertions for both success and failure paths, verifying per-file and per-issue console output

[katriendg]

Thank you @AhmedMustafa249 you are on fire! I'm adding Copilot as a first pass reviewer to address any top of mind before our reviews.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.43%. Comparing base (de5cfd6) to head (6da3de0).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #661      +/-   ##
==========================================
- Coverage   85.43%   85.43%   -0.01%     
==========================================
  Files          23       23              
  Lines        4668     4674       +6     
==========================================
+ Hits         3988     3993       +5     
- Misses        680      681       +1     

Flag	Coverage Δ
pester	85.43% <100.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
scripts/linting/Invoke-LinkLanguageCheck.ps1	86.76% <100.00%> (+1.28%)	⬆️

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[WilliamBerryiii]

I'm going to resolve the build problem on this so we can get it merged. Thanks @AhmedMustafa249 for the contribution here ... solid delivery!