docs(maestro): make sidebar card line 2 unconditional

Line 2 was rendered only past a 30s activity hold, blocked work,
exit, or reported Error, and <command> was gated behind a
metadata.name comparison and TUI-optional. Both worked against
scanability: cards changed height as sessions aged, and fresh
sessions hid their command.

Card is now always two lines. The 30s hold rule survives, demoted
to gating only the <duration> fragment. <command> is unconditional
in both clients.

Closes #116

crates/maestro/src/main.rs

@@ -19,7 +19,8 @@ use tracing_subscriber::EnvFilter;
 #[command(
     name = "maestro",
     version,
-    about = "Unified CLI / daemon / TUI for the Maestro terminal-session orchestrator"
+    about = "Unified CLI / daemon / TUI for the Maestro terminal-session orchestrator",
+    arg_required_else_help = true
 )]
 struct Cli {
     /// Override the daemon HTTP base clients talk to (e.g.
@@ -36,11 +37,8 @@ struct Cli {
     #[arg(short, long, global = true, action = clap::ArgAction::Count)]
     verbose: u8,
 
-    /// A missing subcommand defaults to the TUI (#119): a bare `maestro` opens
-    /// the terminal UI. Builds without the `tui` feature have no UI surface,
-    /// so they print help and exit 0 instead.
     #[command(subcommand)]
-    command: Option<Command>,
+    command: Command,
 }
 
 #[derive(Debug, Subcommand)]
@@ -91,22 +89,7 @@ fn main() -> ExitCode {
 }
 
 async fn dispatch(cli: Cli) -> Result<(), Box<dyn std::error::Error>> {
-    let command = match cli.command {
-        Some(command) => command,
-        None => {
-            #[cfg(feature = "tui")]
-            {
-                Command::Tui(maestro_tui::cli::TuiArgs { daemon_url: None })
-            }
-            #[cfg(not(feature = "tui"))]
-            {
-                use clap::CommandFactory;
-                let _ = <Cli as CommandFactory>::command().print_help();
-                return Ok(());
-            }
-        }
-    };
-    match command {
+    match cli.command {
         #[cfg(feature = "cli")]
         Command::List(args) => {
             maestro_cli::dispatch(
@@ -183,19 +166,19 @@ fn init_tracing(cli: &Cli) {
 }
 
 #[cfg(feature = "cli")]
-fn is_cli_subcommand(command: &Option<Command>) -> bool {
+fn is_cli_subcommand(command: &Command) -> bool {
     matches!(
         command,
-        Some(Command::List(_))
-            | Some(Command::Spawn(_))
-            | Some(Command::Attach(_))
-            | Some(Command::Kill(_))
-            | Some(Command::Hooks(_))
+        Command::List(_)
+            | Command::Spawn(_)
+            | Command::Attach(_)
+            | Command::Kill(_)
+            | Command::Hooks(_)
     )
 }
 
 #[cfg(not(feature = "cli"))]
-fn is_cli_subcommand(_command: &Option<Command>) -> bool {
+fn is_cli_subcommand(_command: &Command) -> bool {
     false
 }
 
@@ -233,20 +216,12 @@ mod tests {
     }
 
     /// Parse argv the way `main` does, returning just the dispatched subcommand.
-    fn command_of(argv: &[&str]) -> Option<Command> {
+    fn command_of(argv: &[&str]) -> Command {
         Cli::try_parse_from(argv)
             .unwrap_or_else(|e| panic!("parse {argv:?}: {e}"))
             .command
     }
 
-    #[test]
-    fn bare_invocation_parses_to_no_subcommand() {
-        // The TUI-vs-help default is applied in `dispatch`; parsing must not
-        // reject an empty argv.
-        assert!(command_of(&["maestro"]).is_none());
-        assert!(command_of(&["maestro", "--verbose"]).is_none());
-    }
-
     #[cfg(feature = "cli")]
     #[test]
     fn cli_subcommands_are_classified_as_cli() {

crates/maestro/tests/cli.rs

@@ -54,35 +54,11 @@ fn version_flag_succeeds() {
     assert!(text.contains("maestro"), "--version output: {text}");
 }
 
-/// A bare `maestro` must never fall back to help on a build that has a TUI:
-/// the missing subcommand defaults to `tui` (#119). Point at a port with
-/// nothing listening so the TUI's health probe fails fast instead of blocking
-/// on a terminal.
-#[cfg(feature = "tui")]
 #[test]
-fn bare_invocation_dispatches_to_the_tui() {
-    let (ok, text) = run(&["--daemon-url", "http://127.0.0.1:9"]);
-    assert!(
-        !ok,
-        "TUI against a dead daemon should exit non-zero:\n{text}"
-    );
-    assert!(
-        text.contains("daemon unreachable"),
-        "bare invocation should have run the TUI's daemon probe:\n{text}"
-    );
-    assert!(
-        !text.contains("Usage"),
-        "bare invocation must not print help when a TUI exists:\n{text}"
-    );
-}
-
-/// Builds without the `tui` feature keep the historical behaviour: no args =>
-/// help, exit 0 (#119).
-#[cfg(not(feature = "tui"))]
-#[test]
-fn bare_invocation_prints_help_and_exits_zero() {
+fn no_args_prints_help_and_fails() {
+    // `arg_required_else_help = true` => exit non-zero but show usage.
     let (ok, text) = run(&[]);
-    assert!(ok, "bare invocation should exit 0:\n{text}");
+    assert!(!ok, "bare invocation should fail:\n{text}");
     assert!(text.contains("Usage"), "expected usage text:\n{text}");
 }
 

docs/INSTALL.md

@@ -119,9 +119,6 @@ The wizard always installs the default-feature build.
 
 `maestro tui` is the keyboard-and-mouse driven terminal UI client. It ships
 in the default feature set, so a vanilla `cargo install maestro` builds it.
-A bare `maestro` opens the TUI too — the missing subcommand defaults to `tui`
-(#119), so `maestro --daemon-url http://host:7070` works as well. Builds
-without the `tui` feature have no UI to open and print help instead (exit 0).
 Drop the `tui` feature to skip it on hosts that don't need the UI surface
 (`--no-default-features --features cli,daemon`).
 

docs/SIDEBAR.md

@@ -5,8 +5,7 @@ sidebar (#107) and the TUI sidebar (#108) describe a session the same way.
 Read this before changing either. Both clients implement exactly what is
 written here; if it needs to change, change it here first.
 
-A card has **line 1** always and **line 2** only when line 2 has something to
-say.
+A card is always two lines: **line 1** and **line 2**.
 
 ## Line 1 — name + actions
 
@@ -25,32 +24,32 @@ badge move off this row into line 2.
 
 ## Line 2 — meta line (adaptive)
 
-Rendered only when at least one of these holds:
+Line 2 always renders — never an empty placeholder row either, since its
+unconditional fragments (see below) always have something to show. Its
+*fragments* are adaptive: some show only when their trigger holds. The line
+itself is not.
 
-1. The session has been held in its current activity state longer than
-   **30 seconds** (`activity_since` from #102). A freshly-active session
-   stays one line.
-2. Its worktree holds blocked work: `blocked_work` is `Some` and not clear
-   (`InTheWay::is_clear()`), rendered in `formatInTheWay`'s phrasing on web
-   and as `⚠ <summary>` on the TUI.
-3. It has exited: `status == Dead`.
-4. An agent-reported state (#105) of `Error` is in force (see Precedence).
-
-Otherwise line 2 is absent — never an empty placeholder row.
-
-When present, line 2 reads left to right:
+Line 2 reads left to right:
 
 ```
-<dot> <duration> [<detail>] [<blocked work> | exited] [<command>]
+<dot> [<duration>] [<detail>] [<blocked work> | exited] <command>
 ```
 
+Its minimum content is therefore the dot and the command.
+
 `<dot>` is a single filled glyph (`●` on both clients) carrying the activity
-state's colour, and `<duration>` follows in the same colour. There is no state
-word and no second badge: the dot exists so the state is still legible when a
-row is dimmed or the terminal renders the duration in the default fg. The dot
-and duration are unconditional parts of line 2; the bracketed fragments appear
-only when their trigger holds. A payload that predates #102 (no usable
-`activity_since`) contributes no duration — the dot still renders.
+state's colour, and `<duration>` follows in the same colour when shown. There
+is no state word and no second badge: the dot exists so the state is still
+legible when a row is dimmed or the terminal renders the duration in the
+default fg. The dot is an unconditional part of line 2; the bracketed
+fragments appear only when their trigger holds.
+
+`<duration>` renders only once the session has been held in its current
+activity state longer than **30 seconds** (`activity_since` from #102) — under
+that threshold the duration is absent and the dot renders alone. A payload
+that predates #102 (no usable `activity_since`) likewise contributes no
+duration — the dot still renders. This rule now governs only the duration
+fragment; it no longer decides whether line 2 exists.
 
 `<detail>` is an agent-reported string (#105) — e.g. why a session is in
 `Error`. It sits right after the duration, in the muted style, and shows only
@@ -60,9 +59,11 @@ truncates with `…` ahead of the trailing fragments — a long detail never
 pushes `<blocked work>`, `exited`, or `<command>` off the line, and neither
 client ever lets it wrap.
 
-`<command>` is optional and muted: the session's command line, shown only when
-the rendered name came from `metadata.name` and differs from the command (the
-web has always surfaced this; the TUI may omit it).
+`<command>` is unconditional and muted: the session's command line, shown on
+every card in both clients — no omission in the TUI, no name-vs-command
+comparison gating it. A session named by its command line then shows the same
+string on both lines; that is accepted, the price of a row that never changes
+height.
 
 ## Colour per activity state