docs: define application parameter contract

CHANGELOG.md

@@ -18,6 +18,7 @@ The format is based on Keep a Changelog and this project follows Semantic Versio
 - **Design system documentation** — added `docs/design-system/` with the current InferHarness visual language overview, token snapshot, bundled token fonts, component primitives, and frontend styling rules.
 - **Schema specifications** — copied the application JSON Schema contract pack into `docs/schemas/` as the durable documentation source while keeping runtime validators on the backend source copy.
 - **Test pipeline specification** — promoted the benchmark execution model into `docs/test-pipeline/` with supporting valid and invalid benchmark document examples.
+- **Application parameter specification** — added `docs/PARAMETERS.md` to define canonical inference, response, tool, reasoning, execution, target, and application parameters with provider mappings, including explicit Mistral and DeepSeek profiles, validation, comparability, persistence, and migration requirements.
 
 ### Changed
 

README.md

@@ -97,6 +97,7 @@ Run separates execution health from functional checks so a technically completed
 **Automated metrics**
 Capture time to first token, total latency, prefill/decode timing, prompt tokens, completion tokens, and tokens per second.
 Canonical metric definitions and the `metrics-v2` contract are maintained in [docs/METRICS.md](docs/METRICS.md).
+Canonical inference, execution, provider-mapping, and application-setting semantics are defined in [docs/PARAMETERS.md](docs/PARAMETERS.md).
 
 **Qualitative evaluation**
 Score model answers on accuracy, relevance, coherence, completeness, and helpfulness. Compare Mode runs the same prompt across up to four models side by side.