ktg-plugin-marketplace/plugins/voyage/tests/synthetic/plan-run-A.md

type	plan_version	created	task	slug	run_id	steps
trekplan-synthetic	1.7	2026-05-04	Add --verbose flag to CLI	verbose-flag	A	Add config entry for verbose flag in package.json Define types for verbose mode in types.ts Update parseArgs to recognize --verbose flag Pass verbose context through main entry point Add log level enum (silent, normal, verbose) Wire log level into logger module Replace console.log with logger.info in handler.ts Add tests for parseArgs --verbose recognition Add tests for log level enum mapping Update README with --verbose flag documentation Add CHANGELOG entry for verbose flag Bump package.json minor version Add lint rule blocking direct console usage Run lint and fix new violations Add CLI integration test for --verbose end-to-end Add fixture file for verbose log capture Document verbose output format in docs/cli.md Add jsdoc for new logger API Verify all existing tests pass with verbose disabled Add backward-compat test for legacy quiet behavior Add edge-case test for repeated --verbose flags Add edge-case test for --verbose with --silent collision Update help text to list --verbose flag Add usage example to docs/quickstart.md Verify CI matrix runs on Node 18 and 20 Add npm script for verbose mode debugging Run security audit on logger dependency tree Verify no PII leaks in verbose log output Add manual test checklist to CONTRIBUTING.md Update .gitignore for verbose log dump files Add cleanup logic for stale verbose logs Add unit test for cleanup logic Verify exit code on verbose mode error Add stderr routing for warnings in verbose Add timestamp prefix in verbose log lines Add test for timestamp format Update troubleshooting guide with verbose flag Verify version sync across all docs Add benchmark for verbose log emission cost Document benchmark methodology in PERF.md

Synthetic plan run A — Add --verbose flag to CLI

This fixture represents one synthesized run of /trekplan against a hand-calibrated brief. It is paired with plan-run-B.md for the plan-determinism.test.mjs Jaccard floor (≥ 0.833).

How this fixture is used

tests/synthetic/plan-determinism.test.mjs reads the steps array from this file's frontmatter and computes jaccardSimilarity(stepsA, stepsB). The test asserts the similarity is at or above the SC7 brief threshold (0.833).

This is a SYNTHETIC fixture — it is NOT the output of a real LLM run. The purpose is to exercise the determinism pipeline (parser + jaccard) on a known input pair so regressions in the pipeline are caught even when LLM determinism cannot be cheaply re-measured.

Fixture math

• A has 40 unique step titles
• B has 40 unique step titles
• Intersection (shared titles): 38
• Union: 42
• Jaccard: 38/42 ≈ 0.9047 (well above 0.833 floor)