Skip to content

fix: clarify single-variant recommendation semantics - #51

Merged
salim4n merged 1 commit into
mainfrom
fix/single-variant-recommendation-semantics
Jul 1, 2026
Merged

fix: clarify single-variant recommendation semantics#51
salim4n merged 1 commit into
mainfrom
fix/single-variant-recommendation-semantics

Conversation

@salim4n

@salim4n salim4n commented Jul 1, 2026

Copy link
Copy Markdown
Member

Summary

  • Treat one-variant recommendations as baseline measurements instead of comparative wins.
  • Add comparisonAvailable and recommendationKind metadata to trainer recommendations/tradeoff explanations.
  • Normalize exporter recommendations so legacy single-variant report inputs render as baseline with low confidence.
  • Update trainer/exporter docs and IgnitionRAG checklist wording.

Test Plan

  • bun test packages/trainer/src/recommendation.test.ts packages/exporters/src/index.test.ts
  • bun run lint
  • bun run typecheck
  • bun run test
  • bun run build
  • bun run pack:check

Notes

  • Multi-variant Markdown still renders Winner: and keeps the existing comparative summary.
  • Existing winner fields are kept for compatibility; consumers should use comparisonAvailable before showing winner/best language.

@salim4n
salim4n merged commit 21cc530 into main Jul 1, 2026
1 check passed
@salim4n
salim4n deleted the fix/single-variant-recommendation-semantics branch July 1, 2026 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant