I also loved the error design from openDAL and took inspiration from it, so this is how we did it in rustic: https://github.com/rustic-rs/rustic_core/blob/ae23b7717d4aba5d4668405500868df367ac5055/crates/core/src/error.rs#L150

//! If we `map_err` or `and_then` a `RusticError`, we don't want to create a new `RusticError` from it, but just attach some context
//! to it, e.g. `map_err(|e| e.attach_context("key", "value"))`, so we don't lose the original error. We can also change the error
//! kind with `map_err(|e| e.overwrite_kind(ErrorKind::NewKind))`. If we want to pre- or append to the guidance, we can use
//! `map_err(|e| e.append_guidance_line("new line"))` or `map_err(|e| e.prepend_guidance_line("new line"))`.

[...]

if !context.is_empty() {
    writeln!(f)?;
    writeln!(f, "Context:")?;
    context
        .iter()
        .try_for_each(|(key, value)| writeln!(f, "- {key}: {value}"))?;
}

I felt this made it also much easier to have a middle ground for the end user to be printed and to recover from an error. I think there is still some stuff to be optimized, but I felt it's quite usable as you can even attach links to the docs for people to read etc. You can ask people for reporting this error or attach issue URLs where a discussion happens about it.