test(cli): add Jest test suite for PromptKit CLI

[abeltrano]

Fixes #147

Adds comprehensive automated test coverage for the PromptKit CLI module.

What's included

53 tests across 4 suites — all passing:

Suite	Tests	Coverage
manifest.test.js	19	loadManifest, getTemplates, all getters, resolveTemplateDeps
assemble.test.js	18	stripFrontmatter, loadComponent, full assembly, param substitution
launch.test.js	9	detectCli priority (mocked child_process), copyContentToTemp
cli.test.js	7	list, assemble, --version, error handling (integration via subprocess)

Infrastructure

• Jest added as dev dependency
• Test scripts: npm test and npm run test:coverage
• Test fixtures in cli/__tests__/fixtures/ — minimal mock persona, protocols, format, taxonomy, templates, and manifest
• CI workflow (.github/workflows/cli-tests.yml) — runs on push/PR when cli/ changes
• coverage/ added to .gitignore

How to run

cd cli && npm ci && npm test

[abeltrano]

Abandoning in favor of generating test cases from newly added validation.md in #145

[abeltrano]

Suggestion: Use data-driven tests instead of hardcoded component names

The tests currently hardcode specific component names (systems-engineer, anti-hallucination, investigate-bug, etc.) throughout all four test files. This means tests will break whenever components are added, renamed, or removed from the manifest — creating an ongoing maintenance burden.

Recommended approach

Iterate over the manifest dynamically so tests automatically cover every component with zero updates needed when the library evolves:

Before (brittle):

test("finds persona by name", () => {
  const persona = getPersona(manifest, "systems-engineer");
  expect(persona).toBeDefined();
  expect(persona.path).toBe("personas/systems-engineer.md");
});

After (data-driven):

for (const p of manifest.personas) {
  test("persona '\' resolves to an existing file", () => {
    const found = getPersona(manifest, p.name);
    expect(found).toBeDefined();
    expect(fs.existsSync(path.join(repoRoot, found.path))).toBe(true);
  });
}

This pattern applies across all test files:

• manifest.test.js — iterate manifest.personas, all protocol categories, manifest.formats, manifest.taxonomies for lookup tests; iterate getTemplates(manifest) for resolveTemplateDeps
• assemble.test.js — loadComponent should verify all manifest-referenced paths load and strip headers; assemble() should verify structural correctness for every template (or at least one per category)
• launch.test.js — copyContentToTemp should load the manifest from the temp dir and verify all referenced paths exist, rather than checking hardcoded filenames
• cli.test.js — use list --json output to pick a template name dynamically instead of hardcoding investigate-bug

Additional gap

resolveTemplateDeps is tested for missing protocols but not for missing persona, format, or taxonomy — those edge cases should be added.