3 Commits

Include renames

Author	SHA1	Message	Date
Miguel PalhasandClaude Opus 5	28778b2224	feat(maestro): add maestro send for typing into a session ... Adds POST /api/sessions/:id/input and a CLI command on top of it, so a script (or another agent) can hand an instruction to a running session without attaching to it. The text goes in as one write and the Enter follows 150ms later: agents that run a full-screen prompt coalesce a burst of input into a paste, and a newline inside that burst becomes a line break instead of sending the message. `--no-enter` skips the Enter and leaves the text in the prompt. The session argument takes an ID, a unique ID prefix, or a session name; names win over prefixes. A session whose pane has exited is refused (409) rather than silently accepted — unlike a stray keystroke on an attach socket, a send that goes nowhere is worth hearing about. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-01 15:10:18 +01:00
Miguel Palhas	0c135aa065	feat(maestro): maestro kill --force ... The flag overrides the kill refusal (#81): the session ends, the guarded worktree is retained, and the CLI prints where the work went — path, branch, force-killed — instead of leaving the operator to wonder. WORKTREES.md: write down that a forced kill of a tree whose guard is clear removes it as usual — force changes what happens to blocked work, not ordinary cleanup.	2026-08-24 11:34:15 +01:00
Miguel PalhasandClaude Opus 5	30bd9d9042	test(maestro): one mock daemon instead of three answers ... There were three answers to "how do I test against a daemon", and the CLI — the thinnest client — had none, so its formatting and error handling were exercised by compiling and forking the real binary plus tmux. Adds crates/maestro-testing with a MockDaemon that serves the real /api/* surface from maestro-protocol types, backed by a Vec<Session>. It replaces two ad-hoc stubs: maestro-web's, which returned [{"id":"session-1"}] — not a valid Session — and maestro-tui's scripted socket with a hardcoded timeline. maestro-cli gets its first tests against a daemon: six cases covering the catalog, that DaemonInfo carries the version and presets its old private copy dropped, that a structured failure surfaces the daemon's own message, and that connection-refused stays distinguishable from an HTTP rejection. maestro-web's proxy suite gains an end-to-end check that an upstream rejection reaches the browser as a 4502 close carrying the daemon's message — upstream_close_reason had only unit tests. e2e keeps the tmux-shaped tests. cli_list_reads_from_daemon still runs the shipped binary as a subprocess but now against MockDaemon, and tui_integration.rs is deleted: the real daemon's /api/events contract is covered by maestro-daemon/tests/local_api.rs and the client reducer by maestro-tui/tests/catalog_ws.rs. The e2e suite drops from ~32s to ~20s. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-22 14:51:22 +01:00