Ed Zynda a95714a22d fix(kit): resolve system-prompt file path before PromptBuilder (#25) ...

When system-prompt was a file path (via --system-prompt, config entry,
or SDK Options.SystemPrompt), the path string itself was used as the
base prompt because config.LoadSystemPrompt only ran later in
BuildProviderConfig — by which point viper had been overwritten with
the path-augmented composed text. The LLM received the path instead of
the prompt contents.

- Call config.LoadSystemPrompt on the raw viper value in New() before
  PromptBuilder composes runtime context (AGENTS.md / skills / date).
- Add HasCustomSystemPrompt() and GetSystemPromptSource() so SDK callers
  can inspect prompt state without reaching into viper.
- Display 'System Prompt loaded: <source>' at startup in CLI and TUI
  modes, paralleling the per-server 'MCP server loaded' notice.
- Add regression tests covering both file-path and inline prompt paths.

Fixes #25

2026-05-08 10:39:14 +03:00

..

extensions/test

fix(test): add return after t.Fatal to silence SA5011 nil-deref warnings

2026-04-01 21:24:02 +03:00

kit

fix(kit): resolve system-prompt file path before PromptBuilder (#25)

2026-05-08 10:39:14 +03:00