docs: add Continuous Compliance reference and expand features in README and user guide

[Copilot]

Pull Request

Description

The README undersold the compliance and quality engineering story, and had no reference to the Continuous Compliance methodology this template implements. The user guide also lacked any explanation of the compliance approach.

README.md — 4 new feature bullets added (existing 6 retained):

• Linting Enforcement — markdownlint, cspell, yamllint enforced before every build
• Continuous Compliance — links to demaconsulting/ContinuousCompliance methodology (reference-style link, consistent with README conventions)
• SonarCloud Integration — quality gate and security analysis on every build
• Requirements Traceability — requirements linked to passing tests, trace matrix auto-generated

docs/guide/guide.md — new # Continuous Compliance section inserted between Introduction and Installation:

• Describes the methodology with a reference-style link
• ## Key Practices subsection covering traceability, linting enforcement, automated audit docs, and CodeQL/SonarCloud

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code quality improvement

Related Issues

Pre-Submission Checklist

Before submitting this pull request, ensure you have completed the following:

Build and Test

• Code builds successfully: dotnet build --configuration Release
• All unit tests pass: dotnet test --configuration Release
• Code produces zero warnings

Code Quality

• Code formatting is correct: dotnet format --verify-no-changes
• New code has appropriate XML documentation comments
• Static analyzer warnings have been addressed

Quality Checks

Please run the following checks before submitting:

• Spell checker passes: cspell "**/*.{md,cs}"
• Markdown linter passes: markdownlint "**/*.md"
• YAML linter passes: yamllint .

Testing

• Added unit tests for new functionality
• Updated existing tests if behavior changed
• All tests follow the AAA (Arrange, Act, Assert) pattern
• Test coverage is maintained or improved

Documentation

• Updated README.md (if applicable)
• Updated ARCHITECTURE.md (if applicable)
• Added code examples for new features (if applicable)
• Updated requirements.yaml (if applicable)

Additional Notes

Documentation-only change. No code or requirements modified.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.