Add reusable domain-bound and quality-threshold profiles

[devkyato]

Datary 0.2.0 delivered explicit counter-reset and monotonicity options, packet-loss evidence, schema/type changes, zero-MAD fallbacks, original record positions, and complete finding metadata.

What remains is a clean configuration model for reusable domain bounds and named threshold profiles. The design must keep every threshold explicit, portable in session metadata, and reviewable instead of silently applying domain assumptions.

[devkyato]

Datary 0.1.2 delivers the monotonicity and counter-reset portion of this roadmap through opt-in CLI and typed API fields, with explainable findings and deterministic tests. The issue remains open for domain bounds, threshold profiles, and broader packet-loss configuration.