RC docs-sync audit log — Yoast SEO

[enricobattocchi]

RC docs-sync — Yoast SEO

This is the audit log for the RC docs-sync workflow running on Yoast SEO (free, Yoast/wordpress-seo).

The workflow runs daily at 06:00 UTC. For every new RC tag in the source repo, it analyzes the diff against the last processed release, decides whether the developer-portal docs need updating, and — when warranted — opens one draft PR per affected feature area. Every run posts one comment to this issue, regardless of whether any PRs were opened, so this thread is the canonical record of what was checked and when.

How to read the comments

Every comment starts with a machine-readable marker. The workflow uses these markers to determine which RCs have already been processed — please do not edit or delete comments that contain a marker, otherwise the next run may re-process or skip RCs.

<!-- rc-docs-sync:v1 product=wordpress-seo rc_tag=27.5-RC1 -->

After the marker, the comment body falls into one of these shapes:

• No-op run — "no doc changes needed". The RC contained only tests, translations, lockfile bumps, or internal refactors with no public-surface impact. The marker is posted; no PR is opened.
• PR-producing run — lists the PRs opened, with links and brief rationales. Each PR's title is Yoast SEO <base-version> — docs(<area>): <title>.
• Coverage gaps observed — if the agent saw new public surface (a new filter, REST route, or top-level src/<subsystem>/) that doesn't match any area in AGENT_MAP.md, it lists them under that heading. Informational only; updating the map is a separate manual PR.

Find the PRs

Filter by labels: rc-doc-sync + product/wordpress-seo.

https://github.com/Yoast/developer/pulls?q=is%3Apr+label%3Arc-doc-sync+label%3Aproduct%2Fwordpress-seo

Backfill a specific past RC

Run the RC docs sync workflow manually via "Run workflow" with product=wordpress-seo and the RC tag you want to backfill.

Pause / disable

Comment out the schedule: trigger in the workflow YAML, or remove the wordpress-seo entry from the PRODUCTS dict at the top of the workflow's resolve-queue step.

Related artifacts

• Workflow: .github/workflows/rc-docs-sync.yml
• Agent orchestration prompt: .github/claude-agent/run.md
• Area taxonomy: AGENT_MAP.md
• Original proposal: RC docs-sync: daily Claude-authored doc PRs (experimental rollout, wordpress-seo) #388

[enricobattocchi]

Yoast SEO 27.6 (RC 27.6-RC1) — manual safety-net marker.

The first agent run for this RC (workflow run) successfully opened PR #393 but hit --max-turns 50 before posting its own summary comment. Without this marker, tomorrow's scheduled run would re-process 27.6-RC1 from scratch and create a duplicate PR. Posting it manually here so state advances.

Follow-up workflow fix incoming in #394: bump --max-turns and add an if: always() safety-net step that posts a marker comment from the workflow itself if the agent step doesn't.

[claude]

Yoast SEO 27.6

RC tag: 27.6-RC2 (tagged 2026-04-29)
Source repo: Yoast/wordpress-seo
Previous release: 27.5 (tagged 2026-04-28)
Diff size (filtered): 62,357 lines across 1 repo
Symbol index: 115 symbols currently documented; 1 new symbol observed in diff (wpseo_content_planner_min_posts) — not yet in the index

---

Outcome: 0 PRs opened

The 27.6-RC2 diff is dominated by the new AI Content Planner feature. This adds AI-powered content suggestions and structured outlines in the block editor. The entire server-side surface — two REST routes and one filter — is classified as internal (see “Internal surface skipped” below). No existing documented features were changed in a way that affects their documented public APIs.

What the RC contains (changelog summary):

Adds the Content Planner feature, which allows users to get AI-powered content suggestions and structured outlines for new posts directly from the block editor. Also: docblock improvements, contributor-guide updates (AGENTS.md, CLAUDE.md, Cursor rules), removal of the Slack notification Grunt task, and minor internal refactoring/typo fixes.

None of these changes affect symbols in the current developer-portal docs, and no new public PHP filter or hook was introduced outside of internal admin-UI paths.

---

Internal surface skipped

• src/ai/content-planner/user-interface/get-outline-route.php — REST route yoast/v1/ai/content-planner/outline
  Signal: explicit @internal PHPDoc annotation (“not part of the plugin’s public REST API surface”) and permission callback enforces edit_posts (user_can($user, ‘edit_posts’)) with no unauthenticated branch.

• src/ai/content-planner/user-interface/get-suggestions-route.php — REST route yoast/v1/ai/content-planner/suggestions
  Signal: explicit @internal PHPDoc annotation (same wording as above) and permission callback enforces edit_posts.

• src/ai/content-planner/user-interface/content-planner-integration.php — filter wpseo_content_planner_min_posts
  Signal: mixed — the filter docblock describes a developer-facing override (“Allows overriding the minimum number of published posts required for the Content Planner feature”), but the registering class lives under user-interface/ (path/class heuristic) and the method is private. Skipping per the “when in doubt, do not document” rule. A maintainer can reverse this if the filter is confirmed as public API.

---

Coverage gaps observed

• src/ai/content-planner/** (multiple new files across application/, domain/, infrastructure/, user-interface/) — The ai area in AGENT_MAP.md lists src/ai-*/** as its source path (hyphenated prefix), which matches src/ai-generator/ etc. but does not match the new src/ai/ directory (non-hyphenated). All new Content Planner PHP lives under src/ai/content-planner/, outside every area’s source_paths. Hypothesis: belongs to the ai area — recommend adding src/ai/** to that area’s source_paths in AGENT_MAP.md.

---

RC docs-sync agent run: https://github.com/Yoast/developer/actions/runs/25102184836