OrthographicConsistency cannot be disabled and false positives for technical terms

harper-ls version: 2.6.0

I'm using Harper Language Server with Zed.

## Issue 1

I receive diagnostics such as:

"This word's canonical spelling is all-caps. (Harper OrthographicConsistency)"

I tried:

{
"harper-ls": {
"linters": {
"OrthographicConsistency": false
}
}
}

but the diagnostic is still reported.

Is this rule configurable? If so, what is the correct configuration key?

## Issue 2

Harper reports false positives for common technical terms and file names, for example:

- index.html
- main.js
- app.ts
- component.tsx
- styles.css
- package.json
- tsconfig.json

These are valid file names and should ideally be ignored or treated as code.

## Feature Request

It would be helpful to:

- Allow disabling `OrthographicConsistency`.
- Ignore common file extensions (.js, .ts, .tsx, .jsx, .html, .css, .json, .md, etc.).
- Treat file names and code identifiers as code rather than prose.
- Improve support for technical documentation.

Start with Harper Language Server's linter configuration and diagnostic handling, then reproduce the OrthographicConsistency setting and technical-name examples in Zed. Done means the rule can be disabled with the correct key and file names or code-like terms no longer produce these false positives.

Written by the indexing model from the issue text.