fix: add curated suggestions for open-url and close-session (#1175)

Last night's help-conformance benchmark showed agents guessing
open-url and close-session with no "did you mean" hint (the
Levenshtein fallback doesn't cover either token — both exceed the
edit-distance threshold for their length). Add curated entries
pointing them at `open <url>` and `close`.

Author: thymikee

src/cli/parser/__tests__/command-suggestions.test.ts

@@ -109,6 +109,26 @@ test('get-text, gettext, and get_text suggest get text', () => {
   }
 });
 
+test('open-url suggests open <url>', () => {
+  assert.throws(
+    () => parseArgs(['open-url', 'https://example.com']),
+    (error: unknown) =>
+      error instanceof AppError &&
+      error.code === 'INVALID_ARGS' &&
+      error.message === 'Unknown command: open-url. Did you mean open <url>?',
+  );
+});
+
+test('close-session suggests close', () => {
+  assert.throws(
+    () => parseArgs(['close-session']),
+    (error: unknown) =>
+      error instanceof AppError &&
+      error.code === 'INVALID_ARGS' &&
+      error.message === 'Unknown command: close-session. Did you mean close?',
+  );
+});
+
 test('screencap and capture suggest screenshot', () => {
   for (const guess of ['screencap', 'capture']) {
     assert.throws(

src/cli/parser/command-suggestions.ts

@@ -38,6 +38,8 @@ const COMMAND_ALIAS_SUGGESTIONS: Record<string, CommandAliasSuggestion> = {
   'get-text': { command: 'get', example: 'get text' },
   gettext: { command: 'get', example: 'get text' },
   get_text: { command: 'get', example: 'get text' },
+  'open-url': { command: 'open', example: 'open <url>' },
+  'close-session': { command: 'close', example: 'close' },
 };
 
 export function listCommandAliasSuggestionEntries(): Array<[string, CommandAliasSuggestion]> {