error-forge 1.0.0

Pragmatic Rust error-handling framework with stable error metadata, contextual diagnostics, optional async support, and synchronous recovery primitives (retry, circuit-breaker, backoff). Optional #[derive(ModError)], declarative define_errors!, and feature-gated logging / tracing / serde adapters.
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
45
46
47
48
49
50
51
52

## Summary

<!-- Short description of what this PR changes and why. -->

## Type of change

<!-- Tick all that apply. -->

- [ ] Bug fix
- [ ] New feature (additive only)
- [ ] Breaking change (requires a major version bump per
      [`docs/STABILITY.md`](../docs/STABILITY.md))
- [ ] Documentation only
- [ ] CI / build / tooling

## Public-surface impact

<!-- Anything externally visible? New `pub fn`, new variant on a
     non-exhaustive enum, new field on a non-exhaustive struct,
     new feature flag, changed MSRV, etc. If none, say "none". -->

## CHANGELOG

- [ ] I added an entry under `## [Unreleased]` in `CHANGELOG.md`
      describing the user-visible effect of this change, per
      [`.dev/DIRECTIVES.md`](../.dev/DIRECTIVES.md) §D-1.

## Local verification

- [ ] `cargo fmt --all -- --check`
- [ ] `cargo clippy --workspace --all-targets --all-features -- -D warnings`
- [ ] `cargo clippy --workspace --all-targets --no-default-features -- -D warnings`
- [ ] `cargo build --workspace --no-default-features`
- [ ] `cargo build --workspace --all-features`
- [ ] `cargo +1.81 build --workspace --all-features` (MSRV)
- [ ] `cargo test --workspace --all-features`
- [ ] `RUSTDOCFLAGS="-D warnings" cargo doc --workspace --all-features --no-deps`
- [ ] `cargo audit` (if dep tree changed)

## Tests

<!-- New tests added? Existing tests cover the change? If
     not, justify why. -->

## Documentation

<!-- Any documentation updated? Public `pub fn` / `pub struct`
     additions need rustdoc with `# Example`. -->

## Additional context

<!-- Anything reviewers should know up front. -->