Yoast SEO 28.2 — docs(yoast-seo-abilities): Document new get-post-seo-data and update-post-seo-data abilities

[claude]

RC docs sync — 28.2-RC2

Product: wordpress-seo
Area: yoast-seo-abilities
Source evidence:

• src/abilities/user-interface/abilities-integration.php: registers yoast-seo/get-post-seo-data (read ability, GET, readonly=true, mcp.public=true) and yoast-seo/update-post-seo-data (write ability, POST, idempotent=true, mcp.public=true)
• src/abilities/application/post-seo-data-collector.php: new Post_SEO_Data_Collector::get_post_seo_data() — resolves posts by ID, permalink, or title keywords and returns the SEO data array
• src/abilities/application/post-seo-data-updater.php: new Post_SEO_Data_Updater::update_post_seo_data() — patch-semantics update cascaded to post meta via Indexable_To_Postmeta_Helper
• src/abilities/infrastructure/post-identifier-resolver.php: resolves identifier (post_id / permalink / title keywords) into indexable(s)
• src/abilities/infrastructure/post-seo-field-map.php: defines the read/write field contract (rendered fields, string fields, boolean fields, noindex tri-state)

Changes in this PR

• docs/features/yoast-seo-abilities/overview.md — updated ability count (3 → 5), added new ability names to the listing, expanded AI-agent use cases to include reading and writing post SEO data
• docs/features/yoast-seo-abilities/post-seo-data.md — new page: documents get-post-seo-data (input identifiers, output field table including *_rendered fields, example GET requests and response) and update-post-seo-data (patch semantics, noindex tri-state, example POST requests); includes full JSON schemas in tabs and a "how to disable" snippet
• sidebars.js — adds features/yoast-seo-abilities/post-seo-data to the Yoast SEO Abilities navigation category

Verification

• yarn build passes locally in this workflow.
• yarn lint clean for files touched by this PR.

Reviewer notes

• AGENT_MAP.md coverage gap: src/abilities/ has no area entry. The path/permission heuristics (Step 1.6) technically fired — /user-interface/ in the path, wpseo_manage_options capability — but the existing three abilities from the same file and with the same capability gate ARE already documented in this section. This PR follows that prior art. A maintainer should add an abilities area to AGENT_MAP.md to prevent future runs from relying on this ad-hoc reasoning.
• The *_rendered fields (e.g. seo_title_rendered) carry the fully-expanded front-end output, not the raw template. This distinction is worth confirming is clearly communicated in the docs.
• The HTTP method for update-post-seo-data (POST) is inferred from the readonly: false annotation and standard REST conventions; the WordPress Abilities API run endpoint should be verified to accept POST for write abilities.
• can_read_scores() is deprecated in 28.2 in favour of can_manage_seo() — no doc change needed as this is an internal PHP method, not a public hook or filter.

---

Authored by the RC docs-sync agent. Not auto-merged — requires human review. Run: https://github.com/Yoast/developer/actions/runs/29898596275

[cloudflare-workers-and-pages]

Deploying yoast-developer with    Cloudflare Pages

Latest commit:	9756568
Status:	✅  Deploy successful!
Preview URL:	https://eb0f29b5.yoast-developer.pages.dev
Branch Preview URL:	https://rc-sync-wordpress-seo-28-2-r.yoast-developer.pages.dev

View logs