docs(contributor): contributors readme action update

[github-actions]

📑 Description

contributors readme action update

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

☢️ Does this introduce a breaking change?

• Yes
• No

---

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a new contributor entry to the README and fixes the contributor table row structure so HTML table rows are correctly grouped.

Flow diagram for updated README contributors table structure

flowchart LR
    subgraph Before
        A[Row 1: existing contributors]
        B[Row 2: Viktorius and Yousef in same row]
        C[Row 3: akhtareimon and following contributors]
        A --> B --> C
    end

    subgraph After
        D[Row 1: existing contributors]
        E[Row 2: new contributor HarryKambo added]
        F[Row 3: Viktorius in previous row, new row break]
        G[Row 4: Yousef and akhtareimon start new correctly grouped row]
        D --> E --> F --> G
    end

    Before --> After

Loading

File-Level Changes

tags so that existing contributors are grouped into correctly structured table rows without splitting Yousef-Majidi and akhtareimon into separate rows.

Ensure indentation and alignment of the modified table markup are consistent with surrounding HTML.

Change	Details	Files
Add a new contributor block to the contributors table and adjust table row tags to maintain valid HTML structure.	Insert a new table cell with avatar image, GitHub profile link, and name for contributor HarryKambo. Move closing and opening
README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[gstraccini]

Please provide a description for this pull request.

[sourcery-ai]

Hey - I've left some high level feedback:

• Please double-check the <tr> grouping so that each row contains a consistent number of contributor <td> cells and the table layout stays aligned across all contributors.
• The mix of tabs and spaces in the modified table rows makes indentation inconsistent; consider normalizing indentation to match the existing style in the README.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Please double-check the `<tr>` grouping so that each row contains a consistent number of contributor `<td>` cells and the table layout stays aligned across all contributors.
- The mix of tabs and spaces in the modified table rows makes indentation inconsistent; consider normalizing indentation to match the existing style in the README.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-07-04T03:40:20Z INF scanning for exposed secrets...
3:40AM INF 807 commits scanned.
2026-07-04T03:40:21Z INF scan completed in 1.23s
2026-07-04T03:40:21Z INF no leaks found

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud