Skip to content

fix(plugin-raven): track SearchConfig's top_k default of 2 #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ypflll merged 1 commit into from
Sep 11, 2026
Merged

fix(plugin-raven): track SearchConfig's top_k default of 2 #25

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion skillcorpus_plugin/plugin-raven/skillsearch_raven/raven-plugin.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,10 @@ weight_local = { type = "number", default = 1.0 }
weight_hub = { type = "number", default = 0.85 }
over_fetch = { type = "integer", default = 2 }
dedup_by = { type = "string", enum = ["name", "qualified_id"], default = "qualified_id" }
top_k = { type = "integer", default = 5 }
# Matches SearchConfig.top_k. Every other host defaults to 2; a 5 here made
# Raven the one host that injected five bodies a turn, because the plugin
# registry fills a declared default for every key the operator leaves out.
top_k = { type = "integer", default = 2 }

# Narrowing. Both the rewriter and the gate need a model; leaving `model`
# empty runs retrieval raw.
Expand Down
Loading