cookcli-core 0.38.0

//! Full-text recipe search.
//!
//! [`search`] walks the `.cook` and `.menu` files under a root, scores each
//! against a query, and returns the matches best first.
//!
//! # What counts as a match
//!
//! **Every term must match.** A recipe is a hit when each whitespace-separated
//! term of the query appears somewhere in its text or in its file name, matched
//! case-insensitively as a substring. Adding a term narrows the results.
//!
//! Ranking is `cooklang-find`'s, and is a separate question from matching:
//!
//! - The file name is matched against the **whole query**, spaces included.
//!   An exact stem match ranks highest, a substring match next.
//! - The contents are matched against each term, and every occurrence adds a
//!   little.
//!
//! # Why matching is not simply `cooklang-find`'s scoring
//!
//! `cooklang-find` keeps anything scoring above zero, and it scores a file for
//! *any* term it contains — so a multi-term query was a union there, and
//! `cook search chicken rice` returned recipes with no rice in them. That
//! contradicted CookCLI's own help text, which had always promised AND
//! (<https://github.com/cooklang/cookcli/issues/425>), and it made a query of
//! common words match most of a collection.
//!
//! The union is still what the library returns; [`search`] intersects it here.
//! A single-term query is unaffected, since AND over one term is that term.

use crate::{find, Context, CoreError, Outcome};
use camino::{Utf8Path, Utf8PathBuf};
use serde::Serialize;

/// A search to run.
#[derive(Debug, Clone)]
pub struct SearchRequest {
    /// The query, as a single string.
    ///
    /// Whitespace splits it into terms for the content match, while the whole
    /// string is what the file name match looks for — so the spacing is part of
    /// the query rather than a separator this crate is free to normalise.
    ///
    /// Callers holding a list of words, such as a command line's arguments,
    /// join them with a space. That loses nothing: `["olive", "oil"]` and
    /// `["olive oil"]` are the same query, and no scoring rule below could tell
    /// them apart if this field kept them separate.
    pub query: String,
    /// Directory to search. Defaults to the context base path.
    ///
    /// Every hit's [`SearchHit::relative_path`] is expressed against this, so
    /// it doubles as the root that results are reported relative to.
    pub base_dir: Option<Utf8PathBuf>,
}

/// One matching recipe.
#[derive(Debug, Clone, Serialize)]
#[non_exhaustive]
pub struct SearchHit {
    /// Where the recipe sits under the search root.
    ///
    /// This is [`SearchHit::path`] with the root stripped off, and is what
    /// `cook search` prints. A path that does not begin with the root is kept
    /// whole rather than mangled; see [`path`](SearchHit::path) for when that
    /// happens.
    pub relative_path: Utf8PathBuf,
    /// The path the search found the recipe at, ready to open.
    ///
    /// Absolute when the search root is absolute, which is the case worth
    /// designing for. When the root is relative the path is too, and is
    /// interpreted against the *process* working directory — for an in-process
    /// editor integration that is the editor's, not the project's. This mirrors
    /// the caveat on [`Context::base_path`] and is the reason a relative root
    /// can leave `relative_path` and `path` equal.
    pub path: Utf8PathBuf,
    /// The recipe's title, falling back to its file stem when it has none.
    ///
    /// Read from front matter that the search has already parsed, so it costs
    /// nothing to carry. `None` only if the entry has neither, which a file
    /// found on disk cannot manage.
    pub name: Option<String>,
}

