docs: stop referencing the removed ably-interactive wrapper

Sweep user-facing and architecture references now that the wrapper binary is
gone and ably interactive handles Ctrl+C in-process:

- env-vars: ABLY_HISTORY_FILE example uses `ably interactive`; reword the note
  (HistoryManager already defaults to ~/.ably/history); update coupled unit test
- Troubleshooting/Debugging: accurate Ctrl+C guidance; no wrapper run-commands
- Exit-Codes: reframe the exit-code consumer as a host session restart loop
- Interactive-REPL: status note marking the bash-wrapper design as superseded
- Project-Structure: drop the deleted bin/ably-interactive(.ps1) tree entries
- manual tests: run `node bin/run.js interactive`; keep the exit-42 contract

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

Author: umair-ably

docs/Debugging.md

@@ -57,7 +57,7 @@ Refer to [Testing.md](Testing.md) for how to run specific tests.
     ```
 *   **Terminal Diagnostics:** Enable terminal state logging for TTY/stdin/stdout issues:
     ```bash
-    TERMINAL_DIAGNOSTICS=1 ably-interactive
+    TERMINAL_DIAGNOSTICS=1 ably interactive
     ```
 *   **Check Configuration:** Use `ably config show` to view stored credentials or `ably config path` to find the config file location.
 *   **Override Configuration:** Use environment variables to override config for testing:

docs/Exit-Codes.md

@@ -6,11 +6,11 @@ This document describes the exit codes used by the Ably CLI, particularly in int
 
 ### 0 - Success
 - Normal successful completion of a command
-- Clean exit after user types `exit` command (in non-wrapper mode)
+- Clean exit after the user types `exit` (when not running under a session restart loop)
 
 ### 42 - User Exit (Interactive Mode)
-- Special exit code used when user types `exit` in interactive mode with wrapper
-- Signals to the wrapper script (`bin/ably-interactive`) to terminate the loop
+- Special exit code emitted when the user types `exit` while running under a session restart loop (`ABLY_WRAPPER_MODE=1`)
+- Signals the restart loop (e.g. the Ably terminal server's session entrypoint) to stop, rather than treating the exit as a crash to relaunch
 - Defined as `Interactive.EXIT_CODE_USER_EXIT`
 
 ### 130 - SIGINT (Ctrl+C)
@@ -40,25 +40,24 @@ This document describes the exit codes used by the Ably CLI, particularly in int
 - Shows "⚠ Force quit" message
 - Bypasses normal cleanup
 
-## Wrapper Script Behavior
+## Session Restart Loop Behavior
 
-The `bin/ably-interactive` wrapper script uses these exit codes to determine whether to restart the interactive shell:
+`ably interactive` is a normal command and handles Ctrl+C in-process — the CLI no longer ships a separate `ably-interactive` wrapper binary. A host that wants the interactive shell to survive a force-quit (for example the Ably terminal server, which keeps a browser session alive) can wrap `ably interactive` in a small restart loop, set `ABLY_WRAPPER_MODE=1`, and key the loop off these exit codes:
 
-- **Exit code 42**: User typed 'exit' - terminate the wrapper loop
-- **Exit code 130**: SIGINT - restart the shell (unless double Ctrl+C)
-- **Exit code 0**: Normal exit - terminate the wrapper loop
-- **Other codes**: Show error message and restart after delay
+- **Exit code 42**: User typed 'exit' - stop the loop
+- **Exit code 0**: Normal exit - stop the loop
+- **Exit code 130**: Force quit (double Ctrl+C) - relaunch the shell
+- **Other codes**: Show an error and relaunch after a short delay
 
 ## Implementation Details
 
 Exit codes are handled in:
 - `src/commands/interactive.ts`: Sets exit code 42 for user exit
 - `src/utils/sigint-exit.ts`: Handles SIGINT behavior and exit code 130
-- `bin/ably-interactive`: Wrapper script that interprets exit codes
 
 ---
 
 ## Related
 
-- [Interactive-REPL.md](Interactive-REPL.md) — Architecture and wrapper script design
+- [Interactive-REPL.md](Interactive-REPL.md) — Interactive mode architecture
 - [Troubleshooting.md](Troubleshooting.md#interactive-mode-issues) — Common interactive mode issues

docs/Interactive-REPL.md

@@ -33,6 +33,15 @@ If there are any existing libraries that we can depend on to enable this functio
 
 ## Execution Plan
 
+> **Status note (superseded design).** This section documents the original
+> bash-wrapper design. The wrapper binary (`bin/ably-interactive`) has since been
+> retired: `ably interactive` now handles Ctrl+C in-process (a single Ctrl+C
+> interrupts the running command and returns to the prompt), and the CLI ships a
+> single `ably` bin. The auto-restart-on-force-quit behaviour is now optional and
+> owned by whichever host wants it — e.g. the Ably terminal server wraps
+> `ably interactive` in a small restart loop (keyed off exit codes 42/130, with
+> `ABLY_WRAPPER_MODE=1`). The historical design below is kept for context.
+
 ### Overview
 
 This execution plan implements an interactive REPL mode using a bash wrapper approach with inline command execution. The design prioritizes simplicity, natural Ctrl+C handling, and seamless user experience.
@@ -414,8 +423,8 @@ This plan delivers a responsive interactive shell with natural Ctrl+C handling a
 
 ## Related
 
-- [Exit Codes](Exit-Codes.md) — Exit codes used in interactive mode and wrapper script behavior
+- [Exit Codes](Exit-Codes.md) — Exit codes used in interactive mode
 - [Troubleshooting](Troubleshooting.md#interactive-mode-issues) — Common interactive mode issues (unexpected exits, Ctrl+C, history)
 - [Auto-completion](Auto-completion.md) — Shell tab completion setup for commands and flags
 - [Testing Guide](Testing.md) — Subprocess and TTY test layers for interactive mode
-- [Project Structure](Project-Structure.md) — Repository layout including `src/commands/interactive.ts` and `bin/ably-interactive`
+- [Project Structure](Project-Structure.md) — Repository layout including `src/commands/interactive.ts`

docs/Project-Structure.md

@@ -8,8 +8,6 @@ This document outlines the directory structure of the Ably CLI project.
 /
 ├── assets/                     # Static assets (e.g. CLI screenshot)
 ├── bin/                        # Executable scripts
-│   ├── ably-interactive        # Bash wrapper for interactive mode (restarts on Ctrl+C)
-│   ├── ably-interactive.ps1    # PowerShell equivalent for Windows
 │   ├── dev.cmd                 # Development run script (Windows)
 │   ├── development.js          # Development run script (Unix)
 │   ├── run.cmd                 # Production run script (Windows)
@@ -175,5 +173,5 @@ This document outlines the directory structure of the Ably CLI project.
 - [Development Stage](Environment-Variables/Development-Usage.md) Env Variables — Development, testing, debugging, and internal env variables. For user-facing variables, run `ably env`.
 - [Testing Guide](Testing.md) — Test layers and directory layout (`test/unit/`, `test/e2e/`, `test/tty/`, `test/integration/`)
 - [Debugging Guide](Debugging.md) — Debugging tips for CLI development
-- [Interactive REPL](Interactive-REPL.md) — Architecture of `src/commands/interactive.ts` and `bin/ably-interactive`
+- [Interactive REPL](Interactive-REPL.md) — Architecture of `src/commands/interactive.ts`
 - [Exit Codes](Exit-Codes.md) — Exit codes handled in `src/commands/interactive.ts` and `src/utils/sigint-exit.ts`

docs/Troubleshooting.md

@@ -226,8 +226,8 @@ Property 'x' does not exist on type 'Y'
 **Solution**:
 - Check the exit code to understand what happened (see [Exit Codes documentation](Exit-Codes.md) and [Development Stage Env Variables](Environment-Variables/Development-Usage.md) for interactive mode env vars)
 - Common exit codes:
-  - Exit code 0: Wrapper (`ably-interactive`) terminated normally
-  - Exit code 42: User typed 'exit' in interactive mode (signals wrapper to terminate)
+  - Exit code 0: Interactive shell exited normally
+  - Exit code 42: User typed 'exit' in interactive mode (signals a session restart loop to stop)
   - Exit code 130: SIGINT/Ctrl+C (double Ctrl+C or force quit)
   - Exit code 143: SIGTERM received
 
@@ -236,10 +236,9 @@ Property 'x' does not exist on type 'Y'
 **Problem**: Ctrl+C doesn't interrupt commands or behaves unexpectedly.
 
 **Solution**:
-- Use the wrapper script `ably-interactive` for better Ctrl+C handling
-- Single Ctrl+C should interrupt running command and return to prompt
+- Single Ctrl+C interrupts the running command and returns to the prompt
+- At an empty prompt, single Ctrl+C prints `^C`; type `exit` (or Ctrl+D) to leave the shell
 - Double Ctrl+C (within 500ms) force quits with exit code 130
-- If running without wrapper, Ctrl+C may exit the entire shell
 
 ### Command History Not Persisting
 

src/data/env-vars.ts

@@ -235,17 +235,17 @@ const ABLY_HISTORY_FILE = new EnvVarEntry(
   "File path",
   "~/.ably/history",
   null,
-  ["ably-interactive"],
+  ["ably interactive"],
   "Override the location of the interactive mode command history file.",
   new Example([
     `export ABLY_HISTORY_FILE="/path/to/custom/history"`,
-    `ably-interactive`,
+    `ably interactive`,
   ]),
   [
     new DetailSection("", [
       {
         kind: "note",
-        text: "Auto-set by the `ably-interactive` shell wrapper; only set manually for a custom location.",
+        text: "Defaults to `~/.ably/history`; only set this to use a custom location.",
       },
     ]),
   ],