Everyday-use refinement roadmap
Why
Threadline's remaining Phase 5 exit criterion in #2 was a ten-user, two-week technical alpha. The owner has chosen to supersede that criterion with a focused everyday-use track. This does not claim the old criterion passed. Signed builds continue through invited sharing until the new flows are accepted.
Delivery order
- Faster connection: reusable identities, opt-in saved SSH passwords, and direct connection from Home.
- Smoother command loop: manual replies to running commands, durable completed turns, honest shell recovery, and automatic persistent/isolated routing.
- Multiple sessions: up to three independent live SSH sessions with switching and one aggregate notification.
- Transcript polish and acceptance: saved-history search, large-output navigation, and a combined minified, installed, and invited-tester check.
Product boundaries
- Unknown host keys still require confirmation; changed keys remain blocked.
- Saved SSH passwords require device approval per use on Android 11+. Older devices keep session-only passwords. Imported-key passphrases and privilege-prompt replies remain session-only.
- Replies to running commands are user-initiated. A masked local field cannot prevent a remote program from echoing a secret into output.
- Automatic command routing is deterministic and best effort. Mixed or risky ambiguous input asks before sending, and an accessible override remains.
- Process death or network loss never claims to resume a remote shell. Reconnect starts a fresh verified shell.
- No cloud backend, analytics, public prerelease, or permanent signing key in CI is part of this track.
Acceptance gates
- Connection: a trusted saved host with a ready identity starts connecting from one Home tap, plus device approval when using a saved password.
- Command loop: ordinary persistent state survives, isolated strict failures do not close the shell, and manual masked replies bypass local history and diagnostics.
- Sessions: three independent connections can coexist; switching never moves input or drafts between them; closing one does not close another.
- Release: relevant JVM, Android, fixture, minified, installed-update, and owner-device checks pass; invited tester feedback covers the new task paths.
Child issues
Faster connection
Smoother command loop
Multiple sessions
Transcript polish and acceptance
Related historical issue: #2.
Documentation PR: #58.
Everyday-use refinement roadmap
Why
Threadline's remaining Phase 5 exit criterion in #2 was a ten-user, two-week technical alpha. The owner has chosen to supersede that criterion with a focused everyday-use track. This does not claim the old criterion passed. Signed builds continue through invited sharing until the new flows are accepted.
Delivery order
Product boundaries
Acceptance gates
Child issues
Faster connection
Smoother command loop
Multiple sessions
Transcript polish and acceptance
Related historical issue: #2.
Documentation PR: #58.