What?

Fixes the Excerpt Generation editor request so it passes the current post ID through the ability's existing context field instead of sending an unsupported post_id field.

Why?

The ai/excerpt-generation ability schema accepts content and context. Its post ID path is triggered when context is numeric.

Before this change, the editor sent post_id, which is not part of the Excerpt Generation ability schema. The request could still generate an excerpt because content was also sent, but the ability skipped the intended post-context path.

This brings Excerpt Generation in line with the existing ability contract and with sibling features like Title Generation and Summarization.

How?

• Sends context: postId.toString() from the Excerpt Generation editor hook.
• Updates the TypeScript input type to match the ability schema.

Testing Instructions

Automated checks run locally:

npm run typecheck
npm run lint:js -- src/experiments/excerpt-generation/components/useExcerptGeneration.ts src/experiments/excerpt-generation/types.ts
npx wp-env run cli --env-cwd=wp-content/plugins/develop vendor/bin/phpunit -c phpunit.xml.dist --filter Excerpt_GenerationTest
npm run build
git diff --check

Manual testing:

1. Enable AI features and the Excerpt Generation experiment.
2. Configure an AI connector.
3. Open a post in the editor.
4. Open DevTools → Network.
5. Click Generate excerpt in the Excerpt panel.
6. Confirm the request to wp-abilities/v1/abilities/ai/excerpt-generation/run sends input.context with the post ID instead of input.post_id.
7. Confirm the excerpt is generated and inserted.

Screenshots/Screencast

Before:

After:

Use of AI Tools

AI assistance: Yes
Tool(s): ChatGPT / Codex
Used for: Repository review, reproduction planning, implementation guidance, test updates, and local verification. I reviewed the changes, tested the behavior locally, and take responsibility for the final submission.