Refactor: enforce canonical messages/output YAML, normalize content_file, and expand fixture-based validation tests

internal/profile/testdata/json_schema_missing_path.yaml

@@ -1,11 +0,0 @@
-id: json-schema-missing-path
-version: "1.0.0"
-inputs:
-  - name: transcript
-    required: true
-templates:
-  - role: user
-    content: "Return JSON"
-output_format: json
-validation:
-  validation_mode: json_schema

internal/profile/testdata/negative_timeout.yaml

@@ -1,11 +0,0 @@
-id: negative-timeout
-version: "1.0.0"
-inputs:
-  - name: transcript
-    required: true
-templates:
-  - role: user
-    content: "Say hi"
-output_format: text
-validation:
-  validation_mode: none

internal/profile/testdata/no_templates.yaml

@@ -1,9 +0,0 @@
-id: no-templates
-version: 1.0.0
-inputs:
-  - name: transcript
-    required: true
-templates: []
-output_format: text
-validation:
-  validation_mode: none

internal/profile/testdata/valid.yaml

@@ -1,19 +0,0 @@
-id: test-profile
-version: "1.0.0"
-default_profile: test-exec
-description: A valid test prompt definition
-inputs:
-  - name: transcript
-    required: true
-    content_type: text/markdown
-  - name: glossary
-    required: false
-    content_type: text/yaml
-templates:
-  - role: system
-    content: "You are a helpful assistant."
-  - role: user
-    content: 'Analyze this: {{input "transcript"}}'
-output_format: markdown
-validation:
-  validation_mode: basic