Added support for the service_tier key in profiles

docs/config.md

@@ -157,6 +157,7 @@ max_tokens: 500
 top_p: 1.0
 timeout_seconds: 90
 api_key_env: SCRIPTORIUM_API_KEY
+service_tier: priority
 ```
 
 Field reference:
@@ -168,6 +169,7 @@ Field reference:
 - `max_tokens` (optional): `>= 0`
 - `top_p` (optional): range `0..1`
 - `timeout_seconds` (optional): `>= 0`
+- `service_tier` (optional): provider-specific request tier such as OpenRouter `flex` or `priority`
 - `reasoning_effort` (optional)
 - `api_key_env` (optional)
 - `extra_params` (optional map of strings)
@@ -181,7 +183,7 @@ Profile rules:
 
 Current outbound request behavior:
 
-- The OpenAI-compatible client currently serializes: `model`, `messages`, `temperature`, `max_tokens`, `top_p`, and optional `response_format` for `json_schema` prompts.
+- The OpenAI-compatible client currently serializes: `model`, `messages`, `temperature`, `max_tokens`, `top_p`, `service_tier`, and optional `response_format` for `json_schema` prompts.
 - `reasoning_effort` and `extra_params` are parsed and carried in effective settings, but are not currently serialized into outbound chat-completions requests.
 
 ## Schema Behavior

docs/integrations/http-api.md

@@ -46,6 +46,7 @@ Copyable request example file:
     "max_tokens": 800,
     "top_p": 1.0,
     "timeout_seconds": 120,
+    "service_tier": "priority",
     "reasoning_effort": "medium",
     "api_key_env": "SCRIPTORIUM_API_KEY",
     "extra_params": {
@@ -114,6 +115,7 @@ Response shape:
       "max_tokens": 800,
       "top_p": 1,
       "timeout_seconds": 120,
+      "service_tier": "priority",
       "reasoning_effort": "medium",
       "api_key_env": "SCRIPTORIUM_API_KEY",
       "extra_params": {

docs/integrations/openai-compatible-chat.md

@@ -30,8 +30,11 @@ Serialized JSON fields:
 - `temperature` (only when non-zero)
 - `max_tokens` (only when non-zero)
 - `top_p` (only when non-zero)
+- `service_tier` (only when non-empty)
 - `response_format` (only when structured output is provided)
 
+`service_tier` is provider-specific. OpenRouter currently documents request values such as `flex` and `priority`; Scriptorium forwards any non-empty configured value and lets the backend validate support.
+
 Structured output is currently `json_schema` only, serialized as:
 
 ```json

docs/internal/adapters.md

@@ -66,7 +66,7 @@ Primary app settings consumed by adapters:
 
 Execution profile/request settings used through runner:
 
-- `endpoint`, `model`, `temperature`, `max_tokens`, `top_p`, `timeout_seconds`, `api_key_env`, `reasoning_effort`, `extra_params`
+- `endpoint`, `model`, `temperature`, `max_tokens`, `top_p`, `timeout_seconds`, `service_tier`, `api_key_env`, `reasoning_effort`, `extra_params`
 
 ## External Dependencies