[create-pull-request] automated change (#2)

Co-authored-by: mrbalov <26161358+mrbalov@users.noreply.github.com>

Author: mrbalov

openspec/specs/guardrails-activity-data/spec.md

@@ -1,6 +1,10 @@
 # Activity Data Guardrails
 
-Guardrails for validating activity input data, user-provided text, and tags.
+## Purpose
+
+Define guardrails for validating activity input data, user-provided text, and tags to ensure data integrity and safe processing.
+
+## Requirements
 
 ### Requirement: Required Activity Fields
 
@@ -202,4 +206,4 @@ Tags SHALL be normalized before use. Tags SHALL influence mood, intensity, and s
 #### Scenario: With kid tag influences scene
 - **GIVEN** an activity with `with kid` tag
 - **WHEN** generating an image
-- **THEN** the tag SHALL influence scene toward playful or warm atmosphere
+- **THEN** the tag SHALL influence scene toward playful or warm atmosphere

openspec/specs/guardrails-image-generation-prompt/spec.md

@@ -1,6 +1,10 @@
 # Image Generation Prompt Guardrails
 
-Guardrails for image generation prompt content, size limits, and safety validation.
+## Purpose
+
+Define guardrails for image generation prompt content, size limits, and safety validation to ensure appropriate and safe image generation.
+
+## Requirements
 
 ### Requirement: Allowed Prompt Content
 
@@ -77,4 +81,4 @@ The maximum prompt length SHALL be 400 characters. Prompts exceeding this limit
 #### Scenario: Prompt exceeding size limit
 - **GIVEN** a prompt with length greater than 400 characters
 - **WHEN** validating the prompt
-- **THEN** the prompt SHALL be truncated or simplified to meet the limit
+- **THEN** the prompt SHALL be truncated or simplified to meet the limit

openspec/specs/guardrails-image-generation/spec.md

@@ -1,6 +1,10 @@
 # Image Generation Guardrails
 
-Guardrails for image style, output characteristics, retry/fallback strategies, failure handling, and determinism.
+## Purpose
+
+Define guardrails for image style, output characteristics, retry/fallback strategies, failure handling, and determinism in image generation.
+
+## Requirements
 
 ### Requirement: Allowed Image Styles
 
@@ -187,4 +191,4 @@ Given identical inputs, classification and style decisions SHOULD be identical.
 #### Scenario: Bounded randomness
 - **GIVEN** an activity requiring image generation
 - **WHEN** applying randomness
-- **THEN** randomness SHALL be bounded and controlled
+- **THEN** randomness SHALL be bounded and controlled

openspec/specs/system-architecture/spec.md

@@ -1,6 +1,10 @@
 # System Architecture Requirements
 
-Architectural requirements for the PACE system's service-oriented architecture.
+## Purpose
+
+Define architectural requirements for the PACE system's service-oriented architecture to ensure robust, deterministic, and safe image generation from Strava activity data.
+
+## Requirements
 
 ### Requirement: Core Functionality Pipeline
 
@@ -245,4 +249,4 @@ Given identical inputs, the system SHALL produce identical classification and st
 #### Scenario: Reproducible behavior
 - **GIVEN** the same activity processed multiple times
 - **WHEN** comparing results
-- **THEN** behavior SHALL be predictable and reproducible
+- **THEN** behavior SHALL be predictable and reproducible