[FEATURE] Hint at 'bm cloud workspace' when user runs 'bm workspace'

[groksrc]

Feature Description

When a user types bm workspace (or bm workspace list, etc.), Typer emits a generic No such command 'workspace'. error with no hint that the workspace verbs actually live under bm cloud workspace. Improve this so users get pointed at the right command.

Problem This Feature Solves

bm project is a top-level command, so users reasonably expect bm workspace to be one too — especially since default_workspace in config and bm cloud workspace set-default both refer to workspaces as a first-class concept. Hitting the bare No such command error gives no path forward; users have to read bm --help and notice that workspace is nested under bm cloud.

Current behavior:

$ bm workspace list
Usage: bm [OPTIONS] COMMAND [ARGS]...
Try 'bm --help' for help.
╭─ Error ──────────────────────────────────────────────────────────────────────╮
│ No such command 'workspace'.                                                 │
╰──────────────────────────────────────────────────────────────────────────────╯

Proposed Solution

Simplest implementation: add a top-level workspace Typer command that's just a redirect stub — when invoked (with or without subcommands/args), it prints something like:

'bm workspace' isn't a command. Workspace verbs live under 'bm cloud workspace':
  bm cloud workspace list
  bm cloud workspace set-default <name>

and exits non-zero. This keeps the actual implementation under bm cloud workspace (consistent with other cloud-only verbs like snapshot, api-key) while giving users who guess bm workspace a clear next step.

Alternative Solutions

• Promote bm cloud workspace to top-level bm workspace as a true alias. More invasive and creates inconsistency with other cloud-only verbs — out of scope for this issue.
• Override Typer/Click's no such command handler with fuzzy-match suggestions. More general but a bigger change.

Additional Context

Spun off from #820 — a related discussion noted that the absence of bm workspace is a discoverability gap, but full promotion to top-level is bigger design territory. This issue scopes the fix to the error message only.

Impact

Smaller papercut, but matters for new users / anyone who's spent time in bm project and assumes bm workspace exists.

[claude]

Claude finished @groksrc's task in 3m 32s —— View job • claude/issue-821-20260514-0210 • Create PR ➔

---

Analysis & Implementation

Triage:

• Type: Enhancement / Feature Request
• Priority: Low (usability/discoverability)
• Component: CLI
• Complexity: Simple
• Labels added: enhancement

Todo:

• Analyze issue and create plan
• Explore CLI structure to find where commands are defined
• Locate bm cloud workspace implementation
• Add top-level workspace stub command with redirect hint
• Add workspace to skip_init_commands in app callback
• Register stub in main.py imports and commands/__init__.py
• Write tests for new stub command
• Commit and push changes

What was implemented

Added a top-level bm workspace stub command that catches invocations with or without subcommands and prints a helpful redirect:

'bm workspace' is not a command. Workspace verbs live under 'bm cloud workspace':
  bm cloud workspace list
  bm cloud workspace set-default <name>

Files changed:

• src/basic_memory/cli/commands/workspace.py — new stub command registered on the top-level app
• src/basic_memory/cli/commands/__init__.py — added workspace to package imports
• src/basic_memory/cli/app.py — added workspace to skip_init_commands (avoids spurious DB init)
• src/basic_memory/cli/main.py — added workspace to the import list so it's registered at startup
• tests/cli/test_workspace_commands.py — three new tests covering bare invocation, invocation with subcommand, and content of redirect message

|