* test(#3072): add failing-first coverage for the mcp served catalog 55 input-class rows from the phase test matrix, across four suites: the catalog module over injected readFile/readDir seams, the protocol surface through handleMessage, the install-vs-catalog parity gate, and fast-check properties for uri round-trip, traversal refusal, and pagination partition. src/mcp-catalog.cts lands as a skeleton whose functions throw, so the suites fail on BEHAVIOR rather than on a missing module. The REASON enum is real so tests assert typed codes instead of message prose. Hostile coverage for the one client-controlled path surface (resources/read): dot-dot and backslash traversal, percent- and double-encoded traversal, absolute posix and windows paths, file:// scheme, null byte, symlink escape, unindexed sibling, non-string and empty uri, wrong root segment. IO faults are injected by monkeypatching the seam, never chmod 0o000 - root bypasses mode bits, so a permission-based test silently passes with zero coverage in root CI. Refs #3072 * feat(#3072): serve the mcp catalog as resources and prompts gsd-mcp-server now serves GSD's own content alongside its three tools: the workflow, reference and command tree as MCP resources (resources/list, cursor paginated, and resources/read over gsd://<segment>/<relpath> uris) and the 71 commands/gsd/*.md as MCP prompts keyed by bare command name. initialize advertises resources and prompts, and deliberately does not advertise subscribe or listChanged - the catalog is fixed for a server process lifetime, so declaring a notification we never send would be a lie a host acts on. Composition scope is SHARED, not re-declared. shouldCompose lives in src/mcp-catalog.cts and bin/install.js now imports it instead of carrying its own regex, so the served catalog and the installed file floor cannot drift on what gets composed. Proven behavior-preserving across all 2871 tracked paths plus windows-backslash, absolute and near-miss-prefix cases: zero mismatches. tests/mcp-catalog-parity.test.cjs asserts served text equals the installer composition-stage text over the real tree, with anti-vacuity guards requiring both a marker-bearing workflow and a non-composed file in the comparison set. Two measurements corrected the literal issue text. Composition is scoped to gsd-core/workflows/ only, because a reference or command that documents marker syntax with an unfenced example would otherwise be parsed as carrying a real marker and have that line lossily dropped. And parity is asserted at the composition stage rather than against an emitted runtime tree, since install applies per-runtime path rewrites afterwards and the catalog is host-agnostic, so byte equality with any one runtime would be false by construction. resources/read is the one client-controlled path surface and is guarded in two independent layers: the uri must be an exact key in the prebuilt index, which defeats every traversal string by construction, and the mapped path is then re-checked with validatePath so a symlink planted inside a root after indexing is still refused. Also fixes a real drift defect found while here: SERVER_VERSION was hardcoded 1.7.0 while the package is at 1.9.1. It now resolves lazily from VERSION or package.json, reusing the precedent in runtime-artifact-conversion. Closes #3072 * test(#3072): make the catalog parity gate drive the real installer Review found the parity gate vacuous: it never imported or spawned bin/install.js, and recomputed the installer side with the SAME shouldCompose and composeWorkflow the catalog calls internally. It therefore proved only that src/mcp-catalog.cts is self-consistent. The old row 52 compared shouldCompose against a regex literal frozen in the test file rather than against the installer at all. An inline divergent regex re-added to bin/install.js - the exact regression ADR-1671 asks this gate to catch - would have left the suite green. The gate now spawns a real bin/install.js and compares the composition DECISION, observed as gsd:section marker survival, against what the catalog serves for the same files. Marker presence is the right observable because the installer applies per-runtime path rewrites after composing while the catalog applies none, so raw byte equality between the two surfaces is false by construction and must not be asserted. Sensitivity was proven, not assumed: overlaying the shouldCompose export that bin/install.js imports so it always returns false makes a real spawned install leave autonomous.md's markers in place while the catalog still strips them, and the row 48 assertion diverges. Anti-vacuity guards are kept and extended - the comparison set must be non-empty, must contain a workflow that actually carries markers, must contain a file the predicate declines to compose, and the install must have emitted a non-zero file count. The marker-documenting reference case has no instance in the real tree, so it uses an overlay fixture built with the same technique workflow-fragments-emission.install.test.cjs already uses. Renamed to .install.test.cjs so it lands in the install suite it now belongs to. Refs #3072 * test(#3072): retarget the unknown-method assertion off a now-implemented method tests/gsd-mcp-server.test.cjs used 'resources/read' as its example of an UNKNOWN JSON-RPC method. The served catalog implements that method, so it now returns -32602 (no uri supplied) rather than -32601. The remote runner caught it deterministically on both linux lanes: -32602 !== -32601. The test's intent is still correct and worth keeping, so it is corrected rather than deleted or weakened. It now uses 'resources/subscribe', which the server deliberately does not implement and deliberately does not advertise in initialize's capabilities, because it never sends the corresponding notification. That turns the assertion into a real contract - the advertised capability surface and the implemented method surface agree - instead of an arbitrary method name a future feature could invalidate the same way. Swept the rest of the suite for other assertions pinning the newly implemented methods; this was the only one. Refs #3072 * chore(#3072): backfill changeset PR number 3083 * test(#3072): make the catalog fake fs separator-agnostic for windows CI caught this on windows-latest (22 and 24): every catalog fixture indexed ZERO entries, surfaced by the anti-vacuity guards as 'fixture catalog must actually index resources for this property to mean anything'. Mechanism: makeFakeFs keyed its dirMap/fileMap on POSIX-joined paths (${root}/${rel}), while production buildCatalog looks paths up with path.join, which is backslash-separated on Windows. Every lookup missed, tryReadDir returned null, and the catalog came back empty. Production is NOT at fault and is unchanged. The same CI run proves it: on windows-latest the real-filesystem tests all passed, including 'installer composition decision matches the served catalog for every file in the real installed tree' and the row-51 non-vacuity proof against a real spawned installer. A real Windows fs accepts both separators; the FAKE did not, so the fake was the unfaithful one and is what changed. Lookup keys are now normalized unconditionally with .replace(/\\/g,'/') in readDir and readFile - never path.sep-conditional, never platform-gated. The row-42/43 injected-fault wrappers got the same treatment, since they compared raw production paths against POSIX-literal fixtures. No assertion was weakened, and the anti-vacuity guards that caught this are untouched - they are the reason this surfaced as a loud failure instead of a suite that silently asserted nothing on Windows. Refs #3072 --------- Co-authored-by: sim <sim@local>
142 lines
7.3 KiB
JavaScript
142 lines
7.3 KiB
JavaScript
'use strict';
|
|
/**
|
|
* Tests for the companion MCP server (ADR-1239 Phase C-2, #1681 slice 3a).
|
|
* Pins: initialize handshake, tools/list, tools/call dispatch to the hub +
|
|
* stateIO seam, method-not-found, notification = no response, parse error in
|
|
* runServer, and a full injectable-stream round-trip.
|
|
*/
|
|
|
|
const { test } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const { Readable } = require('node:stream');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
const {
|
|
handleMessage,
|
|
runServer,
|
|
PROTOCOL_VERSION,
|
|
SERVER_NAME,
|
|
} = require('../gsd-core/bin/lib/mcp-server.cjs');
|
|
const { createTempDir, cleanup } = require('./helpers.cjs');
|
|
|
|
test('initialize: returns protocolVersion + capabilities + serverInfo', () => {
|
|
const res = handleMessage({ jsonrpc: '2.0', id: 1, method: 'initialize' });
|
|
assert.strictEqual(res.jsonrpc, '2.0');
|
|
assert.strictEqual(res.id, 1);
|
|
assert.strictEqual(res.result.protocolVersion, PROTOCOL_VERSION);
|
|
assert.ok(res.result.capabilities && res.result.capabilities.tools, 'must advertise tools capability');
|
|
assert.strictEqual(res.result.serverInfo.name, SERVER_NAME);
|
|
});
|
|
|
|
test('tools/list: advertises the 3 interface-point tools', () => {
|
|
const res = handleMessage({ jsonrpc: '2.0', id: 2, method: 'tools/list' });
|
|
const names = res.result.tools.map((t) => t.name);
|
|
assert.deepStrictEqual(names.sort(), ['gsd_invoke_command', 'gsd_read_state', 'gsd_write_state']);
|
|
});
|
|
|
|
test('tools/call gsd_read_state + gsd_write_state: round-trip through the stateIO seam (point 5)', () => {
|
|
const dir = createTempDir();
|
|
try {
|
|
const file = path.join(dir, 'STATE.md');
|
|
const writeRes = handleMessage({ jsonrpc: '2.0', id: 3, method: 'tools/call', params: { name: 'gsd_write_state', arguments: { path: file, content: '# State\n' } } });
|
|
assert.strictEqual(writeRes.result.isError, undefined, 'write must succeed');
|
|
assert.strictEqual(fs.readFileSync(file, 'utf-8'), '# State\n', 'write went through to fs');
|
|
const readRes = handleMessage({ jsonrpc: '2.0', id: 4, method: 'tools/call', params: { name: 'gsd_read_state', arguments: { path: file } } });
|
|
assert.strictEqual(readRes.result.content[0].text, '# State\n', 'read returns the written content');
|
|
} finally {
|
|
cleanup(dir);
|
|
}
|
|
});
|
|
|
|
test('tools/call gsd_invoke_command: dispatches to the command hub (point 1); unknown family returns a hub error, not a crash', () => {
|
|
const res = handleMessage({ jsonrpc: '2.0', id: 5, method: 'tools/call', params: { name: 'gsd_invoke_command', arguments: { family: 'no-such-family', subcommand: 'x' } } }, { cwd: createTempDirClean() });
|
|
// The hub returns a structured result (ok:false unknown-command) surfaced as text content, not a JSON-RPC error.
|
|
assert.strictEqual(res.jsonrpc, '2.0');
|
|
const payload = JSON.parse(res.result.content[0].text);
|
|
assert.strictEqual(payload.ok, false, 'an unknown command dispatches to the hub and returns ok:false');
|
|
assert.strictEqual(res.result.isError, true, 'unknown family surfaces as isError:true (#2102)');
|
|
});
|
|
|
|
// REGRESSION #2102: gsd_invoke_command previously called
|
|
// `commandRoutingHub.createHub()` with NO arguments, which always hits
|
|
// `if (!_cjsRegistry) return makeUnknownCommand()` — every dispatch, valid
|
|
// family or not, returned UnknownCommand. The test above (family:
|
|
// 'no-such-family') could not catch this: an UnknownCommand result is
|
|
// EXACTLY what an unknown family is supposed to return, whether or not
|
|
// dispatch actually worked — it is vacuous by construction. This test proves
|
|
// the fix: a VALID read-only family/subcommand must reach gsd-tools.cjs for
|
|
// real and come back with actual data (not a crash, not UnknownCommand).
|
|
test('tools/call gsd_invoke_command: REGRESSION #2102 — a valid read-only family dispatches for real (not the createHub()-with-no-args UnknownCommand bug)', () => {
|
|
const dir = createTempDir();
|
|
try {
|
|
const res = handleMessage(
|
|
{ jsonrpc: '2.0', id: 9, method: 'tools/call', params: { name: 'gsd_invoke_command', arguments: { family: 'progress', subcommand: 'json' } } },
|
|
{ cwd: dir },
|
|
);
|
|
assert.strictEqual(res.jsonrpc, '2.0');
|
|
assert.notStrictEqual(res.result.isError, true, 'a valid family must not surface as an error');
|
|
const text = res.result.content[0].text;
|
|
const parsed = JSON.parse(text);
|
|
// Fail-first proof: under the bug, this would be
|
|
// { ok: false, kind: 'UnknownCommand', command: 'progress json' } instead
|
|
// of the real progress payload — `percent` would not exist.
|
|
assert.strictEqual(typeof parsed.percent, 'number', 'the real "progress json" command ran (the engine was reached)');
|
|
} finally {
|
|
cleanup(dir);
|
|
}
|
|
});
|
|
|
|
test('tools/call: unknown tool name surfaces a tool error (isError), not a JSON-RPC protocol error', () => {
|
|
const res = handleMessage({ jsonrpc: '2.0', id: 6, method: 'tools/call', params: { name: 'gsd_bogus' } });
|
|
assert.strictEqual(res.result.isError, true);
|
|
assert.match(res.result.content[0].text, /Unknown tool/);
|
|
});
|
|
|
|
test('tools/call: missing tool name is a JSON-RPC invalid-params error', () => {
|
|
const res = handleMessage({ jsonrpc: '2.0', id: 7, method: 'tools/call', params: {} });
|
|
assert.strictEqual(res.error.code, -32602);
|
|
assert.match(res.error.message, /requires string "name"/);
|
|
});
|
|
|
|
// Previously used 'resources/read' as the example unknown method, but that
|
|
// stopped being unknown once the served catalog shipped in #3072.
|
|
// 'resources/subscribe' is DELIBERATELY not implemented and deliberately NOT
|
|
// advertised in initialize's capabilities, because the server never sends the
|
|
// corresponding notification. So this assertion now pins a real contract --
|
|
// the advertised capability surface and the implemented method surface agree
|
|
// -- rather than an arbitrary method name that a future feature could
|
|
// invalidate the same way.
|
|
test('unknown method: JSON-RPC method-not-found (-32601)', () => {
|
|
const res = handleMessage({ jsonrpc: '2.0', id: 8, method: 'resources/subscribe' });
|
|
assert.strictEqual(res.error.code, -32601);
|
|
assert.match(res.error.message, /Method not found/);
|
|
});
|
|
|
|
test('notification (no id): returns null (no response per JSON-RPC)', () => {
|
|
assert.strictEqual(handleMessage({ jsonrpc: '2.0', method: 'initialize' }), null);
|
|
assert.strictEqual(handleMessage({ jsonrpc: '2.0', method: 'notifications/initialized' }), null);
|
|
});
|
|
|
|
test('runServer: line-delimited JSON-RPC round-trip over injectable streams', async () => {
|
|
const input = Readable.from([
|
|
JSON.stringify({ jsonrpc: '2.0', id: 1, method: 'initialize' }) + '\n',
|
|
'not json\n',
|
|
JSON.stringify({ jsonrpc: '2.0', id: 2, method: 'tools/list' }) + '\n',
|
|
]);
|
|
const out = [];
|
|
const output = { write: (s) => { out.push(s); return true; } };
|
|
await runServer({ input, output });
|
|
const joined = out.join('');
|
|
const responses = joined.trim().split('\n').map((l) => JSON.parse(l));
|
|
assert.strictEqual(responses.length, 3);
|
|
assert.strictEqual(responses[0].result.protocolVersion, PROTOCOL_VERSION, 'initialize handled');
|
|
assert.strictEqual(responses[1].error.code, -32700, 'parse error surfaced');
|
|
assert.ok(Array.isArray(responses[2].result.tools), 'tools/list handled');
|
|
});
|
|
|
|
// tiny helper to get a throwaway cwd without polluting the assertion helpers import above
|
|
function createTempDirClean() {
|
|
const os = require('node:os');
|
|
return fs.mkdtempSync(path.join(os.tmpdir(), 'mcp-cwd-'));
|
|
}
|