fix(settings): remove markdownlint exclusion for collections/*.collection.md

[PratikWayase]

---

Pull Request

Description

Removed the exclusion for collections/*.collection.md from markdownlint configuration and fixed all related lint violations across collection files.

Changes include:

• Added top-level headings to all collection files (MD041)
• Removed multiple consecutive blank lines (MD012)
• Replaced em dashes with compliant alternatives
• Standardized formatting and ensured newline consistency
• Updated Validate-MarkdownFrontmatter.ps1 to align with updated linting rules

---

Related Issue(s)

Closes #1341

---

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

AI Artifacts:

• Reviewed contribution with prompt-builder agent and addressed all feedback
• Copilot instructions (.github/instructions/*.instructions.md)
• Copilot prompt (.github/prompts/*.prompt.md)
• Copilot agent (.github/agents/*.agent.md)
• Copilot skill (.github/skills/*/SKILL.md)

Other:

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

---

Testing

• Ran: npx markdownlint-cli2 "collections/*.collection.md" → 0 errors
• Ran: npm run lint:md → 0 errors
• Verified no regressions in markdown linting across repository

---

Checklist

Required Checks

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

AI Artifact Contributions

• Used /prompt-analyze to review contribution
• Addressed all feedback from prompt-builder review
• Verified contribution follows common standards and type-specific requirements

Required Automated Checks

• 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
• Plugin freshness: npm run plugin:generate
• Docusaurus tests: npm run docs:test

---

Security Considerations

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

---

[katriendg]

Thanks for your contribution @PratikWayase - I believe it will be good to hold off the changes on the collection MD files until PR #1316 is merged as it touches the same files, and you may have some conflicts. FYI @WilliamBerryiii

[katriendg]

Thanks for your work on this one @PratikWayase, nothing we have a PR out that needs to be merged first, and simplifies some of the work: #1316. Then this one can be rebased and simplified:

After #1316 merges, the auto-generated artifact tables will be lint-compliant by construction. The only pieces of which would still be needed are:

• Removing the .markdownlint-cli2.jsonc exclusion
• Removing the Validate-MarkdownFrontmatter.ps1 exclusion
• Fixing any em dashes remaining in the hand-authored intro sections (above the markers)

Thank you for your patience

[WilliamBerryiii]

Thank you so much for picking up #1341, @PratikWayase! The em-dash cleanup, the conversion away from bold-prefix list items, and adding H1s for MD041 all landed cleanly across the 14 collection files, and that is exactly the writing-style direction we have been moving toward. We really appreciate the care you put into this.

Before we merge, we left a few inline suggestions we would love your help tightening up. Happy to pair on any of these if it would be easier.

One last small note for after we land this: please run npm run plugin:generate as the final step so the plugins/ outputs and extension/README.*.md regenerate from the updated collection bodies. Those files are generated, so they need to flow through after the source changes.

Thank you again for tackling this, @PratikWayase. The writing-style improvements here are genuinely useful, and we are looking forward to getting this merged once the items below are sorted. Let us know if you would like a hand with any of them.

[WilliamBerryiii]

Hi @PratikWayase — thanks for picking this up.

Quick status update: PR #1316 merged after you opened this, and it changed the contract for collections/*.collection.md. The artifact tables are now machine-generated by npm run plugin:generate between <!-- BEGIN AUTO-GENERATED ARTIFACTS --> / <!-- END AUTO-GENERATED ARTIFACTS --> markers, so most of the current diff lands inside zones that get overwritten on the next regeneration.

Rather than ask you to redo a large rebase, I'm going to push a rework directly to this branch with you kept as the commit author so you retain credit for #1341. The new shape is much smaller:

• Remove collections/*.collection.md from ignores in .markdownlint-cli2.jsonc.
• Update the inline justification in scripts/linting/Validate-MarkdownFrontmatter.ps1 (the exclusion stays — these files are marker-bearing generated docs without frontmatter).
• Replace em-dashes only in the hand-authored intro lines (above the BEGIN AUTO-GENERATED ARTIFACTS marker) of each *.collection.md.
• Run npm run plugin:generate and npm run lint:all and verify clean.

Two asks before I push:

1. Please confirm "Allow edits from maintainers" is still enabled on this PR (it's the default for fork PRs, but worth checking).
2. If you have any local work-in-progress on fix/markdownlint-collections, push it now or let me know — I'll be force-pushing a rewritten history.

I'll hold off ~24h for your reply, then proceed. Appreciate the contribution.

[PratikWayase]

Yes, "Allow edits from maintainers" is enabled. Feel free to proceed.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.16%. Comparing base (57ea279) to head (3f3f1a9).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1372      +/-   ##
==========================================
- Coverage   87.44%   87.16%   -0.28%     
==========================================
  Files          68       67       -1     
  Lines       10335    10067     -268     
==========================================
- Hits         9037     8775     -262     
+ Misses       1298     1292       -6     

Flag	Coverage Δ
pester	84.79% <100.00%> (-0.02%)	⬇️

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

Files with missing lines	Coverage Δ
scripts/extension/Prepare-Extension.ps1	94.52% <100.00%> (ø)

... and 3 files with indirect coverage changes

🚀 New features to boost your workflow:

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