docs(cli-runtime): use module-form invocation, drop dead shell-alias claim

Same root cause as the workspace/molecule_ai_status.py docstring fix
in this PR: this doc claimed `molecule-monorepo-status` was a usable
shell alias and `from molecule_ai_status import set_status` was a
usable Python import. Both worked under the pre-#87 monolithic-template
layout (where workspace/Dockerfile created the symlink and COPY'd the
modules into /app/) but neither works in current standalone template
images that install the runtime as a wheel:

- `which molecule-monorepo-status` errors — only `a2a-db` and
  `molecule-runtime` are registered console scripts.
- `from molecule_ai_status` raises ImportError — modules are under the
  `molecule_runtime` package now.

Switched both examples to the canonical `python3 -m
molecule_runtime.molecule_ai_status` form (CLI) and `from
molecule_runtime.molecule_ai_status import set_status` (Python). Same
form the runtime ships in its own usage banner, so anyone discovering
this doc gets a runnable example.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docs/agent-runtime/cli-runtime.md

@@ -228,13 +228,13 @@ CLI runtimes keep the same memory tool surface as the Python runtime. When `AWAR
 Any process inside a workspace container (cron jobs, scripts, background tasks) can update the canvas card display:
 
 ```bash
-molecule-monorepo-status "Running weekly SEO audit..."  # show on canvas
-molecule-monorepo-status ""                              # clear when done
+python3 -m molecule_runtime.molecule_ai_status "Running weekly SEO audit..."  # show on canvas
+python3 -m molecule_runtime.molecule_ai_status ""                              # clear when done
 ```
 
 From Python:
 ```python
-from molecule_ai_status import set_status
+from molecule_runtime.molecule_ai_status import set_status
 set_status("Analyzing competitor data...")
 ```