Minor refactor + Add rector

[vjik]

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

[codecov]

Codecov Report

❌ Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.23%. Comparing base (7d060fc) to head (03716d9).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
src/RequestBodyParser.php	50.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master      #47      +/-   ##
============================================
- Coverage     95.40%   95.23%   -0.17%     
  Complexity       34       34              
============================================
  Files             3        3              
  Lines            87       84       -3     
============================================
- Hits             83       80       -3     
  Misses            4        4              

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

🚀 New features to boost your workflow:

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

To fix this problem, the workflow should explicitly set the permissions block at the workflow or job level, specifying the minimum required access for the workflow to function. In the most secure configuration, set permissions: contents: read at the root, or within the specific job if different jobs have different needs. Because this workflow largely delegates to an external reusable workflow (via uses), the safest generic policy is to provide only read access unless a more specific write access is proven necessary for this action to work. The recommended best practice is to add a permissions block at the job level (right under the rector job—next to uses and with). By doing so, we minimize the token’s permissions for this job only, and can later expand them if downstream linter/rector steps require it.

To implement the fix:

• Insert the following block directly after the job name (rector:) or before uses:

  permissions:
    contents: read

• If future requirements necessitate additional permissions (e.g., pull-requests: write), they can be added as new lines under permissions.

---