/// Search the recipes under `req`'s root, best match first.
///
/// The root is [`SearchRequest::base_dir`], or [`Context::base_path`] when that
/// is unset. Nothing else on the context is consulted. A root that does not
/// exist is not an error: there is simply nothing under it to match.
///
/// Every term must match; see the [module documentation](self).
///
/// # Errors
///
/// - [`CoreError::Search`] if the root cannot be searched at all, which in
///   practice means its name contains glob syntax.
/// - [`CoreError::Io`] if a file under the root turned up in the walk but could
///   not be read, or its front matter could not be understood. One such file
///   fails the whole search rather than being skipped — that is
///   `cooklang-find`'s behaviour and this crate does not paper over it. Bytes
///   that are not valid UTF-8 are not such a failure; they are decoded as
///   U+FFFD, as `matches_every_term` describes.
pub fn search(ctx: &Context, req: SearchRequest) -> Result<Outcome<Vec<SearchHit>>, CoreError> {
    let base_dir = req
        .base_dir
        .unwrap_or_else(|| ctx.base_path().to_path_buf());

    tracing::trace!("searching {base_dir} for {:?}", req.query);

    let entries =
        cooklang_find::search(&base_dir, &req.query).map_err(|e| search_error(e, &base_dir))?;

    // `cooklang-find` returns the union over the terms, best first. Narrowing
    // to the intersection keeps that ranking — it only removes rows.
    let terms: Vec<String> = req
        .query
        .split_whitespace()
        .map(str::to_lowercase)
        .collect();

    let mut hits = Vec::new();
    for entry in &entries {
        // A search only ever yields file-backed entries, so this skips nothing
        // today. It is a `continue` rather than an unwrap because a
        // `RecipeEntry` need not have a path, and inventing one for an entry
        // that lacks it would be worse than leaving it out.
        let Some(path) = entry.path() else { continue };
        if !matches_every_term(path, &terms)? {
            continue;
        }
        hits.push(SearchHit {
            relative_path: relative_to(&base_dir, path),
            path: path.clone(),
            name: entry.name().clone(),
        });
    }

    Ok(Outcome::new(hits))
}

/// Whether every term appears in `path`'s text or in its file name.
///
/// Terms are expected already lowercased. Matching is a case-insensitive
/// substring test against the two surfaces `cooklang-find` scores — the file
/// stem and the contents — so that intersecting cannot drop a recipe the
/// library matched on a term it would have counted.
///
/// An empty term list matches everything, which is what an all-whitespace query
/// should do: `cooklang-find` returns nothing for it anyway.
///
/// Bytes that are not valid UTF-8 are decoded as U+FFFD rather than refused.
/// A recipe saved from a Latin-1 editor is still a recipe, and rejecting it
/// here failed the whole search over one stray byte in one file
/// (<https://github.com/cooklang/cookcli/issues/498>). Only the bad bytes
/// themselves stop matching — a term either side of one still does. A genuine
/// I/O failure is a different thing and is still an error, because an
/// unreadable file is not an empty one.
fn matches_every_term(path: &Utf8Path, terms: &[String]) -> Result<bool, CoreError> {
    if terms.is_empty() {
        return Ok(true);
    }

    let bytes = std::fs::read(path).map_err(|source| CoreError::Io {
        path: path.to_owned(),
        source,
    })?;
    let contents = String::from_utf8_lossy(&bytes).to_lowercase();
    let stem = path.file_stem().unwrap_or_default().to_lowercase();

    Ok(terms
        .iter()
        .all(|term| contents.contains(term) || stem.contains(term)))
}

/// Express `path` relative to `base_dir`, leaving it whole when it does not
/// start with it.
///
/// The fallback is load-bearing rather than defensive, because the root is
/// matched as written rather than resolved. A root of `./recipes` has the walk
/// produce `recipes/soup.cook`, which does not begin with `./recipes`, so the
/// hit keeps the root in it. Pass a root without a `./` — or an absolute one —
/// to get the stripping the name promises.
fn relative_to(base_dir: &Utf8Path, path: &Utf8Path) -> Utf8PathBuf {
    path.strip_prefix(base_dir).unwrap_or(path).to_owned()
}

/// Map a search failure onto the error that describes what actually happened.
///
/// Only a bad glob pattern means the root itself was unsearchable; the rest
/// mean a file under it was found and could not be read or understood.
fn search_error(error: cooklang_find::search::SearchError, base_dir: &Utf8Path) -> CoreError {
    use cooklang_find::search::SearchError;
    match error {
        SearchError::PatternError(source) => CoreError::Search {
            base_dir: base_dir.to_owned(),
            message: source.to_string(),
        },
        // Carries the file it failed on, which is more use than the root.
        SearchError::GlobError(source) => CoreError::Io {
            path: Utf8Path::from_path(source.path())
                .map(Utf8Path::to_owned)
                .unwrap_or_else(|| base_dir.to_owned()),
            source: source.into_error(),
        },
        // These two lose the file on the way out of `cooklang-find`, so the
        // root is the most specific thing left to name.
        SearchError::IoError(source) => CoreError::Io {
            path: base_dir.to_owned(),
            source,
        },
        SearchError::RecipeEntryError(source) => CoreError::Io {
            path: base_dir.to_owned(),
            source: find::entry_error(source),
        },
    }
}

#[cfg(test)]
mod tests {
    use super::*;

