Updated the branch with the same golang.org/x dependency bump now on upstream master to address the govulncheck failure from the previous lint job.

Local verification on the new head (1f2c39f):

• go run golang.org/x/vuln/cmd/govulncheck@latest ./... -> no vulnerabilities found
• go test ./backend/sftp -run 'TestRemotePathEncodesRemoteNames|TestRemoteShellPathEncodesRemoteNames|TestRemoteShellPathEncodesPathOverrideNames|TestShellEscapeUnix|TestShellEscapeCmd|TestShellEscapePowerShell|TestParseHash|TestParseUsage' -count=1
• go test ./lib/encoder -count=1
• git diff --cached --check before commit

The new upstream Actions run is currently action_required, so it looks like it needs maintainer approval before CI can execute on this updated head.

Follow-up pushed in 311e6729 and the generated-doc review thread is resolved. The PR diff is now limited to backend/sftp, go.mod, and go.sum; docs/content/sftp.md is no longer changed.

GitHub Actions for the new head are back to action_required after the force-push, so this needs maintainer approval again before CI can run.

Checked the current head ce2a9c50 against the lint note.

Local verification:

• golangci-lint run ./backend/sftp --timeout=10m -> 0 issues
• same package with GOOS=linux, windows, freebsd, and openbsd -> 0 issues
• golangci-lint run --new-from-rev=upstream/master ./... --timeout=10m -> 0 issues
• focused SFTP unit tests -> pass
• go test ./lib/encoder -count=1 -> pass

go test ./backend/sftp -count=1 still reaches the integration tests locally, but those are blocked here by missing flock in fstest/testserver. I do not see a branch-local lint patch needed on this head.

Github actions is down at the moment :-) I think this is ready to merge but I want to see it run through the actions first!