An agentic skills framework & software development methodology that works.
test(pi): scope mapping assertions to the table, not whole file
Gaurav Dubeya60dc2ffe5c5
diff --git a/tests/pi/test-pi-extension.mjs b/tests/pi/test-pi-extension.mjsindex 14380e428..d7af9cb2a 100644--- a/tests/pi/test-pi-extension.mjs+++ b/tests/pi/test-pi-extension.mjs@@ -122,7 +122,16 @@ test('pi tools reference documents pi-specific mappings', async () => {assert.equal(existsSync(piToolsPath), true, 'pi-tools.md should exist');const text = await readFile(piToolsPath, 'utf8');- for (const expected of ['subagent', 'pi-subagents', 'Task', 'TODO.md']) {- assert.match(text, new RegExp(expected));- }+ // Assert against the mapping-table rows only. The surrounding prose mentions+ // these same tokens, so matching the whole file would still pass if the table+ // were deleted — the exact regression this test exists to catch.+ const rows = text.split('\n').filter((line) => line.startsWith('|'));+ assert.ok(+ rows.some((row) => /subagent/i.test(row)),+ 'mapping table documents subagent dispatch',+ );+ assert.ok(+ rows.some((row) => /todo|task/i.test(row)),+ 'mapping table documents task tracking',+ );});