    /// A fixture whose recipes overlap deliberately: `chicken` and `rice`
    /// appear in one recipe each, so a two-term query tells AND and OR apart.
    fn fixture() -> tempfile::TempDir {
        let dir = tempfile::TempDir::new().unwrap();
        let base = base(&dir);
        std::fs::create_dir(base.join("Breakfast")).unwrap();
        write(
            &base.join("Breakfast").join("pancakes.cook"),
            "---\ntitle: Fluffy Pancakes\n---\n\nMix @flour{2%cups} with @milk{1%cup}.\n",
        );
        write(
            &base.join("curry.cook"),
            "Fry @chicken{1} in @oil{1%tbsp}.\n",
        );
        write(
            &base.join("pilaf.cook"),
            "Boil @rice{200%g} in @water{1%l}.\n",
        );
        dir
    }

    fn write(path: &Utf8Path, text: &str) {
        std::fs::write(path, text).unwrap();
    }

    fn base(dir: &tempfile::TempDir) -> Utf8PathBuf {
        Utf8PathBuf::from_path_buf(dir.path().to_path_buf()).unwrap()
    }

    /// Run a search rooted at the context base path.
    fn run(base_dir: &Utf8Path, query: &str) -> Vec<SearchHit> {
        search(
            &Context::new(base_dir.to_owned()),
            SearchRequest {
                query: query.to_string(),
                base_dir: None,
            },
        )
        .expect("search succeeds")
        .into_value()
    }

    /// The hits' paths, left as paths rather than stringified.
    ///
    /// That is what makes the assertions below portable: camino compares a
    /// path component by component, so the `Breakfast\pancakes.cook` the walk
    /// produces on Windows equals the `Breakfast/pancakes.cook` written here,
    /// while comparing the two as strings would not. Nothing else is
    /// loosened — a hit under a different directory, or with a different file
    /// name, still fails.
    fn relative_paths(hits: &[SearchHit]) -> Vec<Utf8PathBuf> {
        hits.iter().map(|h| h.relative_path.clone()).collect()
    }

    #[test]
    fn finds_a_recipe_whose_content_matches_a_term() {
        let dir = fixture();
        let hits = run(&base(&dir), "flour");
        assert_eq!(relative_paths(&hits), ["Breakfast/pancakes.cook"]);
    }

    #[test]
    fn finds_a_recipe_by_its_file_name() {
        let dir = fixture();
        // "pilaf" appears nowhere in any recipe's text.
        let hits = run(&base(&dir), "pilaf");
        assert_eq!(relative_paths(&hits), ["pilaf.cook"]);
    }

    #[test]
    fn a_query_that_matches_nothing_returns_no_hits() {
        let dir = fixture();
        assert!(run(&base(&dir), "kohlrabi").is_empty());
    }

    /// Every term must match. `curry.cook` has no rice in it and `pilaf.cook`
    /// has no chicken, so "chicken rice" matches neither.
    ///
    /// This used to return both: `cooklang-find` scores a file for *any* term
    /// and keeps everything above zero, so a multi-term query was a union
    /// (<https://github.com/cooklang/cookcli/issues/425>).
    #[test]
    fn multiple_terms_are_anded() {
        let dir = fixture();
        assert!(
            run(&base(&dir), "chicken rice").is_empty(),
            "no recipe has both: {:?}",
            relative_paths(&run(&base(&dir), "chicken rice"))
        );
    }

    /// The point of AND: a second term narrows rather than widens.
    #[test]
    fn adding_a_term_narrows_the_result_set() {
        let dir = fixture();
        let base = base(&dir);
        write(
            &base.join("stir-fry.cook"),
            "Fry @chicken{1} and @rice{1}.\n",
        );

        let one = relative_paths(&run(&base, "chicken"));
        let two = relative_paths(&run(&base, "chicken rice"));

        let mut sorted = one.clone();
        sorted.sort();
        assert_eq!(sorted, ["curry.cook", "stir-fry.cook"]);
        assert_eq!(two, ["stir-fry.cook"], "the second term must filter");
        assert!(two.len() < one.len(), "adding a term must not widen");
    }

    /// A term may match the file name rather than the contents, and still
    /// count towards the AND — `pilaf` appears in no recipe's text.
    #[test]
    fn a_term_matching_only_the_file_name_satisfies_the_and() {
        let dir = fixture();
        assert_eq!(
            relative_paths(&run(&base(&dir), "pilaf rice")),
            ["pilaf.cook"]
        );
    }

