cristicretu/diri

Problem Aider's bundled manifest documents several subtle prompt boundaries, but the Rust tree has no Aider-specific screen-rule regression tests. Launch/resume coverage does not protect status detection from false positives. Scope Add focused tests for the existing Aider rules. Use small synthetic terminal screens based on the examples documented in the manifest; label them as synthetic examples, not live captures. No Aider installation, model account, or network access should be required. Start with: diri/crates/diri-engine/manifests/aider.json: confirm-prompt, working-spinner, and idle-prompt. diri/crates/diri-engine/src/detect/mod.rs and detect/manifest.rs: reuse the existing screen/rule test helpers. Acceptance An unanswered (Y)es/(N)o [Yes]: prompt matches the permission rule. An answered prompt ending in : y followed by the working spinner does not remain blocked. Bare > and ask> bottom-row prompts match idle. ->, -->, and a quoted prompt above a non-prompt last row do not ma

Problem In Settings → Skills, opening a skill and choosing Copy instructions writes to the clipboard but gives no confirmation. Keyboard activation has the same behavior, so it is hard to tell whether the copy happened. Scope Give the existing button brief “Copied” feedback after a successful copy. Reuse the current control; no toast, new setting, or dependency is needed. Start in diri/crates/diri-app/src/skills_page.rs. Both the click callback for skills-copy and the detail-view branch of handle_key currently call write_to_clipboard directly. They should share the copy action. Acceptance Pointer, Enter, and Space activation show the same confirmation. The control keeps its width and keyboard focus while its label changes. Repeated copies restart the feedback interval; navigating to another skill clears stale feedback. An unreadable or still-loading skill never reports a successful copy. Include a short recording of mouse and keyboard behavior; keep motion consistent with the ex

Problem dirijor session spawn --help currently exits with “session spawn requires an agent kind”. The top-level help lists the command but does not explain its arguments. A first-time CLI user has to read the source to discover --cwd, --worktree, --branch, and --prompt. Scope Add command-specific help for dirijor session spawn --help and -h. Keep this PR limited to spawn help; no command parser rewrite or new dependency is needed. Start in diri/crates/dirijor-mcp/src/bin/dirijor.rs: run, session, and session_spawn. Acceptance Help exits successfully and prints usage, supported arguments, and one local example. It works without a running Engine and never opens a connection, starts a session, or creates a worktree. Ordinary spawning and missing-argument errors keep their current behavior. Add focused tests for both help flags and the no-Engine path. Run cargo test -p dirijor-mcp from diri/ and follow CONTRIBUTING.md for the remaining checks. No agent account or SSH host is required