Observed (usability feedback round 27)
clear-pause-point accepts only --id / --all, while enable-pause-point and pause-point-status accept --file + --line. Passing --file returns:
"Message": "Unknown option for clear-pause-point: --file",
"NextActions": ["Run `uloop clear-pause-point --help` to inspect supported options."]
The tester needed an extra --help round trip (severity 4/10, 2 round trips). A related case: pause-point-status --captured-variables without --id/--file --line answers "NextActions": ["Correct the command arguments and retry."] while the Message already states the exact requirement.
Proposal
Either accept --file + --line on clear-pause-point and build the <file>:<line> id internally, or at minimum make the unknown-option NextActions say Pass --id "<file>:<line>" (the id returned by enable-pause-point) or --all. Align the pause-point-status NextActions with its Message.
Observed (usability feedback round 27)
clear-pause-pointaccepts only--id/--all, whileenable-pause-pointandpause-point-statusaccept--file+--line. Passing--filereturns:The tester needed an extra
--helpround trip (severity 4/10, 2 round trips). A related case:pause-point-status --captured-variableswithout--id/--file --lineanswers"NextActions": ["Correct the command arguments and retry."]while the Message already states the exact requirement.Proposal
Either accept
--file+--lineonclear-pause-pointand build the<file>:<line>id internally, or at minimum make the unknown-option NextActions sayPass --id "<file>:<line>" (the id returned by enable-pause-point) or --all. Align thepause-point-statusNextActions with its Message.