chore(docs): regenerate impacted README files

[github-actions]

Automated README regeneration, Dependabot-style.

• Fixed branch; subsequent runs update this same PR until merged.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: lightspeedwp/.github/.coderabbit.yml

Review profile: CHILL

Plan: Advanced

Run ID: c814deaa-fd86-4efd-bda6-705a944821be

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[ashleyshaw]

Approved, my only question @eleshar is where are the READMEs being generated in another PR?

[eleshar]

@ashleyshaw Nowhere at the moment , the workflow is broken. I started working on the fix yesterday, but it will take some time to resolve properly.

AI is quite weak when it comes to scripting and configuring workflows. It can generate something that looks correct and may even report that it has passed validation.

[eleshar]

Closing: this run produced no README changes (sole commit touched only .github/metrics/meta-metrics.json). Superseded by #3429, which gates the regeneration job so metrics-only runs no longer open or update this fixed-branch PR.