snappy-koi-58

ROADMAP.md

@@ -337,7 +337,7 @@ Automated + human review threads on [PR #825](https://github.com/gunb-ai/gunbc/p
 
 [PR #901](https://github.com/gunb-ai/gunbc/pull/901) landed typed LLM/GitHub inputs and **named** downstream work as searchable **`closure:<identifier>`** strings in `dsl/extdeps/llm/*.dag`. The three triggers the program still tracks as **explicit closure work** (search these tokens in-repo and in issue bodies):
 
-1. **`rest_typed_response_body` — PARTIAL 2026-05-04 (Row 32 residual slice)** — Typed service inputs; REST `response { 200 => Typed… }` is implemented for the OpenAI ChatCompletion and Anthropic Messages 200-body carriers, and the stale typed-projection receipts `structural_coverage_gap_openai_chat_completion_outputs` / `structural_coverage_gap_anthropic_messages_outputs` are retired with regression witnesses. The Row 32 residual slice typed OpenAI ChatCompletion 200 fidelity fields (`service_tier`, `system_fingerprint`, `logprobs`, `refusal` on the text-bearing message slice, `annotations`, `completion_tokens_details`, `prompt_tokens_details`), typed Anthropic Messages 200 fidelity fields (`container`, citation coproduct, cache-token counters, `service_tier`), and migrated OpenAI Responses from `response { 200 => Json }` to a narrow `OpenAiResponses200Body` proof-of-shape. Remaining response-fidelity residuals stay tracked in `structural_coverage_gap_openai_chat_completion_200_residual`, `structural_coverage_gap_anthropic_messages_200_residual`, and `structural_coverage_gap_openai_responses_200_residual`: OpenAI ChatCompletion tool/function/audio/multimodal response variants and refusal-without-content need a response content/tool/audio coproduct, OpenAI Responses `output_text.logprobs` plus refusal/tool/reasoning/error/multimodal output variants need an output item/content coproduct beyond the current required-text projection carrier, Anthropic thinking/tool/web-search/server-tool content blocks need a content-block coproduct, and Anthropic `container` remains presence-preserved as `Json?` until the container-management response surface has a structural consumer. Broader non-LLM `response { 200 => Json }` operations are separate scope.
+1. **`rest_typed_response_body` — PARTIAL 2026-05-04 (Row 32 residual slice)** — Typed service inputs; REST `response { 200 => Typed… }` is implemented for the OpenAI ChatCompletion and Anthropic Messages 200-body carriers, and the stale typed-projection receipts `structural_coverage_gap_openai_chat_completion_outputs` / `structural_coverage_gap_anthropic_messages_outputs` are retired with regression witnesses. The Row 32 residual slice typed OpenAI ChatCompletion 200 fidelity fields (`service_tier`, `system_fingerprint`, `logprobs`, `refusal` on the text-bearing message slice, `annotations`, `completion_tokens_details`, `prompt_tokens_details`), typed Anthropic Messages 200 fidelity fields (`container`, citation coproduct, cache-token counters, `service_tier`), and migrated OpenAI Responses from `response { 200 => Json }` to a narrow `OpenAiResponses200Body` proof-of-shape. Anthropic Messages 200 response `content[]` now uses `AnthropicMessages200ContentBlock`, a `type`-tagged coproduct for text, thinking, redacted thinking, client tool-use, server tool-use, and web-search tool-result blocks, ratcheted by `anthropic_messages_200_content_blocks_accept_modeled_variants`, `anthropic_messages_200_content_blocks_retire_legacy_text_block_type`, and `anthropic_messages_200_residual_fields_round_trip_representative_wire`; the old thinking/tool/web-search/server-tool variant-pending receipt is narrowed but remains open for `container`, the inner web-search result/error payload, variant-aware typed response projection, and additional current Anthropic beta/server-tool content blocks (`web_fetch_tool_result`, `code_execution_tool_result`, `bash_code_execution_tool_result`, `text_editor_code_execution_tool_result`, `tool_search_tool_result`, `advisor_tool_result`, MCP tool use/result, and `container_upload`) not modeled in this draft. Remaining response-fidelity residuals stay tracked in `structural_coverage_gap_openai_chat_completion_200_residual`, `structural_coverage_gap_anthropic_messages_200_residual`, and `structural_coverage_gap_openai_responses_200_residual`: OpenAI ChatCompletion tool/function/audio/multimodal response variants and refusal-without-content need the pending field-presence coproduct wire contract, OpenAI Responses `output_text.logprobs` plus refusal/tool/reasoning/error/multimodal output variants need an output item/content coproduct beyond the current required-text projection carrier, Anthropic `container` remains presence-preserved as `Json?` until the container-management response surface has a structural consumer, Anthropic web-search result/error payload internals remain `Json` until their array-vs-error-object payload coproduct has a stable structural carrier, Anthropic beta/server-tool content blocks (`web_fetch_tool_result`, `code_execution_tool_result`, `bash_code_execution_tool_result`, `text_editor_code_execution_tool_result`, `tool_search_tool_result`, `advisor_tool_result`, MCP tool use/result, `container_upload`) remain external-spec fidelity debt, modeled `tool_use` now preserves optional `caller` while still needing caller-bound tool-name/input-schema fidelity, modeled `server_tool_use` now uses scaffolded `AnthropicServerToolName` mirrored from Anthropic's generated SDK name literals while still needing per-tool input and optional caller payloads (dissolution shape: fold `name` + `input` into a server-tool-use coproduct keyed by tool name) and spec-watch extension if Anthropic publishes new server_tool_use names, and `llm.Anthropic.Messages.output.content` remains blocked on variant-aware typed REST response projection. Broader non-LLM `response { 200 => Json }` operations are separate scope.
 
 2. **`openai_chat_message_full_coproduct`** — Narrow `OpenAiChatMessage` text row is intentional; full Chat Completions variants (tool role + `tool_call_id`, function role, multimodal `content`) remain gap-carried. Receipt: `structural_coverage_gap_openai_chat_message_full_api_surface` in `dsl/extdeps/llm/openai.dag` (first row carries `closure:openai_chat_message_full_coproduct|…`).
 

dsl/extdeps/llm/anthropic.dag

@@ -32,6 +32,11 @@ data anthropic_assistant_content_block_wire_contract: CoproductWireContract = {
   encoding: InternallyTaggedObject { tag_field: "type", naming: StripPrefixSuffixAndSnakeCase { prefix: "Assistant", suffix: "Block" } }
 }
 
+data anthropic_messages_200_content_block_wire_contract: CoproductWireContract = {
+  coproduct: "AnthropicMessages200ContentBlock",
+  encoding: InternallyTaggedObject { tag_field: "type", naming: StripPrefixSuffixAndSnakeCase { prefix: "Messages", suffix: "Block" } }
+}
+
 // -- Models --------------------------------------------------------
 
 type AnthropicModel
@@ -145,11 +150,28 @@ type AnthropicMessages200Citation
   | WebSearchResultLocation { cited_text: String, encrypted_index: String, title: String?, url: String }
   | SearchResultLocation { cited_text: String, source: String, title: String?, search_result_index: Int, start_block_index: Int, end_block_index: Int }
 
-type AnthropicMessages200TextBlock {
-  type: String
-  text: String
-  citations: List<AnthropicMessages200Citation>?
-}
+// 🟡 SCAFFOLD provider-domain coproduct for Anthropic Messages 200 `content[]`
+// response rows. The outer wire shape is already stable and `type`-tagged, so
+// these arms belong as a coproduct instead of optional coordinates on a text
+// record. Scaffold trigger: `MessagesWebSearchToolResultBlock.content` remains
+// `Json` until the web-search result/error payload gains a structural payload
+// coproduct, and `AnthropicMessages200Body.content/0/text` output projection
+// needs variant-aware typed REST response-path support before this draft can
+// merge.
+type AnthropicMessages200ContentBlock
+  = MessagesTextBlock { text: String, citations: List<AnthropicMessages200Citation>? }
+  | MessagesThinkingBlock { thinking: String, signature: String }
+  | MessagesRedactedThinkingBlock { data: String }
+  | MessagesToolUseBlock { id: String, name: String, input: Json, caller: Json? }
+  | MessagesServerToolUseBlock { id: String, name: AnthropicServerToolName, input: Json, caller: Json? }
+  | MessagesWebSearchToolResultBlock { tool_use_id: String, content: Json }
+
+// 🟡 SCAFFOLD provider-domain enum for Anthropic `server_tool_use.name`
+// values mirrored from Anthropic's generated OpenAPI SDK schema. Scaffold
+// trigger: retire or extend this row when Anthropic publishes additional
+// `server_tool_use.name` values; per-tool input payload typing remains tracked
+// by `server_tool_input_payloads_unmodeled`.
+type AnthropicServerToolName = WebSearch | WebFetch | CodeExecution | BashCodeExecution | TextEditorCodeExecution | ToolSearchToolRegex | ToolSearchToolBm25 | Advisor
 
 type AnthropicMessages200Usage {
   input_tokens: Int
@@ -169,15 +191,12 @@ type AnthropicStopReason = EndTurn | MaxTokens | StopSequence | ToolUse | PauseT
 
 // Message object envelope for POST /v1/messages 200 responses per Anthropic docs
 // (https://docs.anthropic.com/en/api/messages): `id`, `type`, `role`, `content`,
-// `model`, `stop_reason`, optional `stop_sequence`, `usage`. `AnthropicMessages200TextBlock`
-// remains the narrow text slice inside `content[]`; thinking, tool_use, images,
-// and server tools stay gap-carried on the narrower downstream API-surface
-// receipts below.
+// `model`, `stop_reason`, optional `stop_sequence`, `usage`.
 type AnthropicMessages200Body {
   id: String
   type: String
   role: String
-  content: List<AnthropicMessages200TextBlock>
+  content: List<AnthropicMessages200ContentBlock>
   model: String
   stop_reason: AnthropicStopReason
   stop_sequence: String?
@@ -186,7 +205,12 @@ type AnthropicMessages200Body {
 }
 
 data structural_coverage_gap_anthropic_messages_200_residual: List<String> = [
-  "closure:anthropic_messages_200_residual|AnthropicMessages200Body|json_pending:container|AnthropicMessages200TextBlock|variant_pending:thinking|variant_pending:tool_use|variant_pending:redacted_thinking|variant_pending:web_search|variant_pending:server_tool_use|trigger:content block coproduct plus container-management response surface"
+  "closure:anthropic_messages_200_residual|AnthropicMessages200Body|json_pending:container|AnthropicMessages200ContentBlock.MessagesWebSearchToolResultBlock.content|json_pending:web_search_tool_result_payload|trigger:container-management response surface plus web search result/error payload coproduct",
+  "closure:anthropic_messages_200_residual|AnthropicMessages200ContentBlock.MessagesToolUseBlock|residue:client_tool_name_input_and_optional_caller_payloads_not_bound_to_declared_tool_schema|trigger:tool_use response block references declared AnthropicToolDefinition through typed caller carrier and input payload schema",
+  "closure:anthropic_messages_200_residual|AnthropicMessages200ContentBlock.MessagesServerToolUseBlock|residue:server_tool_input_and_optional_caller_payloads_unmodeled|trigger:fold server_tool_use name and input into a server-tool-use coproduct keyed by AnthropicServerToolName",
+  "closure:anthropic_messages_200_residual|AnthropicServerToolName|external_spec_watch:server_tool_use_name_set|trigger:Anthropic publishes additional server_tool_use.name values beyond the generated SDK literal set",
+  "closure:anthropic_messages_200_residual|AnthropicMessages200ContentBlock|variant_pending:web_fetch_tool_result|variant_pending:code_execution_tool_result|variant_pending:bash_code_execution_tool_result|variant_pending:text_editor_code_execution_tool_result|variant_pending:tool_search_tool_result|variant_pending:advisor_tool_result|variant_pending:mcp_tool_use|variant_pending:mcp_tool_result|variant_pending:container_upload|trigger:Anthropic beta/server-tool content-block surface modeled structurally",
+  "closure:anthropic_messages_200_residual|llm.Anthropic.Messages.output.content|blocked:variant_aware_typed_rest_response_projection|path:content/0/text|requires_arm:AnthropicMessages200ContentBlock.MessagesTextBlock|trigger:structural projection metadata carrier lands"
 ]
 
 // Request wire: Messages API expects string `role` + flat `content[]` objects