Context
After an invitation has been received, decrypted, verified, and accepted, the recipient client must join the existing ByteSync session without manual entry. This epic completes the full trusted-session workflow.
Objective
Connect accepted trusted-session invitations to the existing join-session mechanism, then add optional automated inventory, synchronization, CLI waiting, and complete UI feedback.
Expected capabilities
- Join a session automatically after invitation acceptance.
- Use session ID and password from the validated invitation.
- Respect requested modes: join only, inventory, or synchronize.
- Enforce local policy and grants before automatic actions.
- Display status in initiator and recipient UI.
- Provide machine-readable CLI results.
- Log automatic trusted-session actions.
Acceptance criteria
- A recipient can automatically join a session after accepting a valid invitation.
- Requested modes are applied only when locally authorized.
- Grants allow controlled auto-accept.
- The UI can manage automatic authorization rules.
- The CLI can create a session, wait for clients, and return useful output.
- Errors are visible and understandable.
- Automatic actions are logged.
- End-to-end tests cover the full flow.
Out of scope
- Automatic enrollment of new non-trusted clients.
- PKI or MDM integration.
- Direct AES session key sharing outside the existing mechanism.
- Silent synchronization without an explicit grant.
Implementation tickets
Context
After an invitation has been received, decrypted, verified, and accepted, the recipient client must join the existing ByteSync session without manual entry. This epic completes the full trusted-session workflow.
Objective
Connect accepted trusted-session invitations to the existing join-session mechanism, then add optional automated inventory, synchronization, CLI waiting, and complete UI feedback.
Expected capabilities
Acceptance criteria
Out of scope
Implementation tickets