    /// A single-term query means the same thing as it always did: AND over one
    /// term is that term. This is the compatibility guarantee for the change.
    #[test]
    fn a_single_term_query_is_unchanged() {
        let dir = fixture();
        assert_eq!(relative_paths(&run(&base(&dir), "chicken")), ["curry.cook"]);
        assert_eq!(
            relative_paths(&run(&base(&dir), "flour")),
            ["Breakfast/pancakes.cook"]
        );
    }

    /// Matching ignores case on both sides, as the underlying scoring does.
    #[test]
    fn terms_match_regardless_of_case() {
        let dir = fixture();
        assert_eq!(
            relative_paths(&run(&base(&dir), "CHICKEN Oil")),
            ["curry.cook"]
        );
    }

    #[test]
    fn hits_are_relative_to_the_search_root() {
        let dir = fixture();
        let hits = run(&base(&dir), "flour");
        let hit = hits.first().expect("one hit");
        assert_eq!(hit.relative_path, "Breakfast/pancakes.cook");
        assert!(
            hit.relative_path.is_relative(),
            "relative_path must not be absolute: {}",
            hit.relative_path
        );
    }

    #[test]
    fn hits_carry_the_path_the_search_found_them_at() {
        let dir = fixture();
        let base = base(&dir);
        let hits = run(&base, "flour");
        let hit = hits.first().expect("one hit");
        assert_eq!(hit.path, base.join("Breakfast").join("pancakes.cook"));
        assert!(hit.path.is_file(), "path must be openable: {}", hit.path);
    }

    #[test]
    fn a_hit_is_named_by_its_title_when_it_has_one() {
        let dir = fixture();
        let hits = run(&base(&dir), "flour");
        assert_eq!(
            hits.first().expect("one hit").name.as_deref(),
            Some("Fluffy Pancakes")
        );
    }

    #[test]
    fn a_hit_with_no_title_is_named_by_its_file_stem() {
        let dir = fixture();
        let hits = run(&base(&dir), "pilaf");
        assert_eq!(
            hits.first().expect("one hit").name.as_deref(),
            Some("pilaf")
        );
    }

    #[test]
    fn base_dir_overrides_the_context_base_path() {
        let searched = fixture();
        let ignored = tempfile::TempDir::new().unwrap();
        write(&base(&ignored).join("decoy.cook"), "Mix @flour{1%cup}.\n");

        let hits = search(
            &Context::new(base(&ignored)),
            SearchRequest {
                query: "flour".to_string(),
                base_dir: Some(base(&searched)),
            },
        )
        .expect("search succeeds")
        .into_value();

        assert_eq!(relative_paths(&hits), ["Breakfast/pancakes.cook"]);
    }

    #[test]
    fn without_a_base_dir_the_context_base_path_is_searched() {
        let searched = fixture();
        let hits = run(&base(&searched), "flour");
        assert_eq!(relative_paths(&hits), ["Breakfast/pancakes.cook"]);
    }

    /// A filename match outranks a content-only match, so the caller can print
    /// the list as it comes and have the likeliest recipe first.
    #[test]
    fn hits_come_back_best_first() {
        let dir = tempfile::TempDir::new().unwrap();
        let base = base(&dir);
        write(&base.join("aaa-mentions-pilaf.cook"), "Serve with pilaf.\n");
        write(&base.join("pilaf.cook"), "Boil @rice{200%g}.\n");

        // Alphabetically the mention sorts first, so ordering by score is the
        // only thing that can put `pilaf.cook` in front.
        assert_eq!(
            relative_paths(&run(&base, "pilaf")),
            ["pilaf.cook", "aaa-mentions-pilaf.cook"]
        );
    }

    /// Searching somewhere that does not exist is empty, not an error.
    #[test]
    fn a_missing_search_root_yields_no_hits() {
        let dir = tempfile::TempDir::new().unwrap();
        assert!(run(&base(&dir).join("nope"), "flour").is_empty());
    }

    /// `relative_to` is exercised directly for the case that cannot be reached
    /// from a test without changing the process working directory: a search
    /// root spelled relatively.
    ///
    /// The walk resolves `./recipes/**/*.cook` to paths like
    /// `recipes/soup.cook`, dropping the `./` that `strip_prefix` would then
    /// need to find. The root therefore survives into the result. This is
    /// long-standing `cook search --base-dir ./recipes` behaviour, pinned here
    /// rather than endorsed.
    #[test]
    fn a_path_that_does_not_start_with_the_root_is_left_alone() {
        assert_eq!(
            relative_to(
                Utf8Path::new("./recipes"),
                Utf8Path::new("recipes/soup.cook")
            ),
            "recipes/soup.cook"
        );
        assert_eq!(
            relative_to(
                Utf8Path::new("/recipes"),
                Utf8Path::new("/elsewhere/soup.cook")
            ),
            "/elsewhere/soup.cook"
        );
    }

