Repository navigation
fix(cli): fold and suggest near-miss parameter choice values - #889
Conversation
Closes #888 Choice values such as sigmoid-novelty, KEEP_ALL and Linear now resolve to the declared spelling, and a close typo ends with did you mean…? algorithms run --param writes the canonical value into the spec.
|
Verdict: PASS Ran: risk_gate: T2 (94 lines / 5 files). No CHANGES REQUESTED. AGENT_PAUSE=false. |
|
Verdict: PASS Correctness.
Design. This is the natural counterpart of #876 / #874 / #882 / #884: names already folded, choice values did not. Putting the logic in Tests / docs. New Risk. T2 by |
Closes #888
Algorithm parameter values that declare
choicesnow fold case and-/_the same way parameter names already do (#876).--param sampling=sigmoid-novelty,archive_mode=KEEP_ALL, andmode=Linearresolve to the declared spelling, andalgorithms runwrites that canonical value into the spec. A close typo (novlty) ends withdid you mean 'novelty'?; a nonsense value (greedy) still lists the choices and does not guess.The fold lives in
Param.coerce, soplan/ MCP / plugin hosts inherit it too.Verification
pytest -q tests/test_algorithms.py tests/test_cli_algorithms_run.py tests/test_mcp_algorithm_spec.py tests/test_cli_algorithms_bare.py tests/test_changelog_fragments.pypassed