fix(docs): Update quality code section with Super-Linter and StyleCI badges.

[terabytesoftw]

Pull Request

Q	A
Is bugfix?	✔️
New feature?	❌
Breaks BC?	❌

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated changelog entry formatting and added quality code section documentation
  • Reorganized README with new "Quality code" section featuring code quality badges
  • Enhanced project documentation to highlight code quality standards

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

This PR updates project documentation by modifying changelog formatting and reorganizing quality code badges in the README. A new "Quality code" section containing Super-Linter and StyleCI badges is added, replacing the previous centered linter badge placement.

Changes

Cohort / File(s)	Summary
Documentation Updates CHANGELOG.md	Modified formatting of existing enhancement entry and added new bug entry documenting quality code section updates with Super-Linter and StyleCI badges
Documentation Updates README.md	Removed centered linter badge block; introduced dedicated "Quality code" section with Super-Linter and StyleCI badges in multiple locations within the document

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 The badges now shine in their proper place,
Reorganized with style and grace!
Quality code marked with pride so true,
StyleCI and Super-Linter—a stellar crew! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main changes: updating documentation with quality code badges (Super-Linter and StyleCI).
Description check	✅ Passed	The description is related to the changeset, confirming it's a bugfix for documentation updates regarding quality code badges.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@README.md`:
- Around line 162-166: Replace the static Shields.io StyleCI badge in the README
"Quality code" section with StyleCI's native dynamic badge URL so the badge
reflects live status; locate the existing StyleCI badge markup (the second image
link in that section) and update its href and image source to the StyleCI shield
endpoint (the /repos/<repo-id>/shield?branch=main URL) so both the link target
and displayed image use the StyleCI dynamic endpoint.

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2b59c05 and b0e63cb.

📒 Files selected for processing (2)

• CHANGELOG.md
• README.md

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: terabytesoftw
Repo: php-forge/foxy PR: 115
File: tests/Fallback/AssetFallbackTest.php:158-189
Timestamp: 2026-01-23T11:22:07.261Z
Learning: User terabytesoftw prefers not to use aliases when importing classes in PHP. They are comfortable with either fully-qualified class names or direct imports without aliases.

Learnt from: terabytesoftw
Repo: php-forge/support PR: 12
File: src/TestSupport.php:0-0
Timestamp: 2025-08-18T20:13:33.518Z
Learning: User terabytesoftw prefers clean trait-based designs over maintaining backward compatibility wrappers when refactoring utility classes in the php-forge/support project.

Learnt from: terabytesoftw
Repo: php-forge/actions PR: 65
File: .github/workflows/composer-require-checker.yml:80-83
Timestamp: 2025-09-28T15:12:48.345Z
Learning: The user terabytesoftw prefers using floating tags like v1 for third-party actions in GitHub workflows instead of pinning to specific commit SHAs, even when it's a security best practice to pin to immutable commits.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: linter / Super Linter
• GitHub Check: linter / Super Linter

🔇 Additional comments (1)

CHANGELOG.md (1)

5-6: LGTM! Consistent changelog formatting.

The changelog entries are well-formatted with consistent structure. The addition of the colon after "#1" on line 5 improves uniformity with the new entry on line 6.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}