| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(gemini): do not send thinkingConfig to gemini-3.5-flash-lite `default_thinking_config_for` matches on substrings, so `contains("gemini-3.5-flash")` also caught `gemini-3.5-flash-lite`. Verified against the live API: gemini-3.5-flash + thinkingBudget:0 -> 200 gemini-2.5-flash-lite + thinkingBudget:0 -> 200 gemini-3.5-flash-lite + thinkingBudget:0 -> 400 invalid argument gemini-3.5-flash-lite field omitted -> 200 So every call on 3.5-flash-lite would have failed. 2.5 is deliberately left alone — narrowing it too would re-enable its default thinking and let hidden thought tokens truncate strict JSON, which is why this function exists. The e2e handoff smoke test set MODEL_B to gemini-3.5-flash-lite while its `gemini_call` helper hardcodes thinkingBudget=0, so that test would have failed at the session-2 call. MODEL_B stays 2.5-flash-lite. Adds a regression test asserting 3.5-lite omits the field and 2.5-lite still sends it; it fails on the original predicate and passes here. Also corrects the retirement date in the changelog entry: the Gemini API table lists October 16 2026, not the October 20 Vertex/Agent Platform date, and ai-memory talks to the Gemini API. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> | 20 天前 | |
fix(marker): a capture-only marker no longer resets scope to default (#668) A .ai-memory.toml whose only content is a [capture] section shadowed an ancestor marker's workspace/project (and the other forwarded settings) because resolution used the nearest marker unconditionally — so a subdirectory marker added just to exclude paths from capture silently dropped the outer scope, filing pages under default/basename. A pure capture-only marker is now SCOPE/SETTINGS-TRANSPARENT: scope, project_strategy, drop_subagent_captures, default_global, and the [briefing] keys resolve from the nearest ancestor marker that declares at least one of them; [capture]/ignore_paths still comes from the nearest marker. Fixed across all three front doors — shell (hooks/_lib.sh), native (marker.rs/hook_capture.rs), and the generated TS integrations (shared applyMarkerParams / findSettingsMarker, all five adapters). The audit's premise that the TS adapters don't resolve scope was wrong; they do, via applyMarkerParams. Closes #668 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MDbhmszrjG9s5MrPrTuNtm | 1 天前 | |
fix(wrapper): auto-detect podman container engine (#636) | 4 天前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 20 天前 | ||
| 1 天前 | ||
| 4 天前 |