Update README.md

[asmallberg]

Test Plan

Test environment: https://console.your-env.onplural.sh/

Checklist

• I have added a meaningful title and summary to convey the impact of this PR to a user.
• If required, I have updated the Plural documentation accordingly.
• I have added tests to cover my changes.
• I have deployed the agent to a test environment and verified that it works as expected (required only when changing agent code).

Plural Flow: console

[greptile-apps]

Greptile Summary

Updates the README’s Contributor Program to narrow the advertised compatibility bounty.

• Removes rewards for adding an entirely new application and creating a compatibility scraper.
• Retains the $50 reward for adding compatibility data for a specific application version.
• Introduces a minor grammatical error in the revised program description.

Confidence Score: 4/5

The policy update appears safe to merge after correcting the non-blocking grammatical error in README.md.

The bounty removals are internally coherent, but the revised introductory sentence contains a duplicated verb construction that reduces readability.

Files Needing Attention: README.md

Important Files Changed

Filename	Overview
README.md	Updates compatibility bounty guidance but introduces a grammatical error in the contributor-program description.

_{Reviews (1): Last reviewed commit: "Update README.md" | Re-trigger Greptile}

[greptile-apps]

Duplicated Verb Construction

The phrase “getting keeping them up-to-date” uses two conflicting verb forms, making the contributor-program guidance harder to understand. Remove either “getting” or “keeping” to make the sentence grammatical.

Suggested change

We are currently trying to aggregate compatibility and dependency information for many CNCF add-ons within the kubernetes ecosystem. You can see some early examples in `static/compatibilities` and are hoping to get community support getting keeping them up-to-date. We are focused on properly compensating any contributions to the Plural platform, which includes a bounty for updating the information alongside a new version that has been released. Currently the rewards are:

We are currently trying to aggregate compatibility and dependency information for many CNCF add-ons within the kubernetes ecosystem. You can see some early examples in `static/compatibilities` and are hoping to get community support keeping them up-to-date. We are focused on properly compensating any contributions to the Plural platform, which includes a bounty for updating the information alongside a new version that has been released. Currently the rewards are:

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!