# Contributing

Thanks for helping improve `dsh-secure-remote`.

## Before opening a pull request

1. Run `npm run check`.
2. Run `npm test`.
3. Run `npm run pack:check` when changing package metadata or published files.
4. Add or update a regression test for behavior changes.
5. Confirm that logs, fixtures and screenshots contain no SSH credentials or private host data.

## Pull requests

- Keep changes focused and explain the user-visible behavior.
- Preserve the existing `SshProfile`, `RemoteWorkspaceView` and `ssh_workspace` v1 compatibility contract.
- Do not weaken `StrictHostKeyChecking` or the Workspace path boundary.
- Do not add automatic retries to Bash, file writes or terminal startup after a command may have been sent.
- Document platform-specific behavior for macOS, Linux and Windows.

## SSH fixtures

Integration fixtures must use ephemeral test keys and disposable POSIX targets. Never commit a private key or a real server configuration.