root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

test(FN-7077): allow dual-scoped mcpServers in settings parity guard

Browse Source 
mcpServers is intentionally shared across global and project scopes (a
global default applies to every project; a project override tailors the
set per project). Add it to the parity guard's intentional shared-keys
allow-list.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
gsxdsm
2026-06-26 17:33:11 -07:00
parent 525953b494
commit 20002e7186
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
packages/core/src/__tests__/settings-parity.test.ts
View File

@@ -377,11 +377,17 @@ describe("settings key parity", () => {
it("only intentional shared keys appear in both global and project scopes", () => {
const projectKeySet = new Set(PROJECT_SETTINGS_KEYS as readonly string[]);
const overlap = (GLOBAL_SETTINGS_KEYS as readonly string[]).filter((key) => projectKeySet.has(key));
// FNXC:SettingsScopeParity 2026-06-26-17:35:
// mcpServers is intentionally dual-scoped (FN-7077, "inject configured MCP servers across
// agent surfaces"): a global default applies to every project while a project override
// tailors the MCP server set per project. Keep it on the intentional shared-keys allow-list
// in GLOBAL_SETTINGS_KEYS order so this parity guard does not flag the deliberate overlap.
expect(overlap).toEqual([
"testMode",
"mergeRequestContractShadowEnabled",
"taskTokenBudget",
"githubTrackingDefaultRepo",
"mcpServers",
"worktrunk",
"owningNodeHandoffPolicy",
]);