observedAxisArgKey property
Trace-event arg key the audit gate cross-checks against the
capture's expectedMagnitude.observed. Null skips the cross-check.
Same semantics as DetectorMetadata.observedAxisArgKey. Two specs
declared on the same (stableId, severityLabel) must use distinct
argKeys (or one must be null) — the cross-spec uniqueness invariant
on the (stableId, severityLabel, argKey) tuple is what lets
multiple bracket axes coexist on a single family + severity without
double-counting trace events. Specs that differ on severityLabel
validate disjoint sleuth.issue.<id>.<severity> events and never
collide regardless of argKey (canonical tier-stack raise pattern).
Declaration alone does not guarantee the cross-check is active —
the schema's per-record gate skips silently when capture records
lack the arg (observedAxisArgKey != null && observedAxisExpected != null && observedAxisSamples.isNotEmpty in
_checkIssueTraceRecordPresent). The audit invariant
checkCapturesCarryObservedAxisArg (in
test/validation/_support/audit_invariants.dart) enforces capture
fidelity for non-allowlisted runtimeVerified+ brackets; entries in
legacyObservedAxisAllowlist (typed manifest in same file) are
exempt pending capture re-record with a consumeBy deadline.
Implementation
final String? observedAxisArgKey;