Use a loose set of rules for consistent JSDoc comments

While using JSDoc should not be mandatory, I think that its users should aim for more consistency, which may be achieved by the following set of loose ESLint rules:

```json
"valid-jsdoc": ["error", {
"prefer": {
"arg": "param",
"argument": "param",
"class": "constructor",
"return": "returns",
"virtual": "abstract"
},
"preferType": {
"Boolean": "boolean",
"Number": "number",
"object": "Object",
"String": "string"
},
"requireReturn": false
}]
```

No file or test is named in the issue. Start by locating the repository’s ESLint configuration and current JSDoc guidance, then compare them with the proposed valid-jsdoc options. Done means the agreed consistency rules are applied in the appropriate configuration and verified by the relevant lint checks.

Written by the indexing model from the issue text.