chore: remove sync-metadata script and docs/development.md, update documentation links.

[terabytesoftw]

Pull Request

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

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Documentation

  • Removed development guide documentation and associated README reference.
  • Added "Next steps" section to testing documentation with links to Installation Guide, Configuration Reference, and Usage Examples.
  • Reformatted changelog entries to Conventional Commits and Semantic Versioning format.

• Chores

  • Removed sync-metadata composer script.

Walkthrough

This PR removes the sync-metadata Composer script and its associated documentation, standardizes the CHANGELOG.md formatting to follow Conventional Commits style with normalized prefixes and standardized issue references, and adds a "Next steps" section with documentation links to the testing guide.

Changes

Cohort / File(s)	Summary
Changelog & README Standardization CHANGELOG.md, README.md	CHANGELOG.md entries reformatted to Conventional Commits style (fix, feat, chore) with standardized issue references and removed contributor tags across all release versions; README.md removed development guide documentation link.
Sync-metadata Script Removal composer.json, docs/development.md	Composer sync-metadata script entry deleted that previously fetched template configuration files; associated development documentation file removed entirely.
Testing Documentation Enhancement docs/testing.md	New "Next steps" section added with three documentation links: Installation Guide, Configuration Reference, and Usage Examples.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• chore: Update changelog for version 0.2.0 with recent enhancements and bug fixes. #17: Modifies CHANGELOG.md and updates 0.2.0 changelog entries similar to this PR's standardization approach.

Poem

🐰 Hoppy cleanup time! ✨
Scripts removed, the sync-metadata fleet,
Changelog entries now Conventional-neat,
Development docs retire with grace,
Testing guides chart a brighter place! 🌱

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description uses a metadata table format indicating bugfix/feature/BC status, which is related to the PR's general properties but does not substantively describe the changeset contents.	Consider adding a brief explanation of what the changes accomplish and why they are being made, such as the rationale for removing the sync-metadata script.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title accurately and concisely summarizes the main changes: removing the sync-metadata script, deleting docs/development.md, and updating documentation links.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix_mini_50

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (79d8441) to head (8d7282a).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@             Coverage Diff             @@
##                main       #84   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity        81        81           
===========================================
  Files              2         2           
  Lines            156       156           
===========================================
  Hits             156       156           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[terabytesoftw]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Line 75: Update the CHANGELOG entry that currently reads "feat: enable strict
rules and bleeding edge analysis, and update `README.md` with strict
configuration examples (`#29`)" by hyphenating the compound adjective: change
"bleeding edge analysis" to "bleeding-edge analysis" so the line starts "feat:
enable strict rules and bleeding-edge analysis, and update `README.md` with
strict configuration examples (`#29`)"; locate the string by searching for the
exact "feat: enable strict rules and bleeding edge analysis" text and replace it
accordingly.
- Line 12: Update the changelog entry string "- chore: remove `sync-metadata`
script and `docs/development.md`, update documentation links." to include the
issue reference by appending " (`#84`)" immediately before the final period so it
reads "- chore: remove `sync-metadata` script and `docs/development.md`, update
documentation links (`#84`)."; locate and edit this exact line in CHANGELOG.md.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 19375ac7-0737-49fb-83e0-61337e483cf2

📥 Commits

Reviewing files that changed from the base of the PR and between 79d8441 and 8d7282a.

📒 Files selected for processing (5)

• CHANGELOG.md
• README.md
• composer.json
• docs/development.md
• docs/testing.md

💤 Files with no reviewable changes (3)

• docs/development.md
• README.md
• composer.json

📜 Review details

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-06-14T17:41:48.820Z

Learnt from: terabytesoftw
Repo: yii2-extensions/phpstan PR: 40
File: src/ServiceMap.php:0-0
Timestamp: 2025-06-14T17:41:48.820Z
Learning: The yii2-extensions/phpstan repository contains a PHPStan extension specifically designed for static analysis of Yii framework applications.

Applied to files:

• CHANGELOG.md

🪛 LanguageTool

CHANGELOG.md

[grammar] ~36-~36: Ensure spelling is correct
Context: ...update CHANGELOG.md to include recent bugfixes and enhancements for version 0.3.1 (#...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~75-~75: Use a hyphen to join words.
Context: ...- feat: enable strict rules and bleeding edge analysis, and update README.md wi...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (2)

CHANGELOG.md (1)

3-6: LGTM! The header update aligns with Conventional Commits standards.

The updated header clearly states that the changelog follows Conventional Commits and Semantic Versioning, which improves consistency and clarity for contributors.

docs/testing.md (1)

63-67: All referenced documentation files exist. The new "Next steps" section correctly links to installation.md, configuration.md, and examples.md in the docs/ directory. The addition improves navigation between documentation pages without breaking any links.