    #[test]
    fn a_path_under_the_root_is_stripped_to_the_remainder() {
        assert_eq!(
            relative_to(
                Utf8Path::new("/recipes"),
                Utf8Path::new("/recipes/Breakfast/pancakes.cook")
            ),
            "Breakfast/pancakes.cook"
        );
    }

    /// A search root whose name contains glob syntax cannot be turned into a
    /// pattern. It is a real directory that a user can really have, so it gets
    /// an error naming it rather than a silent empty result.
    #[test]
    fn a_search_root_that_is_not_a_valid_glob_pattern_is_reported() {
        let dir = tempfile::TempDir::new().unwrap();
        let root = base(&dir).join("re[ci");
        std::fs::create_dir(&root).unwrap();
        write(&root.join("soup.cook"), "Boil @water{1%l}.\n");

        match search(
            &Context::new(root.clone()),
            SearchRequest {
                query: "water".to_string(),
                base_dir: None,
            },
        ) {
            Err(CoreError::Search { base_dir, message }) => {
                assert_eq!(base_dir, root);
                assert!(
                    message.contains("attern"),
                    "the cause must survive: {message}"
                );
            }
            other => panic!(
                "expected CoreError::Search, got {:?}",
                other.map(|o| o.value)
            ),
        }
    }

    /// A recipe carrying a byte that is not valid UTF-8 is still a recipe.
    ///
    /// `cook search tuna` used to die with "Failed to read '<root>' / stream
    /// did not contain valid UTF-8" over one Latin-1 file, taking every other
    /// recipe's results with it
    /// (<https://github.com/cooklang/cookcli/issues/498>). The bad bytes are
    /// decoded as U+FFFD, so the recipe is found and the text around them still
    /// matches.
    ///
    /// Both files here are needed, because the report had two causes in two
    /// crates. A bad byte in the **body** was this crate's:
    /// [`matches_every_term`] read candidates with `read_to_string`. A bad byte
    /// in the **front matter** was `cooklang-find`'s, which propagated it out
    /// of its own walk instead of skipping the file the way `build_tree` does —
    /// that is the arm that named the search root rather than the file, and it
    /// needs 0.7.1 (cooklang/cooklang-find#13).
    #[test]
    fn a_recipe_that_is_not_valid_utf8_is_still_searchable() {
        let dir = fixture();
        let base = base(&dir);
        // Latin-1: 0xe8 and 0xe9 are an "è" and an "é" that never made it to
        // UTF-8. One file carries its bad byte in the body, the other in the
        // front matter.
        std::fs::write(
            base.join("tuna mornay.cook"),
            b"---\ntitle: Tuna Mornay\n---\n\nBake @tuna{1%can} with cr\xe8me.\n",
        )
        .unwrap();
        std::fs::write(
            base.join("salmon.cook"),
            b"---\ntitle: Saumon \xe9tuv\xe9\n---\n\nSteam @salmon{2} with @dill{}.\n",
        )
        .unwrap();

        assert_eq!(
            relative_paths(&run(&base, "tuna")),
            ["tuna mornay.cook"],
            "a bad byte in the body must not fail the search"
        );
        assert_eq!(
            relative_paths(&run(&base, "salmon")),
            ["salmon.cook"],
            "nor must one in the front matter"
        );

        // Found by an ingredient that only appears in the body, so the hit
        // cannot be coming from the file name. This is what needed 0.7.1:
        // 0.7.0 could not score such a file's contents at all.
        assert_eq!(
            relative_paths(&run(&base, "dill")),
            ["salmon.cook"],
            "a term only in the contents must still match"
        );
        assert_eq!(
            relative_paths(&run(&base, "steam dill")),
            ["salmon.cook"],
            "and must still satisfy every term of an AND query"
        );

        // The title survives, bad byte and all, rather than the entry being
        // dropped or left nameless.
        let hit = run(&base, "salmon");
        assert_eq!(hit[0].name.as_deref(), Some("Saumon \u{fffd}tuv\u{fffd}"));

        // The part the bug was really about: one bad file used to fail every
        // query, not just the ones that matched it.
        assert_eq!(
            relative_paths(&run(&base, "flour")),
            ["Breakfast/pancakes.cook"]
        );
    }

