This documentation was AI-generated, based on the original Features API docs.

My next step will be to review the generated docs manually and update them accordingly.

Thanks for the update! I see that #8 is already in progress. I’ll close my PR to avoid duplication. Happy to help with other issues in the future!

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (trunk@fb95300). Learn more about missing BASE report.

@@           Coverage Diff            @@
##             trunk      #10   +/-   ##
========================================
  Coverage         ?   92.48%           
  Complexity       ?       99           
========================================
  Files            ?        7           
  Lines            ?      519           
  Branches         ?        0           
========================================
  Hits             ?      480           
  Misses           ?       39           
  Partials         ?        0           

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

I updated the branch with GitHub UI to the latest changes from trunk while testing the repo configuration. We are still working on tooling, so there is no need to worry about coding the failing checks with code analysis.

Updated all the factual errors. Last step is to test and verify the code examples, but I'm marking this as ready to review so long.

• Updated PR based on review feedback (props @gziolo)
• Updated Using Abilities examples to rely on WP_Error object return on failure

Would it make sense to land the initial version and tackle the subsequent iterations in follow-up targeted PRs? I approved PR, so with all checks passing, you should be able to merge at any point.

Would it make sense to land the initial version and tackle the subsequent iterations in follow-up targeted PRs? I approved PR, so with all checks passing, you should be able to merge at any point.

Yup, that was my plan as well. Going to merge here in a bit.