Skip to content

feat(mcp): config-file pack selection with env and CLI precedence - #1296

Draft
ohdearquant wants to merge 1 commit into
mainfrom
feat/config-pack-selection
Draft

feat(mcp): config-file pack selection with env and CLI precedence#1296
ohdearquant wants to merge 1 commit into
mainfrom
feat/config-pack-selection

Conversation

@ohdearquant

Copy link
Copy Markdown
Owner

Summary

The discovered configuration file (khive.toml / config.toml) can now declare the pack load list via [runtime].packs, giving deployments KHIVE_PACKS parity without environment plumbing. Resolution precedence in the shared runtime-config path: explicit --pack > non-empty KHIVE_PACKS > [runtime].packs > kg-only default. [packs.<name>] stays backend-assignment only and does not select packs for loading. Precedence is documented in the CLI help source, the configuration example, and the design summary.

Closes #1211.

Testing

  • config_pack_selection_applies_when_no_override_is_set (red before fix: resolved ["kg"] instead of the configured list)
  • env_pack_selection_overrides_config_file
  • cli_pack_selection_overrides_env_and_config_file
  • pack_selection_defaults_to_kg_without_config_or_override
  • clippy -D warnings clean on both changed crates; workspace check clean; fmt clean.

The discovered configuration file can now declare the pack load list via
[runtime].packs. Resolution precedence: explicit --pack, then non-empty
KHIVE_PACKS, then [runtime].packs, then the kg-only default. [packs.<name>]
remains backend assignment only. Precedence is documented in the CLI help,
the full configuration example, and the design summary.

Closes #1211.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(runtime): config-file pack selection — declare the pack load list in discovered configuration (KHIVE_PACKS parity)

1 participant