    /// The bad bytes are the only thing that stops matching: the readable text
    /// on either side of one is still searchable, and still counts towards an
    /// AND query.
    ///
    /// Exercised through [`matches_every_term`] directly, so that the AND
    /// filter's own reading of a malformed file is pinned here rather than
    /// only through a whole search, where `cooklang-find`'s scoring decides
    /// what the filter ever sees.
    #[test]
    fn text_around_an_invalid_byte_still_matches() {
        let dir = tempfile::TempDir::new().unwrap();
        let path = base(&dir).join("tuna mornay.cook");
        std::fs::write(&path, b"Bake @tuna{1%can} with cr\xe8me.\n").unwrap();

        let matches = |query: &str| {
            let terms: Vec<String> = query.split_whitespace().map(str::to_lowercase).collect();
            matches_every_term(&path, &terms).expect("a bad byte is not an i/o failure")
        };

        assert!(matches("bake"), "text before the bad byte");
        assert!(matches("me."), "text after the bad byte");
        assert!(matches("bake mornay"), "body and file name together");
        assert!(matches("bake me."), "both sides of the bad byte");
        assert!(
            !matches("kohlrabi"),
            "and a term that is absent still misses"
        );
        assert!(
            !matches("bake kohlrabi"),
            "AND still narrows: one missing term is enough"
        );
    }

    /// A file with no valid text in it at all — a binary that landed under a
    /// `.cook` name — is the degenerate case of the same thing: nothing to
    /// match, but nothing to fail over either.
    #[test]
    fn a_file_with_no_valid_text_matches_nothing_and_fails_nothing() {
        let dir = tempfile::TempDir::new().unwrap();
        let path = base(&dir).join("junk.cook");
        std::fs::write(&path, [0xff, 0xfe, 0xff, 0xfe, 0x80, 0x81]).unwrap();

        assert!(
            !matches_every_term(&path, &["tuna".to_string()]).expect("must not fail"),
            "there is no text in it to match"
        );
        assert!(
            matches_every_term(&path, &["junk".to_string()]).expect("must not fail"),
            "but the file name is still a surface to match on"
        );
    }

    /// A file that cannot be read at all is still an error. Lossy decoding is
    /// for bytes that are there and malformed, not for bytes that never
    /// arrived — silently treating an unreadable recipe as an empty one would
    /// turn a fixable problem into results that are quietly wrong.
    #[test]
    fn an_unreadable_file_is_still_an_io_error() {
        let dir = tempfile::TempDir::new().unwrap();
        let missing = base(&dir).join("gone.cook");

        match matches_every_term(&missing, &["tuna".to_string()]) {
            Err(CoreError::Io { path, source }) => {
                assert_eq!(path, missing);
                assert_eq!(source.kind(), std::io::ErrorKind::NotFound);
            }
            other => panic!("expected CoreError::Io, got {other:?}"),
        }
    }

    /// The remaining failures mean a file under the root was unusable, not that
    /// the root was. They are pinned through `search_error` directly, because
    /// provoking them needs a file that breaks between the walk finding it and
    /// the walk reading it.
    ///
    /// `SearchError::GlobError` is absent only because `glob` exposes no way to
    /// construct one; its arm is the one that names the failing file rather
    /// than the root.
    #[test]
    fn a_file_that_cannot_be_read_is_an_io_error_not_a_search_error() {
        use cooklang_find::search::SearchError;
        let root = Utf8Path::new("/recipes");

        let unreadable = search_error(
            SearchError::IoError(std::io::Error::new(
                std::io::ErrorKind::PermissionDenied,
                "denied",
            )),
            root,
        );
        match unreadable {
            CoreError::Io { path, source } => {
                assert_eq!(path, root);
                assert_eq!(source.kind(), std::io::ErrorKind::PermissionDenied);
            }
            other => panic!("expected CoreError::Io, got {other:?}"),
        }

        let unusable = search_error(
            SearchError::RecipeEntryError(cooklang_find::RecipeEntryError::MetadataError(
                "bad front matter".to_string(),
            )),
            root,
        );
        match unusable {
            CoreError::Io { path, source } => {
                assert_eq!(path, root);
                assert!(
                    source.to_string().contains("bad front matter"),
                    "the cause must survive: {source}"
                );
            }
            other => panic!("expected CoreError::Io, got {other:?}"),
        }
    }
}