From 89396f70c776a50ef436f213f6f207b80c849f3a Mon Sep 17 00:00:00 2001 From: "braintrust-bot[bot]" <215900051+braintrust-bot[bot]@users.noreply.github.com> Date: Mon, 21 Sep 2026 23:44:29 +0000 Subject: [PATCH] chore: sync OpenAPI spec --- openapi/spec.json | 127 ++++++++++++++++++-- openapi/spec.yaml | 288 +++++++++++++++++++++++++++++++++++----------- 2 files changed, 341 insertions(+), 74 deletions(-) diff --git a/openapi/spec.json b/openapi/spec.json index 57dbf6f..20c205d 100644 --- a/openapi/spec.json +++ b/openapi/spec.json @@ -806,11 +806,21 @@ "nullable": true, "description": "If true, use metrics.start rather than created for monitor chart time bucket dimensions." }, + "coding_agent_insights_dashboard": { + "type": "boolean", + "nullable": true, + "description": "If true, enable the agent insights dashboard for this project." + }, "blind_reviews": { "type": "boolean", "nullable": true, "description": "If true, hide peer review scores, comments, and aggregate results from reviewers without project update permissions until they submit their own review." }, + "require_all_human_review_scores": { + "type": "boolean", + "nullable": true, + "description": "If true, automatically complete a review after every assigned reviewer fills all human review scores visible to them." + }, "default_preprocessor": { "$ref": "#/components/schemas/NullableSavedFunctionId" } @@ -947,6 +957,7 @@ "preprocessor", "classifier", "review", + "question", "log", null ], @@ -972,6 +983,20 @@ null ], "description": "A special value that indicates the span was generated by a scoring automation" + }, + "log_level": { + "type": "string", + "nullable": true, + "enum": [ + "trace", + "debug", + "info", + "warn", + "error", + "fatal", + null + ], + "description": "Severity level of a log" } }, "additionalProperties": { @@ -3516,6 +3541,62 @@ ], "title": "image_url" }, + "ChatCompletionContentPartInputAudioWithTitle": { + "type": "object", + "properties": { + "input_audio": { + "type": "object", + "properties": { + "data": { + "type": "string" + }, + "format": { + "type": "string", + "enum": [ + "wav", + "mp3" + ] + } + }, + "required": [ + "data", + "format" + ] + }, + "type": { + "type": "string", + "enum": [ + "input_audio" + ] + }, + "cache_control": { + "type": "object", + "properties": { + "type": { + "type": "string", + "enum": [ + "ephemeral" + ] + }, + "ttl": { + "type": "string", + "enum": [ + "5m", + "1h" + ] + } + }, + "required": [ + "type" + ] + } + }, + "required": [ + "input_audio", + "type" + ], + "title": "input_audio" + }, "ChatCompletionContentPartFileFile": { "type": "object", "properties": { @@ -3579,6 +3660,9 @@ { "$ref": "#/components/schemas/ChatCompletionContentPartImageWithTitle" }, + { + "$ref": "#/components/schemas/ChatCompletionContentPartInputAudioWithTitle" + }, { "$ref": "#/components/schemas/ChatCompletionContentPartFileWithTitle" } @@ -6040,7 +6124,7 @@ "type": "string", "minLength": 1, "maxLength": 10000, - "description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report." + "description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report." } }, "required": [ @@ -6321,7 +6405,7 @@ "type": "number", "nullable": true, "minimum": 60, - "description": "How much recent history to relabel after a new topic map version becomes active" + "description": "Deprecated. How much recent history to relabel after a new topic map version becomes active. Data planes v2.15.0 and later ignore this and apply a topic map version after the first only to traces classified once it is active." }, "backfill_time_range": { "anyOf": [ @@ -6409,7 +6493,7 @@ "type": "string", "minLength": 1, "maxLength": 10000, - "description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report." + "description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report." } }, "required": [ @@ -6547,7 +6631,7 @@ "type": "string", "minLength": 1, "maxLength": 10000, - "description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report." + "description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report." } }, "required": [ @@ -6889,7 +6973,7 @@ "type": "string", "minLength": 1, "maxLength": 10000, - "description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report." + "description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report." } }, "required": [ @@ -6918,6 +7002,21 @@ } ], "description": "The configuration for the automation rule" + }, + "runtime_block": { + "type": "object", + "properties": { + "reason": { + "type": "string" + }, + "model": { + "type": "string" + } + }, + "required": [ + "reason", + "model" + ] } }, "required": [ @@ -7023,7 +7122,7 @@ "type": "string", "minLength": 1, "maxLength": 10000, - "description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report." + "description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report." } }, "required": [ @@ -7365,7 +7464,7 @@ "type": "string", "minLength": 1, "maxLength": 10000, - "description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report." + "description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report." } }, "required": [ @@ -7494,7 +7593,7 @@ "type": "string", "minLength": 1, "maxLength": 10000, - "description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report." + "description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report." } }, "required": [ @@ -7836,7 +7935,7 @@ "type": "string", "minLength": 1, "maxLength": 10000, - "description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report." + "description": "Publish a Slack mrkdwn digest.\n\nPattern selection requirement: include every selected Pattern whose final status is active at the end of this automation run, plus every selected Pattern that changed from active to inactive during this run (a newly inactive outcome). Exclude Patterns that were already inactive before this run and remained inactive. Do not mention excluded Patterns anywhere in the digest, including Highlights. If no selected Patterns meet these criteria, say \"No current pattern outcomes.\" This requirement overrides conflicting formatting guidance.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every included Pattern.\n\nUse this row format exactly:\n• — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any active selected Pattern.\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out among the included active Patterns. Do not introduce new claims beyond the run report." } }, "required": [ @@ -11226,6 +11325,16 @@ "format": "date-time", "description": "Date of organization creation" }, + "archived_at": { + "type": "string", + "nullable": true, + "format": "date-time" + }, + "deleted_at": { + "type": "string", + "nullable": true, + "format": "date-time" + }, "image_rendering_mode": { "$ref": "#/components/schemas/ImageRenderingMode" } diff --git a/openapi/spec.yaml b/openapi/spec.yaml index e707fc7..a8b6ae4 100644 --- a/openapi/spec.yaml +++ b/openapi/spec.yaml @@ -688,12 +688,21 @@ components: nullable: true description: If true, use metrics.start rather than created for monitor chart time bucket dimensions. + coding_agent_insights_dashboard: + type: boolean + nullable: true + description: If true, enable the agent insights dashboard for this project. blind_reviews: type: boolean nullable: true description: If true, hide peer review scores, comments, and aggregate results from reviewers without project update permissions until they submit their own review. + require_all_human_review_scores: + type: boolean + nullable: true + description: If true, automatically complete a review after every assigned + reviewer fills all human review scores visible to them. default_preprocessor: $ref: "#/components/schemas/NullableSavedFunctionId" Project: @@ -798,6 +807,7 @@ components: - preprocessor - classifier - review + - question - log - null description: Type of the span, for display purposes only @@ -819,6 +829,18 @@ components: - null description: A special value that indicates the span was generated by a scoring automation + log_level: + type: string + nullable: true + enum: + - trace + - debug + - info + - warn + - error + - fatal + - null + description: Severity level of a log additionalProperties: nullable: true description: Human-identifying attributes of the span, such as name, type, etc. @@ -3406,6 +3428,44 @@ components: - image_url - type title: image_url + ChatCompletionContentPartInputAudioWithTitle: + type: object + properties: + input_audio: + type: object + properties: + data: + type: string + format: + type: string + enum: + - wav + - mp3 + required: + - data + - format + type: + type: string + enum: + - input_audio + cache_control: + type: object + properties: + type: + type: string + enum: + - ephemeral + ttl: + type: string + enum: + - 5m + - 1h + required: + - type + required: + - input_audio + - type + title: input_audio ChatCompletionContentPartFileFile: type: object properties: @@ -3447,6 +3507,7 @@ components: anyOf: - $ref: "#/components/schemas/ChatCompletionContentPartTextWithTitle" - $ref: "#/components/schemas/ChatCompletionContentPartImageWithTitle" + - $ref: "#/components/schemas/ChatCompletionContentPartInputAudioWithTitle" - $ref: "#/components/schemas/ChatCompletionContentPartFileWithTitle" title: chat_completion_content_part ChatCompletionMessageToolCall: @@ -5304,10 +5365,20 @@ components: Publish a Slack mrkdwn digest. + Pattern selection requirement: include every selected + Pattern whose final status is active at the end of this + automation run, plus every selected Pattern that changed + from active to inactive during this run (a newly inactive + outcome). Exclude Patterns that were already inactive + before this run and remained inactive. Do not mention + excluded Patterns anywhere in the digest, including + Highlights. If no selected Patterns meet these criteria, + say "No current pattern outcomes." This requirement + overrides conflicting formatting guidance. + + Include a complete "*Pattern outcomes*" section with one - row for every selected Pattern from the run report, - including created, updated, unchanged, failed, skipped, - and newly inactive outcomes. + row for every included Pattern. Use this row format exactly: @@ -5318,15 +5389,14 @@ components: If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any - selected Pattern. If there are no selected Patterns, say - "No pattern outcomes." + active selected Pattern. After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. - Summarize what changed or what broadly stands out from - this run. Do not introduce new claims beyond the run - report. + Summarize what changed or what broadly stands out among + the included active Patterns. Do not introduce new claims + beyond the run report. required: - type - workspace_id @@ -5504,8 +5574,10 @@ components: type: number nullable: true minimum: 60 - description: How much recent history to relabel after a new topic map version - becomes active + description: Deprecated. How much recent history to relabel after a new topic + map version becomes active. Data planes v2.15.0 and later ignore + this and apply a topic map version after the first only to traces + classified once it is active. backfill_time_range: anyOf: - type: string @@ -5571,10 +5643,19 @@ components: Publish a Slack mrkdwn digest. + Pattern selection requirement: include every selected Pattern + whose final status is active at the end of this automation run, + plus every selected Pattern that changed from active to inactive + during this run (a newly inactive outcome). Exclude Patterns + that were already inactive before this run and remained + inactive. Do not mention excluded Patterns anywhere in the + digest, including Highlights. If no selected Patterns meet these + criteria, say "No current pattern outcomes." This requirement + overrides conflicting formatting guidance. + + Include a complete "*Pattern outcomes*" section with one row for - every selected Pattern from the run report, including created, - updated, unchanged, failed, skipped, and newly inactive - outcomes. + every included Pattern. Use this row format exactly: @@ -5584,14 +5665,13 @@ components: If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must - remain clickable. Do not omit any selected Pattern. If there are - no selected Patterns, say "No pattern outcomes." + remain clickable. Do not omit any active selected Pattern. After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what - changed or what broadly stands out from this run. Do not - introduce new claims beyond the run report. + changed or what broadly stands out among the included active + Patterns. Do not introduce new claims beyond the run report. required: - type - workspace_id @@ -5700,10 +5780,22 @@ components: Publish a Slack mrkdwn digest. + Pattern selection requirement: include every + selected Pattern whose final status is active at the + end of this automation run, plus every selected + Pattern that changed from active to inactive during + this run (a newly inactive outcome). Exclude + Patterns that were already inactive before this run + and remained inactive. Do not mention excluded + Patterns anywhere in the digest, including + Highlights. If no selected Patterns meet these + criteria, say "No current pattern outcomes." This + requirement overrides conflicting formatting + guidance. + + Include a complete "*Pattern outcomes*" section with - one row for every selected Pattern from the run - report, including created, updated, unchanged, - failed, skipped, and newly inactive outcomes. + one row for every included Pattern. Use this row format exactly: @@ -5714,16 +5806,14 @@ components: If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain - clickable. Do not omit any selected Pattern. If - there are no selected Patterns, say "No pattern - outcomes." + clickable. Do not omit any active selected Pattern. After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly - stands out from this run. Do not introduce new - claims beyond the run report. + stands out among the included active Patterns. Do + not introduce new claims beyond the run report. required: - type - workspace_id @@ -5961,10 +6051,22 @@ components: Publish a Slack mrkdwn digest. + Pattern selection requirement: include every + selected Pattern whose final status is active at the + end of this automation run, plus every selected + Pattern that changed from active to inactive during + this run (a newly inactive outcome). Exclude + Patterns that were already inactive before this run + and remained inactive. Do not mention excluded + Patterns anywhere in the digest, including + Highlights. If no selected Patterns meet these + criteria, say "No current pattern outcomes." This + requirement overrides conflicting formatting + guidance. + + Include a complete "*Pattern outcomes*" section with - one row for every selected Pattern from the run - report, including created, updated, unchanged, - failed, skipped, and newly inactive outcomes. + one row for every included Pattern. Use this row format exactly: @@ -5975,16 +6077,14 @@ components: If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain - clickable. Do not omit any selected Pattern. If - there are no selected Patterns, say "No pattern - outcomes." + clickable. Do not omit any active selected Pattern. After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly - stands out from this run. Do not introduce new - claims beyond the run report. + stands out among the included active Patterns. Do + not introduce new claims beyond the run report. required: - type - workspace_id @@ -5997,6 +6097,16 @@ components: - $ref: "#/components/schemas/TopicAutomationConfig" - $ref: "#/components/schemas/TopicDigestAutomationConfig" description: The configuration for the automation rule + runtime_block: + type: object + properties: + reason: + type: string + model: + type: string + required: + - reason + - model required: - id - project_id @@ -6081,10 +6191,22 @@ components: Publish a Slack mrkdwn digest. + Pattern selection requirement: include every + selected Pattern whose final status is active at the + end of this automation run, plus every selected + Pattern that changed from active to inactive during + this run (a newly inactive outcome). Exclude + Patterns that were already inactive before this run + and remained inactive. Do not mention excluded + Patterns anywhere in the digest, including + Highlights. If no selected Patterns meet these + criteria, say "No current pattern outcomes." This + requirement overrides conflicting formatting + guidance. + + Include a complete "*Pattern outcomes*" section with - one row for every selected Pattern from the run - report, including created, updated, unchanged, - failed, skipped, and newly inactive outcomes. + one row for every included Pattern. Use this row format exactly: @@ -6095,16 +6217,14 @@ components: If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain - clickable. Do not omit any selected Pattern. If - there are no selected Patterns, say "No pattern - outcomes." + clickable. Do not omit any active selected Pattern. After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly - stands out from this run. Do not introduce new - claims beyond the run report. + stands out among the included active Patterns. Do + not introduce new claims beyond the run report. required: - type - workspace_id @@ -6342,10 +6462,22 @@ components: Publish a Slack mrkdwn digest. + Pattern selection requirement: include every + selected Pattern whose final status is active at the + end of this automation run, plus every selected + Pattern that changed from active to inactive during + this run (a newly inactive outcome). Exclude + Patterns that were already inactive before this run + and remained inactive. Do not mention excluded + Patterns anywhere in the digest, including + Highlights. If no selected Patterns meet these + criteria, say "No current pattern outcomes." This + requirement overrides conflicting formatting + guidance. + + Include a complete "*Pattern outcomes*" section with - one row for every selected Pattern from the run - report, including created, updated, unchanged, - failed, skipped, and newly inactive outcomes. + one row for every included Pattern. Use this row format exactly: @@ -6356,16 +6488,14 @@ components: If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain - clickable. Do not omit any selected Pattern. If - there are no selected Patterns, say "No pattern - outcomes." + clickable. Do not omit any active selected Pattern. After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly - stands out from this run. Do not introduce new - claims beyond the run report. + stands out among the included active Patterns. Do + not introduce new claims beyond the run report. required: - type - workspace_id @@ -6457,10 +6587,22 @@ components: Publish a Slack mrkdwn digest. + Pattern selection requirement: include every + selected Pattern whose final status is active at the + end of this automation run, plus every selected + Pattern that changed from active to inactive during + this run (a newly inactive outcome). Exclude + Patterns that were already inactive before this run + and remained inactive. Do not mention excluded + Patterns anywhere in the digest, including + Highlights. If no selected Patterns meet these + criteria, say "No current pattern outcomes." This + requirement overrides conflicting formatting + guidance. + + Include a complete "*Pattern outcomes*" section with - one row for every selected Pattern from the run - report, including created, updated, unchanged, - failed, skipped, and newly inactive outcomes. + one row for every included Pattern. Use this row format exactly: @@ -6471,16 +6613,14 @@ components: If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain - clickable. Do not omit any selected Pattern. If - there are no selected Patterns, say "No pattern - outcomes." + clickable. Do not omit any active selected Pattern. After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly - stands out from this run. Do not introduce new - claims beyond the run report. + stands out among the included active Patterns. Do + not introduce new claims beyond the run report. required: - type - workspace_id @@ -6718,10 +6858,22 @@ components: Publish a Slack mrkdwn digest. + Pattern selection requirement: include every + selected Pattern whose final status is active at the + end of this automation run, plus every selected + Pattern that changed from active to inactive during + this run (a newly inactive outcome). Exclude + Patterns that were already inactive before this run + and remained inactive. Do not mention excluded + Patterns anywhere in the digest, including + Highlights. If no selected Patterns meet these + criteria, say "No current pattern outcomes." This + requirement overrides conflicting formatting + guidance. + + Include a complete "*Pattern outcomes*" section with - one row for every selected Pattern from the run - report, including created, updated, unchanged, - failed, skipped, and newly inactive outcomes. + one row for every included Pattern. Use this row format exactly: @@ -6732,16 +6884,14 @@ components: If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain - clickable. Do not omit any selected Pattern. If - there are no selected Patterns, say "No pattern - outcomes." + clickable. Do not omit any active selected Pattern. After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly - stands out from this run. Do not introduce new - claims beyond the run report. + stands out among the included active Patterns. Do + not introduce new claims beyond the run report. required: - type - workspace_id @@ -9157,6 +9307,14 @@ components: nullable: true format: date-time description: Date of organization creation + archived_at: + type: string + nullable: true + format: date-time + deleted_at: + type: string + nullable: true + format: date-time image_rendering_mode: $ref: "#/components/schemas/ImageRenderingMode" required: