Windows smoke testing showed users can reasonably expect cc-clip send --paste C:\test.png to upload that file, but the previous parser left the path in fs.Args() and silently read the clipboard instead. This makes one positional image path an explicit --file equivalent while preserving host-first/default-host forms and rejecting trailing flags after positionals.

Constraint: Go flag package stops at first positional arg, so parser has to normalize leading and trailing positionals before upload

Rejected: Error on all unexpected positionals | would preserve the reporter's confusing failure mode instead of supporting the intuitive path form

Confidence: high

Scope-risk: narrow

Directive: Keep send parser tests covering default-host, host-first, post-flag, and conflict forms before changing CLI grammar

Tested: go test ./... -count=1; go vet ./...; go run ./cmd/cc-clip --help; env GOOS=windows GOARCH=amd64 go test -c ./cmd/cc-clip -o /tmp/cc-clip-windows.test.exe

Not-tested: Real Windows clipboard paste against a remote host