rtb-error 0.6.4

Error types and the diagnostic report pipeline. Part of the phpboyscout Rust toolkit.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

<!-- Defect report: something in THIS project behaves differently from what is
     documented or implied. Apply `bug`.
     If the defect was found while working in another project, add
     `origin::handover` and say so under Use case. -->

## What happens

The observed behaviour, in one sentence.

## What should happen

The expected behaviour, and what makes it the expectation — the documentation,
the type signature, the spec decision, or the stated contract. "It surprised me"
is a real signal, but say so plainly rather than implying a broken promise.

## Reproduction

Smallest sequence that shows it. A failing test or a runnable snippet beats
prose.

```
```

## Evidence

Actual output — the error, the wrong value, the stack trace. Paste it; do not
summarise it.

```
```

## Environment

Version or commit of this project, plus anything that plausibly matters:
consumer version, OS, toolchain, runner. Say where it was observed — CI or
local — because the two fail differently.

## Impact

Who hits this and how often. Whether there is a workaround, and what it costs.

<!-- Do not diagnose in the title. A report that names the wrong cause sends
     triage down it — put the symptom in the title and any suspicion in a
     clearly-marked section below. -->