Kjell Tore Guttormsen 7a90d348ad feat(voyage)!: marketplace handoff — rename plugins/ultraplan-local to plugins/voyage [skip-docs]

Session 5 of voyage-rebrand (V6). Operator-authorized cross-plugin scope.

- git mv plugins/ultraplan-local plugins/voyage (rename detected, history preserved)
- .claude-plugin/marketplace.json: voyage entry replaces ultraplan-local
- CLAUDE.md: voyage row in plugin list, voyage in design-system consumer list
- README.md: bulk rename ultra*-local commands -> trek* commands; ultraplan-local refs -> voyage; type discriminators (type: trekbrief/trekreview); session-title pattern (voyage:<command>:<slug>); v4.0.0 release-note paragraph
- plugins/voyage/.claude-plugin/plugin.json: homepage/repository URLs point to monorepo voyage path
- plugins/voyage/verify.sh: drop URL whitelist exception (no longer needed)

Closes voyage-rebrand. bash plugins/voyage/verify.sh PASS 7/7. npm test 361/361.

2026-05-05 15:37:52 +02:00

2 KiB

Raw Blame History

trekreview determinism fixtures

Synthetic fixtures for the Jaccard-similarity determinism test in tests/lib/review-determinism.test.mjs.

What's here

review-run-A.md — synthetic review with 5 findings on a fictional JWT auth task
review-run-B.md — same fictional task, "re-reviewed" — same 5 findings as A plus 1 extra (a placeholder TODO that A missed)

Construction

Run A's finding-IDs are a strict subset of Run B's (A ⊂ B), so:

Intersection: |A ∩ B| = 5
Union: |A ∪ B| = 6
Jaccard: 5 / 6 = 0.833… (above the 0.70 SC4 threshold from brief.md)

Each ID is a real 40-char SHA1 computed via lib/parsers/finding-id.mjs: sha1(file:line:rule_key). Don't hand-edit the IDs — recompute via the helper if you change the underlying (file, line, rule_key) triplet, or both fixtures will fall out of sync.

Why synthetic for v1.0

Hand-curated for v1.0. Edit JSON IDs directly to test new Jaccard scenarios. Real-LLM determinism measurement is deferred to v1.1 once /trekreview has produced enough real outputs to capture as fixtures.

These fixtures prove the Jaccard PIPELINE works given a known input — they do NOT measure real LLM determinism. The brief's SC4 (Jaccard ≥ 0.70 across two runs) is verified at the pipeline level today; capturing real LLM runs to verify the model-level claim is open work for v1.1.

Adding a new scenario

Pick (file, line, rule_key) triplets — rule_key must be one of the 12 keys in lib/review/rule-catalogue.mjs.

Compute IDs via:

node -e "import('./lib/parsers/finding-id.mjs').then(({computeFindingId}) => console.log(computeFindingId('lib/foo.mjs', 42, 'SECURITY_INJECTION')))"

Add the IDs to findings: block-style YAML in frontmatter and to ### <id> subsections in the body.
Run node lib/validators/review-validator.mjs --json tests/fixtures/trekreview/review-run-X.md to confirm the fixture validates.
Update tests/lib/review-determinism.test.mjs if you want a new assertion.

2 KiB Raw Blame History Unescape Escape