…ehavior

Simplifies annotation field validation logic by removing unnecessary conditional checks for specific field names after earlier validation has already filtered them out.

Inverts the conditional logic in priority validation to use early returns for valid cases instead of checking for invalid ranges.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Eliminates duplicate annotation mapping code by creating a centralized utility class.

The identical mapping logic was previously duplicated across prompt and resource registration classes, violating DRY principles and making maintenance more difficult.

Creates a new static utility class that handles the conversion of WordPress ability annotations to MCP-compliant format, including validation and normalization of audience, lastModified, and priority fields.

Improves code maintainability by providing a single source of truth for annotation transformation logic.

…to fix/tool-annotations-mapping

Resolved conflicts by keeping local refactored code that uses shared utility classes (McpAnnotationMapper and McpValidator) instead of inline methods.

Add is_null() check in annotation field conversion to prevent null
values from being cast to false. Null annotations are now properly
filtered out as expected.

Remove no-op assertion when no annotations are present. The test
already has assertions and the early return is a valid pass condition.

Replace conditional checks with required assertions to prevent false
positives. Verify annotations and audience are present, priority is
clamped to 0.0, and invalid values are filtered. Update fixture to
include mixed valid/invalid audience values.

- centralize ability→MCP annotation mapping so MCP-native values are preserved and WP-format overrides take precedence
- trim ability metadata, normalize resource URIs, and enforce server guards before validating prompts/resources/tools
- reuse shared annotation validator logic in tool validator + tests, and add coverage for whitespace URIs and missing MCP server cases

- Updated annotation keys from 'readOnlyHint', 'destructiveHint', and 'idempotentHint' to 'readonly', 'destructive', and 'idempotent' across multiple ability classes for uniformity.
- Ensured that the metadata structure aligns with the new naming conventions.

- Implemented logic to set the annotations.title from the label if annotations exist but the title is not set, ensuring better metadata completeness.

- Replaced 'readOnlyHint', 'destructiveHint', and 'idempotentHint' with 'readonly', 'destructive', and 'idempotent' in the DiscoverAbilitiesAbilityTest, ExecuteAbilityAbilityTest, and GetAbilityInfoAbilityTest for consistency with the updated metadata structure.

…a handling

- Adjusted the validation flow for the 'title' field to streamline error handling and ensure non-empty string requirements are enforced.
- Cleaned up whitespace handling in the RegisterAbilityAsMcpResource class to enhance URI normalization.
- Made minor formatting adjustments in ExecuteAbilityAbility for consistency.

Replace if statements with switch...case in
get_annotation_validation_errors() and fix priority validation logic.

Replace if statements with switch...case in annotation validation
methods and fix priority validation logic.

Return value directly instead of array structure with has_value flag