docs: roadmap additions from audit batch (doctor, CLI flags, local-only)#24
Merged
Conversation
Three new user-facing items surfaced by the latest audits: - `sshshot doctor`: health-check command (Node, tools, config, daemon PID, SSH auth, target reachability) - Non-interactive CLI surface (`start <target>`, `--json`, `--local`, `--foreground`, `--yes`, `config add/remove/list`) for scripting - Allow starting in `local` mode with zero configured remotes Internal reliability backlog from the same audits (P0/P1/P2 fixes, test gaps, doc drift) is recorded in project memory rather than the README — those are housekeeping, not user direction.
2 tasks
flamerged
added a commit
that referenced
this pull request
May 2, 2026
## Summary Course correction on PR #24. I was too strict on "user-facing only" — a bunch of the Round-M items I'd parked in private memory are actually user-visible bugs (uploads hang, screenshot bursts dropped, slow upload misses next poll, typo'd commands silently run setup, fatal errors exit 0). Those belong in the public roadmap. This PR: 1. Splits \`## Roadmap\` into two subsections — **Reliability fixes** and **Features and ergonomics** — so the list stays scannable. 2. Pulls 11 user-visible bug-class items out of memory into the Reliability subsection. 3. Leaves purely-internal items (commitlint config doc, semantic-release idempotency wiring, package.json metadata cleanup, CI smoke checks, monitor.ts split, tsconfig test/ inclusion) in memory — those are housekeeping, not user direction. ## Items added under **Reliability fixes** - SSH upload \`BatchMode=yes\` + timeout + EPIPE handler - \`sshshot stop\` honors the 5 s graceful-shutdown window - Decouple poll loop from upload completion - macOS screenshot burst handling (oldest-first) - \`sshshot config\` preserves \`activeTarget\` + \`paused\` - Typo'd CLI commands print error + exit 1 - Fatal CLI errors set non-zero exit code - \`loadConfig\` shape validation + \`saveConfig\` atomic writes - Cache clipboard-tool availability at startup - \`~/.ssh/config\` parse defensiveness + \`?\` wildcard filter + dedup - \`removePidFile\` only-if-still-ours guard \`docs:\` only, no release fired. ## Test plan - [x] yarn format:check - [ ] CI matrix Node 20/22/24 green (no source changes)
|
🎉 This PR is included in version 0.9.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three new user-facing roadmap items from the latest 3-audit batch. Most of the audit findings overlapped with what's already in the Roadmap or in the project's internal reliability backlog (recorded in memory, not here).
Internal reliability fixes (`pipeToRemote` BatchMode/timeout/EPIPE, killAllSshshotProcesses respecting the daemon's grace window, decoupling uploads from polling, mac-screenshot burst handling, atomic config writes, unknown-command exit code, PID-file race, etc.) are tracked in project memory as the Round-M reliability backlog — not user-facing roadmap items.
`docs:` only, no release fired.
Test plan