fix(conformance): discard SelectNReq uses Resolution context

[delebedev]

Closes #175

Summary

• Fix 3 wrong fields in discard SelectNReq: context (Discard→Resolution), listType (Static→Dynamic), optionContext (unset→Resolution)
• Wire evidence: discard prompts use same context/listType/optionContext as legend-rule, only sourceId differs

Test plan

• New test: discard SelectNReq uses Resolution context and Dynamic listType — verifies all 3 fixed fields + existing correct fields
• LegendRuleTest — still passes (shared builder path)
• BundleBuilderTest — 14/14 pass

🤖 Generated with Claude Code

[github-actions]

Test Results

  227 files  ±0  227 suites  ±0   2m 14s ⏱️ -9s
  996 tests +1  964 ✅ +1   32 💤 ±0  0 ❌ ±0 
1 778 runs  +2  978 ✅ +1  800 💤 +1  0 ❌ ±0 

Results for commit 0ecfa08. ± Comparison against base commit c58f0b2.

[github-actions]

CI Report — Gate

Tests: 816/816 passed (189 skipped)

Coverage: 10.5% (615/5852 lines)

Module	Coverage	Lines
tooling	🔴 11%	615/5852

Slow tests (>3s): 1

• InstanceIdReallocTest.Limbo grows across multiple plays (5.6s)

[delebedev]

@claude please review this ralph PR

[claude]

Claude finished @delebedev's task in 42s —— View job

---

PR Review

• Gather context
• Read changed files
• Provide review feedback

---

Overall: LGTM with one minor doc nit. The fix is correct, minimal, and well-evidenced.

What changed

buildSelectNReq previously branched on isLegendRule for context, listType, and optionContext. Wire evidence shows discard and legend-rule use identical values for all three fields — only the prompt shape and sourceId differ. The fix:

1. context: Discard_a163 → Resolution_a163 (unconditional)
2. listType: Static → Dynamic (unconditional)
3. optionContext: moved out of the isLegendRule branch → unconditional

The diff is clean and the isLegendRule variable is still correctly used for prompt/sourceId differentiation.

One nit: stale KDoc

RequestBuilder.kt:139–142 has a doc comment that now documents the old (wrong) behavior:

 * Context/listType vary by prompt type:
 * - `legend_rule`: context=Resolution, listType=Dynamic
 * - `choose_cards` (discard): context=Discard, listType=Static

This should be updated to reflect that both paths use Resolution/Dynamic/optionContext=Resolution. Fix this →

Test coverage

The new test at BundleBuilderTest.kt:288 is well-structured — it exercises the discard path end-to-end via RequestBuilder.buildSelectNReq and asserts all 3 fixed fields plus the stable ones (idType, validationType, minSel, maxSel, idsCount, promptId). This is the right level of coverage.

CI is green: 996 tests, +1 new, 0 failures.