Description
The independent completed-soak Azure capture settled 23 of 25 managed producer claims. The exact servererrors_total_count and usererrors_total_count signal/producer selectors remained empty while eight sibling claim families were observed. A separate six-message signed send/receive exercise succeeded and a malformed-header request returned 400; neither proves an exported error family. No server fault was induced. Absent metadata remains unknown and absence is not unsupportedness. The immutable final capture hash and pair-level reasons are recorded in reality-corpus/cspazure/managed-paired.json and reality-corpus/verdicts/producer-resolution-2026-09-08.json. This is a follow-up to genuinely unsettled campaign acceptance, not permission to manufacture an error or reopen the one-environment lifecycle.
Acceptance Criteria
- #1 Independently observe or source a precise current limitation for each exact error-family producer pair, retaining per-series route/job evidence and load/fault conditions without inventing type from a suffix
- #2 Reconcile the corpus and pair-level reasons without weaker matching, label ignores, capture rewriting or a lower configured producer bound
- #3 Any future authorized capture environment is fully torn down with verified all-cloud absence; do not induce a provider server fault without an explicit safe method and authority
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/
Implementation Plan
Wave 2026-09-17: L4 reads current official Service Bus documentation and forwarding conditions. Root reconciles pair-level reasons only where sourced; no Azure lifecycle, induced fault, capture rewrite or comparator change.
Implementation Notes
Current Microsoft Service Bus monitoring and supported-metrics docs define ServerErrors and UserErrors; current Grafana supported-resource-types docs list their exact mapped names. Neither source specifies zero-valued versus omitted output when qualifying errors do not occur. Both pairs remain unsettled. Only pair reason text changed; no Azure lifecycle, fault, capture rewrite, label ignore, matching change or producer-bound reduction.
Sibling wave2026-09-21 context only: final producer ratchet is observed=expected_count=len(claims)=189, stale0 untriaged0. Zero headroom means a new no_comparable_producer finding fails even for an unmodelled permutation. This does not settle either Service Bus error pair, change Azure acceptance, or authorize a capture/fault. Existing precise resume boundary and Parked status remain unchanged.
Final Summary
Documentary route completed with honest non-settlement. Resume with precise source for zero-versus-absent export and forwarding behavior, or separately authorized qualifying-load evidence. AC1 remains open; no new Azure estate was created.