fix: apply change undefined property to null

[8471919]

This pull request standardizes the handling of optional fields in the agent’s analyze and review interfaces and prompt examples. All fields that indicate possible reviewer revisions (such as revisedSections, revisedUnits, revisedTitle, revisedSummary, and language) are now explicitly set to either a value or null instead of being omitted or left undefined. This change improves type safety, clarity, and consistency across the codebase.

API and Type Consistency Improvements:

• All revision-related fields in event and application interfaces (e.g., revisedSections, revisedUnits, revisedTitle, revisedSummary) are now required and set to either their value or null if no revisions were made, replacing previous optional/undefined usage. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
• The language field in scenario-related interfaces is now always present and set to either a string or null if not specified, instead of being optional. [1] [2]

Prompt Example Updates:

• All prompt example files now include revisedSections, revisedUnits, revisedTitle, and revisedSummary fields set to null when no revisions are present, ensuring alignment with the updated interface requirements. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

These changes ensure a more predictable and robust contract between the agent’s backend and its consumers, reducing ambiguity and potential bugs related to missing or undefined fields.