Integrate exhaustiveness metadata into solution payload for printSolutionAndAssert APIs

[Copilot]

printSolutionAndAssert and printSolutionAndAssertWithMinimum previously split “exhaustiveness wording” (Bool) from the optional solution payload. This change folds that flag into the solution payload itself so “what to show” and “how to phrase it” are carried together.

• API shape change

  • Updated both functions to accept:
    • Maybe (Bool, ArticleToUse, String)
  • Removed the separate Bool parameter from both signatures.

• Call-site adaptation

  • extendedMultipleChoice now injects mentionExhaustiveness into the optional solution tuple before calling printSolutionAndAssertWithMinimum.
  • singleChoice now passes (False, articleToUse, solutionString) to preserve current wording behavior.

• Behavior preservation

  • Output strings and grading/refusal flow remain unchanged; this is a parameter-model refactor to align semantics at the API boundary.

-- before
printSolutionAndAssertWithMinimum
  :: MinimumThreshold
  -> Bool
  -> Maybe (ArticleToUse, String)
  -> Rational
  -> Rated m

-- after
printSolutionAndAssertWithMinimum
  :: MinimumThreshold
  -> Maybe (Bool, ArticleToUse, String)
  -> Rational
  -> Rated m

[Copilot]

Pull request overview

This PR refactors the solution-printing API so the exhaustiveness flag travels with the optional solution payload, keeping display content and phrasing metadata together.

Changes:

• Updates printSolutionAndAssert and printSolutionAndAssertWithMinimum to accept Maybe (Bool, ArticleToUse, String).
• Adapts extendedMultipleChoice and singleChoice call sites to construct the new tuple shape while preserving existing behavior.
• Updates Haddock comments for the revised parameter model.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Addressed in 32d4f0e.