You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Fix multimodal chat content handling
* Harden multimodal validation and guardrail handling
* Fix multimodal schema and null-content handling
* Update contract goldens for tool-call null content
* Tighten multimodal schemas and request handling
* Guard multimodal rewrite allocations
* Fix responses schemas and multimodal guardrail merges
* Preserve tool calls and adapter request options
* Adjust README and CLAUDE guidance
* Preserve responses tool controls in JSON
* Fix responses JSON roundtrip and anthropic bounds
* Harden multimodal guardrail and responses merges
* Unify ContentPart types and add input_audio test coverage
Eliminate duplicate ResponsesContentPart struct (identical to ContentPart)
and use ContentPart everywhere. Add 11 tests covering input_audio
unmarshaling, normalization, validation, and mixed content scenarios.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Fix multimodal guardrail and responses adaptation
* Clean up duplicate code, dead code, and add test coverage
- Deduplicate isNullEquivalentContent (was two identical functions)
- Remove unreachable trailing loop in applySystemMessagesToMultimodalChat
- Remove unused anthropicMessageContentBlock type alias
- Simplify single-variable var block
- Add test for input_text → text normalization in Anthropic conversion
- Add test for maxContentParts overflow guard
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Enable dupl linter and deduplicate GetConversation logic
Add dupl linter (threshold 150, excluded for test files) to catch
duplicate code blocks. Extract shared conversation thread-walking
logic into buildConversationThread helper used by both MongoDB and
PostgreSQL readers.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Replace ResponsesInputItem with discriminated union ResponsesInputElement
The old ResponsesInputItem only modeled chat messages (role + content),
forcing function_call and function_call_output items through untyped
map[string]interface{} handling. The new ResponsesInputElement struct
explicitly represents all three input variants via a Type discriminator,
with typed fields for each shape. JSON unmarshal now produces
[]ResponsesInputElement instead of []interface{}, eliminating
map[string]interface{} from the hot path.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CLAUDE.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,9 +164,8 @@ Full reference: `.env.template` and `config/config.yaml`
164
164
165
165
After completing any code change, routinely check whether documentation needs updating. This applies to all three documentation layers:
166
166
167
-
1.**README files** (`README.md`, `helm/README.md`, `tests/contract/README.md`) — Update when adding/removing features, changing setup steps, modifying CLI flags, or altering configuration options.
168
-
2.**In-code documentation** (Go doc comments on exported types, functions, interfaces) — Update when changing public APIs, adding new exported symbols, or modifying function signatures/behavior.
169
-
3.**Mintlify / technical docs** (`docs/` directory) — Update `docs/advanced/*.mdx` pages when changing configuration options or guardrails behavior. Update `docs/adr/` when making significant architectural decisions. Update `docs/plans/` if implementation diverges from existing plans. Check `docs.json` if new pages need to be added to the navigation.
167
+
1.**In-code documentation** (Go doc comments on exported types, functions, interfaces) — Update when changing public APIs, adding new exported symbols, or modifying function signatures/behavior.
168
+
2.**Mintlify / technical docs** (`docs/` directory) — Update `docs/advanced/*.mdx` pages when changing configuration options or guardrails behavior. Update `docs/adr/` when making significant architectural decisions. Update `docs/plans/` if implementation diverges from existing plans. Check `docs.json` if new pages need to be added to the navigation.
170
169
171
170
**When to update:**
172
171
- Adding a new provider, endpoint, config option, or feature
0 commit comments