caixa_core/

dep.rs

use serde::{Deserialize, Serialize};
use thiserror::Error;

/// A single dependency declaration in a `caixa.lisp` manifest.
///
/// **Store model = Git, like Zig.** There is no central registry; a caixa is
/// just a Git repo with a `caixa.lisp` at its root. When `:fonte` is omitted,
/// the resolver falls back to `github:<default-org>/<nome>` (org defaults to
/// `pleme-io`, override via `~/.config/caixa/config.yaml`).
///
/// ```lisp
/// ;; Shorthand — resolves to github:pleme-io/caixa-teia (or your default org):
/// (:nome "caixa-teia" :versao "^0.1")
///
/// ;; Explicit git source:
/// (:nome "caixa-teia"
///  :versao "^0.1"
///  :fonte (:tipo git :repo "github:pleme-io/caixa-teia" :tag "v0.1.0"))
///
/// ;; Arbitrary git URL (not limited to GitHub):
/// (:nome "private-caixa"
///  :versao "*"
///  :fonte (:tipo git :repo "ssh://git@git.example/team/priv-caixa.git" :branch "main"))
///
/// ;; Local path (dev only; not publishable):
/// (:nome "caixa-teia"
///  :versao "0.1.0"
///  :fonte (:tipo path :caminho "../caixa-teia"))
/// ```
#[derive(Serialize, Deserialize, Debug, Clone, PartialEq)]
#[serde(rename_all = "camelCase")]
pub struct Dep {
    /// Caixa name — must match the target caixa's `:nome`.
    pub nome: String,

    /// Semver constraint string (`"^0.1"`, `"~0.1.2"`, `"0.1.0"`, `"*"`).
    pub versao: String,

    /// Where to fetch the caixa from. Defaults to the feira registry.
    #[serde(default, skip_serializing_if = "Option::is_none")]
    pub fonte: Option<DepSource>,

    /// If true, a missing `:fonte` is not a build failure.
    #[serde(default, skip_serializing_if = "is_false")]
    pub opcional: bool,

    /// Feature flags to enable on the target caixa.
    #[serde(default, skip_serializing_if = "Vec::is_empty")]
    pub caracteristicas: Vec<String>,
}

/// Where a dep is fetched from. Tagged via `:tipo` in Lisp.
///
/// Only two shapes — Git and local Path. No central registry variant: a caixa
/// is just a Git repo. Omitting `:fonte` means *"use the default resolver
/// convention"*, which is `github:<default-org>/<nome>`; the resolver fills
/// that in when computing the lacre.
#[derive(Serialize, Deserialize, Debug, Clone, PartialEq, Eq)]
#[serde(tag = "tipo", rename_all = "lowercase")]
pub enum DepSource {
    /// Clone from Git. One of `:tag`, `:rev`, or `:branch` may be set.
    /// `repo` can be a `github:org/repo` shorthand, a full `https://…` URL,
    /// or any git-ssh URL.
    Git {
        repo: String,
        #[serde(default, skip_serializing_if = "Option::is_none")]
        tag: Option<String>,
        #[serde(default, skip_serializing_if = "Option::is_none")]
        rev: Option<String>,
        #[serde(default, skip_serializing_if = "Option::is_none")]
        branch: Option<String>,
    },
    /// Local filesystem path — dev only; cannot be published.
    Path { caminho: String },
}

impl DepSource {
    /// Build a registry-shorthand git source (`github:<org>/<nome>`).
    ///
    /// This is the resolver-side fallback for `dep.fonte: None`, not an
    /// author-surface value — it carries no pin (`:tag`/`:rev`/`:branch`
    /// all `None`) and is therefore rejected by [`Self::validate`]. The
    /// resolver fills the pin in at fetch time from the resolved commit;
    /// authors never serialize this shape as a `Dep::fonte` value.
    #[must_use]
    pub fn default_github(org: &str, nome: &str) -> Self {
        Self::Git {
            repo: format!("github:{org}/{nome}"),
            tag: None,
            rev: None,
            branch: None,
        }
    }

    /// Substrate-canonical per-`:fonte` sole-set git-pin scalar accessor
    /// every consumer that reads "which single git ref does this source
    /// resolve to?" keys off — returns the author-declared `:tag` /
    /// `:rev` / `:branch` byte-string verbatim as an `Option<&str>`,
    /// borrowed from the typed slot's own `Option<String>` storage; `None`
    /// on [`Self::Path`] (a path source carries no git-ref) and on a
    /// [`Self::Git`] variant whose `tag`, `rev`, and `branch` are all
    /// `None` (the [`Self::default_github`] shorthand shape the resolver
    /// materializes when the author omits `:fonte` — rejected by
    /// [`Self::validate`], but the accessor's return is defined on this
    /// arm too so pre-validate consumers reach for the same typed dispatch
    /// as post-validate ones).
    ///
    /// **Precedence: rev > tag > branch.** The canonical precedence every
    /// per-`:fonte` git-ref consumer already applies: caixa-resolver's
    /// per-fetch `git checkout <ref>` reads through the same
    /// `rev.or(tag).or(branch)` cascade at caixa-resolver/src/resolve.rs,
    /// and caixa-crd's `dep_into_ref` `CaixaSource.git_ref` fill reads
    /// through the same cascade at caixa-crd/src/conversion.rs. The
    /// [`Self::validate`] gate enforces "exactly one pin set" — under
    /// that invariant every accepted [`Self::Git`] carries exactly one
    /// non-`None` pin and the precedence is unobservable, but the
    /// precedence remains defined for pre-validate consumers (the
    /// resolver's `MissingPin` diagnostic path, the caixa-crd
    /// round-trip's default `"main"` fallback the author never sees a
    /// diagnostic on) and defense-in-depth for a hypothetical future
    /// state where multiple pins survive the gate. The precedence is
    /// **rev before tag** because `:rev` (a git commit OID) is the
    /// reproducibility-strongest identifier — an OID resolves to exactly
    /// one commit regardless of which refname points at it, whereas
    /// `:tag` and `:branch` are refnames the remote can silently move
    /// (a tag re-push, a branch head advance); the resolver's freeze
    /// step at fetch time promotes the resolved commit to `:rev` for
    /// exactly this reason. **Tag before branch** because `:tag` is
    /// conventionally immutable (a release tag) whereas `:branch` is
    /// conventionally mutable (a tracking ref) — a caixa carrying both
    /// a release tag and a tracking branch reads as "prefer the release
    /// pin, fall through to the tracking pin only if the release is
    /// missing". The cascade order also matches the byte-order every
    /// per-`:tag`/`:rev`/`:branch` diagnostic tuple this crate emits
    /// (`(":tag", tag), (":rev", rev), (":branch", branch)` — see
    /// [`Self::validate`]'s `pins` array).
    ///
    /// Prior to this lift the "sole set pin" projection sat twice in the
    /// workspace — inline at caixa-resolver's `fetch_git` (`let gitref =
    /// rev.or(tag).or(branch).ok_or_else(|| ResolveError::MissingPin
    /// { … })?;`) and at caixa-crd's `dep_into_ref`
    /// (`git_ref: rev.clone().or(tag.clone()).or(branch.clone())
    /// .unwrap_or_else(|| "main".to_string())`) — two open-coded copies
    /// of the same precedence cascade with no compile-time link back to
    /// the typed slot. A future extension of the pin axis to a richer
    /// author surface (a `:commit` pin peer of `:rev` once the substrate
    /// grows a signed-commit-verification pin, a `:ref` pin the M4
    /// substrate operator resolves per-cluster ahead of fetch, a
    /// promotion of the plain `Option<String>` pins to a typed
    /// `GitPin::{Rev(Oid), Tag(RefName), Branch(RefName)}` newtype
    /// once the sibling [`crate::render::is_git_oid`] /
    /// [`crate::render::is_git_ref_name`] gates land as typed
    /// constructors) would have had to be threaded through both
    /// open-coded copies in lockstep or the resolver's `git checkout`
    /// target would silently disagree with the CRD's `git_ref` fill —
    /// an author's `(:fonte (:tipo git :repo "…" :rev "deadbeef" :tag
    /// "v1"))` would ship with the resolver checking out `deadbeef`
    /// while the CRD round-trip re-emitted a Dep pointing at `v1`, one
    /// lacre closure disagreeing with the emitted K8s CR the operator
    /// reads. Lifting the resolution to a typed method on the substrate
    /// primitive means both downstream consumers reach for exactly one
    /// typed dispatch — the resolver's accept-set migrates as a unit on
    /// any future pin-axis addition.
    ///
    /// Peer of the sibling outer-`Dep` [`Dep::fonte`] (d65d1bf)
    /// `Option<&DepSource>` composite-reference accessor on the outer-
    /// `Dep` `:fonte`-slot axis — extended one nesting level down onto
    /// the per-[`Self::Git`]-variant sole-set-pin projection axis every
    /// git-fetching consumer runs after the outer `:fonte` slot resolves
    /// to a [`Self::Git`] shape. Same "one typed dispatch on the
    /// substrate primitive, thin projections at each consumer" discipline
    /// the outer accessor family already carries.
    #[must_use]
    pub fn sole_pin(&self) -> Option<&str> {
        match self {
            Self::Git {
                tag, rev, branch, ..
            } => rev.as_deref().or(tag.as_deref()).or(branch.as_deref()),
            Self::Path { .. } => None,
        }
    }

    /// Validate the `:fonte` value-shape: every author-surface
    /// `:fonte (:tipo git …)` must carry a non-empty `:repo` and
    /// exactly one of `:tag` / `:rev` / `:branch` set to a non-empty
    /// value; every `:fonte (:tipo path …)` must carry a non-empty
    /// `:caminho`.
    ///
    /// Called from [`Dep::validate`] with the dep's `:nome` so every
    /// diagnostic carries the offending entry verbatim — same
    /// self-locating shape the `:deps :versao` (2420c44),
    /// `:membros :versao` (9888b13), `:children :versao` (b38ff3a),
    /// `:placement :clusters` (6cbb900), and `:membros :caixa`
    /// (3f9d7a0) gates already expose.
    ///
    /// Until this gate landed `:fonte` was the only `:deps`-related
    /// typed surface still untyped past `Caixa::from_lisp`:
    /// - Empty `:repo` (`(:tipo git :repo "" :tag "v1")`) silently
    ///   passed parse and surfaced as a git-clone failure at
    ///   lacre-resolve time, far from the source caixa.lisp.
    /// - A bare `(:tipo git :repo "…")` with no `:tag`/`:rev`/`:branch`
    ///   passed parse and surfaced as the resolver's
    ///   [`ResolveError::MissingPin`](../../caixa-resolver/src/resolve.rs)
    ///   at fetch time, again far from the source caixa.lisp; lifting
    ///   to validate-time gives the author the same diagnostic at the
    ///   edit site.
    /// - `(:tipo git :repo "…" :tag "v1" :branch "main")` — multiple
    ///   pins set — passed parse and the resolver silently picked
    ///   `:rev > :tag > :branch`, ignoring the other pins with no
    ///   diagnostic; the author had no way to know their `:branch`
    ///   was dropped. This is the canonical "pin drift" footgun.
    /// - An empty pin value (`(:tipo git :repo "…" :tag "")`) silently
    ///   passed parse and surfaced as `git checkout ""` at fetch time.
    /// - Empty `:caminho` (`(:tipo path :caminho "")`) silently passed
    ///   parse and surfaced as
    ///   [`ResolveError::MissingPath`](../../caixa-resolver/src/resolve.rs)
    ///   with `path: PathBuf("")` — not actionable.
    ///
    /// Each rejected shape maps to a typed
    /// [`DepError::Fonte*`] variant that names the offending
    /// dep's `:nome` and the specific axis, so the author can grep
    /// their caixa.lisp for the `:nome "<nome>"` block and fix it in
    /// one edit.
    pub fn validate(&self, nome: &str) -> Result<(), DepError> {
        match self {
            Self::Git {
                repo,
                tag,
                rev,
                branch,
            } => {
                if repo.is_empty() {
                    return Err(DepError::FonteRepoEmpty {
                        nome: nome.to_string(),
                    });
                }
                // The `:repo` value flows verbatim into the caixa-resolver's
                // `git clone <repo>` subprocess invocation. Until this gate
                // landed `:repo` was the last untyped `:fonte`-related axis
                // past the empty arm: a malformed-but-non-empty repo URL
                // (`":repo "github:p/x ""` trailing space, paste-from-doc;
                // `":repo "-upload-pack=evil""` leading `-` — the canonical
                // CLI-argument-injection vector at the `git clone` boundary;
                // `":repo "pleme-io/caixa-teia""` missing scheme — `git clone`
                // reads as a relative filesystem path rather than the
                // GitHub-shorthand expansion; `":repo "github:p/x\n""`
                // embedded newline; `":repo "github:café/x""` raw non-ASCII)
                // silently passed validate and the failure surfaced at
                // lacre-resolve time with a porcelain-quoting-confused error
                // far from the source caixa.lisp. The lifted predicate makes
                // the git-porcelain-URL intersection-floor a substrate-level
                // invariant at validate time, peer with the three pin axes
                // (`:tag` + `:branch` via [`crate::render::is_git_ref_name`],
                // e70d213; `:rev` via [`crate::render::is_git_oid`], be07fd5)
                // — every `:fonte (:tipo git …)` past validate is now
                // structurally accept-shaped on every axis the resolver
                // consumes (the `:repo` URL the `git clone` invokes against,
                // the `:tag`/`:branch` refname `git fetch`/`git checkout`
                // accepts, the `:rev` commit OID the lacre's content-
                // addressing equality probe resolves), closing the
                // `:fonte` slot's value-shape trajectory end-to-end.
                if let Err(reason) = crate::render::is_git_repo_url(repo) {
                    return Err(DepError::FonteRepoShape {
                        nome: nome.to_string(),
                        repo: repo.clone(),
                        reason,
                    });
                }
                let pins: [(&'static str, Option<&String>); 3] = [
                    (":tag", tag.as_ref()),
                    (":rev", rev.as_ref()),
                    (":branch", branch.as_ref()),
                ];
                let set: Vec<&'static str> =
                    pins.iter().filter_map(|(n, v)| v.map(|_| *n)).collect();
                match set.len() {
                    0 => {
                        return Err(DepError::FontePinMissing {
                            nome: nome.to_string(),
                        });
                    }
                    1 => {
                        for (pin, value) in pins {
                            if value.is_some_and(String::is_empty) {
                                return Err(DepError::FontePinEmpty {
                                    nome: nome.to_string(),
                                    pin: pin.to_string(),
                                });
                            }
                        }
                    }
                    _ => {
                        return Err(DepError::FontePinAmbiguous {
                            nome: nome.to_string(),
                            pins: set.join(", "),
                        });
                    }
                }
                // Per-pin value-shape gate. The refname-shaped axes
                // (`:tag` + `:branch`) route through
                // [`crate::render::is_git_ref_name`]; the hex-OID-shaped
                // `:rev` axis routes through
                // [`crate::render::is_git_oid`]. The two predicates
                // partition the `:fonte` pin axes structurally — refname
                // vs. hex commit — so a cross-axis mis-slot (the
                // canonical "I conflated `:rev` and `:branch`" footgun:
                // `:rev "main"` defeating the reproducibility contract,
                // `:tag "deadbeef…"` mis-slotting a SHA into the
                // refname-shaped axis) lands at the offending axis's
                // predicate, not at lacre-resolve `git fetch` /
                // `git checkout` time. Their valid sets intersect at
                // the empty set: every refname is rejected by
                // `is_git_oid`, every OID is rejected by
                // `is_git_ref_name`, structurally.
                //
                // Until this gate landed `:tag` / `:branch` were the
                // refname-shaped axes still untyped past the empty-pin
                // arm: a malformed-but-non-empty refname
                // (`:tag "v0.1.0 "` trailing space — the canonical
                // paste-from-doc footgun; `:tag "v0.1.0.lock"` colliding
                // with git's atomic-rename guard suffix; `:tag "../escape"`
                // path-traversal via consecutive dots; `:branch "main "`
                // trailing space; `:branch "feature/foo bar"` embedded
                // space; `:branch "@"` the literal HEAD alias;
                // `:branch "refs/heads/main"` the fully-qualified ref
                // copied from `git show-ref` output that resolves to
                // a literal ref named `refs/heads/refs/heads/main` on
                // disk) silently passed validate; the `:rev` axis was
                // the last `:fonte`-related axis still untyped past the
                // empty-pin arm: a malformed-but-non-empty hex-OID
                // (`:rev "main"` conflating with `:branch` — the
                // reproducibility-contract leak; `:rev "v0.1.0"`
                // conflating with `:tag` — the same mis-slot on the
                // refname/OID boundary; `:rev "c0ffee"` an abbreviated
                // 6-char prefix that's ambiguous across repo history;
                // `:rev "DEADBEEF…"` an uppercase OID that round-trips
                // inconsistently against `git rev-parse HEAD`'s
                // lowercase emission) silently passed validate and the
                // failure surfaced at lacre-resolve `git fetch` /
                // `git checkout` time with a quoting-confused error
                // far from the source caixa.lisp, with no field naming
                // which `:deps` entry carried the typo. Lifting both
                // gates to caixa-build time matches the value-shape
                // trajectory the peer typed axes already follow
                // (c4213a4 typed WitContract endpoint/subject/slot;
                // eb3456d :entrada :paths; c7d05ec :entrada :host;
                // 4f0390b :contratos :endpoint; 6226bf4 :contratos :wit;
                // 63e18a0 :contratos :subject; 2f4316e :contratos
                // :slot; e70d213 :fonte :tag + :branch) — the typed
                // slot's valid set matches its downstream consumer's
                // accepted set (here, the git porcelain's refname /
                // commit-OID grammars at `git fetch` / `git checkout`
                // time), structurally. Same diagnostic shape every
                // per-axis value-shape lift already exposes
                // (`*Invalid { axis, reason }`); the `value:` field
                // carries the offending refname / OID verbatim so the
                // author can grep their caixa.lisp for the
                // `:tag "<value>"` / `:branch "<value>"` /
                // `:rev "<value>"` literal and fix it in one edit.
                for (pin, value) in [(":tag", tag.as_ref()), (":branch", branch.as_ref())] {
                    if let Some(v) = value
                        && let Err(reason) = crate::render::is_git_ref_name(v)
                    {
                        return Err(DepError::FontePinShape {
                            nome: nome.to_string(),
                            pin: pin.to_string(),
                            value: v.clone(),
                            reason,
                        });
                    }
                }
                if let Some(v) = rev.as_ref()
                    && let Err(reason) = crate::render::is_git_oid(v)
                {
                    return Err(DepError::FontePinShape {
                        nome: nome.to_string(),
                        pin: ":rev".to_string(),
                        value: v.clone(),
                        reason,
                    });
                }
                Ok(())
            }
            Self::Path { caminho } => Self::validate_caminho(nome, caminho),
        }
    }

    /// Reproducibility + path-API gate on the `:fonte (:tipo path …)`
    /// `:caminho` axis. Walks the leading-byte cascade closed by the
    /// b94fd83 (`/`), a5c248e (`~`), and f4efe9c (`$`) arms; the
    /// orthogonal embedded-control-byte arm (d624c8d) covering
    /// `0x00..=0x1F` plus `0x7F` anywhere in the value; and the
    /// embedded-`\` Windows-path-separator arm closing the
    /// cross-host-OS-separator divergence vector on the same
    /// THEORY.md §V.2 render-determinism axis.
    ///
    /// Extracted from [`Self::validate`]'s `Self::Path` arm because the
    /// per-arm cascade now spans nine diagnostic shapes — every new
    /// `:caminho` arm (a future `&` / `;` / `|` shell-metachar arm,
    /// a future glob-metachar `*` / `?` arm) lands here rather than
    /// re-inflating `Self::validate`. The
    /// function stays a thin per-arm linear walk for one reason: each
    /// arm's diagnostic carries a distinct typed [`DepError`] variant
    /// rather than a parser-shaped `reason` string, so collapsing the
    /// cascade onto a generic [`crate::render`] predicate would regress
    /// the per-arm self-locating diagnostic that `feira lint` consumers
    /// depend on. The wrapped predicate trajectory ([`crate::render::is_dns_1123_label`],
    /// [`crate::render::is_git_repo_url`], etc.) lives on the
    /// reason-string-shaped axes; the `:caminho` axis keeps its
    /// per-arm variant shape.
    #[allow(
        clippy::too_many_lines,
        reason = "the per-arm cascade is structurally flat by design — every \
                  `:caminho` arm carries its own typed [`DepError`] variant + \
                  per-arm Why comment, so collapsing the cascade onto a generic \
                  [`crate::render`] predicate would regress the per-arm self-locating \
                  diagnostic the `feira lint` consumer surface depends on"
    )]
    fn validate_caminho(nome: &str, caminho: &str) -> Result<(), DepError> {
        if caminho.is_empty() {
            return Err(DepError::FonteCaminhoEmpty {
                nome: nome.to_string(),
            });
        }
        // Reproducibility gate on the `:fonte (:tipo path …)`
        // `:caminho` axis. The lacre pipeline embeds the value
        // verbatim in its per-dep content-address
        // (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189) and that string
        // folds into the BLAKE3 closure the lacre keys every
        // downstream consumer (the substrate's reproducibility
        // contract, CAIXA-SDLC §III.2 — the lacre is the
        // build's content-addressed identity, peer of the Nix
        // store path) against. Until this gate landed an
        // absolute `:caminho` (`/home/me/work/caixa-teia` — the
        // canonical "I dragged the folder out of Finder into
        // my editor" footgun; `/Users/alice/dev/caixa-teia` on
        // the macOS path-layout peer; the
        // `${WORKSPACE}/caixa-teia` shell-expanded literal
        // pasted from a CI manifest) silently passed validate
        // and the failure surfaced *as a successful build with
        // a divergent lacre*: the BLAKE3 closure on Alice's
        // workstation differed from the closure on Bob's
        // workstation, two CI runners with different
        // `${HOME}` layouts emitted two distinct
        // content-addresses for the byte-identical caixa, and
        // the substrate's "the lacre is the build's identity"
        // contract silently broke far from the source
        // caixa.lisp — the most insidious failure mode the
        // typed slot can carry (no error surfaces; the
        // divergence is invisible until two machines compare
        // lacres). The same THEORY.md §V.2 render-determinism
        // discipline `is_sandboxed_relative_path` already
        // applies on the M2 typed path-slots
        // (`:behavior :on-*`, `:upgrade-from :state-change
        // :script`, `:bibliotecas`, `:exe`, `:servicos`), here
        // narrowed to the absolute-vs-relative axis only:
        // `:fonte :caminho`'s canonical author-surface form is
        // the `..`-traversing sibling-workspace path
        // (`"../caixa-teia"`, the in-tree dev-dep frame), so a
        // full `is_sandboxed_relative_path` lift would
        // structurally reject every legitimate path-fonte
        // dep. The narrower
        // `std::path::Path::is_absolute` cut admits the
        // sibling-workspace form while still rejecting the
        // host-layout-leaking absolute shape — the
        // reproducibility contract bites at exactly the
        // absolute boundary, and that's the axis the
        // substrate-level invariant is meant to hold. Same
        // diagnostic shape every per-axis value-shape lift on
        // the surrounding [`DepError::Fonte*`] cluster carries
        // (the offending `:nome` + offending `:caminho`
        // quoted verbatim so the author can grep their
        // caixa.lisp for the `:caminho "<value>"` literal and
        // fix it in one edit). The empty arm strictly
        // precedes this arm so the blank-string footgun
        // surfaces the more self-locating
        // `FonteCaminhoEmpty` diagnostic (the empty string
        // is not absolute under `Path::new("").is_absolute()`
        // so the precedence is a no-op at value level — the
        // pin matters only at the diagnostic-shape level if
        // a future codec round-trip ever produces an empty
        // string that probes as absolute).
        if std::path::Path::new(caminho).is_absolute() {
            return Err(DepError::FonteCaminhoAbsolute {
                nome: nome.to_string(),
                caminho: caminho.to_string(),
            });
        }
        // Reproducibility gate's tilde-expansion arm. The b94fd83
        // `FonteCaminhoAbsolute` closes the leading-`/`
        // host-layout-leak; a `:caminho "~/work/caixa-teia"` (the
        // canonical paste-from-shell-prompt / paste-from-`cd ~`-
        // doc footgun) silently passed both the empty arm and
        // the absolute arm because `Path::new("~").is_absolute()`
        // returns `false` — `~` is a shell-expansion convention,
        // not a POSIX path component, so `std::path::Path` treats
        // it as a literal directory-name segment. The lacre
        // pipeline then embedded the value verbatim
        // (`conteudo: format!("path:~/work/caixa-teia")`) and the
        // failure mode forked per consumer:
        //
        //   - The caixa-resolver's `Path` arm folds `:caminho`
        //     through `Path::new(caminho).join(<file>)` without
        //     `~`-expansion, so the build looked for a literal
        //     `./~/work/caixa-teia` subdirectory and failed at
        //     resolve time with a `No such file or directory`
        //     error far from the source caixa.lisp (the lacre
        //     itself, though, was already byte-identical across
        //     machines — every machine emitted the same
        //     `path:~/work/caixa-teia` content-address).
        //   - A future caixa-resolver pass that *does* expand `~`
        //     (the canonical shell-convention idiom every
        //     resolver eventually reaches for once an author
        //     reports the literal-`~`-directory bug) would re-
        //     introduce the host-layout-leak the b94fd83 absolute
        //     gate closes: Alice's `~` expands to `/home/alice`,
        //     Bob's to `/home/bob`, two CI runners with different
        //     `$HOME` layouts resolve to two distinct paths for
        //     the byte-identical caixa, and the substrate's
        //     "the lacre is the build's identity" contract
        //     silently breaks far from the source caixa.lisp.
        //
        // Closing the gate at `DepSource::validate` (here at the
        // canonical caixa-build-time boundary, peer with the
        // absolute arm above) refuses both failure modes
        // structurally: the typed accepted set excludes every
        // `~`-prefixed authoring shape, so the resolver is
        // free to grow `~`-expansion (or any other convention-
        // expansion the substrate adopts) without re-opening
        // the host-layout-leak at the typed boundary. Same
        // diagnostic shape every per-axis value-shape gate on
        // the surrounding [`DepError::Fonte*`] cluster carries
        // (the offending `:nome` + offending `:caminho` quoted
        // verbatim so the author can grep their caixa.lisp for
        // the `:caminho "<value>"` literal and fix it in one
        // edit).
        //
        // The cascade preserves narrower-diagnostic-first
        // ordering: `FonteCaminhoEmpty` → `FonteCaminhoAbsolute`
        // → `FonteCaminhoTildeExpansion`. The empty arm
        // structurally precedes both (the bytes "" / "~" don't
        // overlap), and the absolute arm structurally precedes
        // the tilde arm (an absolute path can't start with `~`
        // since absolute paths start with `/`; the bytes "/" /
        // "~" don't overlap either). Both arms are
        // value-disjoint, so the precedence is a no-op at value
        // level — the pin matters only at the diagnostic-shape
        // level if a future codec round-trip ever produces a
        // value that probes as both absolute and tilde-prefixed.
        if caminho.starts_with('~') {
            return Err(DepError::FonteCaminhoTildeExpansion {
                nome: nome.to_string(),
                caminho: caminho.to_string(),
            });
        }
        // Reproducibility gate's shell-variable-expansion arm.
        // The b94fd83 `FonteCaminhoAbsolute` closes the leading-`/`
        // host-layout-leak; the a5c248e `FonteCaminhoTildeExpansion`
        // closes the leading-`~` shell-home-expansion shape; the
        // leading-`$` is the sibling shell-variable-expansion shape
        // — same host-layout-leaking semantic, different syntactic
        // surface. A `:caminho "$HOME/work/caixa-teia"` (the
        // canonical paste-from-`echo $HOME`-doc footgun) and the
        // `${VAR}`-braced variant (`"${WORKSPACE}/caixa-teia"` —
        // the canonical paste-from-CI-manifest footgun every
        // GitHub Actions / GitLab CI / Drone manifest carries)
        // silently passed every prior arm because
        // `Path::is_absolute` returns false on `$` (the `$` is a
        // shell convention, not a POSIX path component, so
        // `std::path::Path` treats it as a literal directory-name
        // segment) and the tilde arm's `starts_with('~')` doesn't
        // fire.
        //
        // Same per-consumer failure-fork the tilde arm closes:
        //
        //   - The caixa-resolver's `Path` arm folds `:caminho`
        //     through `Path::new(caminho).join(<file>)` without
        //     `$`-expansion, so the build looks for a literal
        //     `./$HOME/work/caixa-teia` subdirectory and fails at
        //     resolve time with a `No such file or directory`
        //     error far from the source caixa.lisp.
        //   - A future caixa-resolver pass that *does* expand
        //     `$VAR` (the shell-convention idiom every resolver
        //     eventually reaches for once an author reports the
        //     literal-`$HOME`-directory bug, especially for CI's
        //     `${WORKSPACE}` idiom) would re-introduce the host-
        //     layout-leak the b94fd83 absolute gate closes:
        //     Alice's `$HOME` expands to `/home/alice`, Bob's to
        //     `/home/bob`, two CI runners with different
        //     `${WORKSPACE}` layouts resolve to two distinct
        //     paths for the byte-identical caixa, and the
        //     substrate's "the lacre is the build's identity"
        //     contract silently breaks far from the source
        //     caixa.lisp.
        //
        // Closing the gate at `DepSource::validate` (here at the
        // canonical caixa-build-time boundary, peer with the
        // absolute + tilde arms above) refuses both failure modes
        // structurally. Same diagnostic shape every per-axis
        // value-shape gate on the surrounding [`DepError::Fonte*`]
        // cluster carries (the offending `:nome` + offending
        // `:caminho` quoted verbatim).
        //
        // The cascade preserves narrower-diagnostic-first ordering:
        // `FonteCaminhoEmpty` → `FonteCaminhoAbsolute` →
        // `FonteCaminhoTildeExpansion` → `FonteCaminhoVarExpansion`.
        // The empty arm structurally precedes all three subsequent
        // arms; the absolute arm structurally precedes both the
        // tilde and the var arms (absolute paths start with `/`,
        // the bytes `/` / `~` / `$` don't overlap at the leading
        // position); the tilde arm structurally precedes the var
        // arm (`~` and `$` don't overlap at the leading position).
        // Every pair is value-disjoint, so the precedence is a
        // no-op at value level — the pin matters only at the
        // diagnostic-shape level if a future codec round-trip ever
        // produces a probe-as-both value.
        //
        // The gate covers every leading-`$` shape: the canonical
        // `"$HOME/work/caixa-teia"` (POSIX shell), the braced
        // `"${HOME}/work/caixa-teia"` (POSIX shell braces), the
        // CI-manifest idiom `"${WORKSPACE}/caixa-teia"` (the
        // GitHub Actions / GitLab CI / Drone paste footgun), the
        // XDG idiom `"$XDG_CONFIG_HOME/caixa"`, and the bare `$`
        // (degenerate "I meant `$HOME` and forgot the rest"). All
        // shapes route through the same `caminho.starts_with('$')`
        // byte check.
        if caminho.starts_with('$') {
            return Err(DepError::FonteCaminhoVarExpansion {
                nome: nome.to_string(),
                caminho: caminho.to_string(),
            });
        }
        // Reproducibility gate's leading-space arm. The b94fd83 / a5c248e /
        // f4efe9c arms closed the leading-byte host-layout-leak shapes
        // (`/` / `~` / `$`); the embedded-control-byte arm below closes
        // every byte in `0x00..=0x1F` plus `0x7F` (which already includes
        // tab `0x09`, LF `0x0A`, CR `0x0D` — every ASCII whitespace
        // *except* the ASCII space byte `0x20`). The bare ASCII space at
        // the leading position is the orthogonal paste-from-aligned-doc
        // shape that silently passed every prior arm: `Path::is_absolute`
        // returns false on `" ../caixa-teia"` (the leading byte is `0x20`
        // not `0x2F`), `0x20` is not `~` / `$` / `\` / a control byte, and
        // the value's last byte is not `/`, so the canonical
        // paste-from-aligned-`caixa.lisp`-doc footgun (every `:fonte`
        // form in a multi-entry `:deps` block sits at the same column —
        // an author selecting `"<sp><sp><sp>../caixa-teia"` and pasting
        // it from the rendered alignment into a fresh entry preserves the
        // leading whitespace verbatim) silently rendered as a path with
        // a leading-space directory component the resolver folds through
        // `Path::join` looking for a literal `./ ../caixa-teia`
        // subdirectory that fails at resolve time with a non-self-
        // locating `No such file or directory` error.
        //
        // The lacre pipeline's reproducibility contract bites
        // strictly at this byte: `path:" ../caixa-teia"` and
        // `path:"../caixa-teia"` yield distinct BLAKE3 closures
        // (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189) for the byte-divergent /
        // semantic-identical caixa, and the substrate's "the lacre is
        // the build's identity" contract (CAIXA-SDLC §III.2) silently
        // breaks across two workstations whose authors differ only in
        // paste-from-aligned-doc whitespace habits — the most insidious
        // failure mode the typed slot can carry (no error surfaces; the
        // divergence is invisible until two machines compare lacres).
        //
        // The arm fires AFTER the absolute / tilde / var leading-byte
        // arms (each names the more self-locating shell-convention
        // diagnostic on values that probe as that arm's leading-byte
        // sentinel followed by a leading space — e.g.
        // `:caminho "/  /foo"` surfaces `FonteCaminhoAbsolute` because
        // the leading byte is `/`, not space) and BEFORE the
        // embedded-control-byte arm (a leading-space value with an
        // embedded control byte surfaces the broader leading-space
        // diagnostic because the cascade walks leading-byte arms first
        // — peer with how `FonteCaminhoAbsolute` precedes
        // `FonteCaminhoControlChar` on `"/etc/passwd\n"`).
        //
        // The peer single-token-shaped axes already reject leading
        // whitespace on the same paste-from-aligned-doc contract:
        // [`crate::render::is_git_repo_url`] rejects leading whitespace
        // on `:fonte :repo`, [`crate::render::is_git_ref_name`] rejects
        // leading whitespace on `:fonte :tag`/`:branch`,
        // [`crate::render::is_chart_description_shape`] rejects leading
        // whitespace on `:descricao`,
        // [`crate::render::is_spdx_expression_shape`] rejects leading
        // whitespace on `:licenca`. Closing the same byte on
        // `:fonte :caminho` makes the substrate-wide "no leading ASCII
        // space anywhere in a typed string slot" invariant structurally
        // consistent across every value-shape-gated typed surface (the
        // `:caminho` axis was the last typed string surface still
        // admitting a leading space byte).
        if caminho.starts_with(' ') {
            return Err(DepError::FonteCaminhoLeadingWhitespace {
                nome: nome.to_string(),
                caminho: caminho.to_string(),
            });
        }
        // Reproducibility gate's leading-`-` CLI-argument-injection arm.
        // The b94fd83 + a5c248e + f4efe9c + LeadingWhitespace arms closed
        // the four prior leading-byte shapes (`/` / `~` / `$` / space);
        // this arm closes the orthogonal leading-`-` axis on the same
        // subprocess-argument-boundary the peer `is_git_repo_url` arm
        // (render.rs:2037, `-upload-pack=…` on `:fonte :repo`) and
        // `is_git_ref_name` arm (render.rs:1381, 5a28454, `-stable` on
        // `:fonte :tag` / `:branch`) already reject.
        //
        // The lacre pipeline embeds `:caminho` verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189) and the resolver folds the
        // value through `Path::join` looking for a literal `./{caminho}`
        // subdirectory. Every downstream subprocess that consumes the
        // resolved path — a `git -C {caminho} <verb>` invocation, a
        // future `feira tofu` `terraform -chdir={caminho}` shell-out, a
        // future operator-side `nix build --path {caminho}` spawn, an
        // `xargs` / `find {caminho}` / `stat {caminho}` /
        // `rm -rf {caminho}` cleanup — reinterprets a leading-`-` value
        // as a CLI flag rather than a positional path when the
        // subprocess invocation does not carry a `--` argument-list
        // terminator between the flag block and the path argument. The
        // canonical footguns:
        //
        //   - `:caminho "-rf"` — bare short-flag paste (`rm -rf` /
        //     `find -rf` reinterpretation; the byte the peer
        //     `FonteCaminhoShellSemicolon` arm's `; rm -rf build`
        //     example paste-idiom carries as its first token).
        //   - `:caminho "-C"` — `git -C` config-injection paste
        //     (`git -C -C` reinterprets the second `-C` as another
        //     `--change-directory` flag rather than the path
        //     argument; the canonical `git -C <path>` porcelain
        //     idiom every multi-repo workspace tool carries).
        //   - `:caminho "--upload-pack=cat /etc/passwd"` — the
        //     canonical long-flag CLI-arg-injection vector at every
        //     git porcelain entry point (`git clone`, `git fetch`,
        //     `git ls-remote`) that consumes a path or URL
        //     argument; peer with `is_git_repo_url`'s leading-`-`
        //     arm (render.rs:2037) on the sibling `:fonte :repo`
        //     axis, which the arm's diagnostic explicitly cites.
        //   - `:caminho "--config=…"` / `:caminho "-c"` — git-config
        //     override paste-idiom (paste-from-`git -c foo=bar`
        //     shell-history footgun that reinterprets the value as
        //     a `[foo] bar` config injection on every git porcelain
        //     entry point).
        //
        // POSIX `std::path::Path` treats a leading `-` as a literal
        // filename byte, so the resolver folds `-rf` through `Path::join`
        // and looks for a literal `./-rf` subdirectory — the failure
        // surfaces at resolve time with a non-self-locating `No such
        // file or directory` error far from the source caixa.lisp, and
        // the value rides through the lacre content-address into every
        // downstream shell-spawned subprocess. On any consumer that
        // shells out without the `--` terminator (the common case at
        // every porcelain entry-point) the reinterpretation is silent
        // and the failure mode is arbitrary-argument-injection.
        //
        // The arm fires AFTER the absolute / tilde / var / leading-space
        // leading-byte arms (each names the more self-locating shell-
        // convention diagnostic on values that probe as that arm's
        // leading-byte sentinel — the byte sets are pairwise disjoint at
        // the leading position, so the precedence pin is a no-op at
        // value level, but the ordering keeps every leading-byte arm's
        // diagnostic-shape stable) and BEFORE the embedded-control-byte
        // arm (a leading-`-` value with an embedded control byte
        // surfaces the narrower leading-`-` diagnostic because the
        // cascade walks leading-byte arms first — peer with how
        // `FonteCaminhoAbsolute` precedes `FonteCaminhoControlChar` on
        // `"/etc/passwd\n"`, and how `FonteCaminhoLeadingWhitespace`
        // precedes `FonteCaminhoControlChar` on `" ../foo\n"`).
        //
        // The peer single-token-shaped axes already reject leading `-`
        // on the same CLI-arg-injection contract:
        // [`crate::render::is_git_repo_url`] rejects it on `:fonte :repo`
        // (render.rs:2037), [`crate::render::is_git_ref_name`] rejects
        // it on `:fonte :tag` / `:fonte :branch` (render.rs:1381,
        // 5a28454), [`crate::render::is_dns_1123_label`] rejects it on
        // every DNS-1123-shaped axis (top-level Caixa `:nome`, `:membros
        // :caixa`, `:children :caixa`, `:deps :nome`, cluster names),
        // [`crate::render::is_cargo_feature_name`] rejects it on
        // `:caracteristicas`, and the feira `init` / `add <nome>`
        // positional gate (868c191) rejects it on the CLI positional
        // itself. Closing the same byte on `:fonte :caminho` makes the
        // substrate-wide "no leading `-` anywhere in a typed single-
        // token string slot routed through a subprocess argument"
        // invariant structurally consistent across every value-shape-
        // gated typed surface (the `:caminho` axis was the last typed
        // string surface still admitting a leading `-` byte).
        if caminho.starts_with('-') {
            return Err(DepError::FonteCaminhoLeadingHyphen {
                nome: nome.to_string(),
                caminho: caminho.to_string(),
            });
        }
        // Reproducibility gate's embedded-control-byte arm. The
        // b94fd83 + a5c248e + f4efe9c arms closed the three
        // leading-byte host-layout-leak shapes (`/` / `~` / `$`);
        // this arm closes the orthogonal embedded-control-byte
        // axis — any ASCII control byte (`0x00..=0x1F` plus
        // `0x7F` DEL) appearing anywhere in `:caminho`. Same
        // shape every peer single-token-typed-slot value-shape
        // predicate the surrounding [`crate::render`] cluster
        // gates against (the lifted `is_git_repo_url` arm on
        // `:fonte :repo`, the `is_git_ref_name` arm on
        // `:tag`/`:branch`, the `is_chart_description_shape` /
        // `is_chart_maintainer_name_shape` /
        // `is_chart_keyword_shape` arms on the
        // Helm-chart-shaped axes); now consistent on the
        // `:caminho` axis too.
        //
        // Until this gate landed any embedded control byte
        // silently passed validate, the lacre pipeline embedded
        // the value verbatim in its per-dep content-address
        // (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), and the failure
        // forked per byte and per consumer:
        //
        //   - NUL (`0x00`) the canonical "POSIX paths cannot
        //     contain a NUL byte" shape: every `std::fs` syscall
        //     routes the path through `CString::new`, which
        //     fails with `NulError` on the first NUL byte; the
        //     build would surface a `NulError` at resolve time
        //     far from the source caixa.lisp.
        //   - LF (`0x0A`) / CR (`0x0D`) the canonical paste-from-
        //     multiline-doc footgun: a `:caminho
        //     "../caixa-teia\nrm -rf /"` value (paste landed mid-
        //     `:caminho` block from a multi-line code-fence)
        //     silently round-trips through `Path::join` but the
        //     embedded newline class is a sibling of the CRLF-at-
        //     subprocess-argument injection vector
        //     `is_git_repo_url` already closes on `:repo`.
        //   - Tab (`0x09`) the canonical paste-from-aligned-table
        //     footgun: the tab is invisible in most editors, and
        //     the lacre embeds the value verbatim so two
        //     paste-from-distinct-tables yield divergent lacres
        //     across host editors that strip vs preserve tabs.
        //   - DEL (`0x7F`) + every other `0x00..=0x1F` byte: the
        //     paste-from-binary-blob shape every peer single-
        //     token-shaped slot rejects under the same
        //     `b < 0x20 || b == 0x7F` predicate.
        //
        // Mirrors the cascade discipline every prior `:caminho`
        // arm establishes: `FonteCaminhoEmpty` →
        // `FonteCaminhoAbsolute` → `FonteCaminhoTildeExpansion`
        // → `FonteCaminhoVarExpansion` →
        // `FonteCaminhoLeadingWhitespace` →
        // `FonteCaminhoLeadingHyphen` → `FonteCaminhoControlChar`.
        // The six leading-byte arms structurally precede the
        // embedded-byte arm because the leading-byte shapes are
        // the more self-locating diagnostic on values that probe
        // as both (e.g. `:caminho "/etc/passwd\n"` surfaces the
        // narrower `FonteCaminhoAbsolute` rather than the broader
        // embedded-control-byte arm); the precedence pin matters
        // at the diagnostic-shape level even though the empty /
        // absolute / tilde / var arms are value-disjoint from a
        // bare control byte (which would itself be a leading
        // byte under the empty / absolute / tilde / var arms'
        // leading-position semantics, but those arms guard the
        // specific shell-convention characters `/` / `~` / `$`
        // — a leading `0x01` byte falls through to this arm).
        for &b in caminho.as_bytes() {
            if b < 0x20 || b == 0x7F {
                return Err(DepError::FonteCaminhoControlChar {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's Windows-path-separator arm. The four
        // leading-byte arms (`/` / `~` / `$`) and the embedded-
        // control-byte arm close the host-layout-leaking + paste-from-
        // multiline-doc shapes; the leading-`\` / embedded-`\` byte is
        // the orthogonal cross-host-OS-separator shape — same render-
        // determinism axis, different semantic mechanism. POSIX
        // [`std::path::Path`] treats `\` (0x5C) as a literal byte
        // inside a single path component (so `..\caixa-teia` is one
        // directory named literally `..\caixa-teia`, sibling of `.`
        // and `..`); Windows [`std::path::Path`] treats `\` as a
        // primary path separator equal to `/` (so `..\caixa-teia` is
        // the parent's sibling directory `caixa-teia`). The lacre
        // pipeline embeds the value verbatim in its per-dep content-
        // address (`conteudo: format!("path:{caminho}")`, caixa-
        // resolver/src/resolve.rs:189), so byte-identical caixa.lisp
        // values resolve to two distinct directories across runner
        // OSes — the same THEORY.md §V.2 render-determinism contract
        // the absolute / tilde / var arms protect, here against the
        // cross-host-OS-separator divergence vector. Even on POSIX-
        // only resolvers (the canonical pleme-io substrate posture),
        // a `..\caixa-teia` (the Windows-Explorer "copy as path" /
        // PowerShell `Get-Location` paste-idiom footgun) silently
        // passes every prior arm because `Path::is_absolute` returns
        // false on `..` and `\` is neither a leading-byte sentinel
        // nor a control byte, then the resolver folds the value
        // through `Path::new(caminho).join(<file>)` looking for a
        // literal `./..\caixa-teia` subdirectory and fails at
        // resolve time with a non-self-locating `No such file or
        // directory` error far from the source caixa.lisp.
        //
        // The peer single-token-shaped axes on the same git-CLI /
        // path-CLI consumer cluster already reject `\` under the same
        // Windows-path-leak banner: [`crate::render::is_git_ref_name`]
        // line 1441 (`"must not contain \\ … the canonical Windows-
        // path-leak footgun; use / for hierarchical refs"`) gates
        // `:fonte :tag` / `:fonte :branch` against the same byte,
        // and [`crate::render::is_gateway_api_http_path`] line 506
        // includes `\` in the eleven-byte RFC-3986-reserved rejection
        // set on `:entrada :paths`. Closing the same byte on `:fonte
        // :caminho` makes the substrate-wide "no Windows path
        // separator anywhere in a typed string slot" invariant
        // structurally consistent across every path-shaped typed
        // surface (the `:caminho` axis was the last typed string
        // surface still admitting `\`).
        //
        // The arm fires AFTER the control-char arm because the
        // control-char diagnostic is the more self-locating axis on
        // values that probe as both (`"..\caixa\0teia"` carries both
        // a `\` and a NUL — NUL is the load-bearing POSIX-syscall-
        // rejected byte, so `FonteCaminhoControlChar` wins). Same
        // narrower-diagnostic-first cascade discipline every prior
        // arm establishes. A pure-`\` value
        // (`"..\caixa-teia"` with no control bytes) falls through
        // every prior arm and lands here.
        for &b in caminho.as_bytes() {
            if b == b'\\' {
                return Err(DepError::FonteCaminhoBackslash {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                });
            }
        }
        // Reproducibility gate's shell-redirection arm. The 3a4e1d7 backslash
        // arm closes the cross-host-OS-separator vector; `<` (`0x3C`) and `>`
        // (`0x3E`) are the orthogonal shell-redirection sentinels — same
        // paste-from-shell-prompt footgun class, different syntactic surface.
        // POSIX `std::path::Path` treats `<` / `>` as literal bytes inside a
        // single path component (so `../caixa-teia>output` is one directory
        // named literally `../caixa-teia>output`, sibling of `.` and `..`),
        // but every interactive shell (bash / zsh / fish / nushell) lexes
        // `<` / `>` as input / output redirection operators — a `:caminho
        // "../caixa-teia>build.log"` (the canonical "I pasted a shell
        // pipeline that wrote build output and forgot to trim the redirect"
        // footgun) or `:caminho "../<input.lisp"` (the symmetric input-
        // redirection paste idiom) silently passes every prior arm because
        // `Path::is_absolute` returns false, `<` / `>` are neither leading-
        // byte sentinels nor control bytes nor `\`, and the value's last byte
        // isn't `/`. The resolver folds the value through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // `./..\caixa-teia>build.log` subdirectory and fails at resolve time
        // with a non-self-locating `No such file or directory` error far
        // from the source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so a `<` / `>` byte lands in
        // the BLAKE3 closure and rides downstream as part of the build's
        // identity. The bytes carry a second class of hazard the prior
        // separator-shaped arms don't: every typed-string slot whose value
        // ever flows verbatim into a shell-spawned subprocess (the caixa-
        // resolver's `git clone` invocation, a future `feira tofu` shell-
        // out, a future operator-side `nix flake check` spawn) is the
        // canonical CRLF-at-subprocess-argument / shell-metachar injection
        // surface that every peer single-token-shaped typed slot already
        // closes. The peer path-shaped axis `[crate::render::is_gateway_api_http_path]`
        // (caixa-core/src/render.rs:506) rejects `<` / `>` as part of its
        // eleven-byte RFC-3986-reserved set on `:entrada :paths`, and the
        // peer git-ref-shaped axis `[crate::render::is_git_ref_name]` rejects
        // `<` / `>` on `:fonte :tag` / `:fonte :branch` under the same
        // shell-metachar-injection banner. The `:caminho` axis was the last
        // typed string surface still admitting these two bytes; this arm
        // closes the gap so the substrate-wide "no shell-redirection
        // metacharacter anywhere in a typed string slot" invariant is now
        // structurally consistent across every path-shaped typed surface.
        //
        // The arm fires AFTER the control-char arm + backslash arm because
        // both prior arms carry more self-locating diagnostics on values
        // that probe as both (`"..\foo<bar"` carries both `\` and `<` — the
        // cross-OS-separator divergence is the load-bearing axis, so the
        // backslash arm wins; `"../foo\n<bar"` carries both LF and `<` —
        // the POSIX-syscall-rejected byte is the load-bearing axis, so the
        // control-char arm wins). The arm fires BEFORE the trailing-`/` arm
        // because the embedded redirection byte is the more semantic-
        // locating axis on probe-as-both values (`"../foo</"` ends in `/`
        // but the load-bearing diagnostic is the embedded `<` shell-
        // redirection — the trailing `/` is the secondary observation, and
        // an author who removes the `<` is likely to also tab-strip the
        // trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'<' || b == b'>' {
                return Err(DepError::FonteCaminhoShellRedirection {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's shell-pipe arm. The e457141 shell-redirection
        // arm closes the `<` / `>` input/output redirection sentinels; `|`
        // (`0x7C`) is the orthogonal shell-pipe sentinel — same paste-from-
        // shell-prompt footgun class, different syntactic surface. POSIX
        // `std::path::Path` treats `|` as a literal path-component byte (so
        // `../caixa-teia|tee` is one directory named literally
        // `../caixa-teia|tee`, sibling of `.` and `..`), but every interactive
        // shell (bash / zsh / fish / nushell) lexes `|` as the pipe operator
        // — a `:caminho "../caixa-teia | grep foo"` (the canonical "I copied a
        // `ls ../caixa-teia | grep` line out of a shell-history block and
        // forgot to trim the pipeline tail" footgun) or `:caminho
        // "../foo||bar"` (the symmetric "I copied a `cmd-a || cmd-b` short-
        // circuit OR line" idiom) silently passes every prior arm because
        // `Path::is_absolute` returns false on `..`, `|` is neither a leading-
        // byte sentinel nor a control byte nor `\` nor `<` / `>`, and the
        // value's last byte isn't `/`. The resolver folds the value through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // `./../caixa-teia | grep foo` subdirectory and fails at resolve time
        // with a non-self-locating `No such file or directory` error far
        // from the source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so a `|` byte lands in the
        // BLAKE3 closure and rides downstream as part of the build's identity
        // into every shell-spawned subprocess (the caixa-resolver's `git
        // clone` invocation, a future `feira tofu` shell-out, a future
        // operator-side `nix flake check` spawn) as the canonical CRLF-at-
        // subprocess-argument / shell-metachar injection surface every peer
        // single-token-shaped typed slot already closes. The peer path-shaped
        // axis [`crate::render::is_gateway_api_http_path`]
        // (caixa-core/src/render.rs:506) rejects `|` as part of its eleven-
        // byte RFC-3986-reserved set on `:entrada :paths`. The `:caminho`
        // axis was the last typed path-string surface still admitting this
        // byte; this arm closes the gap so the substrate-wide "no shell-
        // composition metacharacter anywhere in a typed string slot that
        // flows verbatim into a shell-spawned subprocess" invariant extends
        // from shell-redirection (`<` / `>`) to shell-pipe (`|`) on the
        // `:caminho` axis.
        //
        // The arm fires AFTER the shell-redirection arm because the prior
        // arm's two-byte `byte: u8` payload is the more self-locating axis on
        // values that probe as both (`"../caixa-teia<input|tee"` carries both
        // `<` and `|` — the input-redirection-paste idiom is the load-bearing
        // root-cause edit, so `FonteCaminhoShellRedirection` wins; same
        // cascade discipline every prior `:caminho` arm establishes). The arm
        // fires BEFORE the trailing-`/` arm because the embedded pipe byte is
        // the more semantic-locating axis on probe-as-both values
        // (`"../foo|tee/"` ends in `/` but the load-bearing diagnostic is the
        // embedded `|` shell-pipe — the trailing `/` is the secondary
        // observation, and an author who removes the `|` is likely to also
        // tab-strip the trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'|' {
                return Err(DepError::FonteCaminhoShellPipe {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                });
            }
        }
        // Reproducibility gate's shell-command-separator arm. The 124106f
        // shell-pipe arm closes the `|` byte; `;` (`0x3B`) is the orthogonal
        // shell-command-separator sentinel — same paste-from-shell-prompt
        // footgun class, different syntactic surface. POSIX `std::path::Path`
        // treats `;` as a literal path-component byte (so
        // `../caixa-teia;rm -rf /` is one directory named literally
        // `../caixa-teia;rm -rf /`, sibling of `.` and `..`), but every
        // interactive shell (bash / zsh / fish / nushell) lexes `;` as the
        // sequential-command terminator that fires the next command
        // regardless of the prior command's exit status — a `:caminho
        // "../caixa-teia; rm -rf build"` (the canonical "I pasted a shell
        // one-liner that chained a cleanup tail after the directory name"
        // footgun) or `:caminho "../foo;;bar"` (the symmetric "I copied a
        // POSIX `case` arm's `;;` terminator into the middle of a path"
        // idiom) silently passes every prior arm because `Path::is_absolute`
        // returns false on `..`, `;` is neither a leading-byte sentinel nor a
        // control byte nor `\` nor `<` / `>` nor `|`, and the value's last
        // byte isn't `/`. The resolver folds the value through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // `./../caixa-teia; rm -rf build` subdirectory and fails at resolve
        // time with a non-self-locating `No such file or directory` error far
        // from the source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so a `;` byte lands in the
        // BLAKE3 closure and rides downstream as part of the build's identity
        // into every shell-spawned subprocess (the caixa-resolver's `git
        // clone` invocation, a future `feira tofu` shell-out, a future
        // operator-side `nix flake check` spawn) as the canonical
        // shell-metachar injection surface every peer single-token-shaped
        // typed slot already closes. The peer path-shaped axis
        // [`crate::render::is_gateway_api_http_path`]
        // (caixa-core/src/render.rs:506) rejects `;` as part of its eleven-
        // byte RFC-3986-reserved set on `:entrada :paths`. The `:caminho`
        // axis was the last typed path-string surface still admitting this
        // byte; this arm closes the gap so the substrate-wide "no shell-
        // composition metacharacter anywhere in a typed string slot that
        // flows verbatim into a shell-spawned subprocess" invariant extends
        // from shell-pipe (`|`) to shell-command-separator (`;`) on the
        // `:caminho` axis.
        //
        // The arm fires AFTER the shell-pipe arm because the prior arm's
        // canonical-cmd-a-|-cmd-b shape is the more common shell-history
        // paste idiom on values that probe as both (`"../caixa-teia | tee;
        // rm"` carries both `|` and `;` — the pipeline-tail paste is the
        // load-bearing root-cause edit, so `FonteCaminhoShellPipe` wins; same
        // cascade discipline every prior `:caminho` arm establishes). The arm
        // fires BEFORE the trailing-`/` arm because the embedded
        // command-separator byte is the more semantic-locating axis on
        // probe-as-both values (`"../foo;rm/"` ends in `/` but the
        // load-bearing diagnostic is the embedded `;` shell-command-
        // separator — the trailing `/` is the secondary observation, and an
        // author who removes the `;` is likely to also tab-strip the trailing
        // separator).
        for &b in caminho.as_bytes() {
            if b == b';' {
                return Err(DepError::FonteCaminhoShellSemicolon {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                });
            }
        }
        // Reproducibility gate's shell-background / logical-AND arm. The
        // 05c358e shell-command-separator arm closes the `;` byte; `&`
        // (`0x26`) is the orthogonal shell-background / list-AND sentinel
        // — same paste-from-shell-prompt footgun class, different
        // syntactic surface. POSIX `std::path::Path` treats `&` as a
        // literal path-component byte (so `../caixa-teia & sleep 1` is
        // one directory named literally `../caixa-teia & sleep 1`,
        // sibling of `.` and `..`), but every interactive shell
        // (bash / zsh / fish / nushell) lexes `&` two ways:
        //
        //   - Single `&` as the background-task terminator that detaches
        //     the prior command into the background and returns control
        //     to the prompt immediately (the canonical `cmd &` idiom
        //     every long-running pipeline uses);
        //   - Double `&&` as the logical-AND list operator that fires
        //     the next command only if the prior command succeeded (the
        //     canonical `make && make install` idiom every build script
        //     carries).
        //
        // A `:caminho "../caixa-teia & sleep 1"` (the canonical "I
        // pasted a `cd path & sleep 1` background-launch into the
        // `:caminho` slot" footgun) or `:caminho "../caixa-teia && make"`
        // (the symmetric "I copied a `cd path && make` build chain"
        // idiom) silently passes every prior arm because
        // `Path::is_absolute` returns false on `..`, `&` is neither a
        // leading-byte sentinel nor a control byte nor `\` nor
        // `<` / `>` nor `|` nor `;`, and the value's last byte isn't `/`.
        // The resolver folds the value through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // `./../caixa-teia & sleep 1` subdirectory and fails at resolve
        // time with a non-self-locating `No such file or directory`
        // error far from the source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so an `&` byte lands in
        // the BLAKE3 closure and rides downstream as part of the build's
        // identity into every shell-spawned subprocess (the
        // caixa-resolver's `git clone` invocation, a future `feira tofu`
        // shell-out, a future operator-side `nix flake check` spawn) as
        // the canonical shell-metachar injection surface every peer
        // single-token-shaped typed slot already closes. The peer
        // path-shaped axis [`crate::render::is_gateway_api_http_path`]
        // (caixa-core/src/render.rs:506) rejects `&` as part of its
        // eleven-byte RFC-3986-reserved set on `:entrada :paths`. The
        // `:caminho` axis was the last typed path-string surface still
        // admitting this byte; this arm closes the gap so the
        // substrate-wide "no shell-composition metacharacter anywhere
        // in a typed string slot that flows verbatim into a
        // shell-spawned subprocess" invariant extends from
        // shell-command-separator (`;`) to shell-background /
        // logical-AND (`&`) on the `:caminho` axis.
        //
        // The arm fires AFTER the shell-command-separator arm because
        // the prior arm's `cmd-a; cmd-b` shape is the more common
        // shell-history paste idiom on values that probe as both
        // (`"../caixa-teia; rm & sleep"` carries both `;` and `&` — the
        // command-separator-tail paste is the load-bearing root-cause
        // edit, so `FonteCaminhoShellSemicolon` wins; same cascade
        // discipline every prior `:caminho` arm establishes). The arm
        // fires BEFORE the trailing-`/` arm because the embedded
        // background / list-AND byte is the more semantic-locating axis
        // on probe-as-both values (`"../foo&bar/"` ends in `/` but the
        // load-bearing diagnostic is the embedded `&` shell-background
        // / logical-AND metachar — the trailing `/` is the secondary
        // observation, and an author who removes the `&` is likely to
        // also tab-strip the trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'&' {
                return Err(DepError::FonteCaminhoShellBackground {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                });
            }
        }
        // Reproducibility gate's shell-command-substitution arm. The
        // e12e4f3 shell-background / logical-AND arm closes the `&`
        // byte; the backtick (`0x60`) is the orthogonal POSIX legacy
        // command-substitution sentinel — every POSIX shell (sh /
        // bash / zsh / dash / ksh / fish / nushell) lexes the byte as
        // the canonical legacy wrapper that runs the enclosed command
        // and substitutes its standard-output verbatim into the
        // surrounding word (a `whoami` wrapped in backticks expands
        // to the current user's name; a `cat /etc/passwd` wrapped in
        // backticks expands to the file's contents — the canonical
        // CWE-78 shell-command-injection vector every shell-side
        // hardening guide enumerates first). POSIX
        // `std::path::Path` treats backtick as a literal path-
        // component byte (so `../caixa-teia/<backtick>whoami<backtick>`
        // is one directory named literally that, sibling of `.` and
        // `..`).
        //
        // A `:caminho "../caixa-teia/<backtick>whoami<backtick>"` (the
        // canonical "I pasted a shell one-liner carrying a backticked
        // `whoami` command-substitution expansion into the `:caminho`
        // slot" footgun) or `:caminho "<backtick>pwd<backtick>/caixa-
        // teia"` (the symmetric "I copied a `<backtick>pwd<backtick>/
        // path` working-directory expansion") silently passes every
        // prior arm because `Path::is_absolute` returns false on
        // `..`, the backtick byte is neither a leading-byte sentinel
        // (the f4efe9c `FonteCaminhoVarExpansion` arm catches the
        // modern `$()` form at leading position only; backtick is
        // the orthogonal legacy form) nor a control byte nor `\` nor
        // `<` / `>` nor `|` nor `;` nor `&`, and the value's last
        // byte isn't `/`. The resolver folds the value through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // subdirectory whose name embeds the backticked token and
        // fails at resolve time with a non-self-locating `No such
        // file or directory` error far from the source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-
        // dep content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so a backtick byte
        // lands in the BLAKE3 closure and rides downstream as part
        // of the build's identity into every shell-spawned
        // subprocess (the caixa-resolver's `git clone` invocation, a
        // future `feira tofu` shell-out, a future operator-side
        // `nix flake check` spawn) as the canonical shell-metachar
        // injection surface every peer single-token-shaped typed
        // slot already closes. The peer path-shaped axis
        // [`crate::render::is_gateway_api_http_path`]
        // (caixa-core/src/render.rs:506) rejects backtick as part of
        // its eleven-byte RFC-3986-reserved set on `:entrada
        // :paths`. The `:caminho` axis was the last typed path-
        // string surface still admitting this byte; this arm closes
        // the gap so the substrate-wide "no shell-composition
        // metacharacter anywhere in a typed string slot that flows
        // verbatim into a shell-spawned subprocess" invariant
        // extends from shell-background / logical-AND (`&`) to
        // shell-command-substitution (backtick) on the `:caminho`
        // axis.
        //
        // The arm fires AFTER the shell-background arm because the
        // prior arm's `cmd & sleep` shape is the more common shell-
        // history paste idiom on values that probe as both (a
        // `"../caixa-teia & <backtick>whoami<backtick>"` carries
        // both `&` and a backtick — the background-launch tail is
        // the load-bearing root-cause edit, so
        // `FonteCaminhoShellBackground` wins; same cascade
        // discipline every prior `:caminho` arm establishes). The
        // arm fires BEFORE the trailing-`/` arm because the
        // embedded command-substitution byte is the more semantic-
        // locating axis on probe-as-both values (a
        // `"../<backtick>whoami<backtick>/"` ends in `/` but the
        // load-bearing diagnostic is the embedded backtick shell-
        // command-substitution metachar — the trailing `/` is the
        // secondary observation, and an author who removes the
        // backtick is likely to also tab-strip the trailing
        // separator).
        for &b in caminho.as_bytes() {
            if b == b'`' {
                return Err(DepError::FonteCaminhoShellCommandSubstitution {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                });
            }
        }
        // Reproducibility gate's shell-glob arm. The c4d62b3 shell-command-
        // substitution arm closes the backtick byte; `*` (`0x2A`) and `?`
        // (`0x3F`) are the orthogonal POSIX glob-expansion sentinels — same
        // paste-from-shell-prompt footgun class, different syntactic surface.
        // Every POSIX shell (sh / bash / zsh / dash / ksh / fish / nushell)
        // lexes `*` and `?` as pathname-expansion wildcards: `*` matches any
        // sequence of characters in a path component (including the empty
        // sequence), `?` matches exactly one character. POSIX
        // `std::path::Path` treats both bytes as literal path-component bytes
        // (so `../caixa-teia/*.lisp` is one directory named literally
        // `../caixa-teia/*.lisp`, sibling of `.` and `..`).
        //
        // A `:caminho "../caixa-teia/*"` (the canonical "I pasted a
        // `ls ../caixa-teia/*` shell-listing one-liner into the `:caminho`
        // slot" footgun) or `:caminho "../foo?"` (the symmetric "I copied a
        // `rm foo?` single-char-wildcard removal idiom") silently passes
        // every prior arm because `Path::is_absolute` returns false on `..`,
        // `*` / `?` are neither leading-byte sentinels nor control bytes nor
        // `\` nor `<` / `>` nor `|` nor `;` nor `&` nor backtick, and the
        // value's last byte isn't `/`. The resolver folds the value through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // `./../caixa-teia/*` subdirectory and fails at resolve time with a
        // non-self-locating `No such file or directory` error far from the
        // source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so a `*` or `?` byte lands in
        // the BLAKE3 closure and rides downstream as part of the build's
        // identity into every shell-spawned subprocess (the caixa-resolver's
        // `git clone` invocation, a future `feira tofu` shell-out, a future
        // operator-side `nix flake check` spawn) as the canonical
        // shell-metachar / pathname-expansion surface every peer
        // single-token-shaped typed slot already closes. The peer path-shaped
        // axis [`crate::render::is_gateway_api_http_path`]
        // (caixa-core/src/render.rs:506) rejects `*` and `?` as part of its
        // eleven-byte RFC-3986-reserved set on `:entrada :paths`. The
        // `:caminho` axis was the last typed path-string surface still
        // admitting these two bytes; this arm closes the gap so the
        // substrate-wide "no shell-composition / glob-expansion
        // metacharacter anywhere in a typed string slot that flows verbatim
        // into a shell-spawned subprocess" invariant extends from
        // shell-command-substitution (backtick) to glob-expansion
        // (`*` / `?`) on the `:caminho` axis.
        //
        // The arm fires AFTER the backtick arm because the prior arm's
        // CWE-78 shell-command-injection vector is the load-bearing
        // diagnostic on values that probe as both (a `"../`whoami`/*"`
        // carries both backtick and `*` — the command-substitution paste
        // is the load-bearing root-cause edit, so
        // `FonteCaminhoShellCommandSubstitution` wins; same cascade
        // discipline every prior `:caminho` arm establishes). The arm
        // fires BEFORE the trailing-`/` arm because the embedded glob
        // byte is the more semantic-locating axis on probe-as-both values
        // (`"../foo*/"` ends in `/` but the load-bearing diagnostic is the
        // embedded `*` glob metachar — the trailing `/` is the secondary
        // observation, and an author who removes the `*` is likely to
        // also tab-strip the trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'*' || b == b'?' {
                return Err(DepError::FonteCaminhoShellGlob {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's shell-subshell-grouping arm. The cf9034b
        // shell-glob arm closes the `*` / `?` pathname-expansion sentinels;
        // `(` (`0x28`) and `)` (`0x29`) are the orthogonal POSIX subshell-
        // grouping sentinels — same paste-from-shell-prompt footgun class,
        // different syntactic surface. Every POSIX shell (sh / bash / zsh /
        // dash / ksh / fish / nushell) lexes the parenthesis pair as the
        // subshell-grouping operator: `(<cmd>)` runs `<cmd>` in a child
        // shell with a fresh environment scope (the canonical sandboxing
        // idiom every shell-history `(cd <path> && <cmd>)` one-liner uses
        // to scope a `cd` to one subshell without disturbing the parent's
        // working directory), and `$(<cmd>)` is the modern Bourne
        // command-substitution shape the upstream f4efe9c
        // `FonteCaminhoVarExpansion` arm closes the leading `$` byte of —
        // the closing `)` byte completes that substitution shape and must
        // be refused on the same axis (peer with the
        // [`crate::render::is_git_repo_url`] 3b99147 arm that closes the
        // same byte-pair on the sibling `:fonte :repo` axis under the
        // same shell-subshell-grouping + RFC-3986-sub-delims banner).
        // POSIX `std::path::Path` treats both bytes as literal path-
        // component bytes (so `../caixa-teia/(date)` is one directory
        // named literally `../caixa-teia/(date)`, sibling of `.` and
        // `..`).
        //
        // A `:caminho "../caixa-teia/$(date)/build"` (the canonical "I
        // pasted a `cd ../caixa-teia/$(date)/build` shell-history one-
        // liner whose modern command-substitution expansion lands the
        // current date as a subdirectory name" footgun) or `:caminho
        // "../(cd foo && pwd)/caixa-teia"` (the symmetric "I copied a
        // `(cd foo && pwd)` subshell-grouping working-directory probe
        // idiom") silently passes every prior arm because
        // `Path::is_absolute` returns false on `..`, `(` / `)` are
        // neither leading-byte sentinels nor control bytes nor `\` nor
        // `<` / `>` nor `|` nor `;` nor `&` nor backtick nor `*` / `?`,
        // and the value's last byte isn't `/`. The resolver folds the
        // value through `Path::new(caminho).join(<file>)` looking for a
        // literal `./../caixa-teia/$(date)/build` subdirectory and fails
        // at resolve time with a non-self-locating `No such file or
        // directory` error far from the source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so a `(` or `)` byte lands
        // in the BLAKE3 closure and rides downstream as part of the
        // build's identity into every shell-spawned subprocess (the
        // caixa-resolver's `git clone` invocation, a future `feira tofu`
        // shell-out, a future operator-side `nix flake check` spawn) as
        // the canonical shell-metachar / subshell-grouping surface every
        // peer single-token-shaped typed slot already closes. The peer
        // git-source axis [`crate::render::is_git_repo_url`] (3b99147)
        // rejects the same byte pair on `:fonte :repo` under the same
        // shell-subshell-grouping / RFC-3986-sub-delims banner. The
        // `:caminho` axis was the last typed path-string surface still
        // admitting these two bytes;
        // this arm closes the gap so the substrate-wide "no shell-
        // composition metacharacter anywhere in a typed string slot that
        // flows verbatim into a shell-spawned subprocess" invariant
        // extends from shell-glob (`*` / `?`) to shell-subshell-grouping
        // (`(` / `)`) on the `:caminho` axis. Together with the f4efe9c
        // leading-`$` arm, the typed `:caminho` accepted set now
        // structurally excludes the entire modern Bourne
        // command-substitution surface — leading `$` closes the
        // leading byte of every `$(<cmd>)` shape, this arm closes the
        // trailing `)` boundary.
        //
        // The arm fires AFTER the shell-glob arm because the prior arm's
        // `*` / `?` pathname-expansion shape is the more common shell-
        // history paste idiom on values that probe as both
        // (`"../caixa-teia/*(date)"` carries both `*` and `(` — the
        // glob-paste-tail is the load-bearing root-cause edit, so
        // `FonteCaminhoShellGlob` wins; same cascade discipline every
        // prior `:caminho` arm establishes). The arm fires BEFORE the
        // trailing-`/` arm because the embedded subshell-grouping byte
        // is the more semantic-locating axis on probe-as-both values
        // (`"../foo(date)/"` ends in `/` but the load-bearing diagnostic
        // is the embedded `(` shell-subshell-grouping metachar — the
        // trailing `/` is the secondary observation, and an author who
        // removes the `(` is likely to also tab-strip the trailing
        // separator).
        for &b in caminho.as_bytes() {
            if b == b'(' || b == b')' {
                return Err(DepError::FonteCaminhoShellSubshellGrouping {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's shell-brace-expansion arm. The 0633c91
        // shell-subshell-grouping arm closes `(` / `)`; `{` (`0x7b`) and
        // `}` (`0x7d`) are the orthogonal shell-brace-expansion /
        // URI-Template-placeholder byte pair — same paste-from-shell-
        // prompt + paste-from-templated-doc footgun class, different
        // syntactic surface. Every POSIX-derived shell that implements
        // brace expansion (bash / zsh / ksh / fish; the canonical
        // `mkdir -p ../{caixa-teia,caixa-helm,caixa-flux}` /
        // `cp file{,.bak}` idiom every shell-history block carries)
        // expands `{a,b,c}` to the cross-product of its comma-separated
        // members and `{1..10}` to the integer range; RFC 6570 reserves
        // the matched pair for URI Template placeholders (the canonical
        // `https://{host}/{org}/{repo}` substitution shape every
        // OpenAPI / Swagger / Postman / GitHub Octokit client /
        // Helm chart-URL fragment / Mustache `{{org}}` doubled-brace
        // form carries), and Tera / Jinja2 / Handlebars / Go html/template
        // every IaC tool (Helm, Kustomize, Terraform's `${var}` cousin
        // shape) emit. POSIX `std::path::Path` treats both bytes as
        // literal path-component bytes (so `../{caixa-teia,caixa-helm}`
        // is one directory named literally `../{caixa-teia,caixa-helm}`,
        // sibling of `.` and `..`).
        //
        // A `:caminho "../{caixa-teia,caixa-helm}/build"` (the canonical
        // "I pasted a `cd ../{caixa-teia,caixa-helm}` shell brace-
        // expansion one-liner that fans across two siblings" footgun)
        // or `:caminho "../{{org}}/caixa-teia"` (the symmetric "I copied
        // a `{{org}}` Mustache / Helm template placeholder out of a
        // README quick-start and forgot to substitute") silently passes
        // every prior arm because `Path::is_absolute` returns false on
        // `..`, `{` / `}` are neither leading-byte sentinels nor control
        // bytes nor `\` nor `<` / `>` nor `|` nor `;` nor `&` nor
        // backtick nor `*` / `?` nor `(` / `)`, and the value's last
        // byte isn't `/`. The resolver folds the value through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // `./../{caixa-teia,caixa-helm}/build` subdirectory and fails
        // at resolve time with a non-self-locating `No such file or
        // directory` error far from the source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so a `{` or `}` byte
        // lands in the BLAKE3 closure and rides downstream as part of
        // the build's identity into every shell-spawned subprocess
        // (the caixa-resolver's `git clone` invocation, a future
        // `feira tofu` shell-out, a future operator-side `nix flake
        // check` spawn) as the canonical shell-metachar / brace-
        // expansion surface every peer single-token-shaped typed
        // slot already closes. The peer git-source axis
        // [`crate::render::is_git_repo_url`] (42d8f9d — the URI Template
        // placeholder arm) rejects the same byte pair on `:fonte :repo`
        // under the same RFC-3986-'delims' / RFC-6570-URI-Template /
        // shell-brace-expansion banner. The `:caminho` axis was the last
        // typed path-string surface still admitting these two bytes;
        // this arm closes the gap so the substrate-wide "no shell-
        // composition metacharacter anywhere in a typed string slot
        // that flows verbatim into a shell-spawned subprocess"
        // invariant extends from shell-subshell-grouping (`(` / `)`)
        // to shell-brace-expansion (`{` / `}`) on the `:caminho` axis,
        // and the typed `:caminho` accepted set now also structurally
        // excludes the URI Template / templating-engine placeholder
        // surface that would silently round-trip through any
        // downstream IaC templating-engine layer.
        //
        // The arm fires AFTER the shell-subshell-grouping arm because
        // the prior arm's `(` / `)` shape is the more semantic-locating
        // axis on values that probe as both (`"../{cd foo}(date)"`
        // carries both `{` and `(` — the parenthesis-pair is the
        // load-bearing modern-Bourne-command-substitution surface the
        // prior arm closes; same cascade discipline every prior
        // `:caminho` arm establishes). The arm fires BEFORE the
        // trailing-`/` arm because the embedded brace-expansion byte
        // is the more semantic-locating axis on probe-as-both values
        // (`"../{caixa-teia,caixa-helm}/"` ends in `/` but the
        // load-bearing diagnostic is the embedded `{` brace-expansion
        // metachar — the trailing `/` is the secondary observation,
        // and an author who removes the `{` is likely to also tab-
        // strip the trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'{' || b == b'}' {
                return Err(DepError::FonteCaminhoShellBraceExpansion {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's shell-bracket-expansion arm. The 598b770
        // shell-brace-expansion arm closes `{` / `}`; `[` (`0x5b`) and
        // `]` (`0x5d`) are the orthogonal POSIX glob-character-class /
        // shell-`test`-builtin byte pair — same paste-from-shell-prompt
        // footgun class, different syntactic surface. Every POSIX shell
        // (sh / bash / zsh / dash / ksh / fish / nushell) lexes the
        // bracket pair as the glob character-class operator: `[abc]`
        // matches one of `a`, `b`, `c`; `[a-z]` matches any lowercase
        // ASCII letter; `[^x]` negates (the canonical
        // `ls *.[ch]` C-source-file glob and the `cd ../[a-z]*`
        // lowercase-sibling glob every shell-history block carries —
        // the orthogonal axis to the cf9034b `*` / `?` shell-glob arm
        // closing the unbounded pathname-expansion sentinels). The
        // bracket pair additionally carries the POSIX `test` /
        // `[` builtin command (`[ -d ../caixa-teia ] && cd ...` —
        // the canonical idiom every shell-script conditional uses) and
        // bash's `[[ ... ]]` extended-test grammar. Beyond shell, the
        // bracket pair is the TOML inline-array delimiter
        // (`features = ["a", "b"]` — the canonical paste-from-Cargo-
        // manifest cross-idiom-leak vector), the YAML flow-sequence
        // delimiter (`paths: [/a, /b]` — the canonical paste-from-
        // values.yaml cross-idiom leak), the JSON array delimiter,
        // and the POSIX-ERE / PCRE bracket-expression / character-
        // class anchor (the canonical paste-from-regex-doc shape).
        // POSIX `std::path::Path` treats both bytes as literal path-
        // component bytes (so `../[caixa-teia]` is one directory
        // named literally `../[caixa-teia]`, sibling of `.` and
        // `..`).
        //
        // A `:caminho "../caixa-[a-z]/build"` (the canonical "I
        // pasted a `cd ../caixa-[a-z]/build` glob-character-class
        // one-liner that matches every lowercase-sibling-suffix
        // sibling directory" footgun), `:caminho "../[caixa-teia]/
        // build"` (the symmetric "I pasted a TOML inline-array /
        // YAML flow-sequence shape out of an aligned manifest"
        // idiom), or `:caminho "../caixa-[ch]"` (the canonical
        // `*.[ch]` C-source character-class paste-from-shell-history
        // shape) silently passes every prior arm because
        // `Path::is_absolute` returns false on `..`, `[` / `]` are
        // neither leading-byte sentinels nor control bytes nor `\`
        // nor `<` / `>` nor `|` nor `;` nor `&` nor backtick nor
        // `*` / `?` nor `(` / `)` nor `{` / `}`, and the value's
        // last byte isn't `/`. The resolver folds the value through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // `./../caixa-[a-z]/build` subdirectory and fails at resolve
        // time with a non-self-locating `No such file or directory`
        // error far from the source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so a `[` or `]` byte
        // lands in the BLAKE3 closure and rides downstream as part of
        // the build's identity into every shell-spawned subprocess
        // (the caixa-resolver's `git clone` invocation, a future
        // `feira tofu` shell-out, a future operator-side `nix flake
        // check` spawn) as the canonical shell-metachar / glob-
        // character-class / TOML-array surface every peer single-
        // token-shaped typed slot already closes. The `:caminho` axis
        // was the last typed path-string surface still admitting
        // these two bytes; this arm closes the gap so the substrate-
        // wide "no shell-composition metacharacter anywhere in a
        // typed string slot that flows verbatim into a shell-spawned
        // subprocess" invariant extends from shell-brace-expansion
        // (`{` / `}`) to shell-bracket-expansion (`[` / `]`) on the
        // `:caminho` axis. Together with the cf9034b `*` / `?` arm,
        // the typed `:caminho` accepted set now structurally excludes
        // the entire POSIX pathname-expansion / glob surface —
        // unbounded glob (`*` / `?`) AND bounded character-class
        // (`[abc]` / `[a-z]`).
        //
        // The arm fires AFTER the shell-brace-expansion arm because
        // the prior arm's `{` / `}` shape is the more semantic-
        // locating axis on values that probe as both
        // (`"../{a,b}[ch]"` carries both `{` and `[` — the brace-
        // expansion fan is the load-bearing root-cause edit, so
        // `FonteCaminhoShellBraceExpansion` wins; same cascade
        // discipline every prior `:caminho` arm establishes). The arm
        // fires BEFORE the trailing-`/` arm because the embedded
        // bracket-expansion byte is the more semantic-locating axis
        // on probe-as-both values (`"../[a-z]/"` ends in `/` but the
        // load-bearing diagnostic is the embedded `[` glob-character-
        // class metachar — the trailing `/` is the secondary
        // observation, and an author who removes the `[` is likely
        // to also tab-strip the trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'[' || b == b']' {
                return Err(DepError::FonteCaminhoShellBracketExpansion {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's shell-quote-grouping arm. The 986963b
        // shell-bracket-expansion arm closes `[` / `]`; `'` (`0x27`) and
        // `"` (`0x22`) are the orthogonal POSIX shell-string-literal
        // delimiter pair — same paste-from-shell-prompt footgun class,
        // different syntactic surface. Every POSIX shell (sh / bash /
        // zsh / dash / ksh / fish / nushell) lexes the pair as the
        // string-literal quoting operator: `'…'` is the strong
        // (no-expansion) single-quoted string and `"…"` is the weak
        // (variable-/command-substitution-preserving) double-quoted
        // string — the canonical `cd '../caixa-teia'` shell-history
        // idiom every path-with-embedded-whitespace paste block carries,
        // and the symmetric `git clone "$REPO"` weak-quoted CI-manifest
        // shape. Beyond shell, the two bytes carry the JSON string-literal
        // delimiter (`"key": "value"` — the canonical paste-from-JSON-
        // config cross-idiom-leak vector), the YAML double-quoted +
        // single-quoted flow-scalar delimiters (`path: "../caixa-teia"`
        // — the canonical paste-from-values.yaml / paste-from-K8s-YAML-
        // manifest cross-idiom leak), the TOML basic + literal string
        // delimiters (`path = "../caixa-teia"` — the canonical paste-
        // from-Cargo-manifest cross-idiom-leak vector), the tatara-lisp
        // string-literal delimiter itself (`(:caminho "../caixa-teia")`
        // — the canonical "I copied the entire `:caminho "..."` slot
        // rather than just the string body" author-surface footgun),
        // and RFC 3986 §2.2's `gen-delims` / `sub-delims` grammar which
        // excludes both bytes from the `unreserved / pct-encoded /
        // sub-delims / ":" / "@"` `pchar` production. POSIX
        // `std::path::Path` treats both bytes as literal path-component
        // bytes (so `../"caixa-teia"` is one directory named literally
        // `../"caixa-teia"`, sibling of `.` and `..`).
        //
        // A `:caminho "'../caixa-teia'"` (the canonical "I pasted a
        // `cd '../caixa-teia'` shell-history one-liner whose strong-
        // quoting preserved the sibling-workspace path verbatim across
        // the whitespace paste boundary" footgun), `:caminho
        // "\"../caixa-teia\""` (the symmetric weak-quoted paste-from-
        // JSON / paste-from-YAML flow-scalar / paste-from-TOML basic-
        // string / paste-from-tatara-lisp string-literal cross-idiom-
        // leak shape), or `:caminho "../\"caixa-teia\""` (the embedded-
        // quote "I pasted a JSON key-value pair fragment into the
        // middle of the path" idiom) silently passes every prior arm
        // because `Path::is_absolute` returns false on `..` / `'` /
        // `"`, `'` / `"` are neither leading-byte sentinels nor
        // control bytes nor `\` nor `<` / `>` nor `|` nor `;` nor `&`
        // nor backtick nor `*` / `?` nor `(` / `)` nor `{` / `}` nor
        // `[` / `]`, and the value's last byte isn't `/`. The resolver
        // folds the value through `Path::new(caminho).join(<file>)`
        // looking for a literal `./'../caixa-teia'` subdirectory and
        // fails at resolve time with a non-self-locating `No such file
        // or directory` error far from the source caixa.lisp.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so a `'` or `"` byte
        // lands in the BLAKE3 closure and rides downstream as part of
        // the build's identity into every shell-spawned subprocess
        // (the caixa-resolver's `git clone` invocation, a future
        // `feira tofu` shell-out, a future operator-side `nix flake
        // check` spawn) as the canonical shell-metachar / string-
        // literal-delimiter surface every peer single-token-shaped
        // typed slot already closes. The peer `:fonte :repo` axis
        // closes both bytes under the same shell-quote-grouping /
        // RFC-3986-sub-delims banner (e7a109f `'` shell-single-quote
        // + 4267d8b `"` shell-double-quote on `is_git_repo_url`). The
        // `:caminho` axis was the last typed path-string surface
        // still admitting these two bytes; this arm closes the gap
        // so the substrate-wide "no shell-composition metacharacter
        // anywhere in a typed string slot that flows verbatim into a
        // shell-spawned subprocess" invariant extends from shell-
        // bracket-expansion (`[` / `]`) to shell-quote-grouping (`'`
        // / `"`) on the `:caminho` axis. Together with the peer
        // JSON / YAML / TOML string-literal delimiters closing at
        // this arm and the 598b770 `{` / `}` brace-expansion arm
        // closing the templating-engine-placeholder boundary, the
        // typed `:caminho` accepted set now structurally excludes
        // the entire cross-config-DSL string-literal / templating
        // paste-from-aligned-manifest cross-idiom-leak surface that
        // would silently round-trip through any downstream JSON /
        // YAML / TOML / HCL / tatara-lisp parsing layer.
        //
        // The arm fires AFTER the shell-bracket-expansion arm because
        // the prior arm's `[` / `]` shape is the more semantic-
        // locating axis on values that probe as both (`"../[a-z]'x'"`
        // carries both `[` and `'` — the glob-character-class
        // expansion is the load-bearing root-cause edit, so
        // `FonteCaminhoShellBracketExpansion` wins; same cascade
        // discipline every prior `:caminho` arm establishes). The arm
        // fires BEFORE the trailing-`/` arm because the embedded
        // quote-grouping byte is the more semantic-locating axis on
        // probe-as-both values (`"../'caixa-teia'/"` ends in `/` but
        // the load-bearing diagnostic is the embedded `'` shell-
        // string-literal metachar — the trailing `/` is the secondary
        // observation, and an author who removes the `'` is likely to
        // also tab-strip the trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'\'' || b == b'"' {
                return Err(DepError::FonteCaminhoShellQuoteGrouping {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's shell-comment / URL-fragment / YAML-comment arm.
        // The d14cbc5 shell-quote-grouping arm closes `'` / `"`; `#` (`0x23`) is
        // the orthogonal "byte at which four distinct downstream parsers all
        // truncate the value at the first occurrence" surface, and no prior arm
        // has covered it on the `:caminho` axis. Every POSIX shell (sh / bash /
        // zsh / dash / ksh / fish / nushell) lexes an unquoted `#` at the head
        // of a word (or after unquoted whitespace) as the comment-lead: from
        // that byte to the end of the physical line is a comment discarded
        // before command parsing (`cd ../caixa-teia  # legacy sibling` — the
        // canonical paste-from-shell-history-with-trailing-annotation shape
        // every operator-notebook and CI-manifest carries; POSIX.1-2017 §2.3
        // Token Recognition step 6). YAML 1.2 §6.6 makes `#` the comment lead
        // at any position preceded by whitespace or at line-start (`path:
        // ../caixa-teia  # pin` — the canonical paste-from-values.yaml /
        // paste-from-K8s-manifest cross-idiom-leak shape). tatara-lisp itself
        // treats `;` as the comment-lead but a growing number of consumer
        // config-DSL layers (HCL, Terraform, Nix flake attributes, .env
        // dotenv-style files, gitconfig / .gitignore, ini / TOML) use `#` as
        // the comment-lead too — the pair extends the cross-config-DSL
        // paste-idiom surface the d14cbc5 quote-grouping arm and the 598b770
        // brace-expansion arm already cover on adjacent axes. RFC 3986 §3.5
        // reserves `#` as the URL fragment-identifier delimiter (the canonical
        // paste-from-browser-address-bar `github.com/foo/bar#readme` /
        // `github.com/foo/bar#L42` permalink shape, and the symmetric
        // Nix-flake-ref cross-idiom leak `github:foo/bar#packageName` where
        // `#` selects a flake output — the same axis the peer
        // [`crate::render::is_git_repo_url`] closes on the `:fonte :repo`
        // surface at a68f818 with the same downstream-drops-the-tail
        // rationale).
        //
        // POSIX `std::path::Path` treats `#` as a literal path-component byte,
        // so a `:caminho "../caixa-teia # legacy sibling"` (the canonical
        // paste-from-shell-history-with-trailing-annotation footgun),
        // `:caminho "../caixa-teia  # pin"` (the symmetric YAML flow-scalar
        // paste-with-trailing-comment shape), or `:caminho "../caixa-teia
        // #readme"` (the URL fragment paste-from-browser-address-bar shape)
        // silently passes every prior arm because `Path::is_absolute` returns
        // false on `..`, `#` is neither a leading-byte sentinel nor a control
        // byte nor `\` nor `<` / `>` nor `|` nor `;` nor `&` nor backtick nor
        // `*` / `?` nor `(` / `)` nor `{` / `}` nor `[` / `]` nor `'` / `"`,
        // and the value's last byte isn't `/`. The resolver folds the value
        // through `Path::new(caminho).join(<file>)` looking for a literal
        // subdirectory named `../caixa-teia # legacy sibling` and fails at
        // resolve time with a non-self-locating `No such file or directory`
        // error far from the source caixa.lisp — while every downstream
        // shell / YAML / URL parser silently truncates the value at the `#`
        // byte to `../caixa-teia`, so a `feira tofu` shell-out to a
        // `cd '{caminho}'` command line and a `nix flake check` invocation on
        // an emitted YAML `path:` scalar disagree with the resolver on which
        // directory the value names. Two workstations whose downstream
        // shell / YAML / URL parsing layers differ in unquoted-`#`
        // recognition emit divergent build artifacts for the byte-identical
        // caixa.lisp value.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so the byte lands in the BLAKE3
        // closure and rides downstream as part of the build's identity into
        // every shell-spawned subprocess (the caixa-resolver's `git clone`
        // invocation, a future `feira tofu` shell-out, a future operator-side
        // `nix flake check` spawn) as the canonical shell-metachar /
        // comment-lead / URL-fragment-delimiter surface every peer
        // single-token-shaped typed slot already closes. The peer `:fonte
        // :repo` axis closes the byte under the URL-fragment-identifier
        // banner (a68f818 `#` on `is_git_repo_url`); the `:caminho` axis was
        // the last typed path-string surface still admitting the byte. This
        // arm closes the gap so the substrate-wide "no shell-composition
        // metacharacter / comment-lead / URL-fragment-delimiter anywhere in a
        // typed string slot that flows verbatim into a shell-spawned
        // subprocess or downstream YAML / URL parser" invariant extends from
        // shell-quote-grouping (`'` / `"`) to shell-comment / URL-fragment
        // (`#`) on the `:caminho` axis. Together with the peer JSON / YAML /
        // TOML string-literal delimiters the d14cbc5 quote-grouping arm
        // closes and the 598b770 `{` / `}` brace-expansion arm closes on the
        // templating-engine-placeholder boundary, the typed `:caminho`
        // accepted set now structurally excludes the entire
        // paste-with-trailing-annotation / paste-from-URL-permalink /
        // paste-from-YAML-comment cross-idiom-leak surface that would
        // silently round-trip through any downstream shell / YAML / URL /
        // dotenv / gitconfig / HCL parsing layer to a different value than
        // the resolver's `Path::join` sees.
        //
        // The arm fires AFTER the shell-quote-grouping arm because the prior
        // arm's `'` / `"` shape is the more semantic-locating axis on values
        // that probe as both (`"../'x'#pin"` carries both `'` and `#` — the
        // shell-string-literal-delimiter is the load-bearing root-cause edit,
        // so `FonteCaminhoShellQuoteGrouping` wins; same cascade discipline
        // every prior `:caminho` arm establishes). The arm fires BEFORE the
        // trailing-`/` arm because the embedded comment-lead / fragment-
        // delimiter byte is the more semantic-locating axis on probe-as-both
        // values (`"../caixa-teia#pin/"` ends in `/` but the load-bearing
        // diagnostic is the embedded `#` — the trailing `/` is the secondary
        // observation, and an author who removes the `#pin` fragment is
        // likely to also tab-strip the trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'#' {
                return Err(DepError::FonteCaminhoShellComment {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's URL-percent-encoding-escape arm. The 6622063
        // shell-comment arm closes the `#` URL-fragment-identifier byte; `%`
        // (`0x25`) is the orthogonal RFC 3986 §2.1 URL percent-encoding-escape
        // byte — the mandatory encoding mechanism for every byte outside the
        // `unreserved` alphanumeric / `-` / `.` / `_` / `~` set, and `%`
        // itself must be percent-encoded as `%25` to appear literally inside
        // a URL value. The byte carries three distinct render-determinism
        // hazards on the `:caminho` axis, no prior arm has covered it, and
        // the peer `:fonte :repo` axis (a323db8 `%` on `is_git_repo_url`)
        // already closes the same byte under the same URL-percent-encoding
        // banner — the `:caminho` axis was the last typed path-string surface
        // still admitting the byte.
        //
        // First, the paste-from-browser-address-bar percent-encoded-space
        // footgun: an author copies `../caixa%20teia` out of a URL-encoded
        // README hyperlink / a browser address bar / a percent-encoded
        // permalink expecting `%20` to decode to a literal space at the
        // filesystem layer. POSIX `std::path::Path` treats the byte as a
        // literal path-component byte, so `Path::join` looks for a literal
        // `./../caixa%20teia` subdirectory and fails at resolve time with a
        // non-self-locating `No such file or directory` error far from the
        // source caixa.lisp — while the author's mental model was
        // `../caixa teia`, the decoded shape. Two authors whose only
        // difference is percent-encoding presence resolve to two distinct
        // BLAKE3 closures (`path:../caixa%20teia` vs `path:../caixa teia`)
        // for what they intended as the byte-identical sibling-workspace
        // dep. The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so the divergence rides
        // downstream into the BLAKE3 closure and locks the substrate's
        // "the lacre is the build's identity" contract (CAIXA-SDLC §III.2)
        // to the wrong encoding — the same THEORY.md §V.2 render-
        // determinism vector every prior `:caminho` arm protects.
        //
        // Second, the printf-format-specifier lead footgun: `%` is the C /
        // POSIX printf format-directive lead-in (`%s`, `%d`, `%02x`, the
        // canonical `printf "path=%s\n" ../caixa-teia` invocation every
        // shell-diagnostic one-liner carries) and the printf builtin is
        // wired into every POSIX shell (bash / zsh / dash / ksh / busybox
        // ash) as the format-string lead. A `:caminho "../caixa-%s-teia"`
        // value flowing into any future `feira` verb that shells out with a
        // printf-formatted path template silently gets reinterpreted as a
        // format-directive rather than a literal byte — the canonical
        // CWE-134 format-string-injection vector.
        //
        // Third, the bash-job-control-specifier lead footgun: bash / zsh /
        // ksh reserve `%N` at word-start as the job-control specifier —
        // `%1` names "job 1", `%%` names "the current job", `%foo` names
        // "the most recent job whose command started with `foo`". A future
        // `feira` verb that invokes `kill %1` on a caminho-scoped
        // subprocess would silently redirect the signal to a wrong target.
        //
        // Beyond the three shell-side hazards, `%` is a first-class parser
        // byte in three cross-config-DSL layers the substrate's paste-idiom
        // surface routinely crosses: YAML 1.2 §6.8.1 lexes `%` at
        // line-start as the directive lead (`%YAML 1.2` / `%TAG` — a
        // `:caminho "%YAML/1.2/../caixa-teia"` paste from a top-of-doc
        // YAML directive block silently trips the YAML directive parser on
        // any downstream emitted YAML manifest); Prometheus / Grafana
        // template syntax uses `%(var)s` as the substitution lead; and Nix
        // interpolation uses `${var}` (not `%`) but Envsubst /
        // Kubernetes / OpenShift template layers use `%VAR%` as the
        // Windows-shell env-var-reference lead — the paste-from-`.bat` /
        // paste-from-PowerShell-`%env:PATH%` cross-idiom leak.
        //
        // The three malformed-`%HH` classes documented on the peer
        // `is_git_repo_url` `%` arm (a323db8) apply here too:
        //
        //   - The lone-`%` malformed-escape shape (`"../caixa-teia%foo"`
        //     where `%` isn't followed by two hex digits) — every WHATWG-
        //     conformant URL parser rejects the value at parse time per
        //     RFC 3986 §2.1, but the byte rides into the lacre before
        //     the resolver subprocess crosses the URL-parser boundary.
        //   - The over-encoded path-separator shape (`"../caixa%2Fteia"`
        //     intending the `%2F` as the URL encoding of `/`) locks a
        //     `path:../caixa%2Fteia` BLAKE3 closure that diverges from
        //     the byte-identical `path:../caixa/teia` form.
        //   - The double-encoded shape (`"../caixa%2520teia"` — the `%25`
        //     already itself an encoded `%`, so the intent was likely a
        //     literal `%20` that survived one round-trip through a
        //     URL-encoder that shouldn't have run) locks a triply-
        //     divergent closure across the encoded / once-decoded /
        //     twice-decoded chain.
        //
        // POSIX `std::path::Path` treats the byte as a literal path-
        // component byte, so a `:caminho "../caixa%20teia"` (the canonical
        // paste-from-browser-address-bar percent-encoded-space footgun),
        // `:caminho "%YAML/../caixa-teia"` (the symmetric paste-from-YAML-
        // directive-block cross-idiom leak), or `:caminho
        // "../caixa-%s-teia"` (the printf-format-specifier paste-from-
        // shell-diagnostic-one-liner shape) silently passes every prior arm
        // because `Path::is_absolute` returns false on `..`, `%` is neither
        // a leading-byte sentinel nor a control byte nor `\` nor `<` / `>`
        // nor `|` nor `;` nor `&` nor backtick nor `*` / `?` nor `(` / `)`
        // nor `{` / `}` nor `[` / `]` nor `'` / `"` nor `#`, and the
        // value's last byte isn't `/`. The resolver folds the value through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // subdirectory named `../caixa%20teia` and fails at resolve time
        // with a non-self-locating `No such file or directory` error far
        // from the source caixa.lisp — while every downstream URL parser /
        // shell printf builtin / YAML directive parser silently
        // reinterprets the byte to a different value than the resolver's
        // `Path::join` sees. Two workstations whose downstream URL / shell
        // / YAML layers differ in `%HH` recognition emit divergent build
        // artifacts for the byte-identical caixa.lisp value.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`, caixa-
        // resolver/src/resolve.rs:189), so the byte lands in the BLAKE3
        // closure and rides into every shell-spawned subprocess (the
        // resolver's `git clone`, a future `feira tofu` shell-out, a
        // future operator-side `nix flake check` spawn) as the canonical
        // URL-percent-encoding-escape / printf-format-specifier / bash-
        // job-control-specifier surface every peer single-token-shaped
        // typed slot already closes. This arm closes the gap so the
        // substrate-wide "no URL-percent-encoding-escape / printf-format-
        // specifier / job-control-specifier / YAML-directive-lead byte
        // anywhere in a typed string slot that flows verbatim into a
        // shell-spawned subprocess or downstream URL / printf / YAML
        // parser" invariant extends from shell-comment / URL-fragment
        // (`#` — 6622063) to URL-percent-encoding-escape (`%`) on the
        // `:caminho` axis.
        //
        // The arm fires AFTER the shell-comment arm because the prior
        // arm's `#` shape is the more semantic-locating axis on values
        // that probe as both (`"../caixa%20teia#pin"` carries both `%`
        // and `#` — the URL-fragment-identifier is the load-bearing
        // downstream-truncation edit, so `FonteCaminhoShellComment` wins;
        // same cascade discipline every prior `:caminho` arm establishes).
        // The arm fires BEFORE the trailing-`/` arm because the embedded
        // percent-encoding-escape byte is the more semantic-locating axis
        // on probe-as-both values (`"../caixa%20teia/"` ends in `/` but
        // the load-bearing diagnostic is the embedded `%` percent-
        // encoding-escape — the trailing `/` is the secondary observation,
        // and an author who decodes the `%20` to a literal space is
        // likely to also tab-strip the trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'%' {
                return Err(DepError::FonteCaminhoUrlPercentEncoding {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's embedded-`$` shell-variable-expansion /
        // command-substitution / arithmetic-expansion arm. The f4efe9c
        // leading-`$` arm at line 540 routes `caminho.starts_with('$')`
        // through `FonteCaminhoVarExpansion` under the leading-byte-
        // sentinel host-layout-leak banner (peer with the b94fd83
        // absolute / a5c248e tilde leading-byte arms), but the arm
        // fires only at position 0 — a `:caminho "../foo$HOME/bar"`
        // (embedded `$HOME` in a nested path segment — the canonical
        // paste-from-`ls ../foo$HOME/bar`-shell-one-liner footgun where
        // an author copies a partially-substituted shell one-liner and
        // the leading segment is a literal `../foo` while the mid
        // segment carries the un-substituted `$HOME` template), a
        // `:caminho "../foo${WORKSPACE}/bar"` (the symmetric braced-CI-
        // manifest paste-from-`.gitlab-ci.yml` / paste-from-GitHub-
        // Actions-workflow shape), a `:caminho "../foo$(whoami)/bar"`
        // (the paste-from-shell-prompt command-substitution idiom), or
        // a `:caminho "../foo$((1+2))/bar"` (the arithmetic-expansion
        // idiom) silently passes every prior arm because
        // `Path::is_absolute` returns false on `..`, `$` is neither a
        // leading-byte sentinel (the f4efe9c arm fires only at position
        // 0) nor a control byte nor `\` nor `<` / `>` nor `|` nor `;`
        // nor `&` nor backtick nor `*` / `?` nor `(` / `)` nor `{` /
        // `}` nor `[` / `]` nor `'` / `"` nor `#` nor `%`, and the
        // value's last byte isn't `/`. Note that `$(...)` command-
        // substitution and `$((...))` arithmetic-expansion each carry
        // an embedded `(` byte that the 0633c91 shell-subshell-grouping
        // arm catches structurally at the earlier `(` position — but
        // an author who reaches for the sh-brace-substitution
        // `${VAR}` or the bare `$VAR` shape carries only the `$` byte,
        // which no prior arm covers. This arm closes the last
        // positional gap on the `$` byte on the `:caminho` axis so
        // every position — leading (`FonteCaminhoVarExpansion`) and
        // embedded (`FonteCaminhoShellVariableExpansion`) — is
        // structurally rejected.
        //
        // Every POSIX shell (sh / bash / zsh / dash / ksh / busybox
        // ash / fish / nushell) lexes `$` as the variable-expansion /
        // command-substitution / arithmetic-expansion operator per
        // POSIX.1-2017 §2.6 (Word Expansions): `$<name>` (Parameter
        // Expansion) expands a named variable, `${<name>}` (Parameter
        // Expansion braced form) does the same with an explicit token
        // boundary, `$(<cmd>)` (Command Substitution modern form,
        // `` `<cmd>` `` legacy form which the c370458 backtick arm
        // already closes) runs a subshell and substitutes its stdout,
        // and `$((<expr>))` (Arithmetic Expansion) evaluates an
        // arithmetic expression. Every form is a host-layout /
        // environment-state / shell-subprocess-side-effect leak when
        // the byte lands in a value the resolver passes to a shell-
        // spawned subprocess. Beyond the POSIX shell layer, `$` is
        // the Nix `${var}` string-interpolation lead (the paste-from-
        // `flake.nix` / paste-from-`.nix`-attribute cross-idiom leak
        // where an author copies `"${pkgs.hello}/bin/hello"` out of a
        // nix expression), the Make `$(var)` / `$@` / `$<` automatic-
        // variable lead (the paste-from-`Makefile` shape), the
        // JavaScript / TypeScript template-literal `${expr}` interp
        // lead (the paste-from-JS-template-string idiom in a
        // multi-lang-monorepo where a `path` attribute gets copied out
        // of a `package.json` script or a Vite config), the envsubst /
        // Kubernetes / OpenShift template `${VAR}` interp lead (the
        // paste-from-Helm-values / paste-from-K8s-manifest cross-idiom
        // leak), the PHP variable lead (`$_GET`, `$_ENV` — the paste-
        // from-`.php`-config footgun), the Perl scalar-variable lead
        // (`$foo`), the SASS / SCSS variable lead (`$primary-color`),
        // and the SQL bind-parameter lead in PostgreSQL / SQLite
        // (`$1`, `$2` — the paste-from-`.sql`-migration idiom). The
        // cross-idiom paste-footgun surface is broader than any single
        // shell layer — `$` is a first-class parser byte in nearly
        // every config / templating / build-system DSL the substrate's
        // paste-idiom surface routinely crosses. The peer `:fonte
        // :repo` axis closes the byte under the shell-variable-
        // expansion / URL-sub-delim banner (b9d187c `$` on
        // `is_git_repo_url`), the peer `:fonte :tag` / `:fonte :branch`
        // axes close `$` as part of `is_git_ref_name`'s printable-
        // ASCII-restricted grammar (`git check-ref-format` rejects the
        // byte outright), and the peer `:entrada :paths` axis closes
        // `$` via `is_gateway_api_http_path`'s eleven-byte RFC-3986-
        // reserved set. The `:caminho` axis was the last typed path-
        // string surface still admitting `$` at positions other than 0.
        //
        // POSIX `std::path::Path` treats `$` as a literal path-
        // component byte, so `:caminho "../foo$HOME/bar"` silently
        // routes through `Path::new(caminho).join(<file>)` looking for
        // a literal `./{caminho}` subdirectory that fails at resolve
        // time with a non-self-locating `No such file or directory`
        // error far from the source caixa.lisp. But every downstream
        // shell / envsubst / Nix / Make / K8s-template parser silently
        // reinterprets the byte to a different value than the
        // resolver's `Path::join` sees — so a `feira tofu` shell-out
        // to a `cd '{caminho}'` command line, a `nix flake check`
        // invocation on an emitted YAML `path:` scalar folded through
        // envsubst, or a `helm template` invocation with a
        // `values.yaml` `path: {caminho}` embedded in a `{{`-quoted
        // template all disagree with the resolver on which directory
        // the value names. Two workstations whose downstream shell /
        // envsubst / Nix / Make / K8s-template parsing layers differ
        // in `$VAR` recognition (or, worse, expand the byte against
        // divergent environments — Alice's `$HOME=/home/alice`, Bob's
        // `$HOME=/home/bob`) emit divergent build artifacts for the
        // byte-identical caixa.lisp value. Even in the case where the
        // resolver strictly does NOT expand `$VAR` (the current
        // implementation) the divergence still bites at the lacre-
        // identity axis: the lacre pipeline embeds the value verbatim
        // in its per-dep content-address (`conteudo:
        // format!("path:{caminho}")`, caixa-resolver/src/resolve.rs:189),
        // so `path:../foo$HOME/bar` locks a BLAKE3 closure distinct
        // from the byte-identical-semantic `path:../foo/home/alice/bar`
        // one author would have produced by substituting the literal
        // value at author time, defeating the THEORY.md §V.2 render-
        // determinism contract on the same axis every prior `:caminho`
        // arm protects.
        //
        // Beyond the render-determinism / host-layout-leak vectors,
        // `$` at any position in a value flowing verbatim into a
        // shell-spawned subprocess is the canonical CWE-78 shell-
        // command-injection surface every peer single-token-shaped
        // typed slot already closes. A `:caminho "../foo$(whoami)/bar"`
        // that rides into a future `feira tofu` shell-out as `cd
        // '../foo$(whoami)/bar'` gets substituted by the shell at
        // subprocess-argument-expansion time even inside single quotes
        // in fewer positions than one might expect (the substitution
        // fires only outside single-quoting per POSIX §2.2.2, but
        // eval-style wrappers and `sh -c` layers that route the value
        // through re-parsing round-trip the substitution — the same
        // vector the c370458 backtick arm closes at the sibling
        // command-substitution-legacy-form surface). Every future
        // `feira` verb that shells out with a `caminho`-formatted
        // subprocess argument silently inherits this substitution
        // vector unless the typed slot's accepted set structurally
        // excludes the byte.
        //
        // Frontier inspiration: OTP's `gen_server` return-value grammar
        // rejects mid-tuple shell-metachar bytes by construction —
        // `{noreply, State}` never carries a raw `$` because the
        // Erlang term type system has no notion of "string that gets
        // shelled out"; caixa's typed slots inherit the same
        // structural discipline (types-are-theorems, the compounding
        // mandate's leverage-point-1) by refusing values that would
        // silently reinterpret at any downstream layer. Peer with
        // Unison's content-addressed code (no ambient environment —
        // every reference is a hash, no `$VAR` substitution possible)
        // and Pony's capabilities (a path capability that carries a
        // `$` would be ill-typed at the reference layer).
        //
        // The arm fires AFTER the URL-percent-encoding-escape arm (the
        // e3558fa `%` arm) because a value carrying both `%` and `$`
        // (`"../foo%20$HOME/bar"` — the canonical "I pasted a percent-
        // encoded space next to a `$HOME` template") surfaces the
        // narrower URL-encoding diagnostic first — the paste-from-
        // browser-address-bar shape is the load-bearing self-locating
        // edit on every probe-as-both value; same cascade discipline
        // every prior `:caminho` arm establishes (a323db8 %  before
        // this arm, this arm before trailing-`/`). The arm fires
        // BEFORE the trailing-`/` arm because the embedded shell-
        // variable-expansion byte is the more semantic-locating axis
        // on probe-as-both values (`"../foo$HOME/bar/"` ends in `/`
        // but the load-bearing diagnostic is the embedded `$` — the
        // trailing `/` is the secondary observation, and an author
        // who substitutes the `$HOME` template with a literal value is
        // likely to also tab-strip the trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'$' {
                return Err(DepError::FonteCaminhoShellVariableExpansion {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's shell-history-expansion / RFC-3986-sub-delims
        // arm. The immediate-predecessor `$` embedded arm closes the shell-
        // variable-expansion / command-substitution byte; `!` (`0x21`) is the
        // orthogonal POSIX shell-history-expansion sentinel every interactive
        // shell with history enabled (bash / ksh / zsh's `bashcompat` /
        // csh / tcsh) lexes as the history-expansion prefix: `!command`
        // re-runs the most recent history entry beginning with `command`,
        // `!!` re-runs the prior command verbatim, `!$` substitutes the
        // last word of the prior command, `!:N` substitutes the Nth word,
        // `^old^new` rewrites the prior command's `old` to `new` (the
        // canonical set of `set -o histexpand` operators bash's default
        // interactive session enables). Beyond the shell-history layer,
        // RFC 3986 §2.2 lists `!` in the `sub-delims` set (the URL grammar
        // admits the byte inside a path segment, but every WHATWG-conformant
        // special-scheme URL parser percent-encodes it inside a query
        // component via the 'special-query percent-encode set' the peer
        // `is_git_repo_url` `*` / `(` / `)` / `'` arms close on); the byte
        // is also the C / C++ / Rust / JavaScript / Python bang-operator
        // (logical-negation prefix — the paste-from-source-code idiom where
        // an author copies `!path.exists()` out of a Rust snippet and the
        // trailing punctuation crosses the string-literal boundary); the
        // canonical English-typography emphasis / exclamation mark (the
        // paste-from-prose enthusiasm-form idiom where an author writes
        // `:caminho "../caixa-teia!"` expecting the substrate to coerce it
        // to a kebab-case slug); and the Nix flake-ref import-attribute
        // `import ./foo.nix { … }` sibling operator surface.
        //
        // POSIX `std::path::Path` treats `!` as a literal path-component
        // byte, so a `:caminho "../caixa-teia!sudo"` (the canonical paste-
        // from-shell-history footgun where the author copies a `cd
        // ../caixa-teia && !sudo make install` one-liner from a quick-
        // start README and the trailing `!sudo` rides in verbatim as a
        // history-expansion reference), a `:caminho "../foo!!/bar"` (the
        // `!!` repeat-prior-command paste idiom), a `:caminho
        // "../caixa-teia!"` (the English-typography enthusiasm-form
        // paste-from-prose footgun), or a `:caminho "../foo!$"` (the
        // last-word-substitution shape) silently pass every prior arm
        // because `Path::is_absolute` returns false on `..`, `!` is neither
        // a leading-byte sentinel nor a control byte nor `\` nor `<` / `>`
        // nor `|` nor `;` nor `&` nor backtick nor `*` / `?` nor `(` / `)`
        // nor `{` / `}` nor `[` / `]` nor `'` / `"` nor `#` nor `%` nor `$`,
        // and the value's last byte isn't `/`. The resolver folds the value
        // through `Path::new(caminho).join(<file>)` looking for a literal
        // `./../caixa-teia!sudo` subdirectory and fails at resolve time
        // with a non-self-locating `No such file or directory` error far
        // from the source caixa.lisp — while every downstream interactive
        // shell with `set -o histexpand` reinterprets the byte as the
        // history-expansion prefix, and the failure mode forks per
        // consumer: a `feira tofu` shell-out to a `cd '{caminho}'` command
        // line executed under `bash -i` (the operator-notebook interactive
        // shell) substitutes the `!sudo` reference to the most recent
        // history entry starting with `sudo`, silently invoking whatever
        // privileged command that entry named.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so the byte lands in the
        // BLAKE3 closure and rides into every shell-spawned subprocess
        // (the resolver's `git clone`, a future `feira tofu` shell-out,
        // a future operator-side `nix flake check` spawn) as the
        // canonical shell-history-expansion / RFC-3986-sub-delims surface
        // every peer single-token-shaped typed slot already closes. The
        // peer `:fonte :repo` axis closes the byte under the same shell-
        // history-expansion / RFC-3986-sub-delims banner (7d53c68 `!` on
        // `is_git_repo_url`); the `:caminho` axis was the last typed
        // path-string surface still admitting the byte. This arm closes
        // the gap so the substrate-wide "no shell-composition
        // metacharacter / history-expansion sentinel anywhere in a typed
        // string slot that flows verbatim into a shell-spawned subprocess"
        // invariant extends from shell-variable-expansion (`$`) to shell-
        // history-expansion (`!`) on the `:caminho` axis. Together with
        // the peer c370458 backtick command-substitution-legacy-form arm
        // and the b9d187c-`$`-embedded-variable-expansion arm on the
        // sibling `:repo` axis, the typed `:caminho` accepted set now
        // structurally excludes every byte the POSIX shell §2.6 Word
        // Expansions section, §2.3 Token Recognition step 6, and every
        // history-expansion / brace-expansion / pathname-expansion /
        // parameter-expansion / command-substitution / arithmetic-
        // expansion operator lexes as a first-class parser byte.
        //
        // Frontier inspiration: Unison's content-addressed code (no
        // ambient environment — every reference is a hash, no `!<num>`
        // history-index substitution possible; the caixa substrate's
        // lacre discipline arrives at the same guarantee by refusing
        // bytes at manifest-parse time that would reinterpret against
        // ambient shell history state); Pony's capabilities (a path
        // capability that carries a `!` would be ill-typed at the
        // reference layer).
        //
        // The arm fires AFTER the shell-variable-expansion arm because a
        // value carrying both `$` and `!` (`"../foo$HOME/bar!sudo"` — the
        // canonical "I pasted a `$HOME`-templated path adjacent to a
        // trailing `!sudo` history-expansion") surfaces the narrower
        // shell-variable-expansion diagnostic first — the paste-from-CI-
        // manifest-with-`$VAR`-template shape is the load-bearing self-
        // locating edit on every probe-as-both value; same cascade
        // discipline every prior `:caminho` arm establishes. The arm
        // fires BEFORE the trailing-`/` arm because the embedded shell-
        // history-expansion byte is the more semantic-locating axis on
        // probe-as-both values (`"../foo!sudo/"` ends in `/` but the
        // load-bearing diagnostic is the embedded `!` — the trailing `/`
        // is the secondary observation, and an author who removes the
        // `!sudo` history reference is likely to also tab-strip the
        // trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'!' {
                return Err(DepError::FonteCaminhoShellHistoryExpansion {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's shell-history-substitution / RFC-3986-unwise
        // / regex-anchor arm. The immediate-predecessor `!` arm closes the
        // POSIX `!command` / `!!` / `!$` history-expansion prefix; `^`
        // (`0x5E`) is the paired-operator half of the same bash-reference
        // §9.3 histexpand feature — the `^old^new^` "quick substitution"
        // form (POSIX bash rewrites the prior command's `old` string to
        // `new` and re-executes it, the canonical typo-correction one-
        // liner idiom `git clone <bad-url>` → `^bad^good` that pastes the
        // trailing substitution fragment verbatim into a `:caminho` value
        // when the author trims only the leading `git clone` prefix). The
        // peer `:fonte :repo` axis closes the byte under the same
        // shell-history-substitution / RFC-3986-unwise banner (49e142f `^`
        // on `is_git_repo_url`); the `:caminho` axis was the last typed
        // path-string surface still admitting the byte after 6a04767
        // landed the `!` arm.
        //
        // Beyond bash history-substitution, `^` carries five distinct
        // downstream-reinterpretation surfaces the typed slot's accepted
        // set must structurally exclude:
        //
        // 1. **RFC 3986 §2 'unwise' set** — the four-byte cross-transport
        //    layer set (`{`, `}`, `|`, `\`) plus `^` every URL parser is
        //    required to percent-encode-or-refuse at the wire boundary.
        //    The WHATWG URL spec's 'fragment percent-encode set' maps
        //    `^` → `%5E` at the query / fragment component transition;
        //    libcurl silently percent-encodes the byte on the wire, so a
        //    `:caminho "../foo^bar"` value the resolver's `Path::join`
        //    sees as a literal `./../foo^bar` subdirectory diverges from
        //    the byte-transformed `%5E` shape any downstream `feira tofu`
        //    curl-invocation or artifact-registry-fetch would emit — the
        //    canonical wire-boundary divergence vector the peer
        //    `{`, `}`, `|`, `\` `:caminho` arms already close (
        //    `FonteCaminhoShellBraceExpansion` at 598b770,
        //    `FonteCaminhoShellPipe` at the pipe arm,
        //    `FonteCaminhoBackslash` at the backslash arm).
        // 2. **Regex character-class negation prefix `[^abc]`** — the
        //    canonical paste-from-doc-regex-pipeline footgun where an
        //    author copies a `grep '[^abc]'` idiom from a docs quick-
        //    listing and the character-class negation byte rides in
        //    verbatim.
        // 3. **Bitwise XOR operator** in C / C++ / Rust / Python /
        //    JavaScript / Nix / Go — the paste-from-source-code idiom
        //    where an author copies an `x ^ y`-shaped expression out of
        //    a source snippet and the operator crosses the string-
        //    literal boundary.
        // 4. **Windows `cmd.exe` escape metacharacter** — the byte
        //    escapes the next character in a `cmd.exe` batch context (a
        //    peer of the backslash arm's Windows-separator-leak vector).
        //    A `:caminho "..^&whoami"` cross-platform paste-from-batch-
        //    file footgun reinterprets at every `cmd.exe`-spawned
        //    subprocess (the resolver's future Windows-runner shell-out,
        //    the operator's WinRM path, a future PowerShell-embedded
        //    invocation).
        // 5. **LaTeX / Markdown / BibTeX superscript operator** — the
        //    paste-from-typeset-doc footgun where a mathematical
        //    superscript notation (`x^2` / `M^T`) leaks from prose.
        //
        // POSIX `std::path::Path` treats `^` as a literal path-component
        // byte, so `:caminho "../foo^bar/baz"` (embedded quick-
        // substitution), `:caminho "../foo^"` (trailing history-
        // substitution-open shape), `:caminho "../[^a-z]/foo"` (regex-
        // negation-prefix paste from a grep pipeline; note the `[` / `]`
        // arm at 986963b fires first on this shape), or `:caminho
        // "../x^y"` (XOR-expression paste-from-source) all silently pass
        // every prior arm (`^` isn't `\` / `<` / `>` / `|` / `;` / `&` /
        // backtick / `*` / `?` / `(` / `)` / `{` / `}` / `[` / `]` / `'`
        // / `"` / `#` / `%` / `$` / `!`) and route through
        // `Path::new(caminho).join(<file>)` looking for a literal
        // `./{caminho}` subdirectory that fails at resolve time with a
        // non-self-locating `No such file or directory` error far from
        // the source caixa.lisp — while every downstream shell / curl /
        // regex / `cmd.exe` layer reinterprets the byte to its own
        // semantic.
        //
        // The lacre pipeline embeds the value verbatim in its per-dep
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so the byte lands in the
        // BLAKE3 closure and rides into every shell-spawned subprocess
        // (the resolver's `git clone`, a future `feira tofu` shell-out,
        // a future operator-side `nix flake check` spawn) as the
        // canonical shell-history-substitution / RFC-3986-unwise /
        // regex-negation surface every peer single-token-shaped typed
        // slot already closes. This arm together with the immediate-
        // predecessor `!` arm (6a04767) closes the full `set -o
        // histexpand` operator surface on the `:caminho` axis — the
        // `!command` / `!!` / `!$` prefix form via `!`, the `^old^new^`
        // quick-substitution form via `^` — so the substrate-wide "no
        // shell-history operator anywhere in a typed string slot that
        // flows verbatim into a shell-spawned subprocess" invariant
        // extends from the `!` prefix half to the `^` quick-substitution
        // half. Every peer bash-history operator now fails at manifest-
        // parse time with a self-locating diagnostic naming the offending
        // caixa.lisp rather than at resolve-time as a `Path::join`-
        // derived `No such file or directory` (harmless but non-self-
        // locating) or worse riding into a downstream `bash -i` context
        // that reinterprets the byte-pair against ambient history state.
        //
        // Frontier inspiration: bash reference §9.3 HISTORY EXPANSION
        // "Quick substitution. Repeat the previous command, replacing
        // string1 with string2." + RFC 3986 §2 'unwise' set
        // ("characters that gateways and other transport agents are
        // known to sometimes modify") + Pony's capabilities (a path
        // capability that carries a `^` would be ill-typed at the
        // reference layer, matching the same structural discipline the
        // sibling `!` history-expansion arm inherits from Unison's
        // content-addressed no-ambient-history discipline).
        //
        // The arm fires AFTER the shell-history-expansion `!` arm because
        // a value carrying both `!` and `^` (`"../foo!sudo^bad^good"` —
        // the canonical "I pasted a `!sudo` history-reference next to a
        // `^bad^good` quick-substitution") surfaces the narrower prefix-
        // form `!` diagnostic first — the `!` form is the load-bearing
        // self-locating edit on every probe-as-both value (an author who
        // removes the `!sudo` reference is likely to also strip the
        // paired `^` substitution fragment); same cascade discipline
        // every prior `:caminho` arm establishes. The arm fires BEFORE
        // the trailing-`/` arm because the embedded shell-history-
        // substitution byte is the more semantic-locating axis on
        // probe-as-both values (`"../foo^bar/"` ends in `/` but the
        // load-bearing diagnostic is the embedded `^` — the trailing `/`
        // is the secondary observation, and an author who removes the
        // `^bar` substitution fragment is likely to also tab-strip the
        // trailing separator).
        for &b in caminho.as_bytes() {
            if b == b'^' {
                return Err(DepError::FonteCaminhoShellHistorySubstitution {
                    nome: nome.to_string(),
                    caminho: caminho.to_string(),
                    byte: b,
                });
            }
        }
        // Reproducibility gate's trailing-`/` arm. The b94fd83 absolute arm
        // closes the leading-`/` host-layout-leak; the embedded-control-byte
        // arm closes any byte-in-the-`0x00..=0x1F` / `0x7F` range; the
        // backslash arm closes the cross-host-OS-separator vector. The
        // trailing-`/` is the orthogonal shell-tab-completion-on-a-directory
        // footgun — `Path::join("../caixa-teia")` and
        // `Path::join("../caixa-teia/")` resolve to the same directory
        // (POSIX path-component-walk treats trailing `/` as a no-op for
        // directory targets, which `:caminho` always names — the sibling-
        // workspace dep root is structurally a directory). The lacre
        // pipeline embeds the value verbatim in its per-dep content-address
        // (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so byte-identical caixa
        // semantic-meaning yields two distinct BLAKE3 closures depending on
        // whether the author shell-tab-completed the path (every interactive
        // shell appends `/` on tab-completing a directory, idiomatic in
        // bash / zsh / fish / nushell), pasted from `pwd` (which on most
        // shells emits without trailing `/`, but `realpath -e -m` on a
        // directory with trailing `/` preserves it), or copied a Cargo
        // `path = "../caixa-teia/"` entry from cross-substrate documentation
        // (Cargo accepts both shapes and folds them the same way). Two
        // workstations whose authors differ only in tab-completion habits
        // emit byte-divergent lacres for the byte-identical-semantic caixa,
        // and the substrate's "the lacre is the build's identity" contract
        // (CAIXA-SDLC §III.2) silently breaks far from the source caixa.lisp.
        //
        // Same THEORY.md §V.2 render-determinism axis every prior `:caminho`
        // arm protects, here against the trailing-separator divergence
        // vector: every typed slot's accepted set excludes byte-divergent
        // values that round-trip to the same downstream semantic. The peer
        // path-shaped axes already reject trailing separators on the same
        // contract: [`crate::render::is_gateway_api_http_path`] gates
        // `:entrada :paths` against any non-canonical normalization, and
        // [`crate::render::is_sandboxed_relative_path`] gates the M2 typed
        // path-slots (`:behavior :on-*`, `:upgrade-from :state-change
        // :script`, `:bibliotecas`, `:exe`, `:servicos`) against shapes
        // whose canonical form would re-introduce determinism divergence.
        //
        // The arm fires last in the cascade because every prior arm carries
        // a more self-locating diagnostic on values that probe as both
        // (e.g. `:caminho "../foo/\0/"` ends in `/` but the load-bearing
        // diagnostic is the NUL byte's POSIX-syscall-rejection — the
        // control-char arm wins; `:caminho "/etc/passwd/"` ends in `/` but
        // the load-bearing diagnostic is the absolute host-layout-leak —
        // the absolute arm wins; `:caminho "..\caixa-teia/"` ends in `/`
        // but the load-bearing diagnostic is the Windows-separator cross-
        // OS divergence — the backslash arm wins). The arm covers every
        // shape where the last byte is `/` regardless of length, including
        // the degenerate single-`/` (which the absolute arm catches first)
        // and the consecutive-`//` (where every prior arm passes on the
        // bytes other than the trailing `/`).
        if caminho.as_bytes().last() == Some(&b'/') {
            return Err(DepError::FonteCaminhoTrailingSlash {
                nome: nome.to_string(),
                caminho: caminho.to_string(),
            });
        }
        Ok(())
    }
}

impl Dep {
    /// Substrate-canonical per-`:deps` / `:deps-dev` entry `:nome` scalar
    /// accessor every consumer of the dep-graph identity axis keys off —
    /// returns the author-declared `:nome` byte-string verbatim as a
    /// `&str`, borrowed from the typed slot's own [`String`] storage.
    ///
    /// The `:deps :nome` / `:deps-dev :nome` slot carries the DNS-1123
    /// label that names the target caixa (validated by [`Self::validate`]
    /// through the shared [`crate::render::is_dns_1123_label`] predicate,
    /// same accept-set the peer caixa-identifier axes carry — top-level
    /// [`crate::Caixa::nome`], per-`:membros` [`crate::Membro::nome`],
    /// per-`:children` [`crate::supervisor::ChildSpec::nome`]). Every
    /// downstream consumer that fans on the dep's name-identity keys off
    /// this scalar: the [`crate::Caixa::validate_deps`] per-list
    /// [`crate::render::insert_first_seen`] dedup key + the paired
    /// [`DepError::DuplicateNome`] carrier the walk raises on collision,
    /// the cross-list [`validate_no_self_dep`] parent-name equality gate
    /// on both `:deps` and `:deps-dev` traversals, the `caixa-resolver`
    /// pipeline's `HashSet<String>` seen-set the closure walker gates
    /// requeueing off (`caixa-resolver/src/resolve.rs:55`), the resolver's
    /// per-transitive-target requeue path (`resolve.rs:63,66`), the
    /// [`crate::DepSource::default_github`]-shaped resolver-side shorthand
    /// fill-in that folds `:nome` into the fetched-git-URL (`resolve.rs:147`),
    /// every `caixa-resolver` `ResolveError::MissingPath` /
    /// `ResolveError::MissingPin` carrier that names the offending dep
    /// (`resolve.rs:177,206`), each resolved
    /// `caixa-lacre::LacreEntry` `nome:` field the closure hash keys off
    /// (`resolve.rs:108,113`), and the peer `feira lock` stub-resolver's
    /// `LacreEntry` emitter (`caixa-feira/src/cmd/lock.rs:59,61,64`).
    ///
    /// Prior to this lift the `.nome` byte-string was read inline at every
    /// production site — the [`crate::Caixa::validate_deps`] paired
    /// `dep.nome.as_str()` / `dep.nome.clone()` accesses on both `:deps`
    /// and `:deps-dev` traversals, the [`validate_no_self_dep`] pair of
    /// parent-equality checks, and every caixa-resolver / caixa-feira
    /// site enumerated above — open-coded field-accesses that expressed
    /// no compile-time link back to the typed slot. A future extension of
    /// the `:deps :nome` axis to a richer author surface (a per-scope
    /// alias table the resolver folds through the `~/.config/caixa/config.yaml`
    /// entry the [`crate::dep::Dep`] docstring already acknowledges, a
    /// namespace-qualified rewrite the future M4 lacre-federation layer
    /// applies per-cluster, a promotion of the plain [`String`] byte-string
    /// to a richer scoped-identifier newtype once cross-registry federation
    /// lands) would have had to be threaded through every open-coded copy
    /// in lockstep or two consumers would silently disagree on which caixa
    /// a given dep resolves to — the [`crate::Caixa::validate_deps`] dedup
    /// set treating the name as `"caixa-teia"` while the caixa-resolver
    /// closure walker treated it as `"tenant-a/caixa-teia"` would silently
    /// split the [`DepError::DuplicateNome`] refusal from the resolver's
    /// requeue-suppression seen-set, one build-time diagnostic
    /// disagreeing with the run-time closure the substrate's lacre
    /// pipeline actually materializes. Lifting the resolution rule to a
    /// typed method on the substrate primitive means every downstream
    /// consumer of the caixa's per-`:deps` identity surface reaches for
    /// exactly one typed dispatch — the resolver's accept-set migrates as
    /// a unit on any future axis addition.
    ///
    /// First accessor on the outer `Dep` type — opens the outer-`Dep`
    /// `&str`-return required-scalar projection pattern the sibling
    /// per-`Dep` `:versao` future lift folds on. Peer of the sibling
    /// per-`:membros` [`crate::Membro::nome`] (4a32abf) /
    /// per-`:children` [`crate::supervisor::ChildSpec::nome`] (dfb4a81)
    /// / top-level [`crate::Caixa::nome`] (e6b7d97) caixa-identity scalar
    /// accessors — same "one typed dispatch on the substrate primitive,
    /// thin projections at each consumer" discipline extended onto the
    /// third named-caixa-referencing axis (`:deps` / `:deps-dev`), the
    /// remaining unlifted caixa-name-referencing accessor family in the
    /// substrate. Named `nome()` to match the tatara-lisp author-surface
    /// term the field's docstring already reaches for ("Caixa name — must
    /// match the target caixa's `:nome`") and the peer caixa-identity
    /// accessor family the substrate already carries.
    #[must_use]
    pub fn nome(&self) -> &str {
        self.nome.as_str()
    }

    /// Substrate-canonical per-`:deps` / `:deps-dev` entry `:versao`
    /// Cargo-shaped semver-requirement scalar accessor every consumer of
    /// the dep-graph version-pin axis keys off — returns the author-
    /// declared `:versao` requirement byte-string verbatim as a `&str`,
    /// borrowed from the typed slot's own [`String`] storage.
    ///
    /// The `:deps :versao` / `:deps-dev :versao` slot carries the
    /// Cargo-shaped semver requirement string (`"^0.1"`, `"~0.1.2"`,
    /// `"0.1.0"`, `"*"`) the shared [`crate::version::parse_requirement`]
    /// entry-point consumes — same accept-set the peer requirement-
    /// carrying axes carry (per-`:membros`
    /// [`crate::Membro::versao_requirement`], per-`:children`
    /// [`crate::supervisor::ChildSpec::versao_requirement`]), validated
    /// through the shared
    /// [`crate::render::require_valid_versao_requirement`] cascade in
    /// [`Self::validate`]. Every downstream consumer that fans on the
    /// dep's version-pin keys off this scalar: the [`Self::validate`]
    /// `require_valid_versao_requirement` gate + the paired
    /// [`DepError::VersaoInvalid`] carrier the cascade raises on
    /// requirement-shape rejection, the `feira lock` stub-resolver's
    /// `format!("{}@{}", dep.nome(), dep.versao_requirement())`
    /// `conteudo` hash-input interpolation and the paired
    /// `LacreEntry.versao:` `String`-carry fill (`caixa-feira/src/cmd/lock.rs`),
    /// and the peer `feira lock` end-to-end fixture in `caixa-feira/tests/feira_e2e.rs`.
    ///
    /// Prior to this lift the `.versao` byte-string was read inline at
    /// every production site — the [`Self::validate`] paired
    /// `&self.versao` requirement-gate reference and `self.versao.clone()`
    /// error-body carrier, the `caixa-feira/src/cmd/lock.rs` paired
    /// `format!("{}@{}", dep.nome(), dep.versao)` `conteudo` interpolation
    /// and `versao: dep.versao.clone()` `LacreEntry` fill, and the
    /// `caixa-feira/tests/feira_e2e.rs` end-to-end fixture's pair of the
    /// same shapes — open-coded field-accesses that expressed no
    /// compile-time link back to the typed slot. A future extension of
    /// the `:deps :versao` axis to a richer author surface (a per-scope
    /// version-lock overlay the resolver folds through the
    /// `~/.config/caixa/config.yaml` entry the [`crate::dep::Dep`]
    /// docstring already acknowledges, a per-cluster canary-version
    /// overlay per MESH-COMPOSITION §III.2, a promotion of the plain
    /// [`String`] requirement to a richer parsed-`VersionReq` newtype
    /// once cross-registry federation lands) would have had to be
    /// threaded through every open-coded copy in lockstep or two
    /// consumers would silently disagree on which release constraint a
    /// given dep resolves to — the [`Self::validate`] requirement-gate
    /// call reading `"^0.1"` while the `feira lock` stub-resolver's
    /// `conteudo` hash-input read `"tenant-a-pin/^0.1"` would silently
    /// split the [`DepError::VersaoInvalid`] refusal from the lacre's
    /// content-addressed hash the substrate's fetch pipeline actually
    /// materializes, one build-time diagnostic disagreeing with the
    /// run-time closure. Lifting the resolution rule to a typed method
    /// on the substrate primitive means every downstream consumer of
    /// the caixa's per-`:deps` version-pin surface reaches for exactly
    /// one typed dispatch — the resolver's accept-set migrates as a
    /// unit on any future axis addition.
    ///
    /// Second accessor on the outer `Dep` type — folds on the outer-
    /// `Dep` `&str`-return required-scalar projection pattern the
    /// sibling per-`Dep` [`Self::nome`] (eba2cde) accessor opened. Peer
    /// of the per-`:membros` [`crate::Membro::versao_requirement`]
    /// (a40b0e3) / per-`:children`
    /// [`crate::supervisor::ChildSpec::versao_requirement`] (7844f4e
    /// family) member/child version-pin accessors — the three
    /// requirement-carrying axes (`Dep::versao_requirement` on the
    /// per-caixa dep-graph edge, `Membro::versao_requirement` on the M3
    /// Aplicacao side, `ChildSpec::versao_requirement` on the M2
    /// Supervisor side) now share one accessor discipline for the
    /// shared substrate concept "another caixa referenced by a
    /// Cargo-shaped semver requirement". The pair
    /// `(nome(), versao_requirement())` jointly projects the
    /// `(nome, versao)` field pair every dep-graph consumer that fans
    /// on per-dep identity + version pin keys off. Named
    /// `versao_requirement()` rather than `versao()` because the field's
    /// storage-side `.versao` label is already the author-surface term
    /// (`:versao`); the accessor's name carries the semantic role — the
    /// semver *requirement* string the shared
    /// [`crate::version::parse_requirement`] entry-point consumes — so a
    /// raw field access and a typed dispatch read differently at every
    /// consumer site. Matches the peer
    /// [`crate::Membro::versao_requirement`] /
    /// [`crate::supervisor::ChildSpec::versao_requirement`] naming
    /// discipline verbatim.
    #[must_use]
    pub fn versao_requirement(&self) -> &str {
        self.versao.as_str()
    }

    /// Substrate-canonical per-`:deps` / `:deps-dev` entry `:fonte`
    /// Zig-store-model per-dep source-tuple optional-composite-reference
    /// accessor every consumer of the dep-graph fetch-source axis keys
    /// off — returns the author-declared `:fonte` typed [`DepSource`]
    /// verbatim as an `Option<&DepSource>` borrowed from the typed slot's
    /// own `Option<DepSource>` storage, with `None` naming the "author
    /// omitted `:fonte`" shorthand every resolver-side default-fill
    /// (`caixa-feira/src/cmd/lock.rs`'s stub, `caixa-resolver/src/resolve.rs`'s
    /// canonical fetcher, per the [`DepSource::default_github`] fallback
    /// the [`Dep::fonte`] field docstring already documents) treats as
    /// the "resolve through the configured default host / org
    /// (`github:<default-org>/<nome>`)" partition.
    ///
    /// The `:deps :fonte` / `:deps-dev :fonte` slot carries the two-
    /// arm typed [`DepSource`] the `Zig-style git-only store model` the
    /// enclosing [`Dep`] docstring names — `DepSource::Git { repo, tag,
    /// rev, branch }` for the git-clone arm every published caixa
    /// resolves through, `DepSource::Path { caminho }` for the dev-only
    /// local-filesystem arm every unpublishable in-tree checkout
    /// resolves through. Every downstream consumer that fans on the
    /// dep's fetch-source keys off this accessor: [`Self::validate`]'s
    /// per-`:fonte` [`DepSource::validate`] delegation (which raises
    /// the empty-`:repo` / missing-pin / multiple-pin / empty-`:caminho`
    /// diagnostics through the [`DepError::Fonte*`] carrier family
    /// naming the offending `Dep::nome`), the caixa-crd conversion
    /// crate's `dep_into_ref` two-arm projection into the `CaixaSource`
    /// `{repo, git_ref}` pair the K8s-CR side consumes
    /// (`caixa-crd/src/conversion.rs`), and — through the paired
    /// resolver-side default-fill's `Option::unwrap_or_else` — every
    /// `caixa-feira` / `caixa-resolver` fetch site that requires a
    /// concrete `DepSource` at run time.
    ///
    /// Prior to this lift the `.fonte` typed slot was read inline at
    /// every production site — the [`Self::validate`]
    /// `if let Some(ref fonte) = self.fonte` bracket the per-`:fonte`
    /// gate delegates through, the caixa-crd `dep_into_ref`
    /// `d.fonte.as_ref().and_then(...)` two-arm `CaixaSource` projector,
    /// the resolver-side `caixa-feira/src/cmd/lock.rs` / `caixa-resolver/src/resolve.rs`
    /// `dep.fonte.clone().unwrap_or_else(...)` default-fill pair — open-
    /// coded field-accesses that expressed no compile-time link back to
    /// the typed slot. A future extension of the `:deps :fonte` axis
    /// to a richer author surface (a per-scope source-override table
    /// the resolver folds through the `~/.config/caixa/config.yaml`
    /// entry the [`Dep`] docstring already acknowledges, a per-org
    /// mirror-fallback list the future M4 lacre-federation resolver
    /// consults ahead of the `default_github` fallback, a promotion of
    /// the plain `Option<DepSource>` to a richer
    /// `{primary, mirrors, integrity}` triple once cross-registry
    /// federation lands, a per-dep `sri:sha256-…` integrity slot the
    /// M4 lacre gate binds against ahead of the git-fetch) would have
    /// had to be threaded through every open-coded copy in lockstep or
    /// two consumers would silently disagree on which fetch source a
    /// given dep resolves to — the [`Self::validate`] per-`:fonte`
    /// gate reading the author-declared source while the caixa-crd
    /// projector read a per-scope-override-resolved source would
    /// silently split the build-time refusal from the CR the
    /// substrate's admission pipeline actually materializes, one
    /// build-time diagnostic disagreeing with the run-time closure.
    /// Lifting the resolution rule to a typed method on the substrate
    /// primitive means every downstream consumer of the caixa's per-
    /// `:deps` fetch-source surface reaches for exactly one typed
    /// dispatch — the resolver's accept-set migrates as a unit on any
    /// future axis addition.
    ///
    /// First outer-`Dep` `Option<&Composite>`-return composite-reference
    /// accessor — opens the outer-`Dep` `Option<&Composite>` composite-
    /// reference projection pattern the sibling per-`Dep` `:opcional`
    /// (`Option<Copy>` — the plain-bool axis) / `:caracteristicas`
    /// (`&[String]` — the feature-flag list) future outer scalar / slice
    /// lifts fold on. Peer of the outer-top-level [`crate::Caixa`]
    /// `Option<&Composite>` composite-reference sub-family the
    /// [`crate::Caixa::limits`] (b2bd9d7) / [`crate::Caixa::behavior`]
    /// (35d8b52) / [`crate::Caixa::politicas`] (5d23d29) /
    /// [`crate::Caixa::placement`] (4fb8074) / [`crate::Caixa::entrada`]
    /// (e4128e4) accessors already close on the outer [`crate::Caixa`]
    /// altitude, and of the outer M3 mesh-slot [`crate::AplicacaoSpec`]
    /// altitude the sibling [`crate::AplicacaoSpec::entrada`] (d32111c)
    /// accessor already carries — extends that "one typed dispatch on
    /// the substrate primitive, thin projections at each consumer"
    /// discipline onto the third outer typed-slot altitude that carries
    /// an `Option<Composite>` axis (`Dep`, the outer per-dep-list-entry
    /// slot). Returns `Option<&DepSource>` (not the owning composite by
    /// copy or clone) because every downstream consumer of the fonte
    /// composite treats it as a read-only per-arm dispatch source — the
    /// reference-view is the narrowest borrow that supports every
    /// present + roadmapped consumer (per-arm match projection at the
    /// caixa-crd `CaixaSource` two-arm emitter, presence-probe early
    /// return on the "author-omitted `:fonte` ⇒ resolver-side
    /// `default_github` fill applies" partition every resolver
    /// consults, `.cloned()`-on-demand for the two resolver-side
    /// default-fill call sites that require an owned `DepSource` for
    /// `Option::unwrap_or_else`) without cloning the composite through
    /// every consumer's fast path. The `Option` half of the return-type
    /// preserves the load-bearing "author-omitted `:fonte` ⇒ resolver-
    /// side default applies" partition (not a default composite the
    /// downstream must reject on emptiness) — the accessor projects the
    /// raw `Option<DepSource>` slot's presence bit through the
    /// reference-return unchanged. Named `fonte()` to match the storage
    /// field's name verbatim and the tatara-lisp author-surface term
    /// (`:fonte`) the field's own docstring already carries.
    #[must_use]
    pub fn fonte(&self) -> Option<&DepSource> {
        self.fonte.as_ref()
    }

    /// Substrate-canonical per-`:deps` / `:deps-dev` entry
    /// `:caracteristicas` Cargo-shaped feature-toggle-set slice accessor
    /// every consumer of the dep-graph feature-flag axis keys off —
    /// returns the author-declared `:caracteristicas` feature-name list
    /// verbatim as a `&[String]` slice-view over the same backing buffer
    /// the raw `self.caracteristicas.as_slice()` field access borrows
    /// from. Empty-list-carrying (`:caracteristicas` is a default-empty
    /// axis every `Dep` supplies with `Vec::new()` when the author omits
    /// the slot; the [`crate::Caixa::from_lisp`] derive folds an omitted
    /// `:caracteristicas` through `#[serde(default)]` to `Vec::new()`,
    /// so a `Dep` past parse definitionally carries a `Vec<String>` slot
    /// — possibly empty — and the returned `&[String]` degenerates to
    /// an empty slice on that arm without any silent `None` collapse).
    ///
    /// The `:deps :caracteristicas` / `:deps-dev :caracteristicas` slot
    /// carries the set-shaped feature-toggle list the substrate walks
    /// through the [`Self::validate_caracteristicas`] per-entry shape +
    /// duplicate cascade — same Cargo `[dependencies.<dep>.features]`
    /// accept-set (per-entry Cargo-feature-name grammar via the shared
    /// [`crate::render::is_cargo_feature_name`] predicate, cross-entry
    /// uniqueness via the shared [`crate::render::insert_first_seen`]
    /// walk, empty-first / value-shape-second / duplicate-third
    /// precedence via the peer per-axis two-arm cascade discipline every
    /// substrate-blessed Vec-keyed-by-name slot already follows).
    /// Every downstream consumer that fans on the dep's feature-toggle
    /// keys off this accessor: [`Self::validate_caracteristicas`]'s
    /// per-entry linear walk that gates each feature-name byte-string
    /// through the empty / value-shape / duplicate arms (raising the
    /// [`DepError::CaracteristicaEmpty`] / [`DepError::CaracteristicaInvalid`]
    /// / [`DepError::CaracteristicaDuplicate`] carrier family naming the
    /// offending `Dep::nome`), and every future
    /// per-`Caixa`-manifest / caixa-resolver / caixa-crd feature-toggle-
    /// facing consumer the CAIXA-SDLC §I roadmap acknowledges (the
    /// future caixa-resolver per-dep feature-projection walk that folds
    /// the toggle set into the resolved [`crate::Caixa`]'s activated
    /// [`crate::render::CARGO_FEATURE_NAME_MAX_LEN`]-bounded feature
    /// closure ahead of the lacre hash, the future caixa-crd per-`spec.deps`
    /// features slice the K8s-CR admission gate consumes, the future
    /// per-cluster feature-overlay the M4 lacre-federation resolver
    /// composes ahead of the substrate-wide feature-name accept-set).
    ///
    /// Prior to this lift the `.caracteristicas` byte-string list was
    /// read inline at the [`Self::validate_caracteristicas`] `for c in
    /// &self.caracteristicas` walk — the only in-crate consumer of the
    /// raw field beyond the per-`Dep` constructor pair
    /// ([`Self::simple`] / [`Self::git`]) and the paired serde
    /// round-trip / per-test fixture-mutation paths — an open-coded
    /// field-access that expressed no compile-time link back to the
    /// typed slot. A future extension of the `:caracteristicas` axis to
    /// a richer author surface (a per-scope feature-overlay the resolver
    /// folds through the `~/.config/caixa/config.yaml` entry the
    /// [`Dep`] docstring already acknowledges, a per-cluster feature-
    /// activation overlay the future M4 lacre-federation layer applies
    /// per-CR, a promotion of the plain `Vec<String>` byte-string list
    /// to a richer parsed-feature-set newtype once the Cargo-shaped
    /// namespaced-dep `dep/feat` syntax the value-shape gate's
    /// docstring anticipates lands) would have had to be threaded
    /// through every open-coded copy in lockstep or two consumers
    /// would silently disagree on which feature closure a given dep
    /// activates — the [`Self::validate_caracteristicas`] gate walking
    /// the author-declared list while a downstream caixa-resolver
    /// consumer walked a per-scope-override-resolved list would
    /// silently split the build-time refusal from the lacre closure
    /// the substrate's fetch pipeline actually materializes, one
    /// build-time diagnostic disagreeing with the run-time closure.
    /// Lifting the resolution rule to a typed method on the substrate
    /// primitive means every downstream consumer of the caixa's per-
    /// `:deps` feature-toggle surface reaches for exactly one typed
    /// dispatch — the resolver's accept-set migrates as a unit on any
    /// future axis addition.
    ///
    /// First outer-`Dep` `&[T]`-return slice accessor — opens the
    /// outer-`Dep` `&[String]` slice projection pattern the sibling
    /// per-`Dep` `:opcional` (`bool` — the plain-`Copy`-scalar axis)
    /// future outer scalar lift folds on and closes the outer-`Dep`
    /// slot-family the sibling [`Self::nome`] (eba2cde) /
    /// [`Self::versao_requirement`] (05529b1) / [`Self::fonte`] (d65d1bf)
    /// accessors already open, leaving the `:opcional` `Copy`-scalar arm
    /// as the sole remaining unlifted outer-`Dep` slot. Peer of the
    /// outer top-level [`crate::Caixa`] `&[String]`-return foreign-code-
    /// slot sub-family ([`crate::Caixa::bibliotecas`] 8a36c23,
    /// [`crate::Caixa::exe`] 65d9527, [`crate::Caixa::servicos`]
    /// 611f78b) and the outer top-level [`crate::Caixa`] universal-axis
    /// text-tag family ([`crate::Caixa::autores`] b5d813f,
    /// [`crate::Caixa::etiquetas`] 78c7d3c) that already carry the
    /// `&[String]` slice-projection discipline on the outer-`Caixa`
    /// altitude — extends the "one typed dispatch on the substrate
    /// primitive, thin projections at each consumer" discipline onto the
    /// outer per-dep-list-entry [`Dep`] altitude's set-shaped byte-
    /// string list slot. Returns `&[String]` (not `&Vec<String>`)
    /// because every downstream consumer of the feature-toggle list
    /// treats it as a read-only sequence — the slice-view is the
    /// narrowest borrow that supports every present + roadmapped
    /// consumer (`.iter()`, `.len()`, `.is_empty()`) without leaking
    /// the backing `Vec`'s grow/push/reserve surface no consumer of
    /// the typed view reaches for (the storage-side `Vec` remains
    /// reachable through the `pub caracteristicas` field for the
    /// mutation-carrying serde round-trip and per-test fixture-mutation
    /// paths). Named `caracteristicas()` to match the storage field's
    /// name verbatim and the tatara-lisp author-surface term
    /// (`:caracteristicas`) the field's own docstring already carries.
    #[must_use]
    pub fn caracteristicas(&self) -> &[String] {
        self.caracteristicas.as_slice()
    }

    /// Substrate-canonical per-`:deps` / `:deps-dev` entry `:opcional`
    /// missing-source-tolerance flag scalar accessor every consumer of
    /// the dep-graph opt-in-fetch axis keys off — returns the author-
    /// declared `:opcional` `bool` verbatim, `Copy`-projected from the
    /// typed slot's own `bool` storage (no borrow of `&self` past the
    /// call; the `Copy`-return arm matches the peer
    /// [`crate::Caixa::max_restarts`] (eba5211) `Option<u32>` `Copy`-
    /// projected sibling discipline the outer flat-spread family
    /// already carries). Default-`false` (`#[serde(default,
    /// skip_serializing_if = "is_false")]` on the storage slot, so a
    /// `Dep` past parse definitionally carries a `bool` — `false` when
    /// the author omits `:opcional` — and the returned value degenerates
    /// to `false` on that arm without any silent `None` collapse).
    ///
    /// The `:deps :opcional` / `:deps-dev :opcional` slot carries the
    /// per-entry "if this dep's `:fonte` cannot be resolved, treat the
    /// missing-source arm as a soft-fail rather than a build refusal"
    /// bit — the same Cargo-shaped `[dependencies.<dep>.optional = true]`
    /// accept-set (an opcional dep whose `:fonte` fails to resolve is
    /// dropped from the resolved dep-graph rather than tripping the
    /// build-refusal edge that a mandatory `:opcional false` entry
    /// would). Every downstream consumer that fans on the dep's
    /// missing-source-tolerance keys off this accessor: the future
    /// caixa-resolver's per-`:fonte` resolve-fail arm (drop-vs-error
    /// dispatch on the opcional bit ahead of the lacre closure
    /// materialization), the future caixa-crd per-`spec.deps`
    /// `optional` boolean the K8s-CR admission gate consumes on the
    /// per-dep partition, and the future feira / caixa-resolver /
    /// caixa-crd feature-projection walk that folds the opcional bit
    /// into the resolved feature-closure the future M4 lacre-federation
    /// layer emits.
    ///
    /// Prior to this lift the `.opcional` `bool` slot was read inline
    /// at the sole in-crate consumer site — the tests-module
    /// `registry_dep_is_minimal` fixture's `assert!(!d.opcional)` gate
    /// pinning the [`Self::simple`] constructor's default-`false` fill
    /// (the only in-crate read of the raw field beyond the per-`Dep`
    /// constructor pair [`Self::simple`] / [`Self::git`] and the paired
    /// serde round-trip / per-test fixture-mutation paths) — an open-
    /// coded field-access that expressed no compile-time link back to
    /// the typed slot. A future extension of the `:opcional` axis to a
    /// richer author surface (a per-scope opcional-override the resolver
    /// folds through the `~/.config/caixa/config.yaml` entry the [`Dep`]
    /// docstring already acknowledges, a per-cluster opcional-override
    /// the future M4 lacre-federation layer applies per-CR, a promotion
    /// of the plain `bool` to a richer `OpcionalPolicy { drop, warn,
    /// error }` tri-state once the CAIXA-SDLC §II opcional-policy
    /// roadmap lands) would have had to be threaded through every open-
    /// coded copy in lockstep or two consumers would silently disagree
    /// on which missing-source arm a given dep resolves to — the
    /// [`Self::simple`] constructor's default-`false` fill reading
    /// verbatim while a downstream caixa-resolver consumer read a per-
    /// scope-override-resolved bit would silently split the build-time
    /// arm from the lacre closure the substrate's fetch pipeline
    /// actually materializes, one build-time diagnostic disagreeing
    /// with the run-time closure. Lifting the resolution rule to a
    /// typed method on the substrate primitive means every downstream
    /// consumer of the caixa's per-`:deps` opcional-tolerance surface
    /// reaches for exactly one typed dispatch — the resolver's accept-
    /// set migrates as a unit on any future axis addition.
    ///
    /// Fifth and final outer-`Dep` accessor — closes the outer-`Dep`
    /// slot-family the sibling per-`Dep` [`Self::nome`] (eba2cde) /
    /// [`Self::versao_requirement`] (05529b1) / [`Self::fonte`] (d65d1bf)
    /// / [`Self::caracteristicas`] (9197944) accessors opened, so every
    /// outer-`Dep` slot (`:nome`, `:versao`, `:fonte`, `:opcional`,
    /// `:caracteristicas`) now routes through exactly one typed
    /// dispatch on the substrate primitive. First outer-`Dep`
    /// `bool`-return / plain-`Copy`-scalar accessor — opens the
    /// outer-`Dep` `Copy`-scalar projection pattern that folds on the
    /// peer outer-top-level [`crate::Caixa`] `Option<Copy>`
    /// flat-spread sub-family ([`crate::Caixa::max_restarts`] eba5211,
    /// [`crate::Caixa::estrategia`] ed04d3c) the outer-`Caixa` altitude
    /// already carries — extends the "one typed dispatch on the
    /// substrate primitive, thin projections at each consumer"
    /// discipline onto the outer per-dep-list-entry [`Dep`] altitude's
    /// bool-shaped missing-source-tolerance slot. Returns `bool` by
    /// `Copy` (not by `&bool` reference) because `bool` is `Copy` and
    /// every downstream consumer treats it as a plain discriminant
    /// value — the by-value return is the narrowest return-shape that
    /// supports every present + roadmapped consumer (`.then(…)` early
    /// return on the resolver-side drop-vs-error partition, direct
    /// bool composition with a per-scope-override projector, plain
    /// `if dep.opcional() { … }` early return at every future admission
    /// gate) without leaking the storage field's `bool`-in-`&self`
    /// lifetime the by-value return elides. Marked `pub const fn` so
    /// the accessor is `const`-callable — same discipline the peer
    /// [`crate::Caixa::max_restarts`] `Option<u32>` `Copy`-return
    /// accessor carries. Named `opcional()` to match the storage
    /// field's name verbatim and the tatara-lisp author-surface term
    /// (`:opcional`) the field's own docstring already carries.
    #[must_use]
    pub const fn opcional(&self) -> bool {
        self.opcional
    }

    /// Build a minimal registry-sourced dep.
    #[must_use]
    pub fn simple(nome: impl Into<String>, versao: impl Into<String>) -> Self {
        Self {
            nome: nome.into(),
            versao: versao.into(),
            fonte: None,
            opcional: false,
            caracteristicas: Vec::new(),
        }
    }

    /// Build a Git-sourced dep (tag-based).
    #[must_use]
    pub fn git(
        nome: impl Into<String>,
        versao: impl Into<String>,
        repo: impl Into<String>,
        tag: impl Into<String>,
    ) -> Self {
        Self {
            nome: nome.into(),
            versao: versao.into(),
            fonte: Some(DepSource::Git {
                repo: repo.into(),
                tag: Some(tag.into()),
                rev: None,
                branch: None,
            }),
            opcional: false,
            caracteristicas: Vec::new(),
        }
    }

    /// Reject dependency entries whose `:nome` or `:versao` are empty,
    /// whose `:nome` is non-empty but not a valid DNS-1123 label,
    /// or whose `:versao` is non-empty but not a valid Cargo-shaped
    /// semver requirement.
    ///
    /// The author surface for `:deps :versao` (and `:deps-dev :versao`)
    /// is the same Cargo-shaped requirement string `:membros :versao`
    /// (validated at [`crate::AplicacaoSpec::validate`] since 9888b13)
    /// and `:children :versao` (validated at
    /// [`crate::SupervisorSpec::validate`] since b38ff3a) carry — and
    /// the lacre pipeline resolves all three axes through the same
    /// [`crate::parse_requirement`] entry-point. Until 2420c44 landed
    /// `:deps :versao` was the last `:versao` axis untyped past
    /// `Caixa::from_lisp`: a malformed-but-non-empty requirement
    /// (`"^bad-version"`, `"^^0.1"`, the canonical git-tag-shape-
    /// leaking-into-:versao `"v0.1"` typo, the accidental
    /// `"not-a-req"`) silently passed parse and the `semver::Error`
    /// surfaced at lacre-resolve time, far from the source
    /// caixa.lisp, with no field naming which `:deps` entry carried
    /// the typo. The diagnostic [`DepError::VersaoInvalid`] carries
    /// the offending entry's `:nome` + the offending `:versao`
    /// verbatim + the parser's own wording in `reason`, so the
    /// author's grep target is unambiguous.
    ///
    /// The author surface for `:deps :nome` is the same DNS-1123 label
    /// the peer caixa-identifier axes carry — top-level Caixa `:nome`
    /// (validated at [`crate::Caixa::validate_nome`] since 6c992f8),
    /// `:membros :caixa` (validated at
    /// [`crate::AplicacaoSpec::validate_membros`] since 3f9d7a0),
    /// `:children :caixa` (validated at
    /// [`crate::SupervisorSpec::validate`] since 31bfa43). A `:deps
    /// :nome` value flows verbatim through the lacre pipeline as the
    /// target caixa's `:nome` (which the gate at the *target* side now
    /// rejects if non-DNS-1123) and lands as the rendered caixa's
    /// `lareira-<nome>` Helm chart name segment, the per-dep
    /// `LABEL_PROGRAM` label value, and the `caixa-resolver`'s
    /// `~/.cache/caixa/<org>/<nome>` checkout-directory leaf. Until
    /// this gate landed `:deps :nome` was the fourth and last
    /// DNS-1123-shaped caixa-identifier axis still untyped past
    /// `Caixa::from_lisp`: a syntactically wrong dep name (`"Caixa-
    /// Teia"` uppercase — the canonical "I copied the README header"
    /// typo; `"caixa_teia"` underscore — the Go module / Python
    /// identifier leak; `"caixa-teia."` trailing dot — the FQDN
    /// confusion; `"-caixa-teia"` leading hyphen; a 64-byte slug)
    /// silently passed parse and surfaced at lacre-resolve time when
    /// the resolved target caixa's `:nome` failed *its* DNS-1123 gate
    /// — far from the source `:deps` entry, with a diagnostic naming
    /// the *target's* `:nome` rather than the dep entry that referenced
    /// it. Mirroring the 3f9d7a0 / 31bfa43 / 6c992f8 trajectory through
    /// the lifted [`crate::render::is_dns_1123_label`] predicate (the
    /// "before its third occurrence" PRIME DIRECTIVE boundary, THEORY.md
    /// §I.3.5): every `Dep::nome` past validate is DNS-1123-label-shaped,
    /// so every downstream consumer (caixa-resolver's lacre fetch,
    /// caixa-helm's `lareira-<nome>` chart name, the future M4 per-dep
    /// fan-out emitter) reaches for the name knowing the value is
    /// apiserver-valid without re-validating.
    ///
    /// Empty checks fire first (narrower diagnostic), parse last —
    /// same ordering discipline as
    /// [`crate::AplicacaoSpec::validate_membros`] and
    /// [`crate::SupervisorSpec::validate`]. `parse_requirement("")`
    /// returns `Ok(VersionReq::STAR)`, so the empty-`:versao` arm is
    /// structurally necessary even with the parse arm in place. The
    /// `:nome` shape gate runs after the `:nome` empty gate and before
    /// the `:versao` checks so a one-entry caixa.lisp with both wrong
    /// sees the name-side diagnostic first (the name is the
    /// self-locating axis — without it, the parse diagnostic can't
    /// quote `:nome "<bad>"`).
    pub fn validate(&self) -> Result<(), DepError> {
        if self.nome.is_empty() {
            return Err(DepError::NomeEmpty);
        }
        if let Err(reason) = crate::render::is_dns_1123_label(&self.nome) {
            return Err(DepError::NomeInvalid {
                nome: self.nome.clone(),
                reason,
            });
        }
        // Delegate the empty-first + `parse_requirement` cascade to the
        // shared [`crate::render::require_valid_versao_requirement`]
        // helper — same two-arm shape the peer
        // [`crate::AplicacaoSpec::validate_membros`] on `:membros
        // :versao` and [`crate::SupervisorSpec::validate`] on `:children
        // :versao` route through, so drift between the three axes'
        // accepted requirement sets is structurally impossible and the
        // parse-side no-op the empty-first arm closes (semver's empty
        // parse yields an implicit `*`) lives in exactly one predicate.
        crate::render::require_valid_versao_requirement(
            self.versao_requirement(),
            || DepError::VersaoEmpty {
                nome: self.nome.clone(),
            },
            |reason| DepError::VersaoInvalid {
                nome: self.nome.clone(),
                versao: self.versao_requirement().to_string(),
                reason,
            },
        )?;
        if let Some(fonte) = self.fonte() {
            fonte.validate(&self.nome)?;
        }
        self.validate_caracteristicas()?;
        Ok(())
    }

    /// Reject per-entry `:caracteristicas` (feature-flag) values that
    /// are operationally meaningless. The `:caracteristicas` slot is
    /// a set of feature toggles to enable on the target caixa — same
    /// shape as Cargo's `[dependencies.<dep>.features]` list — and
    /// two structural footguns close here:
    ///
    ///   - empty-string entry (`(:caracteristicas (""))`): the future
    ///     caixa-resolver lacre pipeline would consume the empty
    ///     identifier as a no-op feature enable, silently dropping the
    ///     author's intent far from the source `caixa.lisp`;
    ///   - duplicate entry within one dep (`(:caracteristicas ("http"
    ///     "http"))`): the feature-toggle slot is set-shaped (enabling
    ///     a feature twice has no additional semantic — there is no
    ///     `feature × 2`), so two entries naming the same feature are
    ///     a silent miscount, the same set-not-multiset distinction
    ///     every peer Vec-keyed-by-name axis already closes
    ///     ([`crate::SupervisorError::DuplicateChildCaixa`] on
    ///     `:children :caixa`, [`crate::AplicacaoError::MembroDuplicate`]
    ///     on `:membros :caixa`, [`crate::AplicacaoError::ContratoDuplicate`]
    ///     on `:contratos`, [`crate::AplicacaoError::PlacementClusterDuplicate`]
    ///     on `:placement :clusters`, [`crate::AplicacaoError::EntradaPathDuplicate`]
    ///     on `:entrada :paths`, [`crate::UpgradeError::DuplicateFrom`]
    ///     on `:upgrade-from :from`, [`crate::UpgradeError::DuplicateLoadModule`]
    ///     / [`crate::UpgradeError::DuplicateStateChange`] /
    ///     [`crate::UpgradeError::DuplicateCleanup`] on the within-
    ///     entry `:upgrade-from` axes, and [`DepError::DuplicateNome`]
    ///     on the cross-entry `:deps`/`:deps-dev` `:nome` axis the
    ///     immediate-predecessor 359fba5 closed).
    ///
    /// Same linear-walk + `HashSet` + first-collision diagnostic shape
    /// every peer set-not-multiset gate uses; the empty arm fires
    /// before the duplicate arm so an entry with both an empty feature
    /// *and* a duplicate of some later feature surfaces the empty-
    /// shape diagnostic first (the empty-feature axis is the
    /// more-actionable defect since the missing-name renders the
    /// duplicate-key arm ambiguous: two `""` entries would both report
    /// `caracteristica: ""` with no way to distinguish the offending
    /// site). Empty-first cascade discipline mirrors every peer per-
    /// entry shape + duplicate gate
    /// (`SupervisorSpec::validate`'s `EmptyChildName` before
    /// `DuplicateChildCaixa`; `validate_membros`'s `MembroCaixaEmpty`
    /// before `MembroDuplicate`).
    ///
    /// The per-entry value-shape gate (Cargo-feature-name grammar via
    /// the lifted [`crate::render::is_cargo_feature_name`] predicate)
    /// fires between the empty arm and the duplicate arm — the
    /// canonical per-entry-shape-before-cross-entry-uniqueness
    /// precedence every peer two-arm + value-shape gate establishes
    /// ([`crate::SupervisorSpec::validate`]'s `EmptyChildName` →
    /// `ChildCaixaInvalid` → `DuplicateChildCaixa`,
    /// [`crate::AplicacaoSpec::validate_membros`]'s `MembroCaixaEmpty`
    /// → `MembroCaixaInvalid` → `MembroDuplicate`, [`Dep::validate`]'s
    /// `NomeEmpty` → `NomeInvalid` → cross-list `DuplicateNome`).
    /// Until the value-shape arm landed `:caracteristicas` accepted
    /// every non-empty distinct string — a structurally invalid
    /// feature name (`"http feature"` whitespace, `"+http"` the
    /// canonical paste-from-`+optional-feature` doc activation-form
    /// footgun, `"-flag"` leading hyphen, `".feat"` leading dot,
    /// `"http/json"` Cargo's `dep/feat` namespaced-dep syntax that
    /// only applies inside list-grammar contexts, `"http,json"`
    /// list-separator-belongs-to-the-list-grammar miscomprehension,
    /// `"café"` un-percent-encoded non-ASCII silently round-tripping
    /// inconsistently across NFC/NFD normalization, the 65-byte
    /// paste-from-binary slug) silently passed validate and the
    /// failure surfaced at `cargo metadata` time as the
    /// `restricted_names::validate_feature_name` parser's rejection,
    /// far from the source `caixa.lisp`, with no field naming which
    /// `:deps` entry's `:caracteristicas` carried the typo. The
    /// lifted predicate makes the Cargo-feature-name-grammar
    /// intersection-floor a substrate-level invariant at validate
    /// time — same trajectory as the eight peer
    /// [`crate::render`] value-shape predicates each typed surface
    /// downstream of a structured grammar already follows
    /// ([`is_dns_1123_label`](crate::render::is_dns_1123_label),
    /// [`is_gateway_api_http_path`](crate::render::is_gateway_api_http_path),
    /// [`is_wit_world_ref`](crate::render::is_wit_world_ref),
    /// [`is_nats_subject`](crate::render::is_nats_subject),
    /// [`is_wasi_keyvalue_slot`](crate::render::is_wasi_keyvalue_slot),
    /// [`is_git_ref_name`](crate::render::is_git_ref_name),
    /// [`is_git_oid`](crate::render::is_git_oid),
    /// [`is_git_repo_url`](crate::render::is_git_repo_url)).
    fn validate_caracteristicas(&self) -> Result<(), DepError> {
        let mut seen = std::collections::HashSet::new();
        for c in self.caracteristicas() {
            if c.is_empty() {
                return Err(DepError::CaracteristicaEmpty {
                    nome: self.nome.clone(),
                });
            }
            if let Err(reason) = crate::render::is_cargo_feature_name(c) {
                return Err(DepError::CaracteristicaInvalid {
                    nome: self.nome.clone(),
                    caracteristica: c.clone(),
                    reason,
                });
            }
            crate::render::insert_first_seen(&mut seen, c.as_str(), || {
                DepError::CaracteristicaDuplicate {
                    nome: self.nome.clone(),
                    caracteristica: c.clone(),
                }
            })?;
        }
        Ok(())
    }
}

/// Cross-slot coherence gate on the dep-graph axis: no `:deps` or
/// `:deps-dev` entry may name the caixa's own `:nome`.
///
/// A caixa that lists itself as a dep is a degenerate self-edge in the
/// lacre closure's dep-graph — the closure is a DAG rooted at the
/// caixa's `:nome`, and the caixa-resolver's lacre pipeline traverses
/// every `:deps` / `:deps-dev` entry's target by name. A self-dep
/// hands the resolver a node that is its own parent: a one-node cycle
/// it either rejects mid-traversal far from the source `caixa.lisp`
/// (the resolver detecting infinite recursion on the closure walk) or,
/// worse, recurses on until it exhausts its stack. Because every
/// `:nome` is a globally-unique substrate identity (DNS-1123 label +
/// lacre closure root), a dep entry whose `:nome` equals the caixa's
/// own `:nome` *is* the caixa itself, not a coincidentally-named peer.
///
/// Lives outside [`Caixa::validate_deps`] because the dep-list view
/// carries the entries but not the parent `:nome`; mirrors the
/// cross-slot self-edge gates [`crate::supervisor::validate_no_self_supervision`]
/// (ad4abf1) on the `:children :caixa` axis and
/// [`crate::aplicacao::validate_no_self_membership`] on the
/// `:membros :caixa` axis — the same "an edge from a graph node to
/// itself is structurally not a tree/graph edge" discipline, here on
/// the third typed-name-graph axis (the dep closure; the supervision
/// tree and the Aplicacao membership set were the prior two).
///
/// Walks `:deps` first then `:deps-dev` so the diagnostic for a caixa
/// that self-references on both axes surfaces the `:deps` arm first —
/// the load-bearing axis the lacre closure resolves at every build,
/// peer with the canonical [`Caixa::validate_deps`] walk order
/// (`:deps` → `:deps-dev`).
///
/// Carries the offending list tag (`":deps"` or `":deps-dev"`)
/// verbatim into the diagnostic so the author can grep their
/// `caixa.lisp` for the offending block in one edit — same
/// `list: &'static str` shape [`DepError::DuplicateNome`] (359fba5)
/// uses on the cross-list duplicate-name axis.
///
/// `Code paths` (`:bibliotecas` / `:exe` / `:servicos`) are the
/// substrate-blessed shape for referencing the caixa's *own* code, so
/// the diagnostic names them as the corrective surface — every
/// legitimate "I want to use code from this caixa" authoring intent
/// routes through one of those three slots, not a self-dep.
pub fn validate_no_self_dep(
    deps: &[Dep],
    deps_dev: &[Dep],
    parent_nome: &str,
) -> Result<(), DepError> {
    for dep in deps {
        if dep.nome() == parent_nome {
            return Err(DepError::DepIsSelf {
                nome: parent_nome.to_string(),
                list: crate::render::DEP_AUTHOR_KEY_DEPS,
            });
        }
    }
    for dep in deps_dev {
        if dep.nome() == parent_nome {
            return Err(DepError::DepIsSelf {
                nome: parent_nome.to_string(),
                list: crate::render::DEP_AUTHOR_KEY_DEPS_DEV,
            });
        }
    }
    Ok(())
}

/// Closed-set typed enum for the two dep-list author-surface axes every
/// top-level [`crate::Caixa`] carries — the runtime-closure `:deps` slot
/// (`Prod`) and the dev-only-closure `:deps-dev` slot (`Dev`). Every
/// substrate consumer that dispatches on "which of the two dep-lists"
/// (the `feira add` mutation head, the future per-cluster dev-closure-
/// audit overlay the M4 CR materializer resolves per-CR, the future
/// `caixa app graph` per-list dep summary, every future
/// `Caixa::push_dep` / `Caixa::deps_by_list` typed-method dispatch a
/// caller reaches for) reads through this enum rather than through a
/// bare `&'static str` — the closed-set is expressed at the type layer,
/// so a future third dep-list axis (a `:deps-build` build-only closure
/// once the substrate grows cross-artifact heterogeneous dep-graphs,
/// per CAIXA-SDLC §I) is one variant plus one arm per method and the
/// compiler enforces exhaustiveness on every consumer's `match` arms.
///
/// The wire byte-string [`Self::as_str`] returns is the same author-
/// surface tag the sibling [`crate::render::DEP_AUTHOR_KEY_DEPS`] /
/// [`crate::render::DEP_AUTHOR_KEY_DEPS_DEV`] constants carry — the
/// [`DepError::DuplicateNome`] / [`DepError::DepIsSelf`] `list:
/// &'static str` payload family the substrate already emits routes
/// through the same source of truth (an author reading a
/// [`DepError::DuplicateNome`] refusal can grep their `caixa.lisp`
/// for the offending `:deps` / `:deps-dev` block in one edit whether
/// the diagnostic came from a `Caixa::validate_deps` walk or a
/// `Caixa::push_dep` mutation).
///
/// Same "closed-set typed-enum discriminator with canonical
/// projections per axis" discipline the sibling closed-set typed enums
/// on the caixa typed surface carry
/// ([`crate::aplicacao::PlacementStrategy`] cc8f749,
/// [`crate::aplicacao::RateLimitUnit`] 6bce03d,
/// [`crate::supervisor::RestartStrategy`],
/// [`crate::supervisor::RestartPolicy`],
/// [`crate::upgrade::UpgradeInstruction`], [`crate::CaixaKind`])
/// — extended onto the outer-`Caixa` two-list dep-graph axis, the
/// substrate's last unlifted closed-set-shaped `&'static str`-carrying
/// axis on the top-level manifest surface.
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash, gen_platform::IsVariant)]
pub enum DepList {
    /// Runtime-closure `:deps` axis — the load-bearing dep-list the
    /// lacre closure resolves at every build. Wire-format
    /// [`crate::render::DEP_AUTHOR_KEY_DEPS`].
    Prod,
    /// Dev-only-closure `:deps-dev` axis — Cargo's `[dev-dependencies]`
    /// table's dev-time-only visibility contract per CAIXA-SDLC §I.
    /// Wire-format [`crate::render::DEP_AUTHOR_KEY_DEPS_DEV`].
    Dev,
}

impl DepList {
    /// Exhaustive iteration surface for every consumer that reads the
    /// full closed-set (the future M4 admission webhook's per-list
    /// summary rejection body, any future round-trip pin harness). A
    /// future variant addition extends this slice as a single edit and
    /// every consumer picks up the new entry by construction — the
    /// compiler-checked exhaustiveness on the sibling method `match`
    /// arms is the build-time guarantee that no arm forgets to grow.
    pub const ALL: &'static [Self] = &[Self::Prod, Self::Dev];

    /// Canonical author-surface tag every substrate consumer that
    /// names the offending dep-list in a diagnostic reaches for —
    /// [`crate::render::DEP_AUTHOR_KEY_DEPS`] for [`Self::Prod`] and
    /// [`crate::render::DEP_AUTHOR_KEY_DEPS_DEV`] for [`Self::Dev`],
    /// the same `&'static str` payload the sibling
    /// [`DepError::DuplicateNome`] and [`DepError::DepIsSelf`] variants
    /// already carry. Routing every dep-list diagnostic through the
    /// closed-set enum's `as_str` closes the last `&'static str`-shape
    /// literal-carry axis on the two-list dep-graph surface — a
    /// future kebab-case rebrand (`":deps"` → `":packages"`) or a
    /// wire-format promotion (a distinct diagnostic form for the
    /// `Dev` arm) reaches every consumer through one edit on the
    /// canonical constant, not a coordinated rewrite across the
    /// substrate's dep-graph consumers.
    #[must_use]
    pub const fn as_str(self) -> &'static str {
        match self {
            Self::Prod => crate::render::DEP_AUTHOR_KEY_DEPS,
            Self::Dev => crate::render::DEP_AUTHOR_KEY_DEPS_DEV,
        }
    }

    /// Substrate-canonical reverse projection on the two-list dep-graph
    /// axis — parses the author-surface wire tag back to the typed
    /// variant, or `None` when `s` is outside the closed-set arm-string
    /// set [`Self::as_str`] emits. Dispatches on the same lifted
    /// [`crate::render::DEP_AUTHOR_KEY_DEPS`] /
    /// [`crate::render::DEP_AUTHOR_KEY_DEPS_DEV`] constants the
    /// [`Self::as_str`] emitter walks, so the parse and emit halves of
    /// the round-trip migrate through one caixa-core edit on any future
    /// list-axis addition.
    ///
    /// Prior to this lift the substrate carried only the forward
    /// `Self → &str` projection on the two-list dep-graph axis (the
    /// [`Self::as_str`] emitter, the [`std::fmt::Display`] impl routed
    /// through it, the two [`DepError::DuplicateNome`] /
    /// [`DepError::DepIsSelf`] variants that carry the wire tag verbatim
    /// as a `&'static str` `list:` field). Every future consumer that
    /// wanted to promote the wire tag back to the typed enum (a future
    /// `feira dep --list <deps|deps-dev>` CLI arg-parse that binds the
    /// wire form into the typed enum before dispatching to
    /// [`crate::Caixa::deps_of`] / [`crate::Caixa::push_dep`], the M4
    /// `mesh.pleme.io/v1alpha1/Caixa` CR materializer's admission-time
    /// wire re-parse of the per-list diagnostic body, a future
    /// [`DepError`] widening that promotes the two `list: &'static str`
    /// fields to a typed `list: DepList` carry so downstream consumers
    /// dispatch on the enum rather than string-comparing the wire
    /// scalar) would have had to re-inline a two-arm `match s { ":deps"
    /// => …, ":deps-dev" => …, _ => … }` cascade that expressed no
    /// compile-time link back to the typed [`DepList`] enum. A future
    /// variant addition (a `:build-dep` or `:test-dep` third list once
    /// the substrate grows Cargo-style split-graphs, a `:tool-dep` for
    /// build-time-only tooling per the peer Cargo `[build-dependencies]`
    /// / `[target.<cfg>.dev-dependencies]` future admission surface)
    /// would silently split the wire byte-string the emitter walks from
    /// the parser's arm-set — the round-trip would carry the new list
    /// through the forward projection but land on the fallback silently
    /// at every non-updated reverse parser, far from the arm-addition
    /// commit that caused the drift. Lifting the resolver to a typed
    /// method on the substrate primitive closes the drift footgun by
    /// construction: the parser's accept-set is the same set the
    /// [`Self::as_str`] emitter walks (routed through the same lifted
    /// [`crate::render::DEP_AUTHOR_KEY_DEPS`] /
    /// [`crate::render::DEP_AUTHOR_KEY_DEPS_DEV`] consts), so both halves
    /// of the round-trip migrate through one caixa-core edit on any
    /// future list-axis addition.
    ///
    /// Same closed-set-reverse-projection discipline the sibling
    /// [`crate::CaixaKind::from_wire`] (2aa6d23) /
    /// [`crate::supervisor::RestartStrategy::from_wire`] (4eec29c) /
    /// [`crate::supervisor::RestartPolicy::from_wire`] (dd32ccf) /
    /// [`crate::aplicacao::PlacementStrategy::from_wire`] (18c7342) /
    /// [`crate::aplicacao::RateLimitUnit::from_suffix`] typed enums
    /// carry on the peer wire-side `str → Self` axes — extended onto
    /// the two-list dep-graph closed-set axis, the sixth substrate-side
    /// closed-set typed enum on the caixa surface to converge on the
    /// two-way `str ↔ Self` round-trip. Method-named `from_wire` (not
    /// `from_str`) to match the peer shapes verbatim and side-step the
    /// derived [`std::str::FromStr`] impls the sibling
    /// [`gen_platform::FromStrKind`]-carrying axes install on their
    /// kebab-case dispatcher-catalog identity. Returns `Option<Self>`
    /// (rather than `Result<Self, _>`) to match the peer shapes: the
    /// caller picks the diagnostic form appropriate for its use site —
    /// a future `feira dep --list …` arg-parse that surfaces
    /// `unknown list: <arg>` at the CLI builds one on top by iterating
    /// [`Self::ALL`], while the future M4 admission-webhook's rejection
    /// path folds `None` onto its per-CR structured refusal body.
    #[must_use]
    pub fn from_wire(s: &str) -> Option<Self> {
        match s {
            crate::render::DEP_AUTHOR_KEY_DEPS => Some(Self::Prod),
            crate::render::DEP_AUTHOR_KEY_DEPS_DEV => Some(Self::Dev),
            _ => None,
        }
    }
}

/// Route [`std::fmt::Display`] through [`DepList::as_str`], so every
/// consumer that formats the axis as user-facing text (a future
/// `feira app graph` per-list summary, a future M4 admission-webhook
/// rejection body naming the offending list, this crate's own
/// [`DepError`] `#[error(...)]` templates when they widen to carry a
/// typed [`DepList`]) lands on the same author-surface tag the
/// [`crate::render::DEP_AUTHOR_KEY_DEPS`] /
/// [`crate::render::DEP_AUTHOR_KEY_DEPS_DEV`] constants carry. Same
/// as-str-through-Display convergence discipline the sibling
/// [`crate::aplicacao::PlacementStrategy`],
/// [`crate::aplicacao::RateLimitUnit`],
/// [`crate::supervisor::RestartStrategy`],
/// [`crate::supervisor::RestartPolicy`], and [`crate::CaixaKind`]
/// closed-set typed enums carry.
impl std::fmt::Display for DepList {
    fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
        f.write_str(self.as_str())
    }
}

/// Errors raised by [`Dep::validate`].
///
/// Mirrors the per-axis error families the other `:versao`-carrying
/// typed surfaces expose
/// ([`crate::AplicacaoError::MembroVersaoEmpty`] /
/// [`crate::AplicacaoError::MembroVersaoInvalid`],
/// [`crate::SupervisorError::EmptyChildVersion`] /
/// [`crate::SupervisorError::ChildVersaoInvalid`]) so a future top-
/// level `CaixaError` (M4) sums these without reshaping the diagnostic.
#[derive(Debug, Error, PartialEq, Eq)]
pub enum DepError {
    #[error(
        ":deps entry has empty :nome (every dep must name a target caixa; \
         omit the entry instead of carrying an empty name)"
    )]
    NomeEmpty,
    #[error(
        ":deps entry :nome {nome:?} is not a valid DNS-1123 label: {reason} \
         (the value flows verbatim as the target caixa's `:nome`, the rendered \
         `lareira-<nome>` Helm chart name segment, the `LABEL_PROGRAM` label \
         value, and the resolver's checkout-directory leaf — each apiserver-side \
         schema rejects non-DNS-1123 names at admission time; use a lowercase \
         RFC 1123 label like `\"caixa-teia\"` or `\"pleme-mesh\"`, 1..=63 bytes, \
         pattern `^[a-z0-9]([-a-z0-9]*[a-z0-9])?$`)"
    )]
    NomeInvalid { nome: String, reason: String },
    #[error(
        ":deps entry {nome:?} has empty :versao (every dep must pin a semver \
         constraint that resolves through the lacre pipeline)"
    )]
    VersaoEmpty { nome: String },
    #[error(
        ":deps entry {nome:?} :versao {versao:?} is not a valid semver \
         requirement: {reason} (use Cargo-shaped forms like `\"^0.1\"`, \
         `\"~0.1.2\"`, `\"0.1.0\"`, or `\"*\"` — the same shape `:membros :versao` \
         and `:children :versao` carry; the lacre pipeline resolves all three \
         through the same parser)"
    )]
    VersaoInvalid {
        nome: String,
        versao: String,
        reason: String,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo git …) has empty :repo \
         (every git source must name a repo — use a `github:org/repo` \
         shorthand, an `https://…` URL, or an ssh-git URL; omit the \
         entire :fonte block to fall back to the default-host resolver \
         convention)"
    )]
    FonteRepoEmpty { nome: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo git …) :repo {repo:?} has \
         invalid value-shape: {reason} (the value flows verbatim into the \
         caixa-resolver's `git clone <repo>` subprocess invocation; every \
         documented form carries a `:` separator and no whitespace / \
         control / non-ASCII bytes — use a `github:org/repo` shorthand, \
         an `https://host/path` / `ssh://[user@]host/path` / \
         `git://host/path` / `file:///path` URL, or the `git@host:path` \
         scp-style SSH form)"
    )]
    FonteRepoShape {
        nome: String,
        repo: String,
        reason: String,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo git …) has no pin set \
         (set exactly one of :tag, :rev, or :branch so the resolver \
         can pick a reproducible commit; omit the entire :fonte block \
         to fall back to the default-host resolver convention, which \
         resolves the latest tag matching :versao)"
    )]
    FontePinMissing { nome: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo git …) has multiple pins \
         set ({pins}); exactly one of :tag, :rev, or :branch must be \
         set so the resolver's checkout target is unambiguous (the \
         resolver's silent precedence is :rev > :tag > :branch — if \
         you intended one specifically, drop the others)"
    )]
    FontePinAmbiguous { nome: String, pins: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo git …) has empty {pin} \
         (a set pin must name a non-empty git ref; drop the {pin} key \
         entirely to fall through to another pin axis)"
    )]
    FontePinEmpty { nome: String, pin: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo git …) {pin} {value:?} has invalid \
         value-shape: {reason} (the git porcelain enforces the same shape at \
         `git fetch` / `git checkout` time on every pin; use a leaf refname \
         like `\"v0.1.0\"` for `:tag` or `\"main\"` / `\"feature/foo\"` for \
         `:branch`, or a full 40/64 lowercase-hex commit OID for `:rev` — \
         drop any `refs/heads/` or `refs/tags/` prefix the caixa-resolver \
         prepends at clone time, and avoid abbreviated SHAs which are \
         ambiguous across repository history)"
    )]
    FontePinShape {
        nome: String,
        pin: String,
        value: String,
        reason: String,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) has empty :caminho \
         (every path source must name a non-empty filesystem path; \
         omit the entire :fonte block to fall back to the default-host \
         resolver convention)"
    )]
    FonteCaminhoEmpty { nome: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} is \
         absolute (the lacre pipeline embeds the value verbatim in its \
         per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189, so an absolute path makes the \
         BLAKE3 closure differ across machines — defeating the \
         reproducibility contract that's load-bearing for CSE; express \
         the path relative to the caixa.lisp location, e.g. \
         \"../caixa-teia\" for a sibling workspace dep)"
    )]
    FonteCaminhoAbsolute { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} starts \
         with `~` (the leading-tilde is a shell-expansion convention, not a \
         POSIX path component — `Path::is_absolute` returns false on it, so \
         the b94fd83 absolute-path gate doesn't catch it, but the lacre \
         pipeline embeds the value verbatim in its per-dep content-address \
         `path:{caminho}` at caixa-resolver/src/resolve.rs:189 and the \
         caixa-resolver folds it through `Path::join` without `~`-expansion, \
         so the build looks for a literal `./{caminho}` subdirectory and \
         fails at resolve time far from the source caixa.lisp; even worse, a \
         future caixa-resolver pass that *does* expand `~` would silently \
         re-open the host-layout-leak the b94fd83 absolute gate closes — \
         Alice's `~` resolves to `/home/alice`, Bob's to `/home/bob`, two CI \
         runners with different `$HOME` layouts resolve to two distinct paths \
         for the byte-identical caixa, defeating the THEORY.md §V.2 render-\
         determinism contract; express the path relative to the caixa.lisp \
         location, e.g. \"../caixa-teia\" for a sibling workspace dep, or \
         spell out the full relative path explicitly if a workstation-rooted \
         dep is genuinely intended)"
    )]
    FonteCaminhoTildeExpansion { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} starts \
         with `$` (the leading-`$` is a shell-variable-expansion convention, \
         not a POSIX path component — `Path::is_absolute` returns false on it \
         and the a5c248e tilde gate doesn't catch it, but the lacre pipeline \
         embeds the value verbatim in its per-dep content-address \
         `path:{caminho}` at caixa-resolver/src/resolve.rs:189 and the \
         caixa-resolver folds it through `Path::join` without `$`-expansion, \
         so the build looks for a literal `./{caminho}` subdirectory and \
         fails at resolve time far from the source caixa.lisp; even worse, a \
         future caixa-resolver pass that *does* expand `$VAR` (the canonical \
         shell-convention idiom that CI's `${{WORKSPACE}}` paste-idiom \
         invites) would silently re-open the host-layout-leak the b94fd83 \
         absolute gate closes — Alice's `$HOME` resolves to `/home/alice`, \
         Bob's to `/home/bob`, two CI runners with different `${{WORKSPACE}}` \
         layouts resolve to two distinct paths for the byte-identical caixa, \
         defeating the THEORY.md §V.2 render-determinism contract; express \
         the path relative to the caixa.lisp location, e.g. \"../caixa-teia\" \
         for a sibling workspace dep, or spell out the full relative path \
         explicitly if a workstation-rooted dep is genuinely intended)"
    )]
    FonteCaminhoVarExpansion { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} starts \
         with a space (the leading ASCII space `0x20` is the orthogonal \
         paste-from-aligned-doc footgun that silently passes \
         `Path::is_absolute` and every prior leading-byte arm — \
         `\" ../caixa-teia\"` resolves via `Path::join` to a literal \
         `./ ../caixa-teia` subdirectory the resolver fails to find at \
         resolve time with a non-self-locating `No such file or directory` \
         error far from the source caixa.lisp; the lacre pipeline embeds \
         the value verbatim in its per-dep content-address `path:{caminho}` \
         at caixa-resolver/src/resolve.rs:189, so byte-divergent / \
         semantic-identical caixa values (` ../caixa-teia` vs \
         `../caixa-teia`) yield two distinct BLAKE3 closures across two \
         workstations whose authors differ only in paste-from-aligned- \
         caixa.lisp-doc whitespace habits — the most insidious failure \
         mode the typed slot can carry (no error surfaces; the divergence \
         is invisible until two machines compare lacres), defeating the \
         THEORY.md §V.2 render-determinism contract. The canonical \
         paste-from-aligned-`:deps`-block footgun (every `:fonte` form in \
         a multi-entry `:deps` block sits at the same column — an author \
         selecting `\"<sp><sp><sp>../caixa-teia\"` and pasting it from \
         the rendered alignment into a fresh entry preserves the leading \
         whitespace verbatim); peer `:fonte :repo` axis already rejects \
         leading whitespace via `is_git_repo_url`, `:fonte :tag` / \
         `:fonte :branch` via `is_git_ref_name`, `:descricao` via \
         `is_chart_description_shape`, `:licenca` via \
         `is_spdx_expression_shape`. Drop the leading space; express the \
         path as a bare relative single-token like \"../caixa-teia\")"
    )]
    FonteCaminhoLeadingWhitespace { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} starts \
         with `-` (the canonical CLI-argument-injection footgun on the \
         `:caminho` axis — the lacre pipeline embeds the value verbatim in \
         its per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189 and the caixa-resolver folds it \
         through `Path::join` looking for a literal `./{caminho}` \
         subdirectory. Every downstream subprocess that consumes the resolved \
         path — `git -C {caminho} <verb>`, `terraform -chdir={caminho}`, \
         `nix build --path {caminho}`, `find {caminho}`, `stat {caminho}`, \
         `cp -r {caminho} …`, `rm -rf {caminho}` — reinterprets a leading-`-` \
         value as a CLI flag rather than a positional path when the invocation \
         does not carry a `--` argument-list terminator between the flag block \
         and the path (the common case at every porcelain entry point). The \
         canonical footguns: `:caminho \"-rf\"` (bare short-flag paste), \
         `:caminho \"-C\"` (`git -C -C` config-injection paste), \
         `:caminho \"--upload-pack=cat /etc/passwd\"` (the canonical long-flag \
         CLI-arg-injection vector at every git porcelain entry point that \
         consumes a path or URL argument, peer with is_git_repo_url's \
         leading-`-` arm on the sibling `:fonte :repo` axis), \
         `:caminho \"--config=…\"` (`git -c foo=bar` config-override paste). \
         POSIX `std::path::Path` treats a leading `-` as a literal filename \
         byte so the resolver folds `\"-rf\"` through `Path::join` and looks \
         for a literal `./-rf` subdirectory that fails at resolve time with a \
         non-self-locating `No such file or directory` error far from the \
         source caixa.lisp — but on any downstream shell-out without `--` the \
         reinterpretation is silent and the failure mode is arbitrary-\
         argument-injection. Peer arms: `is_git_repo_url` (render.rs:2037) \
         rejects leading `-` on `:fonte :repo` for `git clone <repo>` CLI-\
         arg-injection; `is_git_ref_name` (render.rs:1381, 5a28454) rejects \
         leading `-` on `:fonte :tag` / `:branch` for `git checkout <ref>` \
         CLI-arg-injection; `is_dns_1123_label` rejects leading `-` on every \
         DNS-1123-shaped axis (top-level Caixa `:nome`, `:membros :caixa`, \
         `:children :caixa`, `:deps :nome`, cluster names); \
         `is_cargo_feature_name` rejects leading `-` on `:caracteristicas`; \
         the feira `init` / `add <nome>` positional gate (868c191) rejects \
         leading `-` on the CLI positional itself. Express the path as a bare \
         relative single-token like \"../caixa-teia\" — the sibling-workspace \
         directory name carries no leading-hyphen semantic, and `./` / `../` \
         prefixes structurally partition the leading-byte set to safe values.)"
    )]
    FonteCaminhoLeadingHyphen { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains \
         ASCII control byte 0x{byte:02x} (POSIX paths reject NUL `0x00` outright — \
         every `std::fs` syscall routes the path through `CString::new` which \
         fails with `NulError` at resolve time; the lacre pipeline embeds the \
         value verbatim in its per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189 so a control byte anywhere in the \
         value lands in the BLAKE3 closure and breaks the THEORY.md §V.2 render-\
         determinism contract — the canonical paste-from-multiline-doc \
         (`\\n`/`\\r`), paste-from-aligned-table (`\\t`), or paste-from-binary-\
         blob (`0x00`-DEL) footgun every peer single-token-shaped axis \
         (`:fonte :repo`, `:fonte :tag`/`:branch`, the Helm chart-string axes) \
         already gates against. Express the path as a relative single-line ASCII \
         string, e.g. \"../caixa-teia\" for a sibling workspace dep)"
    )]
    FonteCaminhoControlChar {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains `\\` \
         (POSIX `std::path::Path` treats `\\` as a literal byte inside a single path \
         component, so `..\\caixa-teia` is one directory named literally `..\\caixa-teia` — \
         not the parent's sibling — and the caixa-resolver folds the value through \
         `Path::join` looking for a literal `./{caminho}` subdirectory that fails at \
         resolve time with a non-self-locating `No such file or directory` error far \
         from the source caixa.lisp; Windows `std::path::Path` treats `\\` as a \
         primary path separator equal to `/`, so byte-identical caixa.lisp values \
         resolve to two distinct directories across runner OSes — the lacre pipeline \
         embeds the value verbatim in its per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189, defeating the THEORY.md §V.2 render-\
         determinism contract via the cross-host-OS-separator divergence vector. The \
         canonical Windows-Explorer `Copy as path` / PowerShell `Get-Location` \
         paste-idiom footgun; peer `:fonte :tag` / `:fonte :branch` axis already \
         rejects `\\` via `is_git_ref_name` for the same Windows-path-leak reason, \
         and `:entrada :paths` rejects `\\` via `is_gateway_api_http_path`'s eleven-\
         byte RFC-3986-reserved set. Express the path with `/` as the separator, e.g. \
         \"../caixa-teia\" for a sibling workspace dep)"
    )]
    FonteCaminhoBackslash { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         redirection metacharacter 0x{byte:02x} `{ch}` (every interactive shell — bash / \
         zsh / fish / nushell — lexes `<` and `>` as input / output redirection \
         operators, so `:caminho \"../caixa-teia>build.log\"` is the canonical \
         paste-from-shell-pipeline footgun where an author copies a `command > log` \
         tail without trimming the redirect; POSIX `std::path::Path` treats both bytes \
         as literal path-component bytes, so the resolver folds the value through \
         `Path::new(caminho).join(<file>)` looking for a literal `./{caminho}` \
         subdirectory and fails at resolve time with a non-self-locating `No such \
         file or directory` error far from the source caixa.lisp. The lacre pipeline \
         embeds the value verbatim in its per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189, so the byte lands in the BLAKE3 closure \
         and rides into every shell-spawned subprocess (the resolver's `git clone`, a \
         future `feira tofu` shell-out, a future operator-side `nix` spawn) as the \
         canonical CRLF-at-subprocess-argument / shell-metachar injection surface every \
         peer single-token-shaped typed slot already closes. The peer `:fonte :tag` / \
         `:fonte :branch` axis already rejects `<` / `>` via `is_git_ref_name`, and \
         `:entrada :paths` rejects them via `is_gateway_api_http_path`'s eleven-byte \
         RFC-3986-reserved set. Express the path as a bare relative single-token like \
         \"../caixa-teia\" — the sibling-workspace directory name carries no shell-\
         redirection semantic.",
        ch = *byte as char
    )]
    FonteCaminhoShellRedirection {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-pipe \
         metacharacter `|` (every interactive shell — bash / zsh / fish / nushell — lexes \
         `|` as the pipe operator that wires one command's stdout to the next command's \
         stdin, so `:caminho \"../caixa-teia | grep foo\"` is the canonical paste-from-\
         shell-history footgun where an author copies a `ls ../caixa-teia | grep` line \
         without trimming the pipeline tail, and `:caminho \"../foo||bar\"` is the \
         symmetric `cmd-a || cmd-b` short-circuit-OR paste shape; POSIX `std::path::Path` \
         treats `|` as a literal path-component byte, so the resolver folds the value \
         through `Path::new(caminho).join(<file>)` looking for a literal `./{caminho}` \
         subdirectory and fails at resolve time with a non-self-locating `No such file or \
         directory` error far from the source caixa.lisp. The lacre pipeline embeds the \
         value verbatim in its per-dep content-address `path:{caminho}` at caixa-resolver/\
         src/resolve.rs:189, so the byte lands in the BLAKE3 closure and rides into every \
         shell-spawned subprocess (the resolver's `git clone`, a future `feira tofu` \
         shell-out, a future operator-side `nix` spawn) as the canonical CRLF-at-\
         subprocess-argument / shell-metachar injection surface every peer single-token-\
         shaped typed slot already closes. The peer `:entrada :paths` axis rejects `|` \
         via `is_gateway_api_http_path`'s eleven-byte RFC-3986-reserved set. Express the \
         path as a bare relative single-token like \"../caixa-teia\" — the sibling-\
         workspace directory name carries no shell-pipe semantic."
    )]
    FonteCaminhoShellPipe { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         command-separator metacharacter `;` (every interactive shell — bash / zsh / fish \
         / nushell — lexes `;` as the sequential-command terminator that fires the next \
         command regardless of the prior command's exit status, so `:caminho \
         \"../caixa-teia; rm -rf build\"` is the canonical paste-from-shell-one-liner \
         footgun where an author copies a `cd path; do-thing` chain without trimming \
         the cleanup tail, and `:caminho \"../foo;;bar\"` is the symmetric POSIX `case` \
         arm `;;` terminator paste shape; POSIX `std::path::Path` treats `;` as a \
         literal path-component byte, so the resolver folds the value through \
         `Path::new(caminho).join(<file>)` looking for a literal `./{caminho}` \
         subdirectory and fails at resolve time with a non-self-locating `No such file \
         or directory` error far from the source caixa.lisp. The lacre pipeline embeds \
         the value verbatim in its per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189, so the byte lands in the BLAKE3 closure and \
         rides into every shell-spawned subprocess (the resolver's `git clone`, a \
         future `feira tofu` shell-out, a future operator-side `nix` spawn) as the \
         canonical shell-metachar injection surface every peer single-token-shaped \
         typed slot already closes. The peer `:entrada :paths` axis rejects `;` via \
         `is_gateway_api_http_path`'s eleven-byte RFC-3986-reserved set. Express the \
         path as a bare relative single-token like \"../caixa-teia\" — the sibling-\
         workspace directory name carries no shell-command-separator semantic."
    )]
    FonteCaminhoShellSemicolon { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         background / list-AND metacharacter `&` (every interactive shell — bash / zsh \
         / fish / nushell — lexes `&` two ways: single `&` as the background-task \
         terminator detaching the prior command and returning control immediately to \
         the prompt, double `&&` as the logical-AND list operator firing the next \
         command only if the prior succeeded; POSIX `std::path::Path` treats it as a \
         literal byte. The canonical paste-from-shell-prompt footgun is a `cd path & \
         sleep 1` background-launch one-liner or a `cd path && make install` build-\
         chain idiom selected whole into the `:caminho` slot — the prior `;` arm at \
         05c358e closed the sequential-command-separator vector, this arm closes the \
         orthogonal background-task / logical-AND vector on the same paste-from-shell-\
         prompt class. The lacre pipeline embeds the value verbatim in its per-dep \
         content-address `path:{caminho}` at caixa-resolver/src/resolve.rs:189, so the \
         byte lands in the BLAKE3 closure and rides into every shell-spawned \
         subprocess (the resolver's `git clone`, a future `feira tofu` shell-out, a \
         future operator-side `nix` spawn) as the canonical shell-metachar injection \
         surface every peer single-token-shaped typed slot already closes. The peer \
         `:entrada :paths` axis rejects `&` via `is_gateway_api_http_path`'s eleven-\
         byte RFC-3986-reserved set. Express the path as a bare relative single-token \
         like \"../caixa-teia\" — the sibling-workspace directory name carries no \
         shell-background / logical-AND semantic."
    )]
    FonteCaminhoShellBackground { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         command-substitution metacharacter `` ` `` (every POSIX shell — sh / bash / zsh / \
         dash / ksh / fish / nushell — lexes the byte as the legacy command-substitution \
         wrapper that runs the enclosed command and substitutes its standard-output \
         verbatim into the surrounding word, so a backticked `whoami` expands to the \
         current user's name and a backticked `cat /etc/passwd` expands to the file's \
         contents — the canonical CWE-78 shell-command-injection vector; POSIX \
         `std::path::Path` treats the byte as a literal path-component byte. The canonical \
         paste-from-shell-prompt footgun is a `cd ../path/<backtick>whoami<backtick>` legacy substitution \
         one-liner or a `cd <backtick>pwd<backtick>/path` working-directory expansion idiom selected whole \
         into the `:caminho` slot — the prior `&` arm at e12e4f3 closed the shell-\
         background / logical-AND vector, this arm closes the orthogonal command-\
         substitution vector on the same paste-from-shell-prompt class (the modern `$()` \
         form is gated at leading position by the f4efe9c `FonteCaminhoVarExpansion` arm; \
         the legacy backtick form is the orthogonal axis). The lacre pipeline embeds the \
         value verbatim in its per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189, so the byte lands in the BLAKE3 closure and \
         rides into every shell-spawned subprocess (the resolver's `git clone`, a future \
         `feira tofu` shell-out, a future operator-side `nix` spawn) as the canonical \
         shell-metachar injection surface every peer single-token-shaped typed slot \
         already closes. The peer `:entrada :paths` axis rejects the byte via \
         `is_gateway_api_http_path`'s eleven-byte RFC-3986-reserved set. Express the path \
         as a bare relative single-token like \"../caixa-teia\" — the sibling-workspace \
         directory name carries no shell-command-substitution semantic."
    )]
    FonteCaminhoShellCommandSubstitution { nome: String, caminho: String },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         glob / pathname-expansion metacharacter 0x{byte:02x} `{ch}` (every POSIX shell — \
         sh / bash / zsh / dash / ksh / fish / nushell — lexes `*` and `?` as pathname-\
         expansion wildcards: `*` matches any sequence of characters in a path component \
         and `?` matches exactly one character, so a `:caminho \"../caixa-teia/*\"` is the \
         canonical paste-from-shell-listing footgun where an author copies a \
         `ls ../caixa-teia/*` listing without trimming the wildcard, and `:caminho \
         \"../foo?\"` is the symmetric single-char-wildcard paste shape; POSIX \
         `std::path::Path` treats both bytes as literal path-component bytes, so the \
         resolver folds the value through `Path::new(caminho).join(<file>)` looking for \
         a literal `./{caminho}` subdirectory and fails at resolve time with a non-self-\
         locating `No such file or directory` error far from the source caixa.lisp. The \
         lacre pipeline embeds the value verbatim in its per-dep content-address \
         `path:{caminho}` at caixa-resolver/src/resolve.rs:189, so the byte lands in the \
         BLAKE3 closure and rides into every shell-spawned subprocess (the resolver's \
         `git clone`, a future `feira tofu` shell-out, a future operator-side `nix` \
         spawn) as the canonical shell-metachar / glob-expansion surface every peer \
         single-token-shaped typed slot already closes. The peer `:entrada :paths` axis \
         rejects `*` and `?` via `is_gateway_api_http_path`'s eleven-byte RFC-3986-\
         reserved set. Express the path as a bare relative single-token like \
         \"../caixa-teia\" — the sibling-workspace directory name carries no shell-glob \
         / pathname-expansion semantic.",
        ch = *byte as char
    )]
    FonteCaminhoShellGlob {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         subshell-grouping metacharacter 0x{byte:02x} `{ch}` (every POSIX shell — sh / bash / \
         zsh / dash / ksh / fish / nushell — lexes `(` and `)` as the subshell-grouping \
         operator: `(<cmd>)` runs `<cmd>` in a child shell with a fresh environment scope \
         (the canonical `(cd <path> && <cmd>)` shell-history one-liner scopes a `cd` to one \
         subshell without disturbing the parent's working directory), and `$(<cmd>)` is the \
         modern Bourne command-substitution shape the leading-`$` `FonteCaminhoVarExpansion` \
         arm closes the leading byte of — together the two arms now structurally exclude the \
         entire `$(<cmd>)` substitution surface from the typed `:caminho` accepted set. \
         POSIX `std::path::Path` treats the byte as a literal path-component byte, so a \
         `:caminho \"../caixa-teia/$(date)/build\"` (the canonical paste-from-shell-history \
         modern-command-substitution footgun) or `:caminho \"../(cd foo && pwd)/caixa-teia\"` \
         (the symmetric subshell-grouping working-directory-probe paste idiom) silently passes \
         every prior arm and the resolver folds the value through `Path::new(caminho).join(\
         <file>)` looking for a literal subdirectory and fails at resolve time with a non-\
         self-locating `No such file or directory` error far from the source caixa.lisp. The \
         lacre pipeline embeds the value verbatim in its per-dep content-address `path:\
         {caminho}` at caixa-resolver/src/resolve.rs:189, so the byte lands in the BLAKE3 \
         closure and rides into every shell-spawned subprocess (the resolver's `git clone`, a \
         future `feira tofu` shell-out, a future operator-side `nix` spawn) as the canonical \
         shell-metachar / subshell-grouping surface every peer single-token-shaped typed slot \
         already closes. The peer `:fonte :repo` axis (3b99147) closes the same byte under the \
         same shell-subshell-grouping / RFC-3986-sub-delims banner on `is_git_repo_url`, \
         together with the leading-`$` `FonteCaminhoVarExpansion` arm closing the leading byte \
         of every `$(<cmd>)` shape. Express the path as a bare relative single-token \
         like \"../caixa-teia\" — the sibling-workspace directory name carries no shell-\
         subshell-grouping semantic.",
        ch = *byte as char
    )]
    FonteCaminhoShellSubshellGrouping {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         brace-expansion / URI-Template placeholder metacharacter 0x{byte:02x} `{ch}` \
         (every POSIX-derived brace-expanding shell — bash / zsh / ksh / fish — lexes `{{` / \
         `}}` as the brace-expansion operator: `{{a,b,c}}` expands to the cross-product of \
         comma-separated members and `{{1..10}}` expands to the integer range — the \
         canonical `mkdir -p ../{{caixa-teia,caixa-helm,caixa-flux}}` / `cp file{{,.bak}}` \
         idiom every shell-history block carries; RFC 6570 reserves the matched pair for \
         URI Template placeholders (the canonical `https://{{host}}/{{org}}/{{repo}}` \
         substitution shape every OpenAPI / Swagger / Postman / GitHub Octokit client \
         library / Helm chart-URL fragment carries) and the Mustache / Handlebars / \
         Tera / Jinja2 / Go html/template doubled-brace substitution form every IaC \
         templating engine (Helm, Kustomize, Terraform's `${{var}}` cousin) emits. POSIX \
         `std::path::Path` treats the byte as a literal path-component byte, so a \
         `:caminho \"../{{caixa-teia,caixa-helm}}/build\"` (the canonical paste-from-\
         shell-history brace-expansion fan-across-siblings footgun) or `:caminho \"../{{{{org}}}}/\
         caixa-teia\"` (the symmetric paste-from-templated-doc URI-Template placeholder \
         idiom every README quick-start / OpenAPI spec / Helm chart `home:` field carries) \
         silently passes every prior arm and the resolver folds the value through \
         `Path::new(caminho).join(<file>)` looking for a literal subdirectory and fails at \
         resolve time with a non-self-locating `No such file or directory` error far from \
         the source caixa.lisp. The lacre pipeline embeds the value verbatim in its \
         per-dep content-address `path:{caminho}` at caixa-resolver/src/resolve.rs:189, \
         so the byte lands in the BLAKE3 closure and rides into every shell-spawned \
         subprocess (the resolver's `git clone`, a future `feira tofu` shell-out, a \
         future operator-side `nix` spawn) as the canonical shell-metachar / brace-\
         expansion / URI-Template-placeholder surface every peer single-token-shaped \
         typed slot already closes. The peer `:fonte :repo` axis (42d8f9d) closes the \
         same byte pair on `is_git_repo_url` under the same RFC-3986-'delims' / \
         RFC-6570-URI-Template / shell-brace-expansion banner. Express the path as a \
         bare relative single-token like \"../caixa-teia\" — the sibling-workspace \
         directory name carries no shell-brace-expansion / URI-Template-placeholder \
         semantic; if two siblings actually need pinning, author two separate `:deps` \
         entries rather than one brace-expanded `:caminho` value.",
        ch = *byte as char
    )]
    FonteCaminhoShellBraceExpansion {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         bracket-expansion / POSIX glob-character-class / shell-`test`-builtin metacharacter \
         0x{byte:02x} `{ch}` (every POSIX shell — sh / bash / zsh / dash / ksh / fish / nushell \
         — lexes the bracket pair as the glob character-class operator: `[abc]` matches one of \
         `a` / `b` / `c`, `[a-z]` matches any lowercase ASCII letter, `[^x]` negates — the \
         canonical `ls *.[ch]` C-source-file glob and `cd ../caixa-[a-z]*` lowercase-sibling \
         glob every shell-history block carries; the bracket pair additionally carries the \
         POSIX `test` / `[` builtin command (`[ -d ../caixa-teia ] && cd ...` every shell-\
         script conditional uses) and bash's `[[ ... ]]` extended-test grammar; beyond shell \
         the pair is the TOML inline-array delimiter (`features = [\"a\", \"b\"]` — the \
         canonical paste-from-Cargo-manifest cross-idiom-leak vector), the YAML flow-sequence \
         delimiter (`paths: [/a, /b]` — the canonical paste-from-values.yaml cross-idiom \
         leak), the JSON array delimiter, and the POSIX-ERE / PCRE bracket-expression anchor. \
         POSIX `std::path::Path` treats the byte as a literal path-component byte, so a \
         `:caminho \"../caixa-[a-z]/build\"` (the canonical paste-from-shell-history glob-\
         character-class fan-across-siblings footgun) or `:caminho \"../[caixa-teia]/build\"` \
         (the symmetric paste-from-TOML-array / paste-from-YAML-flow-sequence cross-idiom \
         leak) silently passes every prior arm and the resolver folds the value through \
         `Path::new(caminho).join(<file>)` looking for a literal subdirectory and fails at \
         resolve time with a non-self-locating `No such file or directory` error far from \
         the source caixa.lisp. The lacre pipeline embeds the value verbatim in its per-dep \
         content-address `path:{caminho}` at caixa-resolver/src/resolve.rs:189, so the byte \
         lands in the BLAKE3 closure and rides into every shell-spawned subprocess (the \
         resolver's `git clone`, a future `feira tofu` shell-out, a future operator-side \
         `nix` spawn) as the canonical shell-metachar / glob-character-class / TOML-array \
         surface every peer single-token-shaped typed slot already closes. Express the path \
         as a bare relative single-token like \"../caixa-teia\" — the sibling-workspace \
         directory name carries no shell-bracket-expansion / glob-character-class / array-\
         literal semantic; if a family of sibling caixas actually needs pinning, author \
         separate `:deps` entries rather than one character-class-expanded `:caminho` value.",
        ch = *byte as char
    )]
    FonteCaminhoShellBracketExpansion {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         quote-grouping / cross-config-DSL string-literal-delimiter metacharacter \
         0x{byte:02x} `{ch}` (every POSIX shell — sh / bash / zsh / dash / ksh / fish / \
         nushell — lexes `'` as the strong string-literal delimiter (`'…'` — no expansion) \
         and `\"` as the weak string-literal delimiter (`\"…\"` — variable- / command-\
         substitution-preserving); the canonical `cd '../caixa-teia'` shell-history idiom \
         every path-with-embedded-whitespace paste block carries and the symmetric \
         `git clone \"$REPO\"` weak-quoted CI-manifest shape both leak the pair verbatim. \
         Beyond shell the pair is the JSON string-literal delimiter (`\"key\": \"value\"` — \
         the canonical paste-from-JSON-config cross-idiom-leak vector), the YAML double- \
         and single-quoted flow-scalar delimiter (`path: \"../caixa-teia\"` — the canonical \
         paste-from-values.yaml / paste-from-K8s-YAML-manifest cross-idiom leak), the TOML \
         basic and literal string delimiter (`path = \"../caixa-teia\"` — the canonical \
         paste-from-Cargo-manifest cross-idiom leak), the tatara-lisp string-literal \
         delimiter itself (`(:caminho \"../caixa-teia\")` — the canonical \"I copied the \
         entire `:caminho \"...\"` slot rather than just the string body\" author-surface \
         footgun), and RFC 3986 §2.2's `gen-delims` / `sub-delims` grammar which excludes \
         both bytes from the `pchar = unreserved / pct-encoded / sub-delims / \":\" / \"@\"` \
         production. POSIX `std::path::Path` treats the byte as a literal path-component \
         byte, so a `:caminho \"'../caixa-teia'\"` (the canonical paste-from-shell-history \
         strong-quoted sibling-workspace path footgun) or `:caminho \"\\\"../caixa-teia\\\"\"` \
         (the symmetric weak-quoted paste-from-JSON / paste-from-YAML flow-scalar / paste-\
         from-TOML basic-string / paste-from-tatara-lisp string-literal cross-idiom-leak \
         shape) silently passes every prior arm and the resolver folds the value through \
         `Path::new(caminho).join(<file>)` looking for a literal subdirectory and fails at \
         resolve time with a non-self-locating `No such file or directory` error far from \
         the source caixa.lisp. The lacre pipeline embeds the value verbatim in its per-dep \
         content-address `path:{caminho}` at caixa-resolver/src/resolve.rs:189, so the byte \
         lands in the BLAKE3 closure and rides into every shell-spawned subprocess (the \
         resolver's `git clone`, a future `feira tofu` shell-out, a future operator-side \
         `nix` spawn) as the canonical shell-metachar / string-literal-delimiter surface \
         every peer single-token-shaped typed slot already closes. The peer `:fonte :repo` \
         axis closes both bytes under the same shell-quote-grouping / RFC-3986-sub-delims \
         banner (e7a109f `'` shell-single-quote + 4267d8b `\"` shell-double-quote on \
         `is_git_repo_url`). Express the path as a bare relative single-token like \
         \"../caixa-teia\" — the sibling-workspace directory name carries no shell-quote-\
         grouping / string-literal-delimiter semantic; strip the outer quote pair from the \
         paste (the tatara-lisp `:caminho \"...\"` slot already carries the string-literal \
         quoting on the outer syntactic layer, so an inner quote pair would nest and \
         desugar to a broken layer).",
        ch = *byte as char
    )]
    FonteCaminhoShellQuoteGrouping {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         comment / URL-fragment-identifier / YAML-comment cross-config-DSL metacharacter \
         0x{byte:02x} `{ch}` (every POSIX shell — sh / bash / zsh / dash / ksh / fish / \
         nushell — lexes an unquoted `#` at the head of a word or after unquoted \
         whitespace as the comment-lead per POSIX.1-2017 §2.3 Token Recognition step 6, \
         discarding the byte and everything after it to the end of the physical line \
         before command parsing (`cd ../caixa-teia  # legacy sibling` — the canonical \
         paste-from-shell-history-with-trailing-annotation shape every operator-notebook \
         and CI-manifest carries); YAML 1.2 §6.6 makes `#` the comment-lead at any \
         position preceded by whitespace or at line-start (`path: ../caixa-teia  # pin` \
         — the canonical paste-from-values.yaml / paste-from-K8s-manifest cross-idiom-\
         leak); RFC 3986 §3.5 reserves `#` as the URL fragment-identifier delimiter (the \
         canonical paste-from-browser-address-bar `github.com/foo/bar#readme` / \
         `github.com/foo/bar#L42` permalink shape, and the symmetric Nix-flake-ref \
         cross-idiom leak `github:foo/bar#packageName` where `#` selects a flake \
         output); the same cross-config-DSL surface extends to HCL / Terraform / Nix \
         flake attributes / dotenv `.env` / gitconfig / .gitignore / ini / TOML where \
         `#` is likewise the comment-lead. POSIX `std::path::Path` treats the byte as a \
         literal path-component byte, so a `:caminho \"../caixa-teia # legacy sibling\"` \
         (the canonical paste-from-shell-history-with-trailing-annotation footgun), \
         `:caminho \"../caixa-teia  # pin\"` (the symmetric YAML flow-scalar paste-with-\
         trailing-comment shape), or `:caminho \"../caixa-teia#readme\"` (the URL \
         fragment paste-from-browser-address-bar shape) silently passes every prior arm \
         and the resolver folds the value through `Path::new(caminho).join(<file>)` \
         looking for a literal subdirectory named `../caixa-teia # legacy sibling` and \
         fails at resolve time with a non-self-locating `No such file or directory` \
         error far from the source caixa.lisp — while every downstream shell / YAML / \
         URL parser silently truncates the value at the `#` byte to `../caixa-teia`, so \
         a `feira tofu` shell-out and a `nix flake check` on an emitted YAML `path:` \
         scalar disagree with the resolver on which directory the value names. The \
         lacre pipeline embeds the value verbatim in its per-dep content-address \
         `path:{caminho}` at caixa-resolver/src/resolve.rs:189, so the byte lands in \
         the BLAKE3 closure and rides into every shell-spawned subprocess (the \
         resolver's `git clone`, a future `feira tofu` shell-out, a future operator-\
         side `nix` spawn) as the canonical shell-metachar / comment-lead / URL-\
         fragment-delimiter surface every peer single-token-shaped typed slot already \
         closes. The peer `:fonte :repo` axis closes the byte under the same URL-\
         fragment-identifier banner (a68f818 `#` on `is_git_repo_url`). Express the \
         path as a bare relative single-token like \"../caixa-teia\" — the sibling-\
         workspace directory name carries no shell-comment / URL-fragment / YAML-\
         comment semantic; move any trailing annotation to a tatara-lisp `;`-comment \
         on the surrounding form (`;; legacy sibling` above the `(:caminho ...)` slot) \
         and drop any `#fragment` tail entirely (fragment identifiers select \
         renderings, not directories, and `:caminho` names a directory).",
        ch = *byte as char
    )]
    FonteCaminhoShellComment {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains URL-\
         percent-encoding-escape / printf-format-specifier / bash-job-control-specifier \
         / YAML-directive-lead metacharacter 0x{byte:02x} `{ch}` (RFC 3986 §2.1 reserves \
         `%` as the URL percent-encoding-escape — `%HH` is the mandatory encoding \
         mechanism for every byte outside the `unreserved` alphanumeric / `-` / `.` / \
         `_` / `~` set, and `%` itself must be percent-encoded as `%25` to appear \
         literally inside a URL value. The canonical paste-from-browser-address-bar \
         percent-encoded-space footgun (an author copies `../caixa%20teia` out of a URL-\
         encoded README hyperlink / browser address bar / percent-encoded permalink \
         expecting `%20` to decode to a literal space at the filesystem layer) locks two \
         distinct BLAKE3 closures (`path:../caixa%20teia` vs `path:../caixa teia`) for \
         what the author intended as the byte-identical sibling-workspace dep. POSIX \
         `std::path::Path` treats the byte as a literal path-component byte, so \
         `Path::join` looks for a literal `./{caminho}` subdirectory and fails at \
         resolve time with a non-self-locating `No such file or directory` error far \
         from the source caixa.lisp — while every downstream URL parser / shell printf \
         builtin / YAML directive parser silently reinterprets the byte to a different \
         value than the resolver's `Path::join` sees. Beyond the URL-encoding hazard, \
         `%` is the C / POSIX printf format-directive lead-in (`%s`, `%d`, `%02x` — \
         wired into every POSIX shell's `printf` builtin, the canonical CWE-134 format-\
         string-injection vector); the bash / zsh / ksh job-control-specifier lead-in \
         (`%1` names \"job 1\", `%%` names \"the current job\", `%foo` names \"the most \
         recent job whose command started with `foo`\" — a future `kill %1` invocation \
         silently redirects the signal to a wrong target); the YAML 1.2 §6.8.1 \
         directive lead-in (`%YAML 1.2` / `%TAG` — the paste-from-top-of-doc YAML \
         directive block cross-idiom leak); and the Windows-shell env-var-reference \
         lead-in (`%PATH%` — the paste-from-`.bat` / paste-from-PowerShell-`%env:PATH%` \
         cross-idiom leak). The lacre pipeline embeds the value verbatim in its per-dep \
         content-address `path:{caminho}` at caixa-resolver/src/resolve.rs:189, so the \
         byte lands in the BLAKE3 closure and rides into every shell-spawned subprocess \
         (the resolver's `git clone`, a future `feira tofu` shell-out, a future \
         operator-side `nix` spawn) as the canonical URL-percent-encoding-escape / \
         printf-format-specifier / job-control-specifier surface every peer single-\
         token-shaped typed slot already closes. The peer `:fonte :repo` axis closes \
         the byte under the same URL-percent-encoding-escape banner (a323db8 `%` on \
         `is_git_repo_url`). Express the path as a bare relative single-token like \
         \"../caixa-teia\" — the sibling-workspace directory name carries no URL-\
         percent-encoding-escape / format-specifier / job-control semantic; substitute \
         any `%20` percent-encoded-space with a literal space then reject the whole \
         value at the leading-whitespace / embedded-`?` arm on the same axis (a caixa \
         directory name never carries an embedded space in practice); drop any \
         `%2F`-encoded path separator in favor of a literal `/`; and drop any leading \
         `%YAML` / `%PATH%` cross-idiom-leak prefix entirely.",
        ch = *byte as char
    )]
    FonteCaminhoUrlPercentEncoding {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         variable-expansion / command-substitution / arithmetic-expansion / cross-config-\
         DSL-interpolation metacharacter 0x{byte:02x} `{ch}` (every POSIX shell — sh / \
         bash / zsh / dash / ksh / busybox ash / fish / nushell — lexes `$` per \
         POSIX.1-2017 §2.6 as the variable-expansion `$<name>` / braced-form `${{<name>}}` \
         / command-substitution `$(<cmd>)` / arithmetic-expansion `$((<expr>))` operator; \
         Nix uses `${{var}}` as the string-interpolation lead, Make uses `$(var)` / `$@` \
         / `$<` for variables and automatic-variables, JavaScript / TypeScript template \
         literals use `${{expr}}` for interpolation, envsubst / Kubernetes / OpenShift \
         templates use `${{VAR}}` for env-var-reference, PHP uses `$_GET` / `$_ENV` for \
         superglobals, Perl uses `$foo` for scalars, SASS / SCSS uses `$primary-color` \
         for variables, and PostgreSQL / SQLite use `$1` / `$2` for bind parameters — \
         the byte is a first-class parser byte in nearly every config / templating / \
         build-system DSL the substrate's paste-idiom surface routinely crosses. POSIX \
         `std::path::Path` treats the byte as a literal path-component byte, so the \
         canonical paste-from-shell-one-liner `:caminho \"../foo$HOME/bar\"` / paste-\
         from-CI-manifest `:caminho \"../foo${{WORKSPACE}}/bar\"` / paste-from-shell-\
         prompt `:caminho \"../foo$(whoami)/bar\"` footguns silently pass every prior \
         cascade arm (`$` isn't `\\` / `<` / `>` / `|` / `;` / `&` / backtick / `*` / \
         `?` / `(` / `)` / `{{` / `}}` / `[` / `]` / `'` / `\"` / `#` / `%`) and route \
         through `Path::new(caminho).join(<file>)` looking for a literal `./{caminho}` \
         subdirectory that fails at resolve time with a non-self-locating `No such file \
         or directory` error far from the source caixa.lisp. The lacre pipeline embeds \
         the value verbatim in its per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189, so byte-identical caixa.lisp values differing \
         only in whether the author substituted `$HOME` / `${{WORKSPACE}}` at author \
         time lock to two distinct BLAKE3 closures across two workstations whose \
         downstream envsubst / Nix / Make / K8s-template layers differ in `$VAR` \
         recognition — defeating the THEORY.md §V.2 render-determinism contract on the \
         same axis every prior `:caminho` arm protects. Beyond the determinism vector, \
         `$` at any position in a value flowing verbatim into a shell-spawned subprocess \
         is the canonical CWE-78 shell-command-injection surface every peer single-\
         token-shaped typed slot already closes: peer `:fonte :repo` axis rejects `$` \
         under the shell-variable-expansion / URL-sub-delim banner via `is_git_repo_url` \
         (b9d187c), peer `:fonte :tag` / `:fonte :branch` axes reject `$` as part of \
         `is_git_ref_name`'s printable-ASCII-restricted grammar (`git check-ref-format` \
         rejects the byte outright), and peer `:entrada :paths` axis rejects `$` via \
         `is_gateway_api_http_path`'s eleven-byte RFC-3986-reserved set. The leading-`$` \
         position on the same axis routes through `FonteCaminhoVarExpansion` at the \
         f4efe9c leading-byte arm; this arm closes the last positional gap on the byte \
         so every position — leading and embedded — is structurally rejected. Substitute \
         the `$VAR` / `${{VAR}}` / `$(cmd)` template with the literal value at author \
         time, or express the path as a bare relative single-token like \
         \"../caixa-teia\" — the sibling-workspace directory name carries no shell-\
         variable-expansion / command-substitution / arithmetic-expansion semantic.",
        ch = *byte as char
    )]
    FonteCaminhoShellVariableExpansion {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         history-expansion / RFC-3986-sub-delims / bang-operator metacharacter 0x{byte:02x} \
         `{ch}` (every interactive POSIX shell with history enabled — bash / ksh / zsh's \
         `bashcompat` / csh / tcsh — lexes `!` as the history-expansion prefix per bash \
         reference §9.3: `!command` re-runs the most recent history entry beginning with \
         `command`, `!!` re-runs the prior command verbatim, `!$` substitutes the last \
         word of the prior command, `!:N` substitutes the Nth word of the prior command, \
         and the substitution fires at every history-expansion-enabled shell context — \
         `set -o histexpand` is bash's default for interactive sessions and the layer \
         every `feira tofu` / `git clone` / `nix flake check` subprocess-argument \
         invocation crosses when spawned under `bash -i`. Beyond shell history, RFC 3986 \
         §2.2 lists `!` in the `sub-delims` set (the URL grammar admits the byte inside \
         a path segment, but every WHATWG-conformant special-scheme URL parser percent-\
         encodes it inside a query component via the 'special-query percent-encode set' \
         the peer `is_git_repo_url` `*` / `(` / `)` / `'` arms close on); the byte is \
         also the C / C++ / Rust / JavaScript / Python bang-operator (logical-negation \
         prefix — the paste-from-source-code idiom where an author copies \
         `!path.exists()` out of a Rust snippet and the trailing punctuation crosses \
         the string-literal boundary); the canonical English-typography emphasis / \
         exclamation mark (the paste-from-prose enthusiasm-form idiom where an author \
         writes `:caminho \"../caixa-teia!\"` expecting the substrate to coerce it to a \
         kebab-case slug); and the Nix flake-ref attribute-selection operator surface. \
         POSIX `std::path::Path` treats `!` as a literal path-component byte, so the \
         canonical paste-from-shell-history footgun `:caminho \"../caixa-teia!sudo\"` \
         (an author copies a `cd ../caixa-teia && !sudo make install` one-liner from a \
         quick-start README and the trailing `!sudo` rides in verbatim as a history-\
         expansion reference), the symmetric `:caminho \"../foo!!/bar\"` (the `!!` \
         repeat-prior-command paste idiom), the English-typography `:caminho \
         \"../caixa-teia!\"` (paste-from-prose enthusiasm-form), and the last-word-\
         substitution `:caminho \"../foo!$\"` shape silently pass every prior cascade \
         arm (`!` isn't `\\` / `<` / `>` / `|` / `;` / `&` / backtick / `*` / `?` / `(` \
         / `)` / `{{` / `}}` / `[` / `]` / `'` / `\"` / `#` / `%` / `$`) and route \
         through `Path::new(caminho).join(<file>)` looking for a literal `./{caminho}` \
         subdirectory that fails at resolve time with a non-self-locating `No such file \
         or directory` error far from the source caixa.lisp. The lacre pipeline embeds \
         the value verbatim in its per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189, so the byte lands in the BLAKE3 closure and \
         rides into every shell-spawned subprocess (the resolver's `git clone`, a \
         future `feira tofu` shell-out, a future operator-side `nix flake check` spawn) \
         as the canonical shell-history-expansion / RFC-3986-sub-delims surface every \
         peer single-token-shaped typed slot already closes. The peer `:fonte :repo` \
         axis closes the byte under the same shell-history-expansion / RFC-3986-sub-\
         delims banner (7d53c68 `!` on `is_git_repo_url`). Express the path as a bare \
         relative single-token like \"../caixa-teia\" — the sibling-workspace directory \
         name carries no shell-history-expansion / bang-operator semantic; drop any \
         `!sudo` / `!!` / `!$` history-expansion trailing paste-from-shell-history \
         idiom; and drop any trailing English-typography exclamation mark that pasted \
         from prose.",
        ch = *byte as char
    )]
    FonteCaminhoShellHistoryExpansion {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} contains shell-\
         history-substitution / RFC-3986-'unwise' / regex-negation metacharacter 0x{byte:02x} \
         `{ch}` (POSIX bash's `set -o histexpand` mode — the default for every interactive \
         session and every `bash -i` subprocess-argument context `feira tofu` / `git clone` / \
         `nix flake check` cross — lexes `^old^new^` per bash reference §9.3 as the 'quick \
         substitution' history operator that rewrites the prior command's `old` string to \
         `new` and re-executes it verbatim, the canonical typo-correction one-liner idiom \
         (`git clone <bad-url>` → `^bad^good` typo-fix-and-rerun the paste-from-shell-\
         history author trims only the leading `git clone` prefix from). RFC 3986 §2 lists \
         `^` in the 'unwise' set every URL parser is required to percent-encode-or-refuse at \
         the wire boundary, and the WHATWG URL spec's 'fragment percent-encode set' maps \
         `^` → `%5E` at the query / fragment component transition, so `Path::join` on the \
         literal value diverges from every downstream `feira tofu` curl-invocation / \
         artifact-registry-fetch that percent-encodes the byte before the wire. `^` is also \
         the regex character-class negation prefix (`[^abc]`), the bitwise XOR operator in \
         C / C++ / Rust / Python / JavaScript / Nix / Go, the Windows `cmd.exe` escape \
         metacharacter, and the LaTeX / Markdown / BibTeX superscript operator. POSIX \
         `std::path::Path` treats `^` as a literal path-component byte, so \
         `:caminho \"../foo^bar/baz\"` (embedded quick-substitution), `:caminho \
         \"../foo^\"` (trailing history-substitution-open shape), or `:caminho \"../x^y\"` \
         (XOR-expression paste-from-source) silently pass every prior cascade arm (`^` \
         isn't `\\` / `<` / `>` / `|` / `;` / `&` / backtick / `*` / `?` / `(` / `)` / `{{` \
         / `}}` / `[` / `]` / `'` / `\"` / `#` / `%` / `$` / `!`) and route through \
         `Path::new(caminho).join(<file>)` looking for a literal `./{caminho}` subdirectory \
         that fails at resolve time with a non-self-locating `No such file or directory` \
         error far from the source caixa.lisp. The lacre pipeline embeds the value verbatim \
         in its per-dep content-address `path:{caminho}` at caixa-resolver/src/resolve.rs:189, \
         so the byte lands in the BLAKE3 closure and rides into every shell-spawned \
         subprocess (the resolver's `git clone`, a future `feira tofu` shell-out, a future \
         operator-side `nix flake check` spawn) as the canonical shell-history-substitution \
         / RFC-3986-unwise surface every peer single-token-shaped typed slot already closes. \
         The peer `:fonte :repo` axis closes the byte under the same shell-history-\
         substitution / RFC-3986-unwise banner (49e142f `^` on `is_git_repo_url`). Together \
         with the immediate-predecessor `!` arm (6a04767) this arm closes the full `set -o \
         histexpand` operator surface on the `:caminho` axis — the `!command` / `!!` / `!$` \
         prefix form via `!`, the `^old^new^` quick-substitution form via `^`. Express the \
         path as a bare relative single-token like \"../caixa-teia\" — the sibling-workspace \
         directory name carries no shell-history-substitution / regex-negation / XOR-operator \
         semantic; drop any `^old^new` history-substitution paste-from-shell-history idiom; \
         drop any trailing `^` history-substitution-open fragment.",
        ch = *byte as char
    )]
    FonteCaminhoShellHistorySubstitution {
        nome: String,
        caminho: String,
        byte: u8,
    },
    #[error(
        ":deps entry {nome:?} :fonte (:tipo path …) :caminho {caminho:?} has a trailing \
         `/` (the resolver's `Path::join` resolves `\"../caixa-teia\"` and \
         `\"../caixa-teia/\"` to the same directory, but the lacre pipeline embeds the \
         value verbatim in its per-dep content-address `path:{caminho}` at \
         caixa-resolver/src/resolve.rs:189, so two authors whose only difference is \
         shell tab-completion emit byte-divergent BLAKE3 closures for the same caixa — \
         defeating the THEORY.md §V.2 render-determinism contract via the trailing-\
         separator vector (the canonical paste-from-shell-tab-completion + paste-from-\
         `pwd`-with-`/`-suffix footgun, and the canonical Cargo-style `path = \
         \"../caixa-teia/\"` paste-from-Cargo-manifest cross-idiom leak). Drop the \
         trailing `/`; every `:caminho` value names a sibling-workspace directory \
         already, so the trailing separator carries no information. Use \
         `\"../caixa-teia\"` rather than `\"../caixa-teia/\"`)"
    )]
    FonteCaminhoTrailingSlash { nome: String, caminho: String },
    #[error(
        "{list} carries duplicate entry :nome {nome:?} — every dep list keys its \
         entries by caixa name (Cargo's [dependencies] / [dev-dependencies] tables \
         apply the same set-not-multiset discipline; one package per table), and \
         two entries naming the same caixa carry two version constraints / source \
         pins / feature sets for one identity. The caixa-resolver's lacre pipeline \
         consumes the list as a `HashMap`-keyed-by-`:nome` lookup: the second entry \
         silently overwrites the first at the resolver-side `concrete_versao` step, \
         and the dropped entry's pin / features never reach the closure — far from \
         the source caixa.lisp, with no field naming which `:deps` entry was the \
         silent loser. If two version constraints are genuinely needed (the rare \
         multi-version closure case the lacre pipeline doesn't yet support), the \
         author surface is two distinct caixa names (e.g. a `caixa-teia-v01` / \
         `caixa-teia-v02` aliased pair); within one list, one entry per caixa name."
    )]
    DuplicateNome { nome: String, list: &'static str },
    #[error(
        ":deps entry {nome:?} has empty :caracteristicas entry — every feature flag must \
         name a non-empty identifier on the target caixa (Cargo's [dependencies.<dep>.features] \
         applies the same per-entry non-empty discipline). An empty feature flag reaches the \
         caixa-resolver's lacre pipeline as a no-op feature enable, silently dropping the \
         author's intent far from the source caixa.lisp; drop the empty entry, or replace it \
         with the canonical kebab-case feature name the target caixa declares."
    )]
    CaracteristicaEmpty { nome: String },
    #[error(
        ":deps entry {nome:?} :caracteristicas entry {caracteristica:?} is not a valid Cargo \
         feature name: {reason} (the value flows verbatim into Cargo's \
         [dependencies.<dep>.features] list and Cargo's `restricted_names::validate_feature_name` \
         parser enforces the same shape at `cargo metadata` time; use a single-token \
         identifier like `\"http\"`, `\"derive\"`, or `\"runtime-tokio\"` — kebab-case ASCII \
         alphanumeric with `-`, `_`, `+`, or `.` as continuation characters, starting with \
         an ASCII alphanumeric or `_`)"
    )]
    CaracteristicaInvalid {
        nome: String,
        caracteristica: String,
        reason: String,
    },
    #[error(
        ":deps entry {nome:?} :caracteristicas carries duplicate feature {caracteristica:?} — \
         every feature-flag list keys its entries by name (Cargo's \
         [dependencies.<dep>.features] applies the same set-not-multiset discipline; one entry \
         per feature per dep), and two entries naming the same feature are a redundant \
         set-membership declaration for one identity (the feature-toggle slot is set-shaped; \
         enabling a feature twice has no additional semantic). The caixa-resolver's lacre \
         pipeline consumes the list as a set-shaped feature toggle — the resolver enables the \
         feature once regardless of declaration count, so the duplicate's pin / position never \
         reaches the closure with no field naming the silent loser. One entry per feature per \
         dep; if two distinct features are intended, name each verbatim."
    )]
    CaracteristicaDuplicate {
        nome: String,
        caracteristica: String,
    },
    #[error(
        "{list} entry :nome {nome:?} names the caixa itself — a caixa cannot depend \
         on itself (the lacre closure's dep-graph traversal is rooted at the caixa's \
         :nome, and a self-dep would be a one-node cycle the caixa-resolver either \
         rejects mid-traversal far from the source caixa.lisp or recurses on until \
         it exhausts its stack). Every :nome is globally-unique substrate identity, \
         so a :deps / :deps-dev entry whose :nome equals the parent caixa's :nome \
         *is* the parent itself, not a coincidentally-named peer. Drop the \
         self-referential dep entry — to reference code from this caixa, use \
         :bibliotecas / :exe / :servicos (the substrate-blessed shape for \
         referencing the caixa's own code surface) instead."
    )]
    DepIsSelf { nome: String, list: &'static str },
}

#[allow(clippy::trivially_copy_pass_by_ref)]
fn is_false(b: &bool) -> bool {
    !*b
}

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

    #[test]
    fn registry_dep_is_minimal() {
        let d = Dep::simple("caixa-teia", "^0.1");
        assert_eq!(d.nome, "caixa-teia");
        assert_eq!(d.versao, "^0.1");
        assert!(d.fonte.is_none());
        assert!(!d.opcional());
        assert!(d.caracteristicas().is_empty());
    }

    #[test]
    fn git_dep_carries_tag() {
        let d = Dep::git("t", "*", "github:o/r", "v1");
        match d.fonte {
            Some(DepSource::Git {
                ref repo, ref tag, ..
            }) => {
                assert_eq!(repo, "github:o/r");
                assert_eq!(tag.as_deref(), Some("v1"));
            }
            _ => panic!("expected Git source"),
        }
    }

    #[test]
    fn validate_accepts_simple_dep() {
        Dep::simple("caixa-teia", "^0.1").validate().unwrap();
    }

    #[test]
    fn validate_rejects_empty_nome() {
        // The fail-before-pass-after pin for `:nome ""`: the empty-name
        // arm fires first so the per-entry parse-side diagnostic doesn't
        // emit a useless `nome: ""` reference.
        let mut d = Dep::simple("placeholder", "^0.1");
        d.nome = String::new();
        assert_eq!(d.validate().unwrap_err(), DepError::NomeEmpty);
    }

    #[test]
    fn validate_rejects_empty_versao() {
        // `parse_requirement("")` returns `Ok(VersionReq::STAR)` (the
        // semver crate accepts the empty string as a wildcard match),
        // so the empty-`:versao` arm is structurally necessary even
        // with the parse arm in place — mirrors `MembroVersaoEmpty` /
        // `EmptyChildVersion` ordering on the other two `:versao` axes.
        let mut d = Dep::simple("caixa-teia", "ignored");
        d.versao = String::new();
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::VersaoEmpty { ref nome } if nome == "caixa-teia"),
            "got {err:?}"
        );
    }

    // ── value-shape: DNS-1123 label on :deps :nome ────────────────────────

    #[test]
    fn validate_rejects_nome_with_uppercase() {
        // The fail-before-pass-after pin: a non-empty but uppercase
        // `:nome` silently passed `validate()` on every pre-gate
        // codebase because the prior shape only refused the empty
        // string. The DNS-1123 violation surfaced far downstream at
        // lacre-resolve time when the *target* caixa's `:nome` failed
        // its own gate — far from the `:deps` entry, with a diagnostic
        // naming the target rather than the dep entry that referenced
        // it. Same fail-before-pass-after fixture pinned for
        // `:membros :caixa` (3f9d7a0), `:children :caixa` (31bfa43),
        // and Caixa `:nome` (6c992f8).
        let d = Dep::simple("Caixa-Teia", "^0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::NomeInvalid { ref nome, ref reason }
                    if nome == "Caixa-Teia" && reason.contains("uppercase")
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_nome_with_underscore() {
        // RFC 1123 allows `[a-z0-9-]` only; underscore is the canonical
        // "I'm thinking of Go module names / Python identifiers" leak.
        // Same fixture pinned for the peer caixa-identifier axes.
        let d = Dep::simple("caixa_teia", "^0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::NomeInvalid { ref nome, ref reason }
                    if nome == "caixa_teia" && reason.contains('_')
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_nome_with_dot() {
        // A `:deps :nome` is a single DNS-1123 *label*, not a
        // subdomain — dots are rejected. The `"caixa.teia"` shape is
        // the canonical "I confused the dep name with the FQDN /
        // namespace" footgun, distinct from the legitimate
        // `:fonte :repo "github:org/caixa-teia"` axis.
        let d = Dep::simple("caixa.teia", "^0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::NomeInvalid { ref nome, ref reason }
                    if nome == "caixa.teia" && reason.contains('.')
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_nome_with_leading_hyphen() {
        // RFC 1123 requires alphanumeric at both label boundaries.
        // Pinned in parity with the peer DNS-1123 fixtures.
        let d = Dep::simple("-caixa-teia", "^0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::NomeInvalid { ref nome, ref reason }
                    if nome == "-caixa-teia" && reason.contains("alphanumeric")
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_nome_with_trailing_hyphen() {
        let d = Dep::simple("caixa-teia-", "^0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::NomeInvalid { ref nome, ref reason }
                    if nome == "caixa-teia-" && reason.contains("alphanumeric")
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_nome_with_slash() {
        // The canonical "I copied the GitHub repo path into `:nome`
        // instead of `:fonte :repo`" typo. A `/` in the name leaks the
        // lacre-side `:repositorio` shape (`pleme-io/caixa-teia`) into
        // the local-name slot. Same fixture pinned for `:membros
        // :caixa` (3f9d7a0).
        let d = Dep::simple("pleme-io/caixa-teia", "^0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::NomeInvalid { ref nome, ref reason }
                    if nome == "pleme-io/caixa-teia" && reason.contains('/')
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_nome_too_long() {
        // 64-byte label — one over the RFC 1035 / RFC 1123 label cap.
        // Built from a valid character set so the length-bound
        // diagnostic surfaces before any per-character check (the
        // order pin parallel to the per-character predicates inside
        // [`crate::render::is_dns_1123_label`]).
        let long = "a".repeat(64);
        let d = Dep::simple(&long, "^0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::NomeInvalid { ref nome, ref reason }
                    if nome.len() == 64 && reason.contains("max length of 63")
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_accepts_canonical_nome_labels() {
        // Positive-control sweep — every form the K8s apiserver
        // accepts as a DNS-1123 label must round-trip through
        // validate. Covers a hyphen-bearing label, a numeric-suffix
        // label, a leading-digit label, a single-character label, and
        // a 63-byte (exactly the cap) label — the same fixture set
        // the peer `:membros :caixa` / `:children :caixa` positive
        // controls pin.
        for nome in [
            "caixa-teia",
            "caixa-resolver2",
            "2nd-tier-cache",
            "x",
            "abcdefghijklmnopqrstuvwxyz0123456789abcdefghijklmnopqrstuvwxyz0",
        ] {
            Dep::simple(nome, "^0.1")
                .validate()
                .unwrap_or_else(|e| panic!("canonical label {nome:?} must validate, got {e:?}"));
        }
    }

    #[test]
    fn nome_empty_takes_precedence_over_nome_invalid() {
        // Ordering pin: `NomeEmpty` is the more self-locating
        // diagnostic on `""` and must lead — `is_dns_1123_label` is
        // only reached after the empty-check fires at the call site.
        // Mirrors `membro_caixa_empty_takes_precedence_over_invalid`
        // (3f9d7a0) on the peer caixa-identifier axis.
        let mut d = Dep::simple("placeholder", "^0.1");
        d.nome = String::new();
        assert_eq!(d.validate().unwrap_err(), DepError::NomeEmpty);
    }

    #[test]
    fn nome_invalid_fires_before_versao_empty() {
        // Ordering pin: a malformed `:nome` fires before any `:versao`
        // axis check on the *same* entry — the per-entry shape gates
        // run top-to-bottom (nome empty → nome shape → versao empty →
        // versao parse → fonte shape), so a one-entry caixa.lisp with
        // both wrong sees the name-side diagnostic first (the name is
        // the self-locating axis — without a valid name, the parse
        // diagnostic can't quote `:nome "<bad>"`). Same ordering
        // discipline as `membro_caixa_invalid_fires_before_versao_check`
        // (3f9d7a0).
        let mut d = Dep::simple("Caixa-Teia", "^0.1");
        d.versao = String::new();
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::NomeInvalid { ref nome, .. } if nome == "Caixa-Teia"),
            "got {err:?}"
        );
    }

    #[test]
    fn nome_invalid_fires_before_versao_invalid() {
        // Ordering pin: a malformed `:nome` fires before the `:versao`
        // parse-side check on the *same* entry. Pin separately from
        // the empty-versao ordering so a future re-ordering surfaces
        // here, parallel to the b0c8389 / c4213a4 trajectory.
        let d = Dep::simple("Caixa-Teia", "^^0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::NomeInvalid { ref nome, .. } if nome == "Caixa-Teia"),
            "got {err:?}"
        );
    }

    #[test]
    fn nome_invalid_fires_before_fonte_invalid() {
        // Ordering pin: a malformed `:nome` fires before the `:fonte`
        // shape check on the *same* entry. The `:fonte` diagnostic
        // names the offending dep's `:nome` verbatim (via
        // `DepSource::validate(&self.nome)`), so a non-self-locating
        // name would taint the downstream diagnostic too — the gate
        // ordering keeps both diagnostics individually self-locating.
        let mut d = Dep::simple("Caixa-Teia", "^0.1");
        d.fonte = Some(DepSource::Git {
            repo: String::new(),
            tag: None,
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::NomeInvalid { ref nome, .. } if nome == "Caixa-Teia"),
            "got {err:?}"
        );
    }

    #[test]
    fn nome_invalid_diagnostic_carries_offending_name() {
        // The diagnostic-shape pin: the error names the offending
        // `:nome` value verbatim so the author can grep their
        // caixa.lisp without re-running the build, and carries a
        // non-empty `reason` from `is_dns_1123_label` so the
        // predicate's own wording flows through to the diagnostic.
        // Same shape as `MembroCaixaInvalid` (3f9d7a0),
        // `ChildCaixaInvalid` (31bfa43), `ManifestError::NomeInvalid`
        // (6c992f8) — the four DNS-1123 caixa-identifier axes now
        // share a structurally-equivalent diagnostic family.
        let d = Dep::simple("Caixa_Teia", "^0.1");
        let err = d.validate().unwrap_err();
        let DepError::NomeInvalid { nome, reason } = err else {
            panic!("expected NomeInvalid, got other variant");
        };
        assert_eq!(nome, "Caixa_Teia");
        assert!(
            !reason.is_empty(),
            "NomeInvalid `reason` must carry the predicate's wording verbatim"
        );
    }

    #[test]
    fn validate_rejects_invalid_versao_requirement() {
        // The fail-before-pass-after pin: a non-empty but malformed
        // requirement (`"^bad-version"`) silently passed every pre-gate
        // codebase because `:deps :versao` wasn't validated. The parse
        // failure surfaced far downstream at lacre-resolve time with a
        // `semver::Error` that didn't name which `:deps` entry carried
        // the typo. The new gate moves the check to caixa-build time
        // at the source caixa.lisp.
        let d = Dep::simple("caixa-teia", "^bad-version");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::VersaoInvalid { ref nome, ref versao, .. }
                    if nome == "caixa-teia" && versao == "^bad-version"
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_versao_with_double_caret_typo() {
        // `"^^0.1"` is the canonical doubled-caret typo — looks like a
        // Cargo-shaped requirement on first glance but fails the parser
        // because semver doesn't accept stacked operators. Pin this
        // adjacent-shape footgun explicitly so a future relaxation that
        // accepts "looks-canonical-but-isn't" forms surfaces here, in
        // parity with the `:membros` / `:children` fixtures.
        let d = Dep::simple("caixa-teia", "^^0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::VersaoInvalid { ref nome, ref versao, .. }
                    if nome == "caixa-teia" && versao == "^^0.1"
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_versao_with_v_prefixed_tag() {
        // `"v0.1"` is the canonical "git-tag-shape leaking into the
        // semver requirement slot" typo — an author copies the
        // publish-side git-tag string verbatim into `:versao`, but
        // Cargo's semver parser rejects the leading `v`. Same fixture
        // pinned for `:membros :versao` (9888b13) and `:children
        // :versao` (b38ff3a). (Bare `x`-glob shorthands like `^0.1.x`
        // are *accepted* by the semver crate as an `*` wildcard on the
        // patch axis — they're a Cargo-side valid shape, not a typo.)
        let d = Dep::simple("caixa-teia", "v0.1");
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::VersaoInvalid { ref nome, ref versao, .. }
                    if nome == "caixa-teia" && versao == "v0.1"
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_accepts_canonical_versao_forms() {
        // The five Cargo-shaped requirement forms `:membros :versao`
        // and `:children :versao` already accept via
        // `crate::parse_requirement` must pass the deps gate without
        // re-validating at the resolver layer. Pin every leg so a
        // future tightening of the canonical set surfaces here as a
        // test failure.
        for form in [
            "^0.1",      // caret — minor-range pin (the most common shape)
            "~0.1.2",    // tilde — patch-range pin
            "0.1.0",     // exact — single-version pin
            "*",         // wildcard — explicitly any-version
            ">=0.1, <2", // multi-range — comma-separated comparators
        ] {
            Dep::simple("caixa-teia", form)
                .validate()
                .unwrap_or_else(|e| panic!("canonical form {form:?} must validate, got {e:?}"));
        }
    }

    #[test]
    fn versao_empty_takes_precedence_over_invalid() {
        // Order pin: the existing `VersaoEmpty` diagnostic (which
        // doesn't try to parse) fires before the new `VersaoInvalid`
        // parse-side diagnostic, so an empty `:versao` keeps its
        // narrower error message — `parse_requirement("")` would
        // otherwise return `Ok(STAR)` and silently pass, but the empty
        // arm catches it first.
        let mut d = Dep::simple("caixa-teia", "ignored");
        d.versao = String::new();
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::VersaoEmpty { ref nome } if nome == "caixa-teia"),
            "got {err:?}"
        );
    }

    #[test]
    fn nome_empty_takes_precedence_over_versao_invalid() {
        // Order pin: even when `:versao` is malformed and would raise
        // its own diagnostic, `:nome ""` fires first because the
        // per-entry parse diagnostic needs a non-empty name to be
        // self-locating. Mirrors the
        // `membros_validation_runs_before_contratos_membership_check`
        // ordering on the typed-graph layer.
        let mut d = Dep::simple("placeholder", "^bad");
        d.nome = String::new();
        let err = d.validate().unwrap_err();
        assert_eq!(err, DepError::NomeEmpty);
    }

    #[test]
    fn versao_invalid_diagnostic_carries_offending_versao() {
        // The diagnostic-shape pin: the error names the offending
        // `:versao` value verbatim so the author can grep their
        // caixa.lisp without re-running the build, and carries a
        // non-empty `reason` from `semver::VersionReq::parse` so the
        // parser's own wording flows through to the diagnostic.
        let d = Dep::simple("caixa-teia", "not-a-req");
        let err = d.validate().unwrap_err();
        let DepError::VersaoInvalid {
            nome,
            versao,
            reason,
        } = err
        else {
            panic!("expected VersaoInvalid, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(versao, "not-a-req");
        assert!(
            !reason.is_empty(),
            "VersaoInvalid `reason` must carry the parser's wording verbatim"
        );
    }

    // -- :fonte value-shape gate ------------------------------------------

    fn dep_with_fonte(fonte: DepSource) -> Dep {
        let mut d = Dep::simple("caixa-teia", "^0.1");
        d.fonte = Some(fonte);
        d
    }

    #[test]
    fn validate_accepts_git_fonte_with_tag() {
        // The positive-control pin on the canonical git source — exactly
        // one of :tag/:rev/:branch set, non-empty :repo. Mirrors the
        // shape every existing caixa-resolver integration test uses.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_accepts_git_fonte_with_rev() {
        // Each of the three pin axes is independently a valid single-pin
        // shape; pin the :rev arm so a future relaxation that only
        // accepts :tag surfaces here. The value is a full 40-hex SHA-1
        // OID — the canonical `git rev-parse HEAD` emission shape the
        // `crate::render::is_git_oid` value-shape gate now requires;
        // abbreviated OIDs are ambiguous across repo history and
        // rejected at this gate (pinned separately by
        // `validate_rejects_git_fonte_with_rev_abbreviated_prefix`).
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some("c0ffee0123abcdef0123456789abcdef01234567".into()),
            branch: None,
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_accepts_git_fonte_with_branch() {
        // The :branch arm is the third valid single-pin shape — pinned
        // separately so the gate-accepts-all-three-pin-axes contract is
        // a build-error to relax.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: None,
            branch: Some("main".into()),
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_accepts_path_fonte() {
        // The positive-control pin on the path source — non-empty
        // :caminho, no pin axes (paths have no commit identity). Pinned
        // so a future "paths must also pin a rev" tightening surfaces
        // here as a structural decision, not a silent break.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_rejects_git_fonte_with_empty_repo() {
        // The fail-before-pass-after pin for `(:tipo git :repo "" :tag
        // "v1")`: the empty-repo shape silently passed every pre-gate
        // codebase because `:fonte` wasn't validated. The git-clone
        // failure surfaced far downstream at lacre-resolve time with no
        // field naming which `:deps` entry carried the typo. The new
        // gate moves the check to caixa-build time at the source
        // caixa.lisp.
        let d = dep_with_fonte(DepSource::Git {
            repo: String::new(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteRepoEmpty { ref nome } if nome == "caixa-teia"),
            "got {err:?}"
        );
    }

    // -- :repo value-shape gate -------------------------------------------
    //
    // The `:fonte (:tipo git :repo …)` value flows verbatim into the
    // caixa-resolver's `git clone <repo>` subprocess. The pre-gate
    // codebase admitted any non-empty string; the new
    // [`crate::render::is_git_repo_url`] predicate gates the git-porcelain
    // URL intersection-floor at validate time, peer with the three pin
    // axes (`:tag` + `:branch` via `is_git_ref_name`, `:rev` via
    // `is_git_oid`). Every test in this section is a fail-before /
    // pass-after pin on a specific authoring footgun.

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_trailing_space() {
        // The canonical paste-from-doc footgun on `:repo` — an author
        // copies `"github:pleme-io/caixa-teia "` (trailing space) out of
        // a doc paragraph. Until this gate landed the empty-repo arm
        // passed (the string isn't empty), the resolver issued
        // `git clone 'github:pleme-io/caixa-teia '`, and the failure
        // surfaced at clone time with a quoting-confused error far from
        // the source caixa.lisp. Same paste-from-doc footgun the
        // `:tag "v0.1.0 "` gate (e70d213) closes on the peer refname
        // axis — now closed on the `:repo` URL axis too.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia ".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "github:pleme-io/caixa-teia ");
        assert!(
            reason.contains("whitespace"),
            "reason must surface the whitespace arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_starting_with_dash() {
        // The canonical CLI-argument-injection footgun at the `git clone`
        // subprocess boundary — `:repo "-upload-pack=evil"` makes git's
        // argv parser read the value as a CLI flag, escaping the
        // subprocess argument boundary. The `--` separator workaround
        // does not fix the typed slot's accepted set; the gate rejects
        // the shape upstream at validate time so the resolver never
        // invokes a `git clone -…` subprocess.
        let d = dep_with_fonte(DepSource::Git {
            repo: "-upload-pack=evil".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { repo, reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(repo, "-upload-pack=evil");
        assert!(
            reason.contains("must not start with `-`"),
            "reason must surface the leading-`-` arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_embedded_newline() {
        // The canonical paste-from-multiline-doc footgun — a `:repo`
        // string with an embedded `\n` silently breaks git's URL parser
        // and is a class of CRLF-injection at the subprocess-argument
        // boundary. Caught by the control-char arm (0x0A < 0x20).
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia\nrm -rf /".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("control character"),
            "reason must surface the control-char arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_tab() {
        // Tab is the sibling whitespace footgun (the canonical
        // copy-from-aligned-table paste); pinned separately from the
        // space arm so a future relaxation that only catches one
        // surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia\t".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteRepoShape { ref reason, .. }
                    if reason.contains("whitespace")
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_non_ascii() {
        // IDN hosts must be pre-encoded as Punycode (`xn--…`) — raw
        // non-ASCII silently breaks at git's URL parser and round-trips
        // inconsistently across NFC/NFD normalization on APFS /
        // case-folding filesystems. Same intersection-floor
        // [`is_git_ref_name`] enforces on the refname axes.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/café".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteRepoShape { ref reason, .. }
                    if reason.contains("non-ASCII")
            ),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_fragment_anchor() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // browser-address-bar footgun on `:repo`: an author copies a
        // GitHub permalink to a README anchor / line-permalink and
        // forgets to trim the `#fragment` tail. Until this arm landed
        // `:repo "https://github.com/pleme-io/caixa-teia#readme"`
        // silently passed every prior arm (no whitespace, no control
        // chars, no non-ASCII, contains a `:`, doesn't start with `-`
        // or `:`), libcurl's URL parser stripped the `#readme` tail
        // before opening the HTTPS transport, and the lacre embedded
        // the value verbatim in its per-dep BLAKE3 closure — two
        // authors whose values differ only in their fragment anchor
        // (`#readme` vs `#L42`) resolve to the byte-identical upstream
        // `git clone` but lock to two distinct lacres, defeating the
        // THEORY.md §V.2 render-determinism contract. Same value-shape
        // axis-floor every peer typed surface enforces; peer `:fonte
        // :tag` / `:fonte :branch` already reject the byte-class through
        // `is_git_ref_name`'s alphabet (refs are leaf identifiers, no
        // URL grammar admitted) and `:entrada :paths` rejects `#` as
        // part of `is_gateway_api_http_path`'s RFC-3986-reserved set.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/caixa-teia#readme");
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm, got {reason:?}"
        );
        assert!(
            reason.contains("fragment"),
            "reason must name the URL fragment grammar, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_flake_ref_fragment() {
        // The symmetric paste-from-Nix-flake-ref footgun — an author
        // confuses the Nix flake-reference idiom (`github:foo/
        // bar#packageName`, where `#packageName` selects a flake
        // output) with the bare git `:repo` shape. The pleme-io
        // substrate authors compose flakes downstream of caixa
        // (caixa-flake renders a flake.nix), so the cross-idiom leak
        // is the canonical near-miss: the author writes the
        // flake-ref shape into a git `:repo` slot. Pinned separately
        // from the HTTPS-anchor arm so a future relaxation that
        // narrows to one URL scheme surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia#caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm, got {reason:?}"
        );
        assert!(
            reason.contains("Nix flake"),
            "reason must name the Nix-flake-ref cross-idiom footgun, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_query_string() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // browser-address-bar footgun on `:repo` (peer with the
        // a68f818 fragment-`#` arm on the same axis). An author
        // copies a GitHub tab deep-link out of the address bar and
        // forgets to trim the `?tab=…` query tail. Until this arm
        // landed `:repo "https://github.com/pleme-io/caixa-teia?tab=readme-ov-file"`
        // silently passed every prior arm (no whitespace, no control
        // chars, no non-ASCII, no `#` fragment, contains a `:`,
        // doesn't start with `-` or `:`); GitHub silently ignored
        // the `?query` tail and served the same repo regardless;
        // the lacre embedded the value verbatim in its per-dep
        // BLAKE3 closure — two authors whose values differ only in
        // their query tail (`?tab=readme-ov-file` vs `?ref=main` vs
        // `?utm_source=twitter`) resolve to the byte-identical
        // upstream `git clone` but lock to two distinct lacres,
        // defeating the THEORY.md §V.2 render-determinism contract
        // on the same axis the `#` fragment arm closes. Same value-
        // shape axis-floor every peer typed surface enforces; peer
        // `:fonte :tag` / `:fonte :branch` already reject the byte-
        // class through `is_git_ref_name`'s alphabet (refspec glob
        // wildcards, caixa-core/src/render.rs:1426) and `:entrada
        // :paths` rejects `?` as the query separator in
        // `is_gateway_api_http_path` (caixa-core/src/render.rs:473).
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia?tab=readme-ov-file".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(
            repo,
            "https://github.com/pleme-io/caixa-teia?tab=readme-ov-file"
        );
        assert!(
            reason.contains("must not contain `?`"),
            "reason must surface the query-`?` arm, got {reason:?}"
        );
        assert!(
            reason.contains("query"),
            "reason must name the URL query grammar, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_utm_tracker() {
        // The symmetric paste-from-social-share footgun — an author
        // copies a repo URL out of a Slack unfurl / Twitter share /
        // newsletter link / Discord embed and forgets to trim the
        // `?utm_source=…` / `?utm_medium=…` / `?utm_campaign=…`
        // campaign-tracker tail. Every major social-share / unfurl /
        // newsletter platform appends these UTM parameters; the
        // canonical near-miss on the `:repo` axis. Pinned separately
        // from the GitHub-tab-deep-link arm so a future relaxation
        // that narrows to one query-parameter class surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia?utm_source=twitter&utm_campaign=launch"
                .into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `?`"),
            "reason must surface the query-`?` arm, got {reason:?}"
        );
        assert!(
            reason.contains("campaign-tracker"),
            "reason must name the campaign-tracker paste footgun, got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_query_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the query-`?` arm are
        // both per-byte arms inside the same `for &b in s.as_bytes()`
        // loop, so the byte that appears first in the value's byte
        // order wins. A `:repo "https://github.com/p/x#readme?ref=main"`
        // (fragment before query — unusual URL-grammar but value-
        // disjoint at byte level) carries both `#` and `?`; the `#`
        // byte appears first, so the fragment-`#` arm fires, surfacing
        // the more self-locating diagnostic on the byte the author
        // pasted earliest in the URL. Mirrors the peer cascade
        // discipline `fonte_repo_control_char_fires_before_fragment`
        // pins on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme?ref=main".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before query-`?` when \
             `#` byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_control_char_fires_before_fragment() {
        // Cascade pin: the control-char arm structurally precedes the
        // fragment-`#` arm. A value like `"github:p/x\n#readme"` probes
        // positive on both arms (contains LF and `#`), but the narrower
        // POSIX-syscall-rejected / CRLF-injection-class diagnostic
        // (`control character`) wins so the author sees the more
        // self-locating arm first. Mirrors the peer cascade discipline
        // every prior `:repo` byte-class arm establishes.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia\n#readme".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("control character"),
            "reason must surface the control-char arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_embedded_backslash() {
        // The fail-before-pass-after pin for the canonical Windows-
        // file-path-confusion footgun on `:repo` (peer with the 3a4e1d7
        // backslash arm on the sibling `:caminho` path-fonte axis).
        // An author pastes a Windows Explorer address-bar / PowerShell
        // `Get-Location` output into a `file://` URL slot, producing
        // `file:///C:\Users\me\caixa-teia`. Until this arm landed the
        // value silently passed every prior arm (no whitespace, no
        // control chars, no non-ASCII, no `#`, no `?`, doesn't start
        // with `-` or `:`); libcurl's URL parser silently translates
        // `\` → `/` on some platforms and refuses it on others, so
        // the byte rides verbatim into the lacre's per-dep content-
        // address but is silently rewritten / rejected at the wire —
        // two authors whose `:repo` values differ only in backslash-
        // vs-forward-slash (`file:///C:\path` vs `file:///C:/path`)
        // resolve to the byte-identical local clone but lock to two
        // distinct BLAKE3 closures, defeating the THEORY.md §V.2
        // render-determinism contract on the same axis the `#`
        // fragment and `?` query arms close. Same value-shape axis-
        // floor every peer typed surface enforces; the `:caminho`
        // 3a4e1d7 arm closes the same byte on the path-fonte axis.
        let d = dep_with_fonte(DepSource::Git {
            repo: "file:///C:\\Users\\me\\caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "file:///C:\\Users\\me\\caixa-teia");
        assert!(
            reason.contains("must not contain `\\`"),
            "reason must surface the backslash-`\\` arm, got {reason:?}"
        );
        assert!(
            reason.contains("Windows"),
            "reason must name the Windows-path-confusion footgun, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_mangled_https_backslashes() {
        // The symmetric Win32-shell-mangled-slashes footgun — an author
        // copies `https://github.com/foo/bar` into a Win32 shell that
        // rewrites every `/` to `\` (the canonical `cmd.exe` path-
        // separator-coercion bug), pastes the result into a `:repo`
        // slot, and produces `https:\\github.com\foo\bar`. Pinned
        // separately from the `file://` Explorer-paste arm so a future
        // relaxation that narrows to one URL scheme surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https:\\\\github.com\\pleme-io\\caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `\\`"),
            "reason must surface the backslash-`\\` arm, got {reason:?}"
        );
        assert!(
            reason.contains("path separator") || reason.contains("path-segment separator"),
            "reason must name the URL path-segment separator grammar, got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_backslash_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the backslash-`\` arm
        // are both per-byte arms inside the same `for &b in s.as_bytes()`
        // loop, so the byte that appears first in the value's byte order
        // wins. A `:repo "https://github.com/p/x#readme\\foo"` carries
        // both `#` and `\`; the `#` byte appears first, so the fragment-
        // `#` arm fires, surfacing the more self-locating diagnostic on
        // the byte the author pasted earliest in the URL. Mirrors the
        // peer cascade discipline `fonte_repo_fragment_fires_before_query_when_fragment_first`
        // pins on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme\\foo".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before backslash-`\\` when \
             `#` byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_uri_template_placeholder() {
        // The fail-before-pass-after pin for the canonical URI Template
        // (RFC 6570) placeholder footgun on `:repo`. An author copies a
        // README quick-start snippet / OpenAPI `servers:` URL / Helm
        // chart `home:` template that carries unresolved
        // `{org}` / `{repo}` placeholders and pastes the raw template
        // into the `:repo` slot, expecting the substrate to resolve the
        // placeholder downstream. Until this arm landed the value
        // silently passed every prior arm (no whitespace, no control
        // chars, no non-ASCII, no `#`, no `?`, no `\`, doesn't start
        // with `-` or `:`); libcurl percent-encodes `{` / `}` to `%7B`
        // / `%7D` on the wire, so the byte rides verbatim into the
        // lacre's per-dep content-address but round-trips inconsistently
        // between the lacre's per-dep content-address and the
        // resolver's `git clone <repo>` invocation, defeating the
        // THEORY.md §V.2 render-determinism contract on the same axis
        // the `#` fragment, `?` query, and `\` backslash arms close;
        // every git porcelain entry-point additionally fetches a
        // nonexistent literal-`{placeholder}`-named path far from the
        // source caixa.lisp.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/{org}/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/{org}/caixa-teia");
        assert!(
            reason.contains("must not contain `{`"),
            "reason must surface the open-brace `{{` arm, got {reason:?}"
        );
        assert!(
            reason.contains("URI Template") || reason.contains("RFC 6570"),
            "reason must name the RFC 6570 URI Template grammar, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_handlebars_doubled_brace() {
        // The symmetric Mustache / Handlebars doubled-brace
        // substitution-form footgun every CI / IaC templating engine
        // (Argo Workflows, Jinja2, Liquid, Vue / Angular interpolation,
        // GitHub Actions `${{ … }}` even though Actions uses `${{`) /
        // chart README quick-start snippet emits. Pinned separately
        // from the single-`{` `{org}` arm so a future relaxation that
        // narrows to one substitution-form surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/{{org}}/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `{`"),
            "reason must surface the open-brace `{{` arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_closing_brace_only() {
        // Asymmetric `}`-only shape — covers the closing-brace-by-
        // itself footgun (an author truncated `{org}/{repo}` mid-edit
        // and left a trailing `}` from the prior template fragment,
        // or pasted a value that included a closing brace from a
        // surrounding shell context). Pinned to ensure the predicate
        // refuses each brace independently rather than only when both
        // appear — a future regression that ANDs the two byte tests
        // surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia}".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `}`"),
            "reason must surface the close-brace `}}` arm, got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_template_placeholder_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the template-`{` /
        // `}` arm are both per-byte arms inside the same
        // `for &b in s.as_bytes()` loop, so the byte that appears
        // first in the value's byte order wins. A `:repo
        // "https://github.com/p/x#readme{org}"` carries both `#` and
        // `{`; the `#` byte appears first, so the fragment-`#` arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Mirrors the
        // peer cascade discipline `fonte_repo_fragment_fires_before_backslash_when_fragment_first`
        // pins on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme{org}".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before template-`{{` when \
             `#` byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_output_redirection() {
        // The fail-before-pass-after pin for the canonical
        // shell-output-redirection footgun on `:repo`: an author
        // pastes a shell-pipeline tail (`git clone <repo> > build.log`
        // / `… >output.txt`) into the `:repo` slot without trimming
        // the redirect. Until this arm landed the value silently
        // passed every prior arm (no whitespace, no control chars,
        // no non-ASCII, no `#`, no `?`, no `\`, no `{`/`}`, doesn't
        // start with `-` or `:`); RFC 3986 §2 lists `<` / `>` in the
        // 'delims' / 'unwise' set and the WHATWG URL spec's fragment
        // percent-encode set maps `>` → `%3E` on the wire, so the
        // byte rides verbatim into the lacre's per-dep BLAKE3 closure
        // but is silently rewritten or rejected at libcurl's URL-
        // parser layer — two authors whose values differ only in
        // their redirect tail (`>build.log` vs nothing) resolve to
        // the byte-identical upstream `git clone` but lock to two
        // distinct lacres, defeating the THEORY.md §V.2 render-
        // determinism contract. Peer with the `:caminho` axis's
        // `FonteCaminhoShellRedirection` arm (e457141) on the sibling
        // path-fonte axis, and `is_gateway_api_http_path`'s eleven-
        // byte RFC-3986-reserved set on `:entrada :paths`.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia>build.log".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/caixa-teia>build.log");
        assert!(
            reason.contains("must not contain `>`"),
            "reason must surface the output-redirection `>` arm, got {reason:?}"
        );
        assert!(
            reason.contains("redirection") || reason.contains("'delims'"),
            "reason must name the shell-redirection / RFC-3986-unwise rationale, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_input_redirection() {
        // The symmetric shell-input-redirection footgun — an author
        // pastes a shell-pipeline head (`git clone <input.url` /
        // `cat <README.md`) into the `:repo` slot. Pinned separately
        // from the `>`-output arm so a future relaxation that only
        // catches one of the two redirect bytes surfaces here. Peer
        // with the `:caminho` axis's `FonteCaminhoShellRedirection`
        // arm which closes both `<` and `>` under the same banner.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia<input.url".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `<`"),
            "reason must surface the input-redirection `<` arm, got {reason:?}"
        );
        assert!(
            reason.contains("RFC 3986") || reason.contains("'unwise'"),
            "reason must name the RFC 3986 'unwise' grammar, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_backtick_command_substitution() {
        // The fail-before-pass-after pin for the canonical
        // paste-from-shell-prompt-with-backticked-substitution footgun
        // on `:repo` (peer with the c4d62b3 backtick arm on the sibling
        // `:caminho` path-fonte axis). An author pastes a URL whose
        // segment carries a backticked command-substitution wrapper
        // (`` `whoami` ``, `` `git config user.name` ``, `` `pwd` ``)
        // from a doc / README quick-start snippet that expected the
        // substrate to substitute the value downstream. Until this arm
        // landed the value silently passed every prior arm (no
        // whitespace, no control chars, no non-ASCII, no `#`, no `?`,
        // no `\`, no `{`/`}`, no `<`/`>`, doesn't start with `-` or
        // `:`); RFC 3986 §2 lists the backtick byte in the 'delims' /
        // 'unwise' set and the WHATWG URL spec's fragment percent-
        // encode set maps `` ` `` → `%60` on the wire, so the byte
        // rides verbatim into the lacre's per-dep BLAKE3 closure but
        // is silently rewritten or rejected at libcurl's URL-parser
        // layer — two authors whose values differ only in their
        // backtick wrapper (`` `whoami` `` vs nothing) resolve to the
        // byte-identical upstream `git clone` but lock to two distinct
        // lacres, defeating the THEORY.md §V.2 render-determinism
        // contract. Peer with the `:caminho` axis's
        // `FonteCaminhoShellCommandSubstitution` arm (c4d62b3) on the
        // sibling path-fonte axis, and `is_gateway_api_http_path`'s
        // eleven-byte RFC-3986-reserved set on `:entrada :paths`.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/`whoami`/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/`whoami`/caixa-teia");
        assert!(
            reason.contains("must not contain `` ` ``"),
            "reason must surface the backtick command-substitution arm, got {reason:?}"
        );
        assert!(
            reason.contains("command-substitution") || reason.contains("'unwise'"),
            "reason must name the shell-command-substitution / RFC-3986-unwise rationale, \
             got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_backtick_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the backtick command-
        // substitution arm are both per-byte arms inside the same
        // `for &b in s.as_bytes()` loop, so the byte that appears first
        // in the value's byte order wins. A `:repo
        // "https://github.com/p/x#readme/`whoami`"` carries both `#`
        // and backtick; the `#` byte appears first, so the fragment-
        // `#` arm fires, surfacing the more self-locating diagnostic
        // on the byte the author pasted earliest in the URL. Mirrors
        // the peer cascade discipline
        // `fonte_repo_fragment_fires_before_shell_redirection_when_fragment_first`
        // pins on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme/`whoami`".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before backtick when `#` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_shell_redirection_fires_before_backtick_when_redirection_first() {
        // Cascade pin: the shell-redirection `<` / `>` arm and the
        // backtick command-substitution arm are both per-byte arms
        // inside the same `for &b in s.as_bytes()` loop, so the byte
        // that appears first in the value's byte order wins. A `:repo
        // "https://github.com/p/x>build.log/`whoami`"` carries both
        // `>` and backtick; the `>` byte appears first, so the
        // shell-redirection arm fires, surfacing the more self-
        // locating diagnostic on the byte the author pasted earliest
        // in the URL. Pins the natural-order cascade so a future
        // reorder of the per-byte arms surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia>build.log/`whoami`".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `>`"),
            "reason must surface the shell-redirection `>` arm (fires before backtick when \
             `>` byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_shell_redirection_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the shell-redirection
        // `<` / `>` arm are both per-byte arms inside the same
        // `for &b in s.as_bytes()` loop, so the byte that appears
        // first in the value's byte order wins. A `:repo
        // "https://github.com/p/x#readme>build.log"` carries both
        // `#` and `>`; the `#` byte appears first, so the fragment-
        // `#` arm fires, surfacing the more self-locating diagnostic
        // on the byte the author pasted earliest in the URL. Mirrors
        // the peer cascade discipline
        // `fonte_repo_fragment_fires_before_template_placeholder_when_fragment_first`
        // pins on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme>build.log".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before shell-redirection `>` when \
             `#` byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_shell_pipe() {
        // The fail-before-pass-after pin for the canonical
        // paste-from-shell-prompt-with-piped-pipeline footgun on
        // `:repo` (peer with the 124106f pipe arm on the sibling
        // `:caminho` path-fonte axis). An author pastes a shell
        // pipeline (`git clone <url> | tee build.log`,
        // `git ls-remote <url> | head`) into the `:repo` slot,
        // forgetting to trim the `| <consumer>` tail. Until this arm
        // landed the value silently passed every prior arm (no
        // whitespace, no control chars, no non-ASCII, no `#`, no `?`,
        // no `\`, no `{`/`}`, no `<`/`>`, no `` ` ``, doesn't start
        // with `-` or `:`); RFC 3986 §2 lists the pipe byte in the
        // 'unwise' set and the WHATWG URL spec's fragment percent-
        // encode set maps `|` → `%7C` on the wire, so the byte rides
        // verbatim into the lacre's per-dep BLAKE3 closure but is
        // silently rewritten or rejected at libcurl's URL-parser
        // layer — two authors whose values differ only in their pipe
        // tail (`|tee build.log` vs nothing) resolve to the byte-
        // identical upstream `git clone` but lock to two distinct
        // lacres, defeating the THEORY.md §V.2 render-determinism
        // contract. Peer with the `:caminho` axis's
        // `FonteCaminhoShellPipe` arm (124106f) on the sibling path-
        // fonte axis, and `is_gateway_api_http_path`'s eleven-byte
        // RFC-3986-reserved set on `:entrada :paths`.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia|tee build.log".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/caixa-teia|tee build.log");
        assert!(
            reason.contains("must not contain `|`"),
            "reason must surface the shell-pipe arm, got {reason:?}"
        );
        assert!(
            reason.contains("pipe") || reason.contains("'unwise'"),
            "reason must name the shell-pipe / RFC-3986-unwise rationale, got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_pipe_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the pipe arm are both
        // per-byte arms inside the same `for &b in s.as_bytes()` loop,
        // so the byte that appears first in the value's byte order
        // wins. A `:repo "https://github.com/p/x#readme|tee"` carries
        // both `#` and `|`; the `#` byte appears first, so the
        // fragment-`#` arm fires, surfacing the more self-locating
        // diagnostic on the byte the author pasted earliest in the
        // URL. Mirrors the peer cascade discipline
        // `fonte_repo_fragment_fires_before_backtick_when_fragment_first`
        // pins on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme|tee".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before pipe when `#` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_backtick_fires_before_pipe_when_backtick_first() {
        // Cascade pin: the backtick arm and the pipe arm are both per-
        // byte arms inside the same `for &b in s.as_bytes()` loop, so
        // the byte that appears first in the value's byte order wins.
        // A `:repo "https://github.com/p/x/`whoami`|tee"` carries both
        // `` ` `` and `|`; the backtick byte appears first, so the
        // backtick arm fires, surfacing the more self-locating
        // diagnostic on the byte the author pasted earliest in the
        // URL. Pins the natural-order cascade so a future reorder of
        // the per-byte arms surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia/`whoami`|tee".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `` ` ``"),
            "reason must surface the backtick arm (fires before pipe when `` ` `` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_shell_command_separator() {
        // The fail-before-pass-after pin for the canonical
        // paste-from-shell-prompt-with-sequential-command-tail footgun
        // on `:repo` (peer with the 05c358e `;` arm on the sibling
        // `:caminho` path-fonte axis). An author pastes a shell
        // one-liner that chained a cleanup tail after the URL
        // (`git clone <url>; rm -rf build`, `git ls-remote <url>;
        // echo done`) into the `:repo` slot, forgetting to trim the
        // `; <cmd>` tail. Until this arm landed the value silently
        // passed every prior `is_git_repo_url` arm (no whitespace, no
        // control chars, no non-ASCII, no `#`, no `?`, no `\`, no
        // `{`/`}`, no `<`/`>`, no `` ` ``, no `|`, doesn't start with
        // `-` or `:`); RFC 3986 §2 lists `;` in the 'sub-delims' /
        // reserved set and the WHATWG URL spec's fragment percent-
        // encode set maps `;` → `%3B` on the wire, so the byte rides
        // verbatim into the lacre's per-dep BLAKE3 closure but is
        // silently rewritten at libcurl's URL-parser layer — two
        // authors whose values differ only in their sequential-command
        // tail (`; rm -rf build` vs nothing) resolve to the byte-
        // identical upstream `git clone` but lock to two distinct
        // lacres, defeating the THEORY.md §V.2 render-determinism
        // contract. Peer with the `:caminho` axis's
        // `FonteCaminhoShellSemicolon` arm (05c358e) on the sibling
        // path-fonte axis, and `is_gateway_api_http_path`'s eleven-
        // byte RFC-3986-reserved set on `:entrada :paths`.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia; rm -rf build".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/caixa-teia; rm -rf build");
        assert!(
            reason.contains("must not contain `;`"),
            "reason must surface the shell-command-separator arm, got {reason:?}"
        );
        assert!(
            reason.contains("sequential-command") || reason.contains("'sub-delims'"),
            "reason must name the shell-command-separator / RFC-3986-sub-delims \
             rationale, got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_semicolon_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the semicolon arm are
        // both per-byte arms inside the same `for &b in s.as_bytes()`
        // loop, so the byte that appears first in the value's byte
        // order wins. A `:repo "https://github.com/p/x#readme; rm"`
        // carries both `#` and `;`; the `#` byte appears first, so the
        // fragment-`#` arm fires, surfacing the more self-locating
        // diagnostic on the byte the author pasted earliest in the URL.
        // Mirrors the peer cascade discipline
        // `fonte_repo_fragment_fires_before_pipe_when_fragment_first`
        // pins on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme; rm".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before semicolon when `#` \
             byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_pipe_fires_before_semicolon_when_pipe_first() {
        // Cascade pin: the pipe arm and the semicolon arm are both
        // per-byte arms inside the same `for &b in s.as_bytes()` loop,
        // so the byte that appears first in the value's byte order
        // wins. A `:repo "https://github.com/p/x|tee; rm"` carries
        // both `|` and `;`; the `|` byte appears first, so the
        // pipe arm fires, surfacing the more self-locating diagnostic
        // on the byte the author pasted earliest in the URL. Pins the
        // natural-order cascade so a future reorder of the per-byte
        // arms surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia|tee; rm".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `|`"),
            "reason must surface the pipe arm (fires before semicolon when `|` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_shell_background() {
        // The fail-before-pass-after pin for the canonical
        // paste-from-shell-prompt-with-background-launch-tail footgun
        // on `:repo` (peer with the e12e4f3 `&` arm on the sibling
        // `:caminho` path-fonte axis). An author pastes a shell one-
        // liner that detached the clone into the background
        // (`git clone <url> & sleep 1`, `git clone <url> && cd …`)
        // into the `:repo` slot, forgetting to trim the `& <cmd>` /
        // `&& <cmd>` tail. Until this arm landed the value silently
        // passed every prior `is_git_repo_url` arm (no whitespace,
        // no control chars, no non-ASCII, no `#`, no `?`, no `\`,
        // no `{`/`}`, no `<`/`>`, no `` ` ``, no `|`, no `;`,
        // doesn't start with `-` or `:`); RFC 3986 §2 lists `&` in
        // the 'sub-delims' / reserved set and the WHATWG URL spec's
        // fragment percent-encode set maps `&` → `%26` on the wire,
        // so the byte rides verbatim into the lacre's per-dep
        // BLAKE3 closure but is silently rewritten at libcurl's
        // URL-parser layer — two authors whose values differ only
        // in their background-launch tail (`& sleep 1` vs nothing)
        // resolve to the byte-identical upstream `git clone` but
        // lock to two distinct lacres, defeating the THEORY.md
        // §V.2 render-determinism contract. Peer with the
        // `:caminho` axis's `FonteCaminhoShellBackground` arm
        // (e12e4f3) on the sibling path-fonte axis, and
        // `is_gateway_api_http_path`'s eleven-byte RFC-3986-
        // reserved set on `:entrada :paths`.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia&sleep".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/caixa-teia&sleep");
        assert!(
            reason.contains("must not contain `&`"),
            "reason must surface the shell-background / logical-AND arm, got {reason:?}"
        );
        assert!(
            reason.contains("background-task") || reason.contains("'sub-delims'"),
            "reason must name the shell-background / RFC-3986-sub-delims rationale, \
             got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_logical_and() {
        // The fail-before-pass-after pin for the symmetric `&&`
        // logical-AND build-chain paste footgun: an author pastes
        // a `git clone <url> && cd <repo>` build-chain one-liner
        // and forgets to trim the `&& <cmd>` tail. The `&&` shape
        // is the same `&` byte twice in a row; the per-byte arm
        // fires on the first `&` it sees. Pinned separately from
        // the single-`&` background-launch shape so a future
        // diagnostic-surface change that special-cased the
        // doubled-byte form surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia&&echo".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `&`"),
            "reason must surface the shell-background / logical-AND arm on the doubled-`&&` \
             shape too, got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_background_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the background-`&`
        // arm are both per-byte arms inside the same `for &b in
        // s.as_bytes()` loop, so the byte that appears first in the
        // value's byte order wins. A `:repo
        // "https://github.com/p/x#readme & sleep"` carries both `#`
        // and `&`; the `#` byte appears first, so the fragment-`#`
        // arm fires, surfacing the more self-locating diagnostic on
        // the byte the author pasted earliest in the URL. Mirrors
        // the peer cascade discipline
        // `fonte_repo_fragment_fires_before_semicolon_when_fragment_first`
        // on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme&sleep".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before background-`&` when `#` \
             byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_semicolon_fires_before_background_when_semicolon_first() {
        // Cascade pin: the semicolon arm and the background-`&` arm
        // are both per-byte arms inside the same `for &b in
        // s.as_bytes()` loop, so the byte that appears first in the
        // value's byte order wins. A `:repo
        // "https://github.com/p/x; rm & sleep"` carries both `;` and
        // `&`; the `;` byte appears first, so the semicolon arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Pins the
        // natural-order cascade so a future reorder of the per-byte
        // arms surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia;rm&sleep".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `;`"),
            "reason must surface the semicolon arm (fires before background-`&` when `;` \
             byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_shell_variable_expansion() {
        // The fail-before-pass-after pin for the canonical
        // paste-from-shell-prompt-with-unsubstituted-variable footgun
        // on `:repo` (peer with the f4efe9c `$` arm on the sibling
        // `:caminho` path-fonte axis). An author pastes a shell one-
        // liner that referenced an environment variable
        // (`git clone https://github.com/$ORG/x`, `git clone
        // github:$USER/repo`) into the `:repo` slot, forgetting to
        // substitute the literal value at author time. Until this arm
        // landed the value silently passed every prior
        // `is_git_repo_url` arm (no whitespace, no control chars, no
        // non-ASCII, no `#`, no `?`, no `\`, no `{`/`}`, no `<`/`>`,
        // no `` ` ``, no `|`, no `;`, no `&`, doesn't start with `-`
        // or `:`); RFC 3986 §2 lists `$` in the 'sub-delims' /
        // reserved set and the WHATWG URL spec's fragment percent-
        // encode set maps `$` → `%24` on the wire, so the byte rides
        // verbatim into the lacre's per-dep BLAKE3 closure but is
        // silently rewritten at libcurl's URL-parser layer — two
        // authors whose values differ only in their `$VAR` /
        // `${VAR}` / `$(cmd)` expansion tail resolve to the byte-
        // identical upstream `git clone` but lock to two distinct
        // lacres, defeating the THEORY.md §V.2 render-determinism
        // contract. Beyond determinism, the value is a structural
        // host-layout leak: two authors with the same `:repo` slot
        // but different `$ORG` / `$HOME` / `$WORKSPACE` resolve
        // different upstreams. Peer with the `:caminho` axis's
        // `FonteCaminhoVarExpansion` arm (f4efe9c) on the sibling
        // path-fonte axis, and `is_gateway_api_http_path`'s eleven-
        // byte RFC-3986-reserved set on `:entrada :paths`.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/$ORG/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/$ORG/caixa-teia");
        assert!(
            reason.contains("must not contain `$`"),
            "reason must surface the shell-variable-expansion arm, got {reason:?}"
        );
        assert!(
            reason.contains("variable-expansion") || reason.contains("'sub-delims'"),
            "reason must name the shell-variable-expansion / RFC-3986-sub-delims \
             rationale, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_braced_variable_expansion() {
        // The fail-before-pass-after pin for the symmetric POSIX-
        // shell braced `${VAR}` expansion paste footgun: an author
        // pastes a CI-manifest line `git clone
        // https://github.com/${WORKSPACE}/x` (the canonical GitHub
        // Actions / GitLab CI / Drone shape) and forgets to
        // substitute the literal value. The `${...}` shape is the
        // same `$` byte at the leading position of the expansion;
        // the per-byte arm fires on the `$`. Pinned separately from
        // the bare-`$VAR` shape so a future diagnostic-surface
        // change that special-cased the braced form surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/${WORKSPACE}/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `$`"),
            "reason must surface the shell-variable-expansion arm on the braced `${{...}}` \
             shape too, got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_var_expansion_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the var-expansion-`$`
        // arm are both per-byte arms inside the same `for &b in
        // s.as_bytes()` loop, so the byte that appears first in the
        // value's byte order wins. A `:repo
        // "https://github.com/p/x#readme$HOME"` carries both `#` and
        // `$`; the `#` byte appears first, so the fragment-`#` arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Mirrors the
        // peer cascade discipline
        // `fonte_repo_fragment_fires_before_background_when_fragment_first`
        // on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme$HOME".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before var-expansion-`$` when \
             `#` byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_background_fires_before_var_expansion_when_background_first() {
        // Cascade pin: the background-`&` arm and the
        // var-expansion-`$` arm are both per-byte arms inside the
        // same `for &b in s.as_bytes()` loop, so the byte that
        // appears first in the value's byte order wins. A `:repo
        // "https://github.com/p/x&sleep$HOME"` carries both `&` and
        // `$`; the `&` byte appears first, so the background arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Pins the
        // natural-order cascade so a future reorder of the per-byte
        // arms surfaces here — `$` is the most recent byte-class arm,
        // so the cascade-pin sweep extends to cover every immediately
        // prior byte arm (`#`, `&`) firing first when ordered ahead
        // of `$` in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia&sleep$HOME".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `&`"),
            "reason must surface the background-`&` arm (fires before var-expansion-`$` when \
             `&` byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_shell_glob_wildcard() {
        // The fail-before-pass-after pin for the canonical
        // paste-from-shell-prompt glob footgun on `:repo` (peer with
        // the cf9034b `*` / `?` arm on the sibling `:caminho`
        // path-fonte axis). An author pastes a shell one-liner that
        // referenced a glob expansion (`ls
        // github.com/pleme-io/caixa-*`, `git clone
        // github:pleme-io/caixa-*`) into the `:repo` slot, forgetting
        // to substitute the literal repo name. Until this arm landed
        // the `*` byte silently passed every prior `is_git_repo_url`
        // arm (no whitespace, no control chars, no non-ASCII, no `#`,
        // no `?`, no `\`, no `{`/`}`, no `<`/`>`, no `` ` ``, no `|`,
        // no `;`, no `&`, no `$`, doesn't start with `-` or `:`); RFC
        // 3986 §2 lists `*` in the 'sub-delims' / reserved set and
        // the WHATWG URL spec's special-query percent-encode set maps
        // `*` → `%2A` on the wire, so the byte rides verbatim into
        // the lacre's per-dep BLAKE3 closure but is silently
        // rewritten at libcurl's URL-parser layer — two authors
        // whose values differ only in their asterisk presence
        // resolve to the byte-identical upstream `git clone` but
        // lock to two distinct lacres, defeating the THEORY.md §V.2
        // render-determinism contract. Peer with the `:caminho`
        // axis's `FonteCaminhoShellGlob` arm (cf9034b) on the
        // sibling path-fonte axis, and the `is_git_ref_name`
        // refspec-wildcard cascade on the `:fonte :tag` / `:branch`
        // axes.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-*".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/caixa-*");
        assert!(
            reason.contains("must not contain `*`"),
            "reason must surface the shell-glob arm, got {reason:?}"
        );
        assert!(
            reason.contains("pathname-expansion") || reason.contains("'sub-delims'"),
            "reason must name the shell-glob / pathname-expansion / \
             RFC-3986-sub-delims rationale, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_recursive_shell_glob() {
        // The fail-before-pass-after pin for the symmetric bash
        // `globstar` recursive-glob paste footgun: an author pastes
        // a `ls github.com/pleme-io/**/x` (the canonical
        // `globstar`-shopt-enabled recursive-listing tail) into the
        // `:repo` slot. The `**` shape is two `*` bytes adjacent;
        // the per-byte arm fires on the first `*`. Pinned
        // separately from the single-`*` shape so a future
        // diagnostic-surface change that special-cased the
        // double-`*` form surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/**/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `*`"),
            "reason must surface the shell-glob arm on the `**` recursive-glob shape too, \
             got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_glob_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the glob-`*` arm are
        // both per-byte arms inside the same `for &b in s.as_bytes()`
        // loop, so the byte that appears first in the value's byte
        // order wins. A `:repo
        // "https://github.com/p/x#readme*tail"` carries both `#` and
        // `*`; the `#` byte appears first, so the fragment-`#` arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Mirrors the
        // peer cascade discipline
        // `fonte_repo_fragment_fires_before_var_expansion_when_fragment_first`
        // on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme*tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before glob-`*` when `#` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_var_expansion_fires_before_glob_when_var_expansion_first() {
        // Cascade pin: the var-expansion-`$` arm and the glob-`*`
        // arm are both per-byte arms inside the same `for &b in
        // s.as_bytes()` loop, so the byte that appears first in the
        // value's byte order wins. A `:repo
        // "https://github.com/p/$ORG-*"` carries both `$` and `*`;
        // the `$` byte appears first, so the var-expansion arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Pins the
        // natural-order cascade so a future reorder of the per-byte
        // arms surfaces here — `*` is the most recent byte-class
        // arm, so the cascade-pin sweep extends to cover the
        // immediately prior `$` byte arm firing first when ordered
        // ahead of `*` in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/$ORG-caixa-*".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `$`"),
            "reason must surface the var-expansion-`$` arm (fires before glob-`*` when `$` \
             byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_subshell_open_paren() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // shell-prompt subshell-grouping footgun on `:repo`. An author
        // pastes a doc / README snippet carrying a regex-alternation
        // grouping shape (`https://github.com/(foo|bar)/repo`) or a
        // dynamic-config-substitution wrapper (`$(<cmd>)`) into the
        // `:repo` slot, forgetting to substitute one literal org name.
        // Until this arm landed the `(` byte silently passed every
        // prior `is_git_repo_url` arm (no whitespace, no control
        // chars, no non-ASCII, no `#`, no `?`, no `\`, no `{`/`}`, no
        // `<`/`>`, no `` ` ``, no `|`, no `;`, no `&`, no `$`, no
        // `*`, doesn't start with `-` or `:`); RFC 3986 §2 lists `(`
        // / `)` in the 'sub-delims' / reserved set, and the WHATWG
        // URL spec's special-query percent-encode set maps `(` →
        // `%28` and `)` → `%29` on the wire, so the byte rides
        // verbatim into the lacre's per-dep BLAKE3 closure but is
        // silently rewritten at libcurl's URL-parser layer —
        // defeating the THEORY.md §V.2 render-determinism contract on
        // the same axis the prior twelve byte-class arms close.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/(foo|bar)/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/(foo|bar)/caixa-teia");
        assert!(
            reason.contains("must not contain `(`"),
            "reason must surface the subshell-open-paren arm, got {reason:?}"
        );
        assert!(
            reason.contains("subshell-grouping") || reason.contains("'sub-delims'"),
            "reason must name the shell-subshell-grouping / RFC-3986-sub-delims rationale, \
             got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_subshell_close_paren() {
        // The symmetric arm pin on the closing `)` byte: an author
        // pastes a `$(date)` command-substitution wrapper or a
        // regex-alternation `(foo|bar)` tail into the `:repo` slot.
        // Pinned separately from the opening `(` shape so a future
        // diagnostic-surface change that only checked one boundary
        // surfaces here. The `(` byte appears earlier in the
        // canonical regex / subshell wrapper so the per-byte loop
        // fires on `(` first; this test exercises a `:repo` value
        // carrying only the closing `)` byte (no opening paren) so
        // the `)` arm fires directly — pinning the byte-class arm
        // independent of order.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia)tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `)`"),
            "reason must surface the subshell-close-paren arm on the bare `)` shape, \
             got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_subshell_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the subshell-`(` arm
        // are both per-byte arms inside the same `for &b in
        // s.as_bytes()` loop, so the byte that appears first in the
        // value's byte order wins. A `:repo
        // "https://github.com/p/x#readme(tail)"` carries both `#` and
        // `(`; the `#` byte appears first, so the fragment-`#` arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Mirrors the
        // peer cascade discipline
        // `fonte_repo_fragment_fires_before_glob_when_fragment_first`
        // on the prior `:repo` byte-class arm.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme(tail)".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before subshell-`(` when `#` \
             byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_glob_fires_before_subshell_when_glob_first() {
        // Cascade pin: the glob-`*` arm (the immediate-predecessor
        // byte-class arm, 3902a9a) and the subshell-`(` arm are both
        // per-byte arms inside the same `for &b in s.as_bytes()`
        // loop, so the byte that appears first in the value's byte
        // order wins. A `:repo
        // "https://github.com/p/x-*-(date)"` carries both `*` and
        // `(`; the `*` byte appears first, so the glob arm fires,
        // surfacing the more self-locating diagnostic on the byte
        // the author pasted earliest in the URL. Pins the natural-
        // order cascade so a future reorder of the per-byte arms
        // surfaces here — `(` is the most recent byte-class arm,
        // so the cascade-pin sweep extends to cover the immediately
        // prior `*` byte arm firing first when ordered ahead of `(`
        // in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia-*-(date)".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `*`"),
            "reason must surface the glob-`*` arm (fires before subshell-`(` when `*` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_shell_double_quote() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // doc-shell-quoting footgun on `:repo`. An author copies a
        // README quick-start snippet (`$ git clone "https://github.com/
        // foo/bar"`) and keeps the surrounding double-quote bytes when
        // pasting into the `:repo` slot — the doc wraps the URL in
        // double quotes so the shell doesn't re-lex metachars inside,
        // but the typed slot is itself a byte-level string parser, not
        // a shell context, so the quote bytes ride into the value
        // verbatim. Until this arm landed the `"` byte silently passed
        // every prior `is_git_repo_url` arm (no whitespace, no control
        // chars, no non-ASCII, no `#`, no `?`, no `\`, no `{`/`}`, no
        // `<`/`>`, no `` ` ``, no `|`, no `;`, no `&`, no `$`, no `*`,
        // no `(`/`)`, doesn't start with `-` or `:`); RFC 3986 §2 lists
        // `"` in the strict four-byte 'delims' subset (with `<`, `>`,
        // `` ` ``) every URL parser is required to refuse or percent-
        // encode, and the WHATWG URL spec's 'C0 control percent-encode
        // set' maps `"` → `%22` on the wire, so the byte rides verbatim
        // into the lacre's per-dep BLAKE3 closure but is silently
        // rewritten at libcurl's URL-parser layer, defeating the
        // THEORY.md §V.2 render-determinism contract.
        let d = dep_with_fonte(DepSource::Git {
            repo: "\"https://github.com/pleme-io/caixa-teia\"".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "\"https://github.com/pleme-io/caixa-teia\"");
        assert!(
            reason.contains("must not contain `\"`"),
            "reason must surface the shell-double-quote arm, got {reason:?}"
        );
        assert!(
            reason.contains("double-quote") || reason.contains("'delims'"),
            "reason must name the shell-double-quote / RFC-3986-delims rationale, \
             got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_stray_trailing_double_quote() {
        // The symmetric stray-quote tail pin: an author pastes only a
        // closing `"` from a shell-history line like `git clone
        // "https://github.com/foo/bar" && cd …` (the trim went too
        // far in one direction but not the other) into the `:repo`
        // slot. Pinned separately from the wrapped-quote shape so a
        // future diagnostic-surface change that only checked one
        // boundary (only leading, only trailing, only paired) surfaces
        // here — the per-byte arm fires anywhere `"` appears.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia\"".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `\"`"),
            "reason must surface the shell-double-quote arm on the trailing-`\"` shape, \
             got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_double_quote_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the double-quote arm
        // are both per-byte arms inside the same `for &b in
        // s.as_bytes()` loop, so the byte that appears first in the
        // value's byte order wins. A `:repo
        // "https://github.com/p/x#readme\"tail"` carries both `#` and
        // `"`; the `#` byte appears first, so the fragment-`#` arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme\"tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before double-quote when `#` \
             byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_subshell_fires_before_double_quote_when_subshell_first() {
        // Cascade pin: the subshell-`(` arm (the immediate-predecessor
        // byte-class arm, 3b99147) and the double-quote arm are both
        // per-byte arms inside the same `for &b in s.as_bytes()` loop,
        // so the byte that appears first in the value's byte order
        // wins. A `:repo "github:p/x(date)\"tail"` carries both `(`
        // and `"`; the `(` byte appears first, so the subshell arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Pins the natural-
        // order cascade so a future reorder of the per-byte arms
        // surfaces here — `"` is the most recent byte-class arm, so
        // the cascade-pin sweep extends to cover the immediately prior
        // `(` byte arm firing first when ordered ahead of `"` in the
        // value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia(date)\"tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `(`"),
            "reason must surface the subshell-`(` arm (fires before double-quote when `(` \
             byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_shell_single_quote() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // doc-strong-quoting footgun on `:repo`. An author copies a
        // security-conscious README quick-start snippet (`$ git clone
        // 'https://github.com/foo/bar'`) and keeps the surrounding
        // single-quote bytes when pasting into the `:repo` slot — the
        // doc strong-quotes the URL so the shell suppresses every form
        // of expansion on the bytes inside (no `$`, no backtick, no
        // glob, no word-splitting), but the typed slot is itself a
        // byte-level string parser, not a shell context, so the quote
        // bytes ride into the value verbatim. Until this arm landed the
        // `'` byte silently passed every prior `is_git_repo_url` arm
        // (no whitespace, no control chars, no non-ASCII, no `#`, no
        // `?`, no `\`, no `{`/`}`, no `<`/`>`, no `` ` ``, no `|`, no
        // `;`, no `&`, no `$`, no `*`, no `(`/`)`, no `"`, doesn't start
        // with `-` or `:`); RFC 3986 §2.2 lists `'` in the 'sub-delims'
        // set, peer with the `\"` 'delims' double-quote arm and the
        // partner ASCII shell-string-delimiter byte every byte-level
        // string parser sharing a value-shape with a shell argument
        // must refuse on a URL-shaped slot.
        let d = dep_with_fonte(DepSource::Git {
            repo: "'https://github.com/pleme-io/caixa-teia'".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "'https://github.com/pleme-io/caixa-teia'");
        assert!(
            reason.contains("must not contain `'`"),
            "reason must surface the shell-single-quote arm, got {reason:?}"
        );
        assert!(
            reason.contains("single-quote") || reason.contains("strong-quote"),
            "reason must name the shell-single-quote / strong-quote rationale, \
             got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_english_apostrophe() {
        // The symmetric English-typography pin: an author writes
        // `:repo "github:p/repo's-fork"` (the possessive-form paste-
        // from-prose idiom every README / commit-message / chat-thread
        // reference to a repo carries) expecting the substrate to
        // coerce it to a kebab-case slug — but the byte rides into the
        // lacre verbatim. Pinned separately from the wrapped-quote
        // shape so a future diagnostic-surface change that only checked
        // the boundary positions (only leading, only trailing, only
        // paired) surfaces here — the per-byte arm fires anywhere `'`
        // appears in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/repo's-fork".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `'`"),
            "reason must surface the shell-single-quote arm on the mid-string \
             apostrophe shape, got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_single_quote_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the single-quote arm
        // are both per-byte arms inside the same `for &b in
        // s.as_bytes()` loop, so the byte that appears first in the
        // value's byte order wins. A `:repo
        // "https://github.com/p/x#readme'tail"` carries both `#` and
        // `'`; the `#` byte appears first, so the fragment-`#` arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme'tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before single-quote when `#` \
             byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_double_quote_fires_before_single_quote_when_double_quote_first() {
        // Cascade pin: the double-quote-`"` arm (the immediate-predecessor
        // byte-class arm, 4267d8b) and the single-quote arm are both
        // per-byte arms inside the same `for &b in s.as_bytes()` loop,
        // so the byte that appears first in the value's byte order
        // wins. A `:repo "github:p/x\"mid'tail"` carries both `"` and
        // `'`; the `"` byte appears first, so the double-quote arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Pins the natural-
        // order cascade so a future reorder of the per-byte arms
        // surfaces here — `'` is the most recent byte-class arm, so
        // the cascade-pin sweep extends to cover the immediately prior
        // `"` byte arm firing first when ordered ahead of `'` in the
        // value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia\"mid'tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `\"`"),
            "reason must surface the double-quote arm (fires before single-quote when `\"` \
             byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_shell_history_expansion() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // shell-history footgun on `:repo`. An author copies a `git
        // clone <url>!sudo make install` one-liner from a README's
        // quick-start snippet, intending the trailing `!sudo` as a
        // shell-history-expansion reference but the typed slot is itself
        // a byte-level string parser, not a shell context, so the byte
        // rides into the value verbatim. Until this arm landed the `!`
        // byte silently passed every prior `is_git_repo_url` arm (no
        // whitespace, no control chars, no non-ASCII, no `#`, no `?`,
        // no `\`, no `{`/`}`, no `<`/`>`, no `` ` ``, no `|`, no `;`,
        // no `&`, no `$`, no `*`, no `(`/`)`, no `"`, no `'`, doesn't
        // start with `-` or `:`); bash with the default `histexpand`
        // mode rewrites `!command` to the most recent history entry
        // beginning with `command`, the canonical RCE-class injection
        // vector when the byte rides into a shell argument.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia!sudo".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/caixa-teia!sudo");
        assert!(
            reason.contains("must not contain `!`"),
            "reason must surface the shell-history-expansion arm, got {reason:?}"
        );
        assert!(
            reason.contains("history-expansion") || reason.contains("bang"),
            "reason must name the shell-history-expansion / bang rationale, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_double_bang_history_reference() {
        // The symmetric `!!` repeat-prior-command pin: an author paste-
        // trims a `git clone <url>` retry idiom from shell history that
        // expands to the previous command via `!!`. Pinned separately
        // from the wrapped `!command` shape so a future diagnostic-
        // surface change that only checked the leading or paired-bang
        // position surfaces here — the per-byte arm fires anywhere `!`
        // appears in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia!!".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `!`"),
            "reason must surface the shell-history-expansion arm on the trailing-`!!` shape, \
             got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_bang_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the bang arm are both
        // per-byte arms inside the same `for &b in s.as_bytes()` loop,
        // so the byte that appears first in the value's byte order
        // wins. A `:repo "https://github.com/p/x#readme!tail"` carries
        // both `#` and `!`; the `#` byte appears first, so the
        // fragment-`#` arm fires, surfacing the more self-locating
        // diagnostic on the byte the author pasted earliest in the URL.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme!tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before bang when `#` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_single_quote_fires_before_bang_when_single_quote_first() {
        // Cascade pin: the single-quote-`'` arm (the immediate-predecessor
        // byte-class arm, e7a109f) and the bang arm are both per-byte
        // arms inside the same `for &b in s.as_bytes()` loop, so the
        // byte that appears first in the value's byte order wins. A
        // `:repo "github:p/x'mid!tail"` carries both `'` and `!`; the
        // `'` byte appears first, so the single-quote arm fires,
        // surfacing the more self-locating diagnostic on the byte the
        // author pasted earliest in the URL. Pins the natural-order
        // cascade so a future reorder of the per-byte arms surfaces
        // here — `!` is the most recent byte-class arm, so the
        // cascade-pin sweep extends to cover the immediately prior `'`
        // byte arm firing first when ordered ahead of `!` in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia'mid!tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `'`"),
            "reason must surface the single-quote arm (fires before bang when `'` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_list_separator_comma() {
        // The fail-before-pass-after pin for the canonical
        // list-separator-belongs-to-list-grammar footgun on `:repo`.
        // An author copies a `git clone <a>, <b>, <c>` paste-from-CSV
        // one-liner from a multi-repo bootstrap doc, intending the
        // comma to separate multiple repo entries but the typed
        // `:repo` slot names *one* repo (the list-separator belongs
        // to the `:deps` list grammar, not to the value). Until this
        // arm landed the `,` byte silently passed every prior
        // `is_git_repo_url` arm (no whitespace, no control chars, no
        // non-ASCII, no `#`, no `?`, no `\`, no `{`/`}`, no `<`/`>`,
        // no `` ` ``, no `|`, no `;`, no `&`, no `$`, no `*`, no
        // `(`/`)`, no `"`, no `'`, no `!`, doesn't start with `-` or
        // `:`); the byte rode into the lacre's per-dep content-
        // address and the resolver's `git clone <repo>` subprocess
        // invocation, where no host's repo registry resolved the
        // comma-bearing slug.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia,github:pleme-io/caixa-feira".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(
            repo,
            "github:pleme-io/caixa-teia,github:pleme-io/caixa-feira"
        );
        assert!(
            reason.contains("must not contain `,`"),
            "reason must surface the list-separator-comma arm, got {reason:?}"
        );
        assert!(
            reason.contains("list-separator") || reason.contains("sub-delims"),
            "reason must name the list-separator / RFC-3986-sub-delims rationale, \
             got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_trailing_comma() {
        // The symmetric trailing-`,` paste-from-prose pin: an author
        // writes `:repo "github:pleme-io/caixa-feira,"` (the trailing
        // comma every README-prose list-of-projects sentence carries,
        // mistakenly retained when the slug is pasted mid-sentence)
        // expecting the substrate to coerce it to a kebab-case slug.
        // Pinned separately from the wrapped mid-token shape so a
        // future diagnostic-surface change that only checked the
        // leading or paired-comma position surfaces here — the
        // per-byte arm fires anywhere `,` appears in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-feira,".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `,`"),
            "reason must surface the list-separator-comma arm on the trailing-`,` shape, \
             got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_comma_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the comma arm are
        // both per-byte arms inside the same `for &b in s.as_bytes()`
        // loop, so the byte that appears first in the value's byte
        // order wins. A `:repo "https://github.com/p/x#readme,tail"`
        // carries both `#` and `,`; the `#` byte appears first, so
        // the fragment-`#` arm fires, surfacing the more self-
        // locating diagnostic on the byte the author pasted earliest
        // in the URL.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme,tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before comma when `#` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_bang_fires_before_comma_when_bang_first() {
        // Cascade pin: the bang-`!` arm (the immediate-predecessor
        // byte-class arm, 7d53c68) and the comma arm are both
        // per-byte arms inside the same `for &b in s.as_bytes()`
        // loop, so the byte that appears first in the value's byte
        // order wins. A `:repo "github:p/x!mid,tail"` carries both
        // `!` and `,`; the `!` byte appears first, so the bang arm
        // fires, surfacing the more self-locating diagnostic on the
        // byte the author pasted earliest in the URL. Pins the
        // natural-order cascade so a future reorder of the per-byte
        // arms surfaces here — `,` is the most recent byte-class
        // arm, so the cascade-pin sweep extends to cover the
        // immediately prior `!` byte arm firing first when ordered
        // ahead of `,` in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia!mid,tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `!`"),
            "reason must surface the bang arm (fires before comma when `!` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_shell_env_var_assignment() {
        // The fail-before-pass-after pin for the canonical
        // shell-env-var-assignment-belongs-to-shell-grammar footgun
        // on `:repo`. An author copies
        // `GIT_TERMINAL_PROMPT=0 git clone <url>` (or
        // `GIT_SSL_NO_VERIFY=1 git clone <url>`, `HTTPS_PROXY=…
        // git clone <url>`, etc. — the canonical
        // git-troubleshooting README idiom for a one-shot env-var
        // scoped to the `git clone` invocation) from a shell-prompt
        // one-liner, intending the `KEY=VALUE` prefix as a shell-
        // grammar env-var assignment but the typed `:repo` slot is
        // a value parser, not a shell context, so the bytes ride
        // into the value verbatim. Until this arm landed the `=`
        // byte silently passed every prior `is_git_repo_url` arm
        // (no whitespace, no control chars, no non-ASCII, no `#`,
        // no `?`, no `\`, no `{`/`}`, no `<`/`>`, no `` ` ``, no
        // `|`, no `;`, no `&`, no `$`, no `*`, no `(`/`)`, no `"`,
        // no `'`, no `!`, no `,`, doesn't start with `-` or `:`);
        // the byte rode into the lacre's per-dep content-address
        // and the resolver's `git clone <repo>` subprocess
        // invocation, where the upstream host's git porcelain
        // fetched a literal `GIT_TERMINAL_PROMPT=0 https://…`-shaped
        // path that no host's repo registry resolves.
        let d = dep_with_fonte(DepSource::Git {
            repo: "GIT_TERMINAL_PROMPT=0 https://github.com/pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(
            repo,
            "GIT_TERMINAL_PROMPT=0 https://github.com/pleme-io/caixa-teia"
        );
        // The `=` byte at position 19 of `GIT_TERMINAL_PROMPT=0 …`
        // appears before the ` ` byte at position 21, so the `=`
        // arm fires (not the whitespace arm) — both arms guard
        // the slot, but the per-byte for-loop scans left-to-right
        // and the first matching byte wins.
        assert!(
            reason.contains("must not contain `=`"),
            "reason must surface the equals-`=` arm on the env-var-assignment \
             paste shape, got {reason:?}"
        );
        assert!(
            reason.contains("env-var-assignment") || reason.contains("KEY=VALUE"),
            "reason must name the shell-env-var-assignment rationale, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_gitconfig_url_key_prefix() {
        // The symmetric paste-from-gitconfig pin: an author copies
        // `url=https://github.com/p/x` from `git config --get-all
        // remote.origin.url` output, a `.gitconfig` `[remote
        // "origin"] url = https://…` ini-stanza paste, or a
        // `git config remote.origin.url <value>` doc snippet,
        // intending the `url=` prefix as the ini-key but the typed
        // `:repo` slot is a URL value parser, not a gitconfig
        // grammar. With no leading whitespace and no earlier-arm
        // bytes in the value, the `=` arm itself fires (rather
        // than cascading to the whitespace arm as in the env-var
        // paste shape). Pinned separately so a future diagnostic-
        // surface change that only checked the whitespace-leading
        // shape surfaces here — the per-byte arm fires anywhere
        // `=` appears in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "url=https://github.com/pleme-io/caixa-feira".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `=`"),
            "reason must surface the equals-`=` arm on the `url=…` gitconfig \
             paste shape, got {reason:?}"
        );
        assert!(
            reason.contains("key-value-separator") || reason.contains("sub-delims"),
            "reason must name the key-value-separator / RFC-3986-sub-delims \
             rationale, got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_equals_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the `=` arm are
        // both per-byte arms inside the same `for &b in s.as_bytes()`
        // loop, so the byte that appears first in the value's byte
        // order wins. A `:repo "https://github.com/p/x#readme=tail"`
        // carries both `#` and `=`; the `#` byte appears first, so
        // the fragment-`#` arm fires, surfacing the more self-
        // locating diagnostic on the byte the author pasted earliest
        // in the URL.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#readme=tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before equals when \
             `#` byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_comma_fires_before_equals_when_comma_first() {
        // Cascade pin: the comma-`,` arm (the immediate-predecessor
        // byte-class arm, 775b80e) and the `=` arm are both per-byte
        // arms inside the same `for &b in s.as_bytes()` loop, so
        // the byte that appears first in the value's byte order
        // wins. A `:repo "github:p/x,mid=tail"` carries both `,`
        // and `=`; the `,` byte appears first, so the comma arm
        // fires, surfacing the more self-locating diagnostic on
        // the byte the author pasted earliest in the URL. Pins the
        // natural-order cascade so a future reorder of the per-byte
        // arms surfaces here — `=` is the most recent byte-class
        // arm, so the cascade-pin sweep extends to cover the
        // immediately prior `,` byte arm firing first when ordered
        // ahead of `=` in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia,mid=tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `,`"),
            "reason must surface the comma arm (fires before equals when `,` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_percent_encoded_space() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // browser-address-bar percent-encoded-space footgun on `:repo`.
        // An author copies `https://github.com/p/x%20test` from a
        // browser address bar (or a percent-encoded README hyperlink,
        // or a `curl --data-urlencode` shell-pipeline output)
        // intending `%20` as the URL encoding of a literal space; the
        // typed `:repo` slot already rejects the literal space byte
        // (the whitespace arm at the top of `is_git_repo_url`), so an
        // author trying to express "I really meant a space" reaches
        // for percent-encoding. Until this arm landed the `%` byte
        // silently passed every prior `is_git_repo_url` arm and rode
        // verbatim into the lacre's per-dep content-address — but
        // libcurl re-percent-encodes `%` to `%25` on the wire (since
        // `%` is reserved as the escape-sequence lead-in), so the
        // wire request becomes `https://github.com/p/x%2520test`, a
        // path the lacre's content-address never names. The classic
        // render-determinism violation on the encoding-mechanism axis
        // itself.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia%20test".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/caixa-teia%20test");
        assert!(
            reason.contains("must not contain `%`"),
            "reason must surface the percent-`%` arm on the percent-encoded-space \
             paste shape, got {reason:?}"
        );
        assert!(
            reason.contains("percent-encoding") || reason.contains("%25"),
            "reason must name the percent-encoding / `%25` re-encoding rationale, \
             got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_percent_encoded_slash() {
        // The symmetric over-encoded-path-separator pin: an author
        // writes `:repo "https://github.com/p%2Fx"` intending the
        // `%2F` as the URL encoding of `/` (the canonical
        // paste-from-OpenAPI-spec / paste-from-percent-encoded-template
        // footgun every API client library and OAuth redirect-URI
        // documentation surfaces — the `/` is the URL-path-separator
        // and some templates percent-encode it to escape interpretation
        // as a path separator). The GitHub Smart-HTTP transport
        // resolves the URL's path-segment grammar before the
        // percent-decoding pass, so the value identifies a different
        // resource on the wire than the literal-`/` form the lacre's
        // content-address must agree with — two authors whose `:repo`
        // values differ only in their `/` vs `%2F` presence lock to
        // two distinct BLAKE3 closures for the byte-identical upstream
        // `git clone`. Pinned separately so a future diagnostic
        // surface that only catches the `%20` shape surfaces here too.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io%2Fcaixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `%`"),
            "reason must surface the percent-`%` arm on the over-encoded-path \
             shape, got {reason:?}"
        );
        assert!(
            reason.contains("render-determinism") || reason.contains("BLAKE3"),
            "reason must name the render-determinism / BLAKE3-closure rationale, \
             got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_fragment_fires_before_percent_when_fragment_first() {
        // Cascade pin: the fragment-`#` arm and the `%` arm are both
        // per-byte arms inside the same `for &b in s.as_bytes()` loop,
        // so the byte that appears first in the value's byte order
        // wins. A `:repo "https://github.com/p/x#sec%20tail"` carries
        // both `#` and `%`; the `#` byte appears first, so the
        // fragment-`#` arm fires, surfacing the more self-locating
        // diagnostic on the byte the author pasted earliest in the URL.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia#sec%20tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `#`"),
            "reason must surface the fragment-`#` arm (fires before percent when \
             `#` byte appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_equals_fires_before_percent_when_equals_first() {
        // Cascade pin: the equals-`=` arm (the immediate-predecessor
        // byte-class arm, acf99af) and the `%` arm are both per-byte
        // arms inside the same `for &b in s.as_bytes()` loop, so the
        // byte that appears first in the value's byte order wins.
        // A `:repo "github:p/x=mid%20tail"` carries both `=` and `%`;
        // the `=` byte appears first, so the equals arm fires,
        // surfacing the more self-locating diagnostic on the byte the
        // author pasted earliest in the URL. Pins the natural-order
        // cascade so a future reorder of the per-byte arms surfaces
        // here — `%` is the most recent byte-class arm, so the
        // cascade-pin sweep extends to cover the immediately prior
        // `=` byte arm firing first when ordered ahead of `%` in the
        // value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia=mid%20tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `=`"),
            "reason must surface the equals arm (fires before percent when `=` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_caret_history_substitution() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // shell-history footgun on `:repo`. An author copies a
        // `git clone <url>` line from their terminal followed by a
        // bash / ksh / zsh `^typo^fix^` quick-edit-and-rerun shell-
        // history shorthand (the `^old^new^` form re-runs the prior
        // history entry with the first `old` substituted by `new`,
        // bash's default behavior on interactive sessions with
        // `set -o histexpand`), forgetting to trim the trailing
        // `^...^...` shell-history fragment from the URL value. The
        // `^` byte sits in the RFC 3986 §2 'unwise' set (peer with
        // `{`, `}`, `|`, `\\` — the strictest of the §2 reserved
        // classes), the WHATWG URL spec's 'fragment percent-encode
        // set' maps `^` → `%5E` on the wire, so the byte rides
        // verbatim into the lacre's per-dep content-address but
        // libcurl re-encodes it to `%5E` at `git clone` time — the
        // classic render-determinism violation on the same axis the
        // peer `%`, `=`, `,`, `!`, `'`, `"`, `(`, `)`, `*`, `$`,
        // `&`, `;`, `|`, backtick, `<`, `>`, `{`, `}`, `\\`, `?`,
        // `#` arms close.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia^typo^fix".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "https://github.com/pleme-io/caixa-teia^typo^fix");
        assert!(
            reason.contains("must not contain `^`"),
            "reason must surface the caret-`^` arm on the paste-from-shell-history \
             shape, got {reason:?}"
        );
        assert!(
            reason.contains("history-substitution") || reason.contains("%5E"),
            "reason must name the shell-history-substitution / `%5E` wire-encoding \
             rationale, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_carrying_caret_regex_anchor() {
        // The symmetric paste-from-doc-grep-pipeline footgun: an
        // author writes `:repo "github:p/^archived"` after copying a
        // `grep '^archived'` regex-anchor / negation idiom from a
        // doc / README quick-listing snippet, expecting the substrate
        // to coerce it to a literal repo name. The byte rides
        // verbatim into the lacre's per-dep content-address and
        // diverges from the byte-identical literal `archived` form
        // every other author authored — the canonical render-
        // determinism violation pin on the second footgun shape the
        // caret-`^` arm closes.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/^archived".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `^`"),
            "reason must surface the caret-`^` arm on the regex-anchor shape, \
             got {reason:?}"
        );
        assert!(
            reason.contains("render-determinism") || reason.contains("BLAKE3"),
            "reason must name the render-determinism / BLAKE3-closure rationale, \
             got {reason:?}"
        );
    }

    #[test]
    fn fonte_repo_percent_fires_before_caret_when_percent_first() {
        // Cascade pin: the `%` arm (the immediate-predecessor byte-
        // class arm, a323db8) and the `^` arm are both per-byte arms
        // inside the same `for &b in s.as_bytes()` loop, so the byte
        // that appears first in the value's byte order wins. A
        // `:repo "https://github.com/p/x%20mid^tail"` carries both
        // `%` and `^`; the `%` byte appears first, so the percent
        // arm fires, surfacing the more self-locating diagnostic on
        // the byte the author pasted earliest in the URL. Pins the
        // natural-order cascade so a future reorder of the per-byte
        // arms surfaces here — `^` is the most recent byte-class arm,
        // so the cascade-pin sweep extends to cover the immediately
        // prior `%` byte arm firing first when ordered ahead of `^`
        // in the value.
        let d = dep_with_fonte(DepSource::Git {
            repo: "https://github.com/pleme-io/caixa-teia%20mid^tail".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not contain `%`"),
            "reason must surface the percent arm (fires before caret when `%` byte \
             appears first in value), got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_missing_colon_separator() {
        // The "I dropped the scheme" footgun — `:repo "pleme-io/caixa-teia"`
        // (no `github:` prefix, no scheme). Every documented form
        // carries a `:` (`github:`, `https://`, `ssh://`, `git://`,
        // `file://`, or `git@host:path`); a bare `org/repo` is
        // ambiguous (`git clone` reads as a relative filesystem path
        // rather than the GitHub-shorthand expansion the author
        // probably intended) and the gate rejects the shape upstream.
        let d = dep_with_fonte(DepSource::Git {
            repo: "pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must contain a `:`"),
            "reason must surface the missing-`:` arm, got {reason:?}"
        );
        assert!(
            reason.contains("github:"),
            "reason must name the canonical `github:` shorthand prefix, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_leading_colon() {
        // The "empty scheme" footgun — `:repo ":foo"` has a zero-length
        // scheme that no git porcelain entry-point accepts. Pinned
        // separately from the missing-`:` arm because a value with a
        // leading `:` does technically contain a `:` separator; the
        // shape gate rejects on a dedicated arm so the diagnostic
        // names the specific footgun.
        let d = dep_with_fonte(DepSource::Git {
            repo: ":pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("must not start with `:`"),
            "reason must surface the leading-`:` arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_repo_too_long() {
        // The cap arm — a `:repo` value longer than
        // [`crate::render::GIT_REPO_URL_MAX_LEN`] (2048) bytes is
        // structurally untenable on every realistic landing site (the
        // resolver's `git clone` invocation, the future M4 CR
        // materializer's per-dep `repo:` axis); a value of that length
        // is almost certainly a paste-from-binary slug.
        let too_long = format!(
            "github:pleme-io/{}",
            "x".repeat(crate::render::GIT_REPO_URL_MAX_LEN)
        );
        let d = dep_with_fonte(DepSource::Git {
            repo: too_long.clone(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { reason, .. } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert!(
            reason.contains("2048"),
            "reason must name the cap, got {reason:?}"
        );
    }

    #[test]
    fn validate_accepts_canonical_git_fonte_repo_shapes() {
        // The positive-control sweep: every documented author shape on
        // the `:fonte :repo` axis ([`crate::DepSource::Git`] doc comment)
        // must pass the value-shape gate. Pinned so a future tightening
        // (e.g. forbidding `http://` in favor of `https://`-only) surfaces
        // here as a structural decision. Each form is exercised with the
        // same canonical `:tag` pin so only the `:repo` axis varies.
        for repo in [
            // The pleme-io registry-shorthand convention — `github:org/repo`.
            "github:pleme-io/caixa-teia",
            // Other host-aliased shorthands (the resolver's pluggable
            // host-prefix table).
            "gitlab:pleme-io/caixa-teia",
            "codeberg:pleme-io/caixa-teia",
            "sourcehut:~pleme-io/caixa-teia",
            // Full HTTPS URL with and without `.git` suffix.
            "https://github.com/pleme-io/caixa-teia",
            "https://github.com/pleme-io/caixa-teia.git",
            // HTTP (rare; dev / mirror).
            "http://example.com/pleme-io/caixa-teia.git",
            // SSH URL.
            "ssh://git@github.com/pleme-io/caixa-teia.git",
            "ssh://git@git.example.com:2222/pleme-io/caixa-teia.git",
            // Scp-style SSH — the canonical `git@host:path` short form.
            "git@github.com:pleme-io/caixa-teia.git",
            "git@git.example.com:team/private.git",
            // Anonymous git protocol.
            "git://git.example.com/pleme-io/caixa-teia.git",
            // Local file URL (dev path).
            "file:///tmp/caixa-teia",
        ] {
            let d = dep_with_fonte(DepSource::Git {
                repo: repo.into(),
                tag: Some("v0.1.0".into()),
                rev: None,
                branch: None,
            });
            d.validate()
                .unwrap_or_else(|e| panic!("canonical repo {repo:?} must validate, got {e:?}"));
        }
    }

    #[test]
    fn fonte_repo_empty_takes_precedence_over_shape() {
        // Order pin: the existing `FonteRepoEmpty` diagnostic (narrower
        // diagnostic; doesn't try to parse the URL shape) fires before
        // the new `FonteRepoShape` per-axis gate, so an empty `:repo`
        // keeps its narrower error message. Mirrors
        // `fonte_repo_empty_fires_before_pin_missing` (already pinned)
        // on the ordering layer.
        let d = dep_with_fonte(DepSource::Git {
            repo: String::new(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteRepoEmpty { .. }),
            "got {err:?}"
        );
    }

    #[test]
    fn fonte_repo_shape_fires_before_pin_missing() {
        // Order pin: a malformed `:repo` value on a dep with no pin set
        // surfaces the `:repo` shape diagnostic (the more self-locating
        // axis — the `:repo` is the load-bearing identity of the source;
        // a missing pin is downstream from "do we even know the repo")
        // rather than collapsing onto the pin-missing diagnostic. The
        // shape gate runs inline before the pin enumeration in
        // `DepSource::validate`.
        let d = dep_with_fonte(DepSource::Git {
            repo: "pleme-io/caixa-teia".into(), // missing `:` separator
            tag: None,
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteRepoShape { .. }),
            "got {err:?}"
        );
    }

    #[test]
    fn fonte_repo_shape_diagnostic_carries_offending_repo_verbatim() {
        // The diagnostic-shape pin: the error names the offending
        // `:repo` value verbatim plus a non-empty parser-shaped `reason`
        // so the author can grep their caixa.lisp without re-running
        // the build. Mirrors the diagnostic-shape sweep on every prior
        // value-shape gate (3f9d7a0, 6cbb900, c7d05ec, e70d213, be07fd5).
        let d = dep_with_fonte(DepSource::Git {
            repo: "pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteRepoShape { nome, repo, reason } = err else {
            panic!("expected FonteRepoShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(repo, "pleme-io/caixa-teia");
        assert!(
            !reason.is_empty(),
            "FonteRepoShape `reason` must carry the predicate's wording verbatim"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_no_pin() {
        // The fail-before-pass-after pin for the canonical
        // `(:tipo git :repo "github:pleme-io/x")` shape with no
        // :tag/:rev/:branch — until this gate landed the resolver's
        // ResolveError::MissingPin surfaced at fetch time, far from the
        // source caixa.lisp. The new gate moves the check to validate
        // time and names the offending dep.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FontePinMissing { ref nome } if nome == "caixa-teia"),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_ambiguous_tag_and_branch() {
        // The canonical "pin drift" footgun: an author writes
        // `:tag "v1"` and later adds `:branch "main"` without removing
        // the :tag, and the resolver silently picks :tag (precedence
        // :rev > :tag > :branch). The :branch was dropped with no
        // diagnostic. The gate now rejects multi-pin shapes so the
        // author makes the precedence explicit at the source.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: Some("main".into()),
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinAmbiguous { nome, pins } = err else {
            panic!("expected FontePinAmbiguous");
        };
        assert_eq!(nome, "caixa-teia");
        assert!(pins.contains(":tag"));
        assert!(pins.contains(":branch"));
        assert!(!pins.contains(":rev"));
    }

    #[test]
    fn validate_rejects_git_fonte_with_ambiguous_tag_and_rev() {
        // Sibling arm of the pin-drift footgun: :tag + :rev set
        // simultaneously. Pinned separately so a future relaxation
        // that only catches the (:tag, :branch) pair surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: Some("c0ffee".into()),
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinAmbiguous { nome, pins } = err else {
            panic!("expected FontePinAmbiguous");
        };
        assert_eq!(nome, "caixa-teia");
        assert!(pins.contains(":tag"));
        assert!(pins.contains(":rev"));
    }

    #[test]
    fn validate_rejects_git_fonte_with_all_three_pins() {
        // The maximal ambiguity case — every pin axis set. Pinned so a
        // future relaxation that only catches pairs surfaces here. The
        // diagnostic must enumerate every offending axis so the author
        // sees the full set, not just the first match.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: Some("c0ffee".into()),
            branch: Some("main".into()),
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinAmbiguous { nome, pins } = err else {
            panic!("expected FontePinAmbiguous");
        };
        assert_eq!(nome, "caixa-teia");
        assert!(pins.contains(":tag"));
        assert!(pins.contains(":rev"));
        assert!(pins.contains(":branch"));
    }

    #[test]
    fn validate_rejects_git_fonte_with_empty_tag_pin() {
        // The empty-pin arm: exactly one pin axis is `Some(_)`, but its
        // inner string is empty. Distinct from FontePinMissing (where
        // every axis is None) — pinned separately so a future
        // tightening collapsing them surfaces here as a structural
        // decision.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some(String::new()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinEmpty { nome, pin } = err else {
            panic!("expected FontePinEmpty");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(pin, ":tag");
    }

    #[test]
    fn validate_rejects_git_fonte_with_empty_rev_pin() {
        // Sibling arm — the empty-pin diagnostic names which axis
        // carries the empty value, so the author's grep target is
        // unambiguous.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some(String::new()),
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinEmpty { nome, pin } = err else {
            panic!("expected FontePinEmpty");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(pin, ":rev");
    }

    #[test]
    fn validate_rejects_path_fonte_with_empty_caminho() {
        // The fail-before-pass-after pin for `(:tipo path :caminho "")`:
        // until this gate landed the resolver's
        // ResolveError::MissingPath surfaced with `path: PathBuf("")` at
        // fetch time — not actionable. The new gate moves the check to
        // validate time and names the offending dep.
        let d = dep_with_fonte(DepSource::Path {
            caminho: String::new(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoEmpty { ref nome } if nome == "caixa-teia"),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_absolute_caminho() {
        // The fail-before-pass-after pin for the absolute-`:caminho`
        // shape: `(:tipo path :caminho "/home/me/work/caixa-teia")`.
        // Until this gate landed an absolute `:caminho` silently
        // passed validate; the lacre pipeline embedded the
        // host-specific filesystem path verbatim in its
        // content-address (`conteudo: format!("path:{caminho}")`,
        // caixa-resolver/src/resolve.rs:189), so the BLAKE3 closure
        // differed per machine — the build succeeded but two CI
        // runners with different `${HOME}` layouts emitted two
        // distinct lacres for the byte-identical caixa, silently
        // breaking the THEORY.md §V.2 render-determinism contract
        // far from the source caixa.lisp. The new gate moves the
        // check to validate time and names the offending dep +
        // caminho verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/home/me/work/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoAbsolute { nome, caminho } = err else {
            panic!("expected FonteCaminhoAbsolute, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "/home/me/work/caixa-teia");
    }

    #[test]
    fn validate_accepts_path_fonte_with_parent_escape_caminho() {
        // The canonical sibling-workspace dep form
        // (`:caminho "../caixa-teia"`) remains accepted. The
        // absolute-path gate above is specifically narrower than the
        // shared [`crate::render::is_sandboxed_relative_path`]
        // predicate (which additionally forbids `..` traversal): a
        // local-path dep's canonical author surface is the in-tree
        // sibling-workspace path, so a full sandboxed-relative-path
        // lift would structurally reject every legitimate path-fonte
        // dep. Pinned so a future tightening to the full predicate
        // surfaces here as a structural decision, not a silent break.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_accepts_path_fonte_with_deeply_nested_relative_caminho() {
        // A multi-segment relative `:caminho`
        // (`"vendor/forks/caixa-teia"`) remains accepted — the
        // absolute-path gate brackets the host-layout-leaking shape
        // at the leading-`/` boundary only; every relative shape past
        // the empty arm continues to pass. Pinned alongside the
        // `..`-traversal positive control so a future tightening
        // surfaces the full set of legitimate relative forms here
        // rather than at a downstream consumer.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "vendor/forks/caixa-teia".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_rejects_path_fonte_with_tilde_prefix_caminho() {
        // The fail-before-pass-after pin for the tilde-expansion
        // `:caminho` shape: `(:tipo path :caminho "~/work/caixa-teia")`.
        // Until this gate landed the b94fd83 absolute arm let `~/foo`
        // through (`Path::is_absolute` returns false on a leading `~`
        // — the tilde is a shell-expansion convention, not a POSIX
        // path component), so the lacre embedded the value verbatim
        // and the resolver folded it through `Path::join` without
        // expansion, looking for a literal `./~/work/caixa-teia`
        // subdirectory and failing at resolve time with a
        // `No such file or directory` error far from the source
        // caixa.lisp. The new gate moves the check to validate time
        // and names the offending dep + caminho verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "~/work/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoTildeExpansion { nome, caminho } = err else {
            panic!("expected FonteCaminhoTildeExpansion, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "~/work/caixa-teia");
    }

    #[test]
    fn validate_rejects_path_fonte_with_bare_tilde_caminho() {
        // The bare `~` form (canonical "I meant `$HOME` and forgot
        // the rest"): both the leading-tilde arm catches it and the
        // canonical-user-tilde shell idiom (`~alice/dev/caixa-teia`)
        // sweeps through the same arm. Pinned both to ensure the
        // gate doesn't narrow to `~/` only.
        for s in ["~", "~alice/dev/caixa-teia", "~/", "~root/work"] {
            let d = dep_with_fonte(DepSource::Path { caminho: s.into() });
            let err = d.validate().unwrap_err();
            assert!(
                matches!(err, DepError::FonteCaminhoTildeExpansion { .. }),
                "{s:?} → {err:?}",
            );
        }
    }

    #[test]
    fn validate_accepts_path_fonte_with_mid_path_tilde_caminho() {
        // The leading-`~` is the canonical shell-expansion footgun —
        // a tilde mid-path (`"../foo~bar/caixa-teia"` — the canonical
        // backup-file-suffix idiom) is a legitimate POSIX path byte
        // with no shell-expansion semantic at the leading position.
        // Pinned so the gate doesn't widen to a full no-tilde-anywhere
        // sweep that would break every legitimate-shape backup-file
        // path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo~bar/caixa-teia".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_empty_fires_before_tilde_expansion() {
        // Cascade pin: the empty arm structurally precedes the
        // tilde arm (the bytes `""` and `"~"` don't overlap), but the
        // pin establishes the precedence at the diagnostic-shape
        // level should a future codec round-trip ever produce a
        // probe-as-both value. Mirrors the peer
        // `fonte_repo_empty_fires_before_pin_missing` cascade
        // discipline.
        let d = dep_with_fonte(DepSource::Path {
            caminho: String::new(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoEmpty { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_tilde_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with
        // `validate_rejects_path_fonte_with_absolute_caminho`'s
        // payload assertion): the error's Display surfaces both the
        // offending `:nome` and the offending `:caminho` verbatim
        // so a `feira lint` run can render the diagnostic without
        // re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "~alice/dev/caixa-teia".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("~alice/dev/caixa-teia"),
            "diagnostic must quote the offending caminho: {rendered}",
        );
        assert!(
            rendered.contains('~'),
            "diagnostic must reference the tilde footgun: {rendered}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_dollar_prefix_caminho() {
        // The fail-before-pass-after pin for the shell-variable-
        // expansion `:caminho` shape: `(:tipo path :caminho
        // "$HOME/work/caixa-teia")`. Until this gate landed the
        // b94fd83 absolute arm + the a5c248e tilde arm both let
        // `$HOME/foo` through (`Path::is_absolute` returns false on
        // a leading `$` — the `$` is a shell convention, not a POSIX
        // path component; `starts_with('~')` returns false too), so
        // the lacre embedded the value verbatim and the resolver
        // folded it through `Path::join` without `$`-expansion,
        // looking for a literal `./$HOME/work/caixa-teia`
        // subdirectory and failing at resolve time with a
        // `No such file or directory` error far from the source
        // caixa.lisp. The new gate moves the check to validate time
        // and names the offending dep + caminho verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$HOME/work/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoVarExpansion { nome, caminho } = err else {
            panic!("expected FonteCaminhoVarExpansion, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "$HOME/work/caixa-teia");
    }

    #[test]
    fn validate_rejects_path_fonte_with_dollar_brace_prefix_caminho() {
        // Sweep over every leading-`$` shape: the `${VAR}`-braced
        // form (canonical "paste-from-CI-manifest" footgun every
        // GitHub Actions / GitLab CI / Drone manifest carries on
        // `${WORKSPACE}`), the XDG idiom (`$XDG_CONFIG_HOME/caixa`,
        // canonical "I'm referencing a per-user config dir"),
        // and the bare `$` (canonical "I meant `$HOME` and forgot
        // the rest"). All shapes route through the same gate's
        // byte check. Pinned so the gate doesn't narrow to a
        // single shape (e.g. `$HOME/` only).
        for s in [
            "${HOME}/work/caixa-teia",
            "${WORKSPACE}/caixa-teia",
            "$XDG_CONFIG_HOME/caixa",
            "$",
        ] {
            let d = dep_with_fonte(DepSource::Path { caminho: s.into() });
            let err = d.validate().unwrap_err();
            assert!(
                matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
                "{s:?} → {err:?}",
            );
        }
    }

    #[test]
    fn validate_rejects_path_fonte_with_mid_path_dollar_caminho() {
        // The `$` byte is the canonical shell-variable-expansion /
        // command-substitution / arithmetic-expansion sentinel and
        // is rejected at *every* position on the `:caminho` axis: the
        // leading arm surfaces `FonteCaminhoVarExpansion`, the
        // embedded arm surfaces `FonteCaminhoShellVariableExpansion`
        // (6620f39). Pinned so a future arm doesn't narrow the gate
        // back to the leading position and re-open the paste-from-
        // shell-one-liner `"../foo$HOME/bar"` / paste-from-CI-
        // manifest `"../foo${WORKSPACE}/bar"` / paste-from-shell-
        // prompt `"../foo$(whoami)/bar"` cross-idiom-leak surface on
        // the lacre content-address (`path:{caminho}`,
        // caixa-resolver/src/resolve.rs:189).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo$bar/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellVariableExpansion { byte: b'$', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_tilde_fires_before_var_expansion() {
        // Cascade pin: the tilde arm structurally precedes the var
        // arm (the bytes `~` and `$` don't overlap at the leading
        // position), but the pin establishes the precedence at the
        // diagnostic-shape level should a future codec round-trip
        // ever produce a probe-as-both value. Mirrors the peer
        // `fonte_caminho_empty_fires_before_tilde_expansion` cascade
        // discipline on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "~/work/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoTildeExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_var_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_tilde_diagnostic_carries_offending_dep_and_caminho`'s
        // payload assertion on the immediate-predecessor arm): the
        // error's Display surfaces both the offending `:nome` and
        // the offending `:caminho` verbatim plus the `$` footgun
        // character itself so a `feira lint` run can render the
        // diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "${WORKSPACE}/caixa-teia".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("${WORKSPACE}/caixa-teia"),
            "diagnostic must quote the offending caminho: {rendered}",
        );
        assert!(
            rendered.contains('$'),
            "diagnostic must reference the dollar footgun: {rendered}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_nul() {
        // The fail-before-pass-after pin for the load-bearing NUL byte:
        // POSIX paths cannot contain `0x00` (every `std::fs` syscall
        // routes the path through `CString::new` which fails with
        // `NulError`); until this gate landed a `:caminho
        // "../caixa\0teia"` silently passed validate, the lacre
        // pipeline embedded the value verbatim, and the failure
        // surfaced at the resolver's `Path::join` → `CString::new`
        // boundary with a non-self-locating `NulError` far from the
        // source caixa.lisp. The new gate moves the check to validate
        // time and names the offending dep + caminho + offending byte
        // verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa\0teia".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoControlChar {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoControlChar, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa\0teia");
        assert_eq!(byte, 0x00);
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_newline() {
        // The canonical paste-from-multiline-doc footgun on `:caminho`
        // — author copies `"../caixa-teia\n"` (trailing newline) out
        // of a multi-line code-fence or, worse, a `:caminho
        // "../caixa-teia\nrm -rf /"` value (CRLF-at-subprocess-argument
        // injection sibling on the path axis the `is_git_repo_url`
        // control-char arm already closes on `:repo`). Pinned
        // separately from the NUL arm so a future relaxation that
        // catches one but not the other surfaces here.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia\n".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoControlChar { byte, .. } = err else {
            panic!("expected FonteCaminhoControlChar, got {err:?}");
        };
        assert_eq!(byte, 0x0A);
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_carriage_return() {
        // The CRLF sibling of the LF arm — Windows-line-ending
        // paste-from-multiline-doc on a `\r\n`-terminated buffer
        // leaves a stray `\r` mid-string after the LF strip. Pinned
        // separately from the LF arm so a future relaxation that
        // only catches LF surfaces here.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia\r".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoControlChar { byte, .. } = err else {
            panic!("expected FonteCaminhoControlChar, got {err:?}");
        };
        assert_eq!(byte, 0x0D);
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_tab() {
        // The canonical paste-from-aligned-table footgun — a `\t`
        // mid-`:caminho` is invisible in most editors but rides
        // through the lacre's content-address verbatim, so two
        // paste-from-distinct-tables (one editor strips tabs, one
        // preserves them) yield divergent lacres for the byte-
        // identical-looking caixa. Pinned separately from the
        // whitespace-shaped LF/CR arms so a future relaxation that
        // narrows to line-terminator-only surfaces here.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa\tteia".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoControlChar { byte, .. } = err else {
            panic!("expected FonteCaminhoControlChar, got {err:?}");
        };
        assert_eq!(byte, 0x09);
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_del() {
        // The DEL byte (`0x7F`) closes the upper-end paste-from-
        // binary-blob footgun — the gate's contract is `b < 0x20 ||
        // b == 0x7F`, matching the `is_git_repo_url` /
        // `is_git_ref_name` predicates' control-char arms. Pinned
        // separately from the lower-range arms so a future narrowing
        // to `< 0x20` only surfaces here.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa\x7fteia".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoControlChar { byte, .. } = err else {
            panic!("expected FonteCaminhoControlChar, got {err:?}");
        };
        assert_eq!(byte, 0x7F);
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_high_bit_utf8() {
        // The control-byte arm targets `0x00..=0x1F` + `0x7F` only —
        // high-bit / non-ASCII UTF-8 bytes are not gated. POSIX paths
        // are opaque byte sequences and UTF-8 multi-byte sequences
        // are a legitimate filename shape (the `café-teia/foo` idiom).
        // Pinned so the gate doesn't widen to a full ASCII-only sweep
        // that would break every legitimate-shape UTF-8 path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../café-teia/foo".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_var_fires_before_control_char() {
        // Cascade pin: the var-expansion arm structurally precedes the
        // control-char arm. A value like `"$\n"` probes positive on
        // both arms (`starts_with('$')` and contains LF), but the
        // narrower leading-byte diagnostic (`FonteCaminhoVarExpansion`)
        // wins so the author sees the more self-locating shell-
        // expansion arm first. Mirrors the
        // `fonte_caminho_tilde_fires_before_var_expansion` cascade
        // discipline on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$HOME\n".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_leading_space_caminho() {
        // The fail-before-pass-after pin for the leading ASCII space
        // `:caminho` shape: `(:tipo path :caminho " ../caixa-teia")`.
        // Until this gate landed the b94fd83 absolute arm + the a5c248e
        // tilde arm + the f4efe9c var arm + the d624c8d control-byte arm
        // all let `" ../caixa-teia"` through: `Path::is_absolute` returns
        // false on a leading space (the leading byte is `0x20`, not `0x2F`),
        // `starts_with('~')` / `starts_with('$')` return false, and `0x20`
        // is not in the `0x00..=0x1F` plus `0x7F` control-byte set (the
        // four ASCII whitespace bytes `0x09` tab, `0x0A` LF, `0x0D` CR
        // are caught, but the most common whitespace `0x20` space is
        // not). The lacre embedded the value verbatim and the resolver
        // folded it through `Path::join` looking for a literal `./ ../
        // caixa-teia` subdirectory and failing at resolve time with a
        // non-self-locating `No such file or directory` error far from
        // the source caixa.lisp. The new gate moves the check to
        // validate time and names the offending dep + caminho verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: " ../caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoLeadingWhitespace { nome, caminho } = err else {
            panic!("expected FonteCaminhoLeadingWhitespace, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, " ../caixa-teia");
    }

    #[test]
    fn validate_rejects_path_fonte_with_multiple_leading_spaces_caminho() {
        // The aligned-doc paste footgun sweep: more than one leading
        // space (`"   ../caixa-teia"` — the canonical "I selected the
        // aligned column from a four-`:fonte`-entry `:deps` block"
        // paste) routes through the same gate's `starts_with(' ')`
        // byte check. Pinned so the gate doesn't narrow to a
        // single-space prefix.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "   ../caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoLeadingWhitespace { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_mid_path_space_caminho() {
        // The leading-space is the canonical paste-from-aligned-doc
        // footgun — a space mid-path (`"../my dir/caixa-teia"` — the
        // canonical "I have a directory with a space in its name"
        // idiom; ASCII `0x20` is a valid POSIX filename byte) is a
        // legitimate path with no whitespace-leak semantic at the
        // non-leading position. Pinned so the gate doesn't widen to a
        // full no-space-anywhere sweep that would break every
        // legitimate-shape space-in-filename path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../my dir/caixa-teia".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_var_fires_before_leading_whitespace() {
        // Cascade pin: the var-expansion arm structurally precedes the
        // leading-whitespace arm. A value like `"$ "` would probe positive
        // on var (`starts_with('$')`) but the leading-byte arms walk
        // left-to-right so the var arm fires on the leading `$` before
        // the leading-whitespace arm probes. Mirrors the
        // `fonte_caminho_tilde_fires_before_var_expansion` cascade
        // discipline on the immediate-predecessor arms.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$VAR".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_leading_whitespace_fires_before_control_char() {
        // Cascade pin: the leading-whitespace arm structurally precedes
        // the control-char arm. A value like `" ../foo\n"` probes
        // positive on both (starts with space AND contains LF), but
        // the narrower leading-byte diagnostic
        // (`FonteCaminhoLeadingWhitespace`) wins so the author sees the
        // more self-locating paste-from-aligned-doc arm first. Mirrors
        // the `fonte_caminho_var_fires_before_control_char` cascade
        // discipline on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: " ../foo\n".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoLeadingWhitespace { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_leading_whitespace_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_var_diagnostic_carries_offending_dep_and_caminho`'s
        // payload assertion on the immediate-predecessor arm): the
        // error's Display surfaces both the offending `:nome` and the
        // offending `:caminho` verbatim, so a `feira lint` run can
        // render the diagnostic without re-parsing and the author can
        // grep their caixa.lisp for `:caminho "<value>"` and fix it in
        // one edit.
        let d = dep_with_fonte(DepSource::Path {
            caminho: " ../caixa-teia".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains(" ../caixa-teia"),
            "diagnostic must quote the offending caminho: {rendered}",
        );
        assert!(
            rendered.contains("space"),
            "diagnostic must name the space footgun: {rendered}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_control_char() {
        // Cascade pin on the sibling leading-byte arm: a leading `/`
        // value with embedded control byte (`"/etc/passwd\n"`) routes
        // through `FonteCaminhoAbsolute` not `FonteCaminhoControlChar`
        // — the host-layout-leak diagnostic is the load-bearing axis,
        // the control byte is the secondary observation. Same precedence
        // logic on every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/passwd\n".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_leading_hyphen_caminho() {
        // The fail-before-pass-after pin for the leading-`-` CLI-arg-
        // injection `:caminho` shape sweep. Until this gate landed
        // every prior leading-byte arm passed a leading-`-` value
        // through: `Path::is_absolute` returns false on `-` (the
        // leading byte is `0x2D`, not `0x2F`), `starts_with('~')` /
        // `starts_with('$')` / `starts_with(' ')` all return false,
        // and `0x2D` sits outside the control-byte set. The lacre
        // embedded the value verbatim and the resolver folded it
        // through `Path::join` looking for a literal `./-rf` /
        // `./-C` / `./--upload-pack=…` subdirectory; the failure at
        // `Path::join` time is non-self-locating but harmless, while
        // the failure at every downstream `git -C {caminho}` /
        // `terraform -chdir={caminho}` / `find {caminho}` shell-out
        // is arbitrary-CLI-arg-injection because none of those
        // porcelains carry a `--` argument-list terminator between
        // the flag block and the path argument. The new arm moves the
        // rejection to `Caixa::from_lisp` boundary time and names
        // the offending dep + caminho verbatim.
        //
        // Sweep spans the canonical CLI-arg-injection shapes matching
        // the peer sweep on the sibling `is_git_ref_name` /
        // `is_git_repo_url` axes: short-flag `-rf` (the `rm -rf` /
        // `find -rf` reinterpretation vector), `-C` (the `git -C`
        // change-directory-config-injection paste), long-flag
        // `--upload-pack=cat /etc/passwd` (the canonical
        // arbitrary-command-execution vector on every git porcelain
        // entry point), git-config-injection `--config=core.merge=ours`,
        // and the degenerate single-byte `-` value.
        for caminho in [
            "-rf",
            "-C",
            "--upload-pack=cat /etc/passwd",
            "--config=core.merge=ours",
            "-",
        ] {
            let d = dep_with_fonte(DepSource::Path {
                caminho: caminho.into(),
            });
            let err = d.validate().unwrap_err();
            let DepError::FonteCaminhoLeadingHyphen { nome, caminho: got } = err else {
                panic!("expected FonteCaminhoLeadingHyphen for {caminho:?}, got {err:?}");
            };
            assert_eq!(nome, "caixa-teia");
            assert_eq!(got, caminho);
        }
    }

    #[test]
    fn validate_accepts_path_fonte_with_mid_path_hyphen_caminho() {
        // The leading-`-` is the canonical CLI-arg-injection footgun
        // — a `-` anywhere else in the path (`"../caixa-teia"` — the
        // canonical kebab-separator-between-alphanumeric-segments
        // shape every DNS-1123-shaped caixa name carries; `"../-hidden"`
        // — a mid-path segment starting with `-`, still a legitimate
        // POSIX filename byte at that non-leading position because the
        // subprocess reads the whole `{caminho}` value as one positional
        // argument, so only the very first byte of the composite path
        // string is at the CLI-arg-injection boundary) is a legitimate
        // path with no CLI-flag-reinterpretation semantic at the non-
        // leading position of the top-level value. Pinned so the gate
        // doesn't widen to a full no-`-`-anywhere sweep that would
        // break every legitimate-shape kebab-in-filename path (i.e.
        // essentially every sibling-workspace caixa dep).
        for caminho in [
            "../caixa-teia",
            "../caixa-teia/-hidden",
            "./my-lib",
            "../foo-bar/baz",
        ] {
            let d = dep_with_fonte(DepSource::Path {
                caminho: caminho.into(),
            });
            d.validate()
                .unwrap_or_else(|e| panic!("mid-path `-` caminho {caminho:?} must pass: {e:?}"));
        }
    }

    #[test]
    fn fonte_caminho_leading_whitespace_fires_before_leading_hyphen() {
        // Cascade pin: the leading-whitespace arm structurally precedes
        // the leading-hyphen arm. A value like `" -rf"` probes positive
        // on both (leading space AND, one byte in, a `-` — though the
        // leading-hyphen arm probes only the very first byte so it
        // wouldn't fire on this value; the pin instead documents the
        // arm order on the more common "leading space then a hyphen"
        // paste-from-aligned-doc paste-flag-shell-one-liner idiom).
        // The narrower leading-space diagnostic (the paste-from-aligned-
        // doc footgun) wins so the author sees the more self-locating
        // whitespace arm first. Mirrors the
        // `fonte_caminho_var_fires_before_leading_whitespace` cascade
        // discipline on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: " -rf".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoLeadingWhitespace { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_leading_hyphen_fires_before_control_char() {
        // Cascade pin: the leading-hyphen arm structurally precedes
        // the control-char arm. A value like `"-rf\n"` probes positive
        // on both (starts with `-` AND contains LF), but the narrower
        // leading-byte diagnostic (`FonteCaminhoLeadingHyphen`) wins so
        // the author sees the more self-locating CLI-arg-injection arm
        // first. Mirrors the
        // `fonte_caminho_leading_whitespace_fires_before_control_char`
        // cascade discipline on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "-rf\n".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoLeadingHyphen { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_leading_hyphen_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_leading_whitespace_diagnostic_carries_offending_dep_and_caminho`'s
        // payload assertion on the immediate-predecessor arm): the
        // error's Display surfaces both the offending `:nome` and the
        // offending `:caminho` verbatim plus the CLI-argument-injection
        // vocabulary, so a `feira lint` run can render the diagnostic
        // without re-parsing and the author can grep their caixa.lisp
        // for `:caminho "<value>"` and fix it in one edit.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "--upload-pack=cat /etc/passwd".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("--upload-pack=cat /etc/passwd"),
            "diagnostic must quote the offending caminho: {rendered}",
        );
        assert!(
            rendered.contains("CLI-argument-injection"),
            "diagnostic must name the CLI-argument-injection vector: {rendered}",
        );
        assert!(
            rendered.contains("`-`"),
            "diagnostic must name the offending byte: {rendered}",
        );
    }

    #[test]
    fn fonte_caminho_control_diagnostic_carries_offending_dep_caminho_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_var_diagnostic_carries_offending_dep_and_caminho`'s
        // payload assertion on the immediate-predecessor arm): the
        // error's Display surfaces the offending `:nome`, the
        // offending `:caminho` verbatim, and the offending byte in
        // hex form (`0x09` for tab) so a `feira lint` run can render
        // the diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa\tteia".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa\tteia"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x09"),
            "diagnostic must name the offending byte in hex: {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_backslash() {
        // The fail-before-pass-after pin for the canonical Windows-
        // path-separator paste footgun: an author who pastes a path
        // from Windows-Explorer's `Copy as path`, PowerShell's
        // `Get-Location`, or any CMD/Cygwin/MSYS shell prompt
        // produces `..\caixa-teia`-shape values that silently passed
        // every prior arm (`Path::is_absolute("..\\caixa-teia")` is
        // false; `\` is neither a leading-byte sentinel nor a
        // control byte). On POSIX resolvers the value rides through
        // `Path::join` as a literal directory name and fails at
        // resolve time with `No such file or directory`; on Windows
        // resolvers the value resolves to the parent's sibling — two
        // distinct directories for the byte-identical caixa.lisp.
        // The new arm moves the rejection to validate time and names
        // the offending dep + caminho verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoBackslash { nome, caminho } = err else {
            panic!("expected FonteCaminhoBackslash, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "..\\caixa-teia");
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_windows_drive_letter() {
        // The Windows drive-letter paste shape (`C:\work\caixa-teia`
        // out of Explorer / `cd`-and-`pwd`-on-Windows). On POSIX
        // hosts `Path::is_absolute("C:\\work\\caixa-teia")` returns
        // false (POSIX absolute paths start with `/`, drive letters
        // are not a POSIX concept), so the b94fd83 absolute arm
        // doesn't fire; the value contains `\` bytes that this arm
        // now catches with the more self-locating Windows-path-
        // separator diagnostic. Pinned separately from the bare
        // `..\caixa-teia` shape so a future arm that targets only
        // leading-`..\` doesn't regress the drive-letter coverage.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "C:\\work\\caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_trailing_backslash() {
        // The trailing-`\` shape (`..\caixa-teia\` — the canonical
        // PowerShell tab-completion-on-a-directory append). Pinned
        // separately from the embedded-`\` shape so the gate's
        // contract is "any `\` anywhere", not "any `\` not at end".
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia\\".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_legitimate_forward_slash() {
        // The positive-control pin: the gate targets `\` only,
        // never `/`. The canonical relative POSIX path
        // (`../caixa-teia/foo/bar`) must continue to validate cleanly
        // so legitimate nested-directory deps aren't broken. Pinned
        // so the gate doesn't accidentally widen to a "no path
        // separators at all" sweep.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/foo/bar".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_backslash() {
        // Cascade pin: the control-char arm structurally precedes the
        // backslash arm. A value like `"..\caixa\0teia"` probes
        // positive on both (`\` byte + NUL byte), but the control-
        // char diagnostic wins so the author sees the more self-
        // locating POSIX-syscall-rejected-byte diagnostic first
        // (NUL outright breaks `CString::new` at every `std::fs`
        // syscall boundary; the `\` divergence is the cross-OS-
        // separator axis). Mirrors the
        // `fonte_caminho_var_fires_before_control_char` cascade
        // discipline on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa\0teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_backslash() {
        // Cascade pin on the load-bearing leading-byte arm: a leading
        // `/` value with embedded `\` (`/etc/passwd\foo`) routes
        // through `FonteCaminhoAbsolute` not `FonteCaminhoBackslash`
        // — the host-layout-leak diagnostic is the load-bearing
        // axis, the `\` byte is the secondary observation. Same
        // precedence logic as every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/passwd\\foo".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_var_fires_before_backslash() {
        // Cascade pin on the var-expansion arm: a leading-`$` value
        // with embedded `\` (`$WORKSPACE\caixa-teia` — the canonical
        // PowerShell-env-var paste-from-CI-manifest footgun) routes
        // through `FonteCaminhoVarExpansion` not `FonteCaminhoBackslash`.
        // The shell-expansion diagnostic is the more self-locating
        // axis since both the leading `$` and the embedded `\`
        // are Windows-shell artifacts but the `$` is the root-cause
        // surface (an author who removes the `$` is likely to leave
        // the `\` too).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$WORKSPACE\\caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with the prior
        // `fonte_caminho_*_diagnostic_carries_*` payload assertions
        // on every preceding arm): the error's Display surfaces the
        // offending `:nome` and the offending `:caminho` verbatim
        // so a `feira lint` run can render the diagnostic without
        // re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("..\\caixa-teia"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains('\\'),
            "diagnostic must reference the backslash footgun: {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_trailing_slash() {
        // The fail-before-pass-after pin for the canonical trailing-`/`
        // paste footgun: an author who shell-tab-completes a sibling
        // directory (every interactive shell — bash/zsh/fish/nushell —
        // appends `/` on tab-completing a directory) produces
        // `"../caixa-teia/"`-shape values that silently passed every
        // prior arm (the leading byte is `.`, no control bytes, no
        // backslash). `Path::join` resolves both shapes to the same
        // directory at the resolver, but the lacre embeds the value
        // verbatim and the BLAKE3 closures diverge across two
        // workstations whose authors differ only in tab-completion
        // habits.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoTrailingSlash { nome, caminho } = err else {
            panic!("expected FonteCaminhoTrailingSlash, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia/");
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_bare_dot_slash() {
        // The `"./"` shape (the canonical "I meant the caixa.lisp's own
        // directory and tab-completed it" footgun). Pinned separately
        // from the canonical `"../caixa-teia/"` shape so the gate's
        // contract is "any trailing `/`", not "trailing `/` after a leaf
        // name".
        let d = dep_with_fonte(DepSource::Path {
            caminho: "./".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoTrailingSlash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_consecutive_trailing_slashes() {
        // The `"foo//"` shape (the canonical "I pasted from a CI manifest
        // that double-templated `${VAR}/` over an already-`/`-suffixed
        // path" footgun). The gate fires on the last byte being `/`
        // regardless of how many `/` precede it; the arm contract is
        // "the value ends with `/`", structurally.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia//".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoTrailingSlash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_dotdot_trailing_slash() {
        // The `"../"` shape (the canonical "I want the parent" tab-
        // completion footgun on a bare `..` path). Pinned separately so
        // the gate doesn't accidentally narrow to "trailing `/` only on
        // multi-segment paths".
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoTrailingSlash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_internal_slashes() {
        // The positive-control pin: the gate targets the trailing byte
        // only, never internal `/` separators. The canonical nested
        // relative POSIX path (`"../caixa-teia/foo/bar"`) must continue
        // to validate cleanly so legitimate deeply-nested deps aren't
        // broken. Pinned so the gate doesn't accidentally widen to a
        // "no `/` separators anywhere" sweep that would defeat the
        // entire path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/foo/bar".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_bare_dot() {
        // The positive-control pin on the degenerate single-`.` shape
        // (the canonical "the caixa.lisp's own directory" idiom). The
        // gate fires on the trailing byte being `/`, not on the path
        // being short, so `"."` (one byte, not `/`) must continue to
        // validate cleanly.
        let d = dep_with_fonte(DepSource::Path {
            caminho: ".".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_trailing_slash() {
        // Cascade pin: the control-char arm structurally precedes the
        // trailing-slash arm. A value like `"../foo\n/"` ends in `/`
        // but the embedded LF (`0x0A`) is the load-bearing diagnostic
        // (control bytes are the paste-from-multiline-doc footgun the
        // d624c8d arm already closes). Mirrors the
        // `fonte_caminho_control_char_fires_before_backslash` cascade
        // discipline on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_trailing_slash() {
        // Cascade pin on the backslash arm: a value like `"..\foo/"`
        // ends in `/` but the embedded `\` is the load-bearing
        // diagnostic (the cross-host-OS-separator divergence vector
        // the 3a4e1d7 arm closes). Same precedence logic as the prior
        // narrower-diagnostic-first cascade.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_trailing_slash() {
        // Cascade pin on the load-bearing leading-byte arm: a leading
        // `/` value with a trailing `/` (`"/etc/passwd/"`) routes
        // through `FonteCaminhoAbsolute` not `FonteCaminhoTrailingSlash`
        // — the host-layout-leak diagnostic is the load-bearing axis,
        // the trailing `/` is the secondary observation. Same
        // precedence logic as every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/passwd/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_trailing_slash_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with the prior
        // `fonte_caminho_*_diagnostic_carries_*` payload assertions on
        // every preceding arm): the error's Display surfaces the
        // offending `:nome` and the offending `:caminho` verbatim so a
        // `feira lint` run can render the diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia/"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("trailing"),
            "diagnostic must reference the trailing-slash footgun: {rendered:?}",
        );
    }

    // -- :caminho shell-redirection metacharacter arm -----------------------

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_gt_redirection() {
        // The fail-before-pass-after pin for the canonical output-redirection
        // paste footgun: an author copies a shell pipeline tail
        // (`"../caixa-teia>build.log"` — the canonical "I selected the whole
        // line including the `> build.log` redirect" idiom) and silently
        // passed every prior arm (`Path::is_absolute` false on `..`, no
        // control bytes, no backslash, doesn't end in `/`). The lacre
        // embedded the value verbatim, the resolver folded it through
        // `Path::join` looking for a literal `./../caixa-teia>build.log`
        // subdirectory, and the failure surfaced at resolve time with a
        // non-self-locating `No such file or directory` error. The new arm
        // moves the rejection to validate time and names the offending dep
        // + caminho + byte verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>build.log".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellRedirection {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellRedirection, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia>build.log");
        assert_eq!(byte, b'>');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_lt_redirection() {
        // The symmetric input-redirection paste shape
        // (`"../caixa-teia<input.lisp"` — the canonical "I copied a
        // `command < input.lisp` line from a tatara-lisp REPL log"
        // idiom). Pinned separately from the `>` shape so the gate's
        // contract is "any `<` or `>` anywhere", not single-byte coverage.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia<input.lisp".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellRedirection { byte, .. } = err else {
            panic!("expected FonteCaminhoShellRedirection, got {err:?}");
        };
        assert_eq!(byte, b'<');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_gt_redirection() {
        // Leading-position `>` shape (`">../caixa-teia"` — the degenerate
        // "I forgot the source side of the redirect" idiom). Pinned
        // separately from the embedded-byte shapes so the gate covers
        // every position, not only mid-path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: ">../caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_double_gt_append() {
        // The bash append-redirection shape (`"../caixa-teia>>build.log"` —
        // the canonical "I copied a `>>` append redirect" idiom). The arm
        // fires on the first `>` encountered; pinned so a future arm that
        // tries to distinguish `>` from `>>` doesn't break the broader
        // contract.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>>build.log".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_redirection() {
        // The positive-control pin: the gate targets only `<` / `>`,
        // never adjacent printable ASCII or POSIX-valid bytes. The
        // canonical relative POSIX path (`"../caixa-teia"`) and a
        // nested deeply-pathed variant (`"../caixa-teia/foo/bar"`) must
        // continue to validate cleanly so the gate doesn't widen to a
        // "no printable punctuation anywhere" sweep that would defeat
        // the entire path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/foo/bar".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_redirection() {
        // Cascade pin on the immediate-predecessor arm: a value carrying
        // both `\` and `<` / `>` (`"..\caixa-teia>build.log"` — the
        // canonical "I pasted a Windows-shell command with output
        // redirect" footgun) routes through `FonteCaminhoBackslash` not
        // `FonteCaminhoShellRedirection`. The cross-host-OS-separator
        // divergence is the load-bearing axis (an author who removes
        // the `\` is the root-cause edit; the `>` falls away in the
        // same edit since it's downstream of the Windows-shell
        // convention).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia>build.log".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_redirection() {
        // Cascade pin on the embedded-control-byte arm: a value carrying
        // both a control byte and `<` / `>` (`"../foo\n>bar"` — the
        // canonical paste-from-multiline-doc footgun where a newline
        // landed mid-caminho) routes through `FonteCaminhoControlChar`
        // not `FonteCaminhoShellRedirection`. The POSIX-syscall-
        // rejected-byte / NUL-`CString::new`-fail diagnostic is the
        // load-bearing axis on every value that probes positive for
        // both — mirrors the cascade discipline on every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n>bar".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_redirection() {
        // Cascade pin on the load-bearing leading-byte arm: a leading
        // `/` value with embedded `<` / `>` (`"/etc/passwd>out"`)
        // routes through `FonteCaminhoAbsolute` not
        // `FonteCaminhoShellRedirection` — the host-layout-leak
        // diagnostic is the load-bearing axis, the `>` byte is the
        // secondary observation. Same precedence logic as every prior
        // leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/passwd>out".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value carrying
        // both `<` / `>` and a trailing `/` (`"../foo></"` — the
        // canonical "I tab-completed a path that already had a
        // redirect" footgun) routes through `FonteCaminhoShellRedirection`
        // not `FonteCaminhoTrailingSlash`. The embedded shell-metachar is
        // the more semantic-locating axis (an author who removes the
        // `<` / `>` typically also drops the trailing separator since
        // both are paste-from-shell artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo></".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_diagnostic_carries_offending_dep_caminho_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_control_diagnostic_carries_offending_dep_caminho_byte`'s
        // payload assertion on the closest peer arm that also carries a
        // `byte` field): the error's Display surfaces the offending
        // `:nome`, the offending `:caminho` verbatim, and the offending
        // byte in hex (`0x3c` for `<`, `0x3e` for `>`) so a `feira lint`
        // run can render the diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>build.log".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia>build.log"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x3e"),
            "diagnostic must name the offending byte in hex: {rendered:?}",
        );
        assert!(
            rendered.contains("redirection"),
            "diagnostic must name the shell-redirection footgun: {rendered:?}",
        );
    }

    // -- :caminho shell-pipe metacharacter arm ----------------------------

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_pipe() {
        // The fail-before-pass-after pin for the canonical shell-pipe
        // paste footgun: an author copies a shell-history line
        // (`"../caixa-teia | grep foo"` — the canonical "I selected
        // the whole `ls dir | grep` line out of zsh history") and
        // silently passed every prior arm (`Path::is_absolute` false
        // on `..`, no control bytes, no backslash, no `<` / `>`,
        // doesn't end in `/`). The lacre embedded the value verbatim,
        // the resolver folded it through `Path::join` looking for a
        // literal `./../caixa-teia | grep foo` subdirectory, and the
        // failure surfaced at resolve time with a non-self-locating
        // `No such file or directory` error. The new arm moves the
        // rejection to validate time and names the offending dep +
        // caminho verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | grep foo".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellPipe { nome, caminho } = err else {
            panic!("expected FonteCaminhoShellPipe, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia | grep foo");
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_pipe() {
        // Leading-position `|` shape (`"|../caixa-teia"` — the
        // degenerate "I forgot the source side of the pipe" idiom).
        // Pinned separately from the embedded-byte shape so the gate
        // covers every position, not only mid-path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "|../caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_double_pipe_or() {
        // The bash short-circuit-OR shape (`"../caixa-teia||fallback"`
        // — the canonical "I copied a `cmd-a || cmd-b` fallback line"
        // idiom). The arm fires on the first `|` encountered; pinned
        // so a future arm that tries to distinguish `|` from `||`
        // doesn't break the broader contract.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia||fallback".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_pipe() {
        // The positive-control pin: the gate targets only `|`, never
        // adjacent printable ASCII or POSIX-valid bytes. The canonical
        // relative POSIX path (`"../caixa-teia"`) and a nested deeply-
        // pathed variant with adjacent printable punctuation
        // (`"../caixa-teia/sub-dir.v2"`) must continue to validate
        // cleanly so the gate doesn't widen to a "no printable
        // punctuation anywhere" sweep that would defeat the entire
        // path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_pipe() {
        // Cascade pin on the immediate-predecessor arm: a value carrying
        // both `<` / `>` and `|` (`"../caixa-teia<input|tee"` — the
        // canonical "I pasted a `cmd < input | tee` pipeline tail"
        // footgun) routes through `FonteCaminhoShellRedirection` not
        // `FonteCaminhoShellPipe`. The input/output redirection
        // metachar carries the more self-locating `byte: u8` payload
        // (it names which of `<` or `>` triggered), so the prior arm
        // wins on every probe-as-both value — same cascade discipline
        // every prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia<input|tee".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'<', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_pipe() {
        // Cascade pin on the upstream backslash arm: a value carrying
        // both `\` and `|` (`"..\caixa-teia|tee"` — the canonical
        // "I pasted a Windows-shell command with pipe to tee"
        // footgun) routes through `FonteCaminhoBackslash` not
        // `FonteCaminhoShellPipe`. The cross-host-OS-separator
        // divergence is the load-bearing axis on every probe-as-both
        // value (an author who removes the `\` is the root-cause edit;
        // the `|` falls away in the same edit since it's downstream of
        // the Windows-shell convention).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia|tee".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_pipe() {
        // Cascade pin on the embedded-control-byte arm: a value
        // carrying both a control byte and `|` (`"../foo\n|bar"` —
        // the canonical paste-from-multiline-doc footgun where a
        // newline landed mid-caminho) routes through
        // `FonteCaminhoControlChar` not `FonteCaminhoShellPipe`. The
        // POSIX-syscall-rejected-byte / NUL-`CString::new`-fail
        // diagnostic is the load-bearing axis on every value that
        // probes positive for both — mirrors the cascade discipline
        // on every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n|bar".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_pipe() {
        // Cascade pin on the load-bearing leading-byte arm: a leading
        // `/` value with embedded `|` (`"/etc/passwd|tee"`) routes
        // through `FonteCaminhoAbsolute` not `FonteCaminhoShellPipe`
        // — the host-layout-leak diagnostic is the load-bearing axis,
        // the `|` byte is the secondary observation. Same precedence
        // logic as every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/passwd|tee".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value carrying
        // both `|` and a trailing `/` (`"../foo|tee/"` — the canonical
        // "I tab-completed a path that already had a pipeline tail"
        // footgun) routes through `FonteCaminhoShellPipe` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-metachar is
        // the more semantic-locating axis (an author who removes the
        // `|` typically also drops the trailing separator since both
        // are paste-from-shell artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo|tee/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_backslash_diagnostic_carries_offending_dep_and_caminho`
        // on the closest single-byte peer arm): the error's Display
        // surfaces the offending `:nome` and the offending `:caminho`
        // verbatim, and names the shell-pipe footgun explicitly so a
        // `feira lint` run can render the diagnostic without
        // re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | grep foo".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia | grep foo"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains('|'),
            "diagnostic must reference the pipe footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("pipe"),
            "diagnostic must name the shell-pipe footgun: {rendered:?}",
        );
    }

    // -- :caminho shell-command-separator metacharacter arm ---------------

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_semicolon() {
        // The fail-before-pass-after pin for the canonical shell-command-
        // separator paste footgun: an author copies a shell one-liner
        // (`"../caixa-teia; rm -rf build"` — the canonical "I selected the
        // whole `cd path; do-thing` chain out of a shell-history block")
        // and silently passed every prior arm (`Path::is_absolute` false
        // on `..`, no control bytes, no backslash, no `<` / `>`, no `|`,
        // doesn't end in `/`). The lacre embedded the value verbatim, the
        // resolver folded it through `Path::join` looking for a literal
        // `./../caixa-teia; rm -rf build` subdirectory, and the failure
        // surfaced at resolve time with a non-self-locating `No such file
        // or directory` error. The new arm moves the rejection to validate
        // time and names the offending dep + caminho verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia; rm -rf build".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellSemicolon { nome, caminho } = err else {
            panic!("expected FonteCaminhoShellSemicolon, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia; rm -rf build");
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_semicolon() {
        // Leading-position `;` shape (`";../caixa-teia"` — the degenerate
        // "I forgot the prior command side of the separator" idiom).
        // Pinned separately from the embedded-byte shape so the gate
        // covers every position, not only mid-path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: ";../caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_double_semicolon() {
        // The POSIX `case` arm `;;` terminator shape
        // (`"../caixa-teia;;next"` — the canonical "I copied a `case`
        // arm tail" idiom). The arm fires on the first `;` encountered;
        // pinned so a future arm that tries to distinguish `;` from `;;`
        // doesn't break the broader contract.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia;;next".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_semicolon() {
        // The positive-control pin: the gate targets only `;`, never
        // adjacent printable ASCII or POSIX-valid bytes. The canonical
        // relative POSIX path (`"../caixa-teia"`) and a nested deeply-
        // pathed variant with adjacent printable punctuation
        // (`"../caixa-teia/sub-dir.v2"`) must continue to validate
        // cleanly so the gate doesn't widen to a "no printable
        // punctuation anywhere" sweep that would defeat the entire
        // path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_shell_semicolon() {
        // Cascade pin on the immediate-predecessor arm: a value carrying
        // both `|` and `;` (`"../caixa-teia | tee; rm"` — the canonical
        // "I pasted a `cmd | tee; cleanup` chain" footgun) routes through
        // `FonteCaminhoShellPipe` not `FonteCaminhoShellSemicolon`. The
        // pipeline-tail paste is the load-bearing root-cause edit on
        // every probe-as-both value (an author who removes the `|`
        // typically also drops the trailing `; cleanup` since both are
        // the same paste-from-shell-history artifact) — same cascade
        // discipline every prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | tee; rm".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_semicolon() {
        // Cascade pin on the upstream shell-redirection arm: a value
        // carrying both `<` / `>` and `;` (`"../caixa-teia>log; rm"` —
        // the canonical "I pasted a `cmd > log; cleanup` chain"
        // footgun) routes through `FonteCaminhoShellRedirection` not
        // `FonteCaminhoShellSemicolon`. The input/output redirection
        // metachar carries the more self-locating `byte: u8` payload
        // (it names which of `<` or `>` triggered), so the prior arm
        // wins on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>log; rm".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_semicolon() {
        // Cascade pin on the upstream backslash arm: a value carrying
        // both `\` and `;` (`"..\caixa-teia;rm"` — the canonical "I
        // pasted a Windows-shell `cd ..\path; cleanup` chain") routes
        // through `FonteCaminhoBackslash` not `FonteCaminhoShellSemicolon`.
        // The cross-host-OS-separator divergence is the load-bearing axis
        // on every probe-as-both value (an author who removes the `\` is
        // the root-cause edit; the `;` falls away in the same edit since
        // it's downstream of the Windows-shell convention).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia;rm".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_semicolon() {
        // Cascade pin on the embedded-control-byte arm: a value carrying
        // both a control byte and `;` (`"../foo\n;bar"` — the canonical
        // paste-from-multiline-doc footgun where a newline landed mid-
        // caminho) routes through `FonteCaminhoControlChar` not
        // `FonteCaminhoShellSemicolon`. The POSIX-syscall-rejected-byte
        // / NUL-`CString::new`-fail diagnostic is the load-bearing axis
        // on every value that probes positive for both — mirrors the
        // cascade discipline on every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n;bar".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_semicolon() {
        // Cascade pin on the load-bearing leading-byte arm: a leading
        // `/` value with embedded `;` (`"/etc/passwd;rm"`) routes
        // through `FonteCaminhoAbsolute` not `FonteCaminhoShellSemicolon`
        // — the host-layout-leak diagnostic is the load-bearing axis,
        // the `;` byte is the secondary observation. Same precedence
        // logic as every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/passwd;rm".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_semicolon_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value carrying
        // both `;` and a trailing `/` (`"../foo;rm/"` — the canonical
        // "I tab-completed a path that already had a `; cleanup` tail"
        // footgun) routes through `FonteCaminhoShellSemicolon` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-metachar is
        // the more semantic-locating axis (an author who removes the
        // `;` typically also drops the trailing separator since both
        // are paste-from-shell artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo;rm/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_semicolon_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_pipe_diagnostic_carries_offending_dep_and_caminho`
        // on the closest single-byte peer arm): the error's Display
        // surfaces the offending `:nome` and the offending `:caminho`
        // verbatim, and names the shell-command-separator footgun
        // explicitly so a `feira lint` run can render the diagnostic
        // without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia; rm -rf build".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia; rm -rf build"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains(';'),
            "diagnostic must reference the semicolon footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("command-separator"),
            "diagnostic must name the shell-command-separator footgun: {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_ampersand() {
        // The fail-before-pass-after pin for the canonical shell-
        // background-task paste footgun: an author copies a shell one-
        // liner (`"../caixa-teia & sleep 1"` — the canonical "I selected
        // the whole `cd path & sleep 1` background-launch out of a
        // shell-history block") and silently passed every prior arm
        // (`Path::is_absolute` false on `..`, no control bytes, no
        // backslash, no `<` / `>`, no `|`, no `;`, doesn't end in `/`).
        // The lacre embedded the value verbatim, the resolver folded it
        // through `Path::join` looking for a literal `./../caixa-teia &
        // sleep 1` subdirectory, and the failure surfaced at resolve
        // time with a non-self-locating `No such file or directory`
        // error. The new arm moves the rejection to validate time and
        // names the offending dep + caminho verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia & sleep 1".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellBackground { nome, caminho } = err else {
            panic!("expected FonteCaminhoShellBackground, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia & sleep 1");
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_ampersand() {
        // Leading-position `&` shape (`"&../caixa-teia"` — the
        // degenerate "I forgot the prior command side of the
        // background terminator" idiom). Pinned separately from the
        // embedded-byte shape so the gate covers every position, not
        // only mid-path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "&../caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_double_ampersand() {
        // The logical-AND `&&` shape (`"../caixa-teia && make"` — the
        // canonical "I copied a `cd path && make` build chain" idiom
        // every Makefile / shell-script wraps). The arm fires on the
        // first `&` encountered; pinned so a future arm that tries to
        // distinguish `&` from `&&` doesn't break the broader contract.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia && make".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_ampersand() {
        // The positive-control pin: the gate targets only `&`, never
        // adjacent printable ASCII or POSIX-valid bytes. The canonical
        // relative POSIX path (`"../caixa-teia"`) and a nested deeply-
        // pathed variant with adjacent printable punctuation
        // (`"../caixa-teia/sub-dir.v2"`) must continue to validate
        // cleanly so the gate doesn't widen to a "no printable
        // punctuation anywhere" sweep that would defeat the entire
        // path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_semicolon_fires_before_shell_background() {
        // Cascade pin on the immediate-predecessor arm: a value carrying
        // both `;` and `&` (`"../caixa-teia; rm & sleep"` — the
        // canonical "I pasted a `cmd; cleanup & sleep` chain" footgun)
        // routes through `FonteCaminhoShellSemicolon` not
        // `FonteCaminhoShellBackground`. The sequential-command-
        // separator paste is the more common shell-history paste idiom
        // on every probe-as-both value (an author who removes the `;`
        // typically also drops the trailing `& sleep` since both are
        // paste-from-shell-history artifacts) — same cascade discipline
        // every prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia; rm & sleep".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_shell_background() {
        // Cascade pin on the upstream shell-pipe arm: a value carrying
        // both `|` and `&` (`"../caixa-teia | tee & sleep"` — the
        // canonical "I pasted a `cmd | tee & sleep` background-pipeline
        // chain" footgun) routes through `FonteCaminhoShellPipe` not
        // `FonteCaminhoShellBackground`. The pipeline-tail paste is the
        // load-bearing root-cause edit on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | tee & sleep".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_background() {
        // Cascade pin on the upstream shell-redirection arm: a value
        // carrying both `>` and `&` (`"../caixa-teia>log & sleep"` —
        // the canonical "I pasted a `cmd > log & sleep` background-
        // redirect chain" footgun) routes through
        // `FonteCaminhoShellRedirection` not
        // `FonteCaminhoShellBackground`. The input/output redirection
        // metachar carries the more self-locating `byte: u8` payload
        // (it names which of `<` or `>` triggered), so the prior arm
        // wins on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>log & sleep".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_background() {
        // Cascade pin on the upstream backslash arm: a value carrying
        // both `\` and `&` (`"..\caixa-teia & sleep"` — the canonical
        // "I pasted a Windows-shell `cd ..\path & sleep` background-
        // launch chain") routes through `FonteCaminhoBackslash` not
        // `FonteCaminhoShellBackground`. The cross-host-OS-separator
        // divergence is the load-bearing axis on every probe-as-both
        // value (an author who removes the `\` is the root-cause edit;
        // the `&` falls away in the same edit since it's downstream of
        // the Windows-shell convention).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia & sleep".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_background() {
        // Cascade pin on the embedded-control-byte arm: a value
        // carrying both a control byte and `&` (`"../foo\n&sleep"` —
        // the canonical paste-from-multiline-doc footgun where a
        // newline landed mid-caminho) routes through
        // `FonteCaminhoControlChar` not `FonteCaminhoShellBackground`.
        // The POSIX-syscall-rejected-byte / NUL-`CString::new`-fail
        // diagnostic is the load-bearing axis on every value that
        // probes positive for both — mirrors the cascade discipline on
        // every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n&sleep".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_background() {
        // Cascade pin on the load-bearing leading-byte arm: a leading
        // `/` value with embedded `&` (`"/etc/passwd & sleep"`) routes
        // through `FonteCaminhoAbsolute` not
        // `FonteCaminhoShellBackground` — the host-layout-leak
        // diagnostic is the load-bearing axis, the `&` byte is the
        // secondary observation. Same precedence logic as every prior
        // leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/passwd & sleep".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_background_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value carrying
        // both `&` and a trailing `/` (`"../foo&sleep/"` — the
        // canonical "I tab-completed a path that already had a `&
        // sleep` background-launch tail" footgun) routes through
        // `FonteCaminhoShellBackground` not `FonteCaminhoTrailingSlash`.
        // The embedded shell-metachar is the more semantic-locating
        // axis (an author who removes the `&` typically also drops
        // the trailing separator since both are paste-from-shell
        // artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo&sleep/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_background_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_semicolon_diagnostic_carries_offending_dep_and_caminho`
        // on the closest single-byte peer arm): the error's Display
        // surfaces the offending `:nome` and the offending `:caminho`
        // verbatim, and names the shell-background / logical-AND
        // footgun explicitly so a `feira lint` run can render the
        // diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia & sleep 1".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia & sleep 1"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains('&'),
            "diagnostic must reference the ampersand footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("background") || rendered.contains("list-AND"),
            "diagnostic must name the shell-background / logical-AND footgun: {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_backtick() {
        // The fail-before-pass-after pin for the canonical shell-
        // command-substitution paste footgun: an author copies a
        // POSIX legacy backticked one-liner (`"../caixa-teia/`whoami`"`
        // — the canonical "I pasted a path that included a `pwd`
        // / `whoami` / `date` legacy command-substitution expansion
        // out of a shell-history block") and silently passed every
        // prior arm (`Path::is_absolute` false on `..`, no control
        // bytes, no `\`, no `<` / `>`, no `|`, no `;`, no `&`, doesn't
        // end in `/`). The lacre embedded the value verbatim, the
        // resolver folded it through `Path::join` looking for a
        // literal `./../caixa-teia/`whoami`` subdirectory, and the
        // failure surfaced at resolve time with a non-self-locating
        // `No such file or directory` error. The new arm moves the
        // rejection to validate time and names the offending dep +
        // caminho verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/`whoami`".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellCommandSubstitution { nome, caminho } = err else {
            panic!("expected FonteCaminhoShellCommandSubstitution, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia/`whoami`");
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_backtick() {
        // Leading-position backtick shape (``"`pwd`/caixa-teia"`` —
        // the canonical `<backtick>pwd<backtick>/path` working-
        // directory expansion shape every shell-side path-composition
        // idiom carries). Pinned separately from the embedded-byte
        // shape so the gate covers every position, not only mid-path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "`pwd`/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_trailing_backtick() {
        // Trailing-position backtick shape (`"../caixa-teia`"` — the
        // degenerate "I selected an unbalanced backtick out of a
        // shell-history block" idiom that probes for the cascade's
        // last-byte handling). The trailing-`/` arm fires only on
        // last-byte `/`; an unbalanced trailing backtick must route
        // through this arm regardless of position.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia`".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_balanced_backtick_pair() {
        // The canonical balanced-pair shape (``"../<backtick>cat
        // /etc/passwd<backtick>"`` — the canonical CWE-78 shell-
        // command-injection paste idiom every shell-side hardening
        // guide enumerates first). The arm fires on the first
        // backtick encountered; pinned so a future arm that tries to
        // distinguish the opening from the closing byte doesn't break
        // the broader contract.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../`cat /etc/passwd`".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_backtick() {
        // The positive-control pin: the gate targets only the
        // backtick byte, never adjacent printable ASCII or POSIX-
        // valid bytes. The canonical relative POSIX path
        // (`"../caixa-teia"`) and a nested deeply-pathed variant with
        // adjacent printable punctuation
        // (`"../caixa-teia/sub-dir.v2"`) must continue to validate
        // cleanly so the gate doesn't widen to a "no printable
        // punctuation anywhere" sweep that would defeat the entire
        // path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_background_fires_before_shell_command_substitution() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both `&` and a backtick (``"../caixa-teia &
        // <backtick>sleep 1<backtick>"`` — the canonical "I pasted a
        // `cmd & <backtick>sleep N<backtick>` background-launch +
        // command-substitution chain" footgun) routes through
        // `FonteCaminhoShellBackground` not
        // `FonteCaminhoShellCommandSubstitution`. The background-
        // launch tail is the more common shell-history paste idiom
        // on every probe-as-both value — same cascade discipline
        // every prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia & `sleep 1`".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_semicolon_fires_before_shell_command_substitution() {
        // Cascade pin on the upstream shell-semicolon arm: a value
        // carrying both `;` and a backtick (``"../caixa-teia;
        // <backtick>whoami<backtick>"`` — the canonical "I pasted a
        // `cmd; <backtick>follow-up<backtick>` sequential-chain
        // footgun) routes through `FonteCaminhoShellSemicolon` not
        // `FonteCaminhoShellCommandSubstitution`. The sequential-
        // command-separator paste is the load-bearing root-cause
        // edit on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia; `whoami`".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_shell_command_substitution() {
        // Cascade pin on the upstream shell-pipe arm: a value
        // carrying both `|` and a backtick (``"../caixa-teia |
        // <backtick>tee log<backtick>"`` — the canonical pipeline-to-
        // command-substitution paste idiom) routes through
        // `FonteCaminhoShellPipe` not
        // `FonteCaminhoShellCommandSubstitution`. The pipeline-tail
        // paste is the load-bearing root-cause edit on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | `tee log`".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_command_substitution() {
        // Cascade pin on the upstream shell-redirection arm: a value
        // carrying both `>` and a backtick (``"../caixa-teia>log
        // <backtick>date<backtick>"`` — the canonical "I pasted a
        // `cmd > log <backtick>date<backtick>` redirect-plus-
        // substitution chain" footgun) routes through
        // `FonteCaminhoShellRedirection` not
        // `FonteCaminhoShellCommandSubstitution`. The input/output
        // redirection metachar carries the more self-locating `byte`
        // payload (it names which of `<` or `>` triggered), so the
        // prior arm wins on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>log `date`".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_command_substitution() {
        // Cascade pin on the upstream backslash arm: a value
        // carrying both `\` and a backtick (``"..\caixa-teia
        // <backtick>whoami<backtick>"`` — the canonical "I pasted a
        // Windows-shell `cd ..\path <backtick>whoami<backtick>`
        // chain") routes through `FonteCaminhoBackslash` not
        // `FonteCaminhoShellCommandSubstitution`. The cross-host-OS-
        // separator divergence is the load-bearing axis on every
        // probe-as-both value (an author who removes the `\` is the
        // root-cause edit; the backtick falls away in the same edit
        // since it's downstream of the Windows-shell convention).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia `whoami`".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_command_substitution() {
        // Cascade pin on the embedded-control-byte arm: a value
        // carrying both a control byte and a backtick (`"../foo\n
        // `whoami`"` — the canonical paste-from-multiline-doc
        // footgun where a newline landed mid-caminho between two
        // paste fragments) routes through `FonteCaminhoControlChar`
        // not `FonteCaminhoShellCommandSubstitution`. The POSIX-
        // syscall-rejected-byte / NUL-`CString::new`-fail diagnostic
        // is the load-bearing axis on every value that probes
        // positive for both — mirrors the cascade discipline on
        // every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n`whoami`".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_command_substitution() {
        // Cascade pin on the load-bearing leading-byte arm: a
        // leading `/` value with embedded backtick (``"/etc/passwd
        // <backtick>whoami<backtick>"``) routes through
        // `FonteCaminhoAbsolute` not
        // `FonteCaminhoShellCommandSubstitution` — the host-layout-
        // leak diagnostic is the load-bearing axis, the backtick
        // byte is the secondary observation. Same precedence logic
        // as every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/passwd `whoami`".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_command_substitution_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value
        // carrying both a backtick and a trailing `/`
        // (``"../`whoami`/"`` — the canonical "I tab-completed a
        // path that already had a backticked `whoami` substitution
        // tail" footgun) routes through
        // `FonteCaminhoShellCommandSubstitution` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-metachar
        // is the more semantic-locating axis (an author who removes
        // the backtick typically also drops the trailing separator
        // since both are paste-from-shell artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../`whoami`/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_command_substitution_diagnostic_carries_offending_dep_and_caminho() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_background_diagnostic_carries_offending_dep_and_caminho`
        // on the closest single-byte peer arm): the error's Display
        // surfaces the offending `:nome` and the offending `:caminho`
        // verbatim, and names the shell-command-substitution footgun
        // explicitly so a `feira lint` run can render the diagnostic
        // without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/`whoami`".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia/`whoami`"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains('`'),
            "diagnostic must reference the backtick footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("command-substitution"),
            "diagnostic must name the shell-command-substitution footgun: {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_star_glob() {
        // The fail-before-pass-after pin for the canonical pathname-
        // expansion paste footgun: an author copies an `ls
        // ../caixa-teia/*` shell-listing tail into the `:caminho`
        // slot and silently passes every prior arm
        // (`Path::is_absolute` false on `..`, no control bytes, no
        // `\`, no `<` / `>`, no `|`, no `;`, no `&`, no backtick,
        // doesn't end in `/`). The lacre embedded the value
        // verbatim, the resolver folded it through `Path::join`
        // looking for a literal `./../caixa-teia/*` subdirectory,
        // and the failure surfaced at resolve time with a non-self-
        // locating `No such file or directory` error. The new arm
        // moves the rejection to validate time and names the
        // offending dep + caminho + byte verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/*".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellGlob {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellGlob, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia/*");
        assert_eq!(byte, b'*');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_question_glob() {
        // The symmetric single-char-wildcard paste shape
        // (`"../foo?"` — the canonical "I copied a `rm foo?` line
        // out of shell history" idiom). Pinned separately from the
        // `*` shape so the gate's contract is "any `*` or `?`
        // anywhere", not single-byte coverage.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo?".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellGlob { byte, .. } = err else {
            panic!("expected FonteCaminhoShellGlob, got {err:?}");
        };
        assert_eq!(byte, b'?');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_star_glob() {
        // Leading-position `*` shape (`"*/caixa-teia"` — the
        // degenerate "I selected only the wildcard prefix out of a
        // shell-glob expression" idiom). Pinned separately from the
        // embedded-byte shapes so the gate covers every position,
        // not only mid-path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "*/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellGlob { byte: b'*', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_double_star_recursive_glob() {
        // The bash/zsh `globstar` recursive-glob shape
        // (`"../caixa-teia/**/foo"` — the canonical "I copied a
        // `find ../caixa-teia/**/foo` recursive expansion" idiom).
        // The arm fires on the first `*` encountered; pinned so a
        // future arm that tries to distinguish single `*` from
        // double `**` doesn't break the broader contract.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/**/foo".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellGlob { byte: b'*', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_dotted_extension_glob() {
        // The canonical extension-glob shape (`"../caixa-teia/*.lisp"`
        // — the "I selected `*.lisp` to mean every Lisp source file
        // in the dep root" footgun the prior arms structurally
        // cannot catch since `.` is a POSIX-valid path-component
        // byte). Pinned so the gate's contract covers the most
        // idiomatic glob-paste shape every author meets first.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/*.lisp".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellGlob { byte: b'*', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_glob() {
        // The positive-control pin: the gate targets only `*` /
        // `?`, never adjacent printable ASCII or POSIX-valid bytes.
        // The canonical relative POSIX path (`"../caixa-teia"`) and
        // a nested deeply-pathed variant with adjacent printable
        // punctuation (`"../caixa-teia/sub-dir.v2"`) must continue
        // to validate cleanly so the gate doesn't widen to a "no
        // printable punctuation anywhere" sweep that would defeat
        // the entire path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_command_substitution_fires_before_shell_glob() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both a backtick and `*` (``"../`whoami`/*"`` —
        // the canonical "I pasted a `cd <backtick>whoami<backtick>/*`
        // command-substitution + glob chain") routes through
        // `FonteCaminhoShellCommandSubstitution` not
        // `FonteCaminhoShellGlob`. The CWE-78 shell-command-
        // injection vector is the load-bearing root-cause edit on
        // every probe-as-both value — same cascade discipline every
        // prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../`whoami`/*".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_background_fires_before_shell_glob() {
        // Cascade pin on the upstream shell-background arm: a value
        // carrying both `&` and `*` (`"../caixa-teia & ls /*"` — the
        // canonical "I pasted a `cmd & ls /*` background + glob
        // chain" footgun) routes through `FonteCaminhoShellBackground`
        // not `FonteCaminhoShellGlob`. The background-launch tail is
        // the load-bearing root-cause edit on every probe-as-both
        // value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia & ls /*".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_semicolon_fires_before_shell_glob() {
        // Cascade pin on the upstream shell-semicolon arm: a value
        // carrying both `;` and `*` (`"../caixa-teia; rm *"` — the
        // canonical sequential-cleanup + glob paste idiom) routes
        // through `FonteCaminhoShellSemicolon` not
        // `FonteCaminhoShellGlob`. The sequential-command-separator
        // paste is the load-bearing root-cause edit on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia; rm *".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_shell_glob() {
        // Cascade pin on the upstream shell-pipe arm: a value
        // carrying both `|` and `*` (`"../caixa-teia | ls *"` — the
        // canonical pipeline-to-glob paste idiom) routes through
        // `FonteCaminhoShellPipe` not `FonteCaminhoShellGlob`. The
        // pipeline-tail paste is the load-bearing root-cause edit
        // on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | ls *".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_glob() {
        // Cascade pin on the upstream shell-redirection arm: a value
        // carrying both `>` and `*` (`"../caixa-teia>log *"` — the
        // canonical "I pasted a `cmd > log *` redirect-plus-glob
        // chain" footgun) routes through
        // `FonteCaminhoShellRedirection` not `FonteCaminhoShellGlob`.
        // The input/output redirection metachar carries the more
        // self-locating `byte` payload (it names which of `<` or `>`
        // triggered), so the prior arm wins on every probe-as-both
        // value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>log *".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_glob() {
        // Cascade pin on the upstream backslash arm: a value
        // carrying both `\` and `*` (`"..\caixa-teia\*"` — the
        // canonical "I pasted a Windows-shell `cd ..\path\*` glob
        // expression" footgun) routes through
        // `FonteCaminhoBackslash` not `FonteCaminhoShellGlob`. The
        // cross-host-OS-separator divergence is the load-bearing
        // axis on every probe-as-both value (an author who removes
        // the `\` is the root-cause edit; the `*` falls away in the
        // same edit since it's downstream of the Windows-shell
        // convention).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia\\*".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_glob() {
        // Cascade pin on the embedded-control-byte arm: a value
        // carrying both a control byte and `*` (`"../foo\n*"` — the
        // canonical paste-from-multiline-doc footgun where a
        // newline landed mid-caminho between two paste fragments)
        // routes through `FonteCaminhoControlChar` not
        // `FonteCaminhoShellGlob`. The POSIX-syscall-rejected-byte /
        // NUL-`CString::new`-fail diagnostic is the load-bearing
        // axis on every value that probes positive for both —
        // mirrors the cascade discipline on every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n*".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_glob() {
        // Cascade pin on the load-bearing leading-byte arm: a
        // leading `/` value with embedded `*` (`"/etc/*"`) routes
        // through `FonteCaminhoAbsolute` not `FonteCaminhoShellGlob`
        // — the host-layout-leak diagnostic is the load-bearing
        // axis, the glob byte is the secondary observation. Same
        // precedence logic as every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/*".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_glob_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value
        // carrying both `*` and a trailing `/` (`"../foo*/"` — the
        // canonical "I tab-completed a path that already had a
        // glob-expansion tail" footgun) routes through
        // `FonteCaminhoShellGlob` not `FonteCaminhoTrailingSlash`.
        // The embedded shell-metachar is the more semantic-locating
        // axis (an author who removes the `*` typically also drops
        // the trailing separator since both are paste-from-shell
        // artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo*/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellGlob { byte: b'*', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_glob_diagnostic_carries_offending_dep_caminho_and_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_redirection_diagnostic_*` on the
        // closest two-byte peer arm): the error's Display surfaces
        // the offending `:nome`, the offending `:caminho` verbatim,
        // the offending byte's hex / character form, and names the
        // shell-glob / pathname-expansion footgun explicitly so a
        // `feira lint` run can render the diagnostic without
        // re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/*.lisp".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia/*.lisp"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x2a"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("glob"),
            "diagnostic must name the shell-glob footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("pathname-expansion"),
            "diagnostic must reference the POSIX pathname-expansion vocabulary: {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_modern_command_substitution() {
        // The fail-before-pass-after pin for the canonical modern-Bourne
        // command-substitution paste footgun: an author copies a
        // `cd ../caixa-teia/$(date)/build` shell-history one-liner whose
        // `$(<cmd>)` expansion would land the current date as a
        // subdirectory name and silently passed every prior arm
        // (`Path::is_absolute` false on `..`, no control bytes, no `\`,
        // no `<` / `>`, no `|`, no `;`, no `&`, no backtick, no `*` /
        // `?`, doesn't end in `/`; the leading-`$` f4efe9c
        // `FonteCaminhoVarExpansion` arm doesn't fire because the `$`
        // sits mid-path). The lacre embedded the value verbatim, the
        // resolver folded it through `Path::join` looking for a literal
        // `./../caixa-teia/$(date)/build` subdirectory, and the failure
        // surfaced at resolve time with a non-self-locating `No such
        // file or directory` error. The new arm moves the rejection to
        // validate time and names the offending dep + caminho + byte
        // verbatim. The arm fires on the first `(` encountered (the
        // opening byte of `$(date)`).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/$(date)/build".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellSubshellGrouping {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellSubshellGrouping, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia/$(date)/build");
        assert_eq!(byte, b'(');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_close_paren() {
        // The symmetric close-paren paste shape (`"../caixa-teia)"` —
        // the degenerate "I selected an unbalanced closing paren out of
        // a shell-history block" idiom that probes for the cascade's
        // last-byte handling on a value carrying only the closing byte).
        // Pinned separately from the open-paren shape so the gate's
        // contract is "any `(` or `)` anywhere", not single-byte
        // coverage. Mirrors the peer `validate_rejects_path_fonte_with_\
        // caminho_carrying_question_glob` shape on the immediate-
        // predecessor `FonteCaminhoShellGlob` arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia)".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellSubshellGrouping { byte, .. } = err else {
            panic!("expected FonteCaminhoShellSubshellGrouping, got {err:?}");
        };
        assert_eq!(byte, b')');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_open_paren() {
        // Leading-position `(` shape (`"(cd foo)/caixa-teia"` — the
        // canonical "I selected a `(cd foo)` subshell-grouping prefix
        // out of a `(cd foo) && cmd` shell-history one-liner" idiom).
        // Pinned separately from the embedded-byte shape so the gate
        // covers every position, not only mid-path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "(cd foo)/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellSubshellGrouping { byte: b'(', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_balanced_subshell_grouping_pair() {
        // The canonical balanced-pair shape (`"../(pwd)/caixa-teia"`
        // — the canonical "I copied a `(pwd)` working-directory-probe
        // subshell-grouping idiom every shell-history block carries"
        // footgun). The value carries no other cascade-preceding
        // shell metachar (`&` / `;` / `|` / `<` / `>` / backtick /
        // `*` / `?`) so the arm fires on the first `(` encountered;
        // pinned so a future arm that tries to distinguish the
        // opening from the closing byte doesn't break the broader
        // contract. Mirrors the peer
        // `validate_rejects_path_fonte_with_caminho_carrying_balanced_\
        // backtick_pair` shape on the upstream `FonteCaminhoShell\
        // CommandSubstitution` arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../(pwd)/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellSubshellGrouping { byte: b'(', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_subshell_grouping() {
        // The positive-control pin: the gate targets only `(` / `)`,
        // never adjacent printable ASCII or POSIX-valid bytes. The
        // canonical relative POSIX path (`"../caixa-teia"`) and a
        // nested deeply-pathed variant with adjacent printable
        // punctuation (`"../caixa-teia/sub-dir.v2"`) must continue to
        // validate cleanly so the gate doesn't widen to a "no printable
        // punctuation anywhere" sweep that would defeat the entire
        // path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_glob_fires_before_shell_subshell_grouping() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both `*` and `(` (`"../caixa-teia/*(date)"` — the
        // canonical "I pasted a glob expansion followed by a
        // subshell-grouping tail" footgun) routes through
        // `FonteCaminhoShellGlob` not
        // `FonteCaminhoShellSubshellGrouping`. The pathname-expansion
        // shape is the more common shell-history paste idiom on every
        // probe-as-both value — same cascade discipline every prior
        // `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/*(date)".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellGlob { byte: b'*', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_command_substitution_fires_before_shell_subshell_grouping() {
        // Cascade pin on the upstream shell-command-substitution arm: a
        // value carrying both a backtick and `(` (``"../`whoami`/$(date)"``
        // — the canonical "I pasted a legacy-backtick + modern-paren
        // command-substitution chain" footgun) routes through
        // `FonteCaminhoShellCommandSubstitution` not
        // `FonteCaminhoShellSubshellGrouping`. The CWE-78 shell-
        // command-injection vector is the load-bearing root-cause edit
        // on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../`whoami`/$(date)".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_background_fires_before_shell_subshell_grouping() {
        // Cascade pin on the upstream shell-background arm: a value
        // carrying both `&` and `(` (`"../caixa-teia & (cd foo)"` —
        // the canonical "I pasted a `cmd & (cd foo)` background-launch
        // + subshell-grouping chain" footgun) routes through
        // `FonteCaminhoShellBackground` not
        // `FonteCaminhoShellSubshellGrouping`. The background-launch
        // tail is the load-bearing root-cause edit on every probe-as-
        // both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia & (cd foo)".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_semicolon_fires_before_shell_subshell_grouping() {
        // Cascade pin on the upstream shell-semicolon arm: a value
        // carrying both `;` and `(` (`"../caixa-teia; (cd foo)"` —
        // the canonical sequential-cleanup + subshell-grouping paste
        // idiom) routes through `FonteCaminhoShellSemicolon` not
        // `FonteCaminhoShellSubshellGrouping`. The sequential-command-
        // separator paste is the load-bearing root-cause edit on
        // every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia; (cd foo)".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_shell_subshell_grouping() {
        // Cascade pin on the upstream shell-pipe arm: a value carrying
        // both `|` and `(` (`"../caixa-teia | (tee log)"` — the
        // canonical pipeline-to-subshell-grouping paste idiom) routes
        // through `FonteCaminhoShellPipe` not
        // `FonteCaminhoShellSubshellGrouping`. The pipeline-tail paste
        // is the load-bearing root-cause edit on every probe-as-both
        // value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | (tee log)".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_subshell_grouping() {
        // Cascade pin on the upstream shell-redirection arm: a value
        // carrying both `>` and `(` (`"../caixa-teia>log (cd foo)"` —
        // the canonical "I pasted a `cmd > log (cd foo)` redirect-
        // plus-subshell-grouping chain" footgun) routes through
        // `FonteCaminhoShellRedirection` not
        // `FonteCaminhoShellSubshellGrouping`. The input/output
        // redirection metachar carries the more self-locating `byte`
        // payload (it names which of `<` or `>` triggered), so the
        // prior arm wins on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>log (cd foo)".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_subshell_grouping() {
        // Cascade pin on the upstream backslash arm: a value carrying
        // both `\` and `(` (`"..\caixa-teia\(cd foo)"` — the canonical
        // "I pasted a Windows-shell `cd ..\path\(cmd)` chain") routes
        // through `FonteCaminhoBackslash` not
        // `FonteCaminhoShellSubshellGrouping`. The cross-host-OS-
        // separator divergence is the load-bearing axis on every
        // probe-as-both value (an author who removes the `\` is the
        // root-cause edit; the `(` falls away in the same edit since
        // it's downstream of the Windows-shell convention).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia\\(cd foo)".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_subshell_grouping() {
        // Cascade pin on the embedded-control-byte arm: a value
        // carrying both a control byte and `(` (`"../foo\n(cd bar)"` —
        // the canonical paste-from-multiline-doc footgun where a
        // newline landed mid-caminho between two paste fragments)
        // routes through `FonteCaminhoControlChar` not
        // `FonteCaminhoShellSubshellGrouping`. The POSIX-syscall-
        // rejected-byte / NUL-`CString::new`-fail diagnostic is the
        // load-bearing axis on every value that probes positive for
        // both — mirrors the cascade discipline on every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n(cd bar)".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_subshell_grouping() {
        // Cascade pin on the load-bearing leading-byte arm: a leading
        // `/` value with embedded `(` (`"/etc/(cd foo)"`) routes
        // through `FonteCaminhoAbsolute` not
        // `FonteCaminhoShellSubshellGrouping` — the host-layout-leak
        // diagnostic is the load-bearing axis, the subshell-grouping
        // byte is the secondary observation. Same precedence logic as
        // every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/(cd foo)".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_var_expansion_fires_before_shell_subshell_grouping() {
        // Cascade pin on the upstream leading-`$` var-expansion arm: a
        // value carrying both a leading `$` and a `(` (`"$(date)/\
        // caixa-teia"` — the canonical "I pasted a `$(date)` modern-
        // command-substitution at the head of a sibling-workspace
        // path" footgun) routes through `FonteCaminhoVarExpansion` not
        // `FonteCaminhoShellSubshellGrouping`. The leading-byte
        // shell-variable-expansion is the more self-locating diagnostic
        // on values that probe as both — same load-bearing-leading-
        // byte cascade discipline every prior `:caminho` arm
        // establishes. Closing both halves of `$(<cmd>)` structurally
        // (leading `$` here, trailing `)` on the new arm) excludes the
        // entire modern Bourne command-substitution surface from the
        // typed `:caminho` accepted set; the cascade preserves the
        // narrower leading-byte diagnostic on values that probe both
        // halves at the canonical leading position.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$(date)/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_subshell_grouping_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value carrying
        // both `(` and a trailing `/` (`"../(cd foo)/"` — the canonical
        // "I tab-completed a path that already had a subshell-grouping
        // expansion tail" footgun) routes through
        // `FonteCaminhoShellSubshellGrouping` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-metachar is
        // the more semantic-locating axis (an author who removes the
        // `(` typically also drops the trailing separator since both
        // are paste-from-shell artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../(cd foo)/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellSubshellGrouping { byte: b'(', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_subshell_grouping_diagnostic_carries_offending_dep_caminho_and_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_glob_diagnostic_carries_offending_dep_caminho_and_byte`
        // on the closest two-byte peer arm): the error's Display
        // surfaces the offending `:nome`, the offending `:caminho`
        // verbatim, the offending byte's hex / character form, and
        // names the shell-subshell-grouping footgun explicitly so a
        // `feira lint` run can render the diagnostic without re-
        // parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/$(date)/build".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia/$(date)/build"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x28"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("subshell-grouping"),
            "diagnostic must name the shell-subshell-grouping footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("command-substitution"),
            "diagnostic must reference the `$(<cmd>)` command-substitution vocabulary: \
             {rendered:?}",
        );
    }

    // ── shell-brace-expansion / URI-Template-placeholder arm ───────────
    //
    // Peer with the prior `FonteCaminhoShellSubshellGrouping` (`(` /
    // `)`) byte-pair arm: the same per-byte cascade with the same
    // self-locating `byte: u8` diagnostic on the orthogonal `{` /
    // `}` brace-expansion / URI-Template placeholder axis. The peer
    // [`crate::render::is_git_repo_url`] (42d8f9d) closes the same
    // byte pair on the sibling `:fonte :repo` axis under the same
    // banner.

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_brace_expansion_fan_across_siblings() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // shell-history brace-expansion footgun: an author copies a
        // `cd ../{caixa-teia,caixa-helm}/build` shell-history one-
        // liner whose `{a,b}` brace expansion fans across two siblings
        // and silently passed every prior arm (`Path::is_absolute`
        // false on `..`, no control bytes, no `\`, no `<` / `>`, no
        // `|`, no `;`, no `&`, no backtick, no `*` / `?`, no `(` /
        // `)`, doesn't end in `/`; the leading-`$` f4efe9c
        // `FonteCaminhoVarExpansion` arm doesn't fire because the
        // value starts with `..` not `$`). The lacre embedded the
        // value verbatim, the resolver folded it through `Path::join`
        // looking for a literal `./../{caixa-teia,caixa-helm}/build`
        // subdirectory, and the failure surfaced at resolve time with
        // a non-self-locating `No such file or directory` error. The
        // new arm moves the rejection to validate time and names the
        // offending dep + caminho + byte verbatim. The arm fires on
        // the first `{` encountered.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../{caixa-teia,caixa-helm}/build".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellBraceExpansion {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellBraceExpansion, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../{caixa-teia,caixa-helm}/build");
        assert_eq!(byte, b'{');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_close_brace() {
        // The symmetric close-brace paste shape (`"../caixa-teia}"` —
        // the degenerate "I selected an unbalanced closing brace out
        // of a shell-history block" idiom that probes for the
        // cascade's last-byte handling on a value carrying only the
        // closing byte). Pinned separately from the open-brace shape
        // so the gate's contract is "any `{` or `}` anywhere", not
        // single-byte coverage. Mirrors the peer
        // `validate_rejects_path_fonte_with_caminho_carrying_close_paren`
        // shape on the immediate-predecessor `FonteCaminhoShellSubshellGrouping`
        // arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia}".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellBraceExpansion { byte, .. } = err else {
            panic!("expected FonteCaminhoShellBraceExpansion, got {err:?}");
        };
        assert_eq!(byte, b'}');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_open_brace() {
        // Leading-position `{` shape (`"{caixa-teia,caixa-helm}/build"`
        // — the canonical "I selected a `{a,b}` brace-expansion prefix
        // out of a shell-history one-liner" idiom). Pinned separately
        // from the embedded-byte shape so the gate covers every
        // position, not only mid-path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "{caixa-teia,caixa-helm}/build".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBraceExpansion { byte: b'{', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_uri_template_placeholder() {
        // The canonical URI-Template / Mustache / Helm doubled-brace
        // placeholder shape (`"../{{org}}/caixa-teia"` — the canonical
        // "I copied a `https://github.com/{{org}}/caixa-teia` README
        // quick-start / OpenAPI spec / Helm chart `home:` template
        // and forgot to substitute the placeholder" footgun). The arm
        // fires on the first `{` encountered; pinned so the gate's
        // coverage extends from the bare-brace shell-history shape to
        // the doubled-brace URI-Template / templating-engine shape.
        // Mirrors the peer 42d8f9d `is_git_repo_url` arm on the
        // sibling `:fonte :repo` axis.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../{{org}}/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBraceExpansion { byte: b'{', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_brace_range_expansion() {
        // The canonical bash brace-range-expansion shape (`"../caixa-
        // v{1..10}"` — the `{1..10}` sequence expansion every bash /
        // zsh `for i in {1..10}; do …; done` idiom uses, the symmetric
        // sequence-range form to the `{a,b,c}` comma-separated form).
        // The arm fires on the first `{` encountered; pinned so the
        // gate's coverage extends from the comma-separated form to
        // the integer-range form.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-v{1..10}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBraceExpansion { byte: b'{', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_brace_expansion() {
        // The positive-control pin: the gate targets only `{` / `}`,
        // never adjacent printable ASCII or POSIX-valid bytes. The
        // canonical relative POSIX path (`"../caixa-teia"`) and a
        // nested deeply-pathed variant with adjacent printable
        // punctuation (`"../caixa-teia/sub-dir.v2"`) must continue to
        // validate cleanly so the gate doesn't widen to a "no
        // printable punctuation anywhere" sweep that would defeat
        // the entire path-fonte author surface. Peer with
        // `validate_accepts_path_fonte_with_caminho_carrying_no_subshell_grouping`
        // on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_subshell_grouping_fires_before_shell_brace_expansion() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both `(` and `{` (`"../(cd foo)/{a,b}"` — the
        // canonical "I pasted a subshell-grouping followed by a
        // brace-expansion tail" footgun) routes through
        // `FonteCaminhoShellSubshellGrouping` not
        // `FonteCaminhoShellBraceExpansion`. The subshell-grouping
        // shape is the more semantic-locating axis on every probe-
        // as-both value because it closes both halves of the modern
        // Bourne `$(<cmd>)` command-substitution surface — same
        // cascade discipline every prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../(cd foo)/{a,b}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellSubshellGrouping { byte: b'(', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_glob_fires_before_shell_brace_expansion() {
        // Cascade pin on the upstream shell-glob arm: a value carrying
        // both `*` and `{` (`"../caixa-teia/*{a,b}"` — the canonical
        // "I pasted a glob expansion followed by a brace-expansion
        // tail" footgun) routes through `FonteCaminhoShellGlob` not
        // `FonteCaminhoShellBraceExpansion`. The pathname-expansion
        // shape is the load-bearing root-cause edit on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/*{a,b}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellGlob { byte: b'*', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_command_substitution_fires_before_shell_brace_expansion() {
        // Cascade pin on the upstream shell-command-substitution arm:
        // a value carrying both a backtick and `{` (``"../`whoami`/{a,b}"``
        // — the canonical "I pasted a legacy-backtick command-
        // substitution followed by a brace-expansion fan-out" footgun)
        // routes through `FonteCaminhoShellCommandSubstitution` not
        // `FonteCaminhoShellBraceExpansion`. The CWE-78 shell-
        // command-injection vector is the load-bearing root-cause
        // edit on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../`whoami`/{a,b}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_background_fires_before_shell_brace_expansion() {
        // Cascade pin on the upstream shell-background arm: a value
        // carrying both `&` and `{` (`"../caixa-teia & {a,b}"` — the
        // canonical "I pasted a `cmd & {fork-fan}` background-launch
        // + brace-expansion chain" footgun) routes through
        // `FonteCaminhoShellBackground` not
        // `FonteCaminhoShellBraceExpansion`. The background-launch
        // tail is the load-bearing root-cause edit on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia & {a,b}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_semicolon_fires_before_shell_brace_expansion() {
        // Cascade pin on the upstream shell-semicolon arm: a value
        // carrying both `;` and `{` (`"../caixa-teia; {a,b}"` — the
        // canonical sequential-cleanup + brace-expansion paste
        // idiom) routes through `FonteCaminhoShellSemicolon` not
        // `FonteCaminhoShellBraceExpansion`. The sequential-command-
        // separator paste is the load-bearing root-cause edit on
        // every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia; {a,b}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_shell_brace_expansion() {
        // Cascade pin on the upstream shell-pipe arm: a value
        // carrying both `|` and `{` (`"../caixa-teia | {tee,cat}"`
        // — the canonical pipeline-to-brace-expansion paste idiom)
        // routes through `FonteCaminhoShellPipe` not
        // `FonteCaminhoShellBraceExpansion`. The pipeline-tail paste
        // is the load-bearing root-cause edit on every probe-as-
        // both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | {tee,cat}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_brace_expansion() {
        // Cascade pin on the upstream shell-redirection arm: a value
        // carrying both `>` and `{` (`"../caixa-teia>log {a,b}"` —
        // the canonical "I pasted a `cmd > log {a,b}` redirect-
        // plus-brace-expansion chain" footgun) routes through
        // `FonteCaminhoShellRedirection` not
        // `FonteCaminhoShellBraceExpansion`. The input/output
        // redirection metachar carries the more self-locating
        // `byte` payload, so the prior arm wins on every probe-
        // as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>log {a,b}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_brace_expansion() {
        // Cascade pin on the upstream backslash arm: a value
        // carrying both `\` and `{` (`"..\caixa-teia\{a,b}"` — the
        // canonical "I pasted a Windows-shell `cd ..\path\{a,b}`
        // chain") routes through `FonteCaminhoBackslash` not
        // `FonteCaminhoShellBraceExpansion`. The cross-host-OS-
        // separator divergence is the load-bearing axis on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia\\{a,b}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_brace_expansion() {
        // Cascade pin on the embedded-control-byte arm: a value
        // carrying both a control byte and `{` (`"../foo\n{a,b}"` —
        // the canonical paste-from-multiline-doc footgun where a
        // newline landed mid-caminho between two paste fragments)
        // routes through `FonteCaminhoControlChar` not
        // `FonteCaminhoShellBraceExpansion`. The POSIX-syscall-
        // rejected-byte / NUL-`CString::new`-fail diagnostic is the
        // load-bearing axis on every value that probes positive for
        // both — mirrors the cascade discipline on every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n{a,b}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_brace_expansion() {
        // Cascade pin on the load-bearing leading-byte arm: a
        // leading `/` value with embedded `{` (`"/etc/{a,b}"`)
        // routes through `FonteCaminhoAbsolute` not
        // `FonteCaminhoShellBraceExpansion` — the host-layout-leak
        // diagnostic is the load-bearing axis, the brace-expansion
        // byte is the secondary observation. Same precedence logic
        // as every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/{a,b}".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_var_expansion_fires_before_shell_brace_expansion() {
        // Cascade pin on the upstream leading-`$` var-expansion
        // arm: a value carrying both a leading `$` and a `{`
        // (`"${ORG}/caixa-teia"` — the canonical "I pasted a
        // `${ORG}` shell-variable + curly-brace expansion at the
        // head of a sibling-workspace path" footgun) routes through
        // `FonteCaminhoVarExpansion` not
        // `FonteCaminhoShellBraceExpansion`. The leading-byte
        // shell-variable-expansion is the more self-locating
        // diagnostic on values that probe as both — same
        // load-bearing-leading-byte cascade discipline every prior
        // `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "${ORG}/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_brace_expansion_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value
        // carrying both `{` and a trailing `/`
        // (`"../{caixa-teia,caixa-helm}/"` — the canonical "I
        // tab-completed a path that already had a brace-expansion
        // expansion tail" footgun) routes through
        // `FonteCaminhoShellBraceExpansion` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-metachar
        // is the more semantic-locating axis (an author who removes
        // the `{` typically also drops the trailing separator since
        // both are paste-from-shell artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../{caixa-teia,caixa-helm}/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBraceExpansion { byte: b'{', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_brace_expansion_diagnostic_carries_offending_dep_caminho_and_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_subshell_grouping_diagnostic_carries_offending_dep_caminho_and_byte`
        // on the closest two-byte peer arm): the error's Display
        // surfaces the offending `:nome`, the offending `:caminho`
        // verbatim, the offending byte's hex / character form, and
        // names the shell-brace-expansion / URI-Template footgun
        // explicitly so a `feira lint` run can render the diagnostic
        // without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../{caixa-teia,caixa-helm}/build".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../{caixa-teia,caixa-helm}/build"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x7b"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("brace-expansion"),
            "diagnostic must name the shell-brace-expansion footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("URI Template"),
            "diagnostic must reference the RFC-6570 URI-Template-placeholder vocabulary: \
             {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_bracket_glob_character_class() {
        // The canonical paste-from-shell-history bracket-glob /
        // character-class footgun: an author copies a
        // `cd ../caixa-[a-z]/build` shell-history one-liner whose
        // `[a-z]` POSIX glob character-class matches every lowercase-
        // ASCII-suffix sibling caixa directory and silently passed
        // every prior arm (`Path::is_absolute` false on `..`, no
        // control bytes, no `\`, no `<` / `>`, no `|`, no `;`, no
        // `&`, no backtick, no `*` / `?`, no `(` / `)`, no `{` /
        // `}`, doesn't end in `/`; the leading-`$` f4efe9c
        // `FonteCaminhoVarExpansion` arm doesn't fire because the
        // value starts with `..` not `$`). The lacre embedded the
        // value verbatim, the resolver folded it through
        // `Path::join` looking for a literal `./../caixa-[a-z]/
        // build` subdirectory, and the failure surfaced at resolve
        // time with a non-self-locating `No such file or directory`
        // error. The new arm moves the rejection to validate time
        // and names the offending dep + caminho + byte verbatim.
        // The arm fires on the first `[` encountered.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-[a-z]/build".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellBracketExpansion {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellBracketExpansion, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-[a-z]/build");
        assert_eq!(byte, b'[');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_close_bracket() {
        // The symmetric close-bracket paste shape (`"../caixa-teia]"`
        // — the degenerate "I selected an unbalanced closing bracket
        // out of a glob character-class block" idiom that probes for
        // the cascade's last-byte handling on a value carrying only
        // the closing byte). Pinned separately from the open-bracket
        // shape so the gate's contract is "any `[` or `]` anywhere",
        // not single-byte coverage. Mirrors the peer
        // `validate_rejects_path_fonte_with_caminho_carrying_close_brace`
        // shape on the immediate-predecessor
        // `FonteCaminhoShellBraceExpansion` arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia]".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellBracketExpansion { byte, .. } = err else {
            panic!("expected FonteCaminhoShellBracketExpansion, got {err:?}");
        };
        assert_eq!(byte, b']');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_open_bracket() {
        // Leading-position `[` shape (`"[caixa-teia]/build"` — the
        // canonical "I selected a `[caixa-teia]` TOML-table-header /
        // glob-character-class prefix out of an aligned config /
        // shell-history one-liner" idiom). Pinned separately from
        // the embedded-byte shape so the gate covers every position,
        // not only mid-path.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "[caixa-teia]/build".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBracketExpansion { byte: b'[', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_toml_inline_array() {
        // The canonical TOML inline-array / YAML flow-sequence
        // paste shape (`"../[\"a\", \"b\"]/caixa-teia"` — the
        // canonical "I copied a `features = [\"a\", \"b\"]` TOML
        // inline-array out of a sibling-Cargo manifest" cross-idiom
        // leak; the symmetric YAML flow-sequence form `paths: [/a,
        // /b]` paste-from-values.yaml shape carries the same
        // bracket pair). The arm fires on the first `[` encountered;
        // pinned so the gate's coverage extends from the bare-
        // bracket glob-character-class shape to the TOML / YAML /
        // JSON array-literal shape.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../[\"a\", \"b\"]/caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBracketExpansion { byte: b'[', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_shell_test_builtin() {
        // The canonical POSIX `test` / `[` builtin command paste
        // shape (`"../[ -d caixa-teia ]"` — the `[ <expr> ]` shell-
        // script conditional every paste-from-shell-script idiom
        // carries; bash's `[[ <expr> ]]` extended-test grammar
        // would surface the same byte pair). The arm fires on the
        // first `[` encountered; pinned so the gate's coverage
        // extends from the embedded-glob-character-class shape to
        // the leading-`test`-builtin / extended-test form.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../[ -d caixa-teia ]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBracketExpansion { byte: b'[', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_bracket_expansion() {
        // The positive-control pin: the gate targets only `[` /
        // `]`, never adjacent printable ASCII or POSIX-valid bytes.
        // The canonical relative POSIX path (`"../caixa-teia"`) and
        // a nested deeply-pathed variant with adjacent printable
        // punctuation (`"../caixa-teia/sub-dir.v2"`) must continue
        // to validate cleanly so the gate doesn't widen to a "no
        // printable punctuation anywhere" sweep that would defeat
        // the entire path-fonte author surface. Peer with
        // `validate_accepts_path_fonte_with_caminho_carrying_no_brace_expansion`
        // on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_brace_expansion_fires_before_shell_bracket_expansion() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both `{` and `[` (`"../{a,b}[ch]"` — the
        // canonical "I pasted a brace-expansion fan followed by a
        // glob-character-class tail" footgun) routes through
        // `FonteCaminhoShellBraceExpansion` not
        // `FonteCaminhoShellBracketExpansion`. The brace-expansion
        // fan is the load-bearing root-cause edit on every
        // probe-as-both value because the bracket-class tail
        // typically rides on a prior brace-expansion expansion;
        // same cascade discipline every prior `:caminho` arm
        // establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../{a,b}[ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBraceExpansion { byte: b'{', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_subshell_grouping_fires_before_shell_bracket_expansion() {
        // Cascade pin on the upstream shell-subshell-grouping arm:
        // a value carrying both `(` and `[` (`"../(cd foo)/[ch]"` —
        // the canonical "I pasted a subshell-grouping followed by
        // a glob-character-class tail" footgun) routes through
        // `FonteCaminhoShellSubshellGrouping` not
        // `FonteCaminhoShellBracketExpansion`. The modern Bourne
        // `$(<cmd>)` command-substitution boundary is the load-
        // bearing axis on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../(cd foo)/[ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellSubshellGrouping { byte: b'(', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_glob_fires_before_shell_bracket_expansion() {
        // Cascade pin on the upstream shell-glob arm: a value
        // carrying both `*` and `[` (`"../caixa-teia/*[ch]"` — the
        // canonical "I pasted a `*.[ch]` C-source-file glob whose
        // unbounded `*` precedes the bracket character-class"
        // footgun) routes through `FonteCaminhoShellGlob` not
        // `FonteCaminhoShellBracketExpansion`. The unbounded
        // pathname-expansion sentinel is the load-bearing root-
        // cause edit on every probe-as-both value — the unbounded
        // `*` carries the more aggressive expansion vector than
        // the bounded `[ch]` class, so the prior arm wins.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/*[ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellGlob { byte: b'*', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_command_substitution_fires_before_shell_bracket_expansion() {
        // Cascade pin on the upstream shell-command-substitution
        // arm: a value carrying both a backtick and `[`
        // (``"../`whoami`/[ch]"`` — the canonical "I pasted a
        // legacy-backtick command-substitution followed by a
        // glob-character-class tail" footgun) routes through
        // `FonteCaminhoShellCommandSubstitution` not
        // `FonteCaminhoShellBracketExpansion`. The CWE-78 shell-
        // command-injection vector is the load-bearing root-cause
        // edit on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../`whoami`/[ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_background_fires_before_shell_bracket_expansion() {
        // Cascade pin on the upstream shell-background arm: a
        // value carrying both `&` and `[` (`"../caixa-teia & [ch]"`
        // — the canonical "I pasted a `cmd & [glob]` background-
        // launch + bracket-class chain" footgun) routes through
        // `FonteCaminhoShellBackground` not
        // `FonteCaminhoShellBracketExpansion`. The background-
        // launch tail is the load-bearing root-cause edit on
        // every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia & [ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_semicolon_fires_before_shell_bracket_expansion() {
        // Cascade pin on the upstream shell-semicolon arm: a value
        // carrying both `;` and `[` (`"../caixa-teia; [ch]"` — the
        // canonical sequential-cleanup + bracket-class paste
        // idiom) routes through `FonteCaminhoShellSemicolon` not
        // `FonteCaminhoShellBracketExpansion`. The sequential-
        // command-separator paste is the load-bearing root-cause
        // edit on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia; [ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_shell_bracket_expansion() {
        // Cascade pin on the upstream shell-pipe arm: a value
        // carrying both `|` and `[` (`"../caixa-teia | [tee]"` —
        // the canonical pipeline-to-bracket-class paste idiom)
        // routes through `FonteCaminhoShellPipe` not
        // `FonteCaminhoShellBracketExpansion`. The pipeline-tail
        // paste is the load-bearing root-cause edit on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | [tee]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_bracket_expansion() {
        // Cascade pin on the upstream shell-redirection arm: a
        // value carrying both `>` and `[` (`"../caixa-teia>log
        // [ch]"` — the canonical "I pasted a `cmd > log [glob]`
        // redirect-plus-bracket chain" footgun) routes through
        // `FonteCaminhoShellRedirection` not
        // `FonteCaminhoShellBracketExpansion`. The input/output
        // redirection metachar carries the more self-locating
        // `byte` payload, so the prior arm wins on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>log [ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_bracket_expansion() {
        // Cascade pin on the upstream backslash arm: a value
        // carrying both `\` and `[` (`"..\caixa-teia\[ch]"` — the
        // canonical "I pasted a Windows-shell `cd ..\path\[glob]`
        // chain") routes through `FonteCaminhoBackslash` not
        // `FonteCaminhoShellBracketExpansion`. The cross-host-OS-
        // separator divergence is the load-bearing axis on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia\\[ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_bracket_expansion() {
        // Cascade pin on the embedded-control-byte arm: a value
        // carrying both a control byte and `[` (`"../foo\n[ch]"` —
        // the canonical paste-from-multiline-doc footgun where a
        // newline landed mid-caminho between two paste fragments)
        // routes through `FonteCaminhoControlChar` not
        // `FonteCaminhoShellBracketExpansion`. The POSIX-syscall-
        // rejected-byte / NUL-`CString::new`-fail diagnostic is
        // the load-bearing axis on every value that probes
        // positive for both — mirrors the cascade discipline on
        // every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n[ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_bracket_expansion() {
        // Cascade pin on the load-bearing leading-byte arm: a
        // leading `/` value with embedded `[` (`"/etc/[ch]"`)
        // routes through `FonteCaminhoAbsolute` not
        // `FonteCaminhoShellBracketExpansion` — the host-layout-
        // leak diagnostic is the load-bearing axis, the bracket-
        // expansion byte is the secondary observation. Same
        // precedence logic as every prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/[ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_var_expansion_fires_before_shell_bracket_expansion() {
        // Cascade pin on the upstream leading-`$` var-expansion
        // arm: a value carrying both a leading `$` and a `[`
        // (`"$DIR/[ch]"` — the canonical "I pasted a `$DIR` shell-
        // variable + bracket-class at the head of a sibling-
        // workspace path" footgun) routes through
        // `FonteCaminhoVarExpansion` not
        // `FonteCaminhoShellBracketExpansion`. The leading-byte
        // shell-variable-expansion is the more self-locating
        // diagnostic on values that probe as both — same
        // load-bearing-leading-byte cascade discipline every
        // prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$DIR/[ch]".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_bracket_expansion_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value
        // carrying both `[` and a trailing `/` (`"../[a-z]/"` —
        // the canonical "I tab-completed a path that already had
        // a bracket-glob-character-class expansion tail" footgun)
        // routes through `FonteCaminhoShellBracketExpansion` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-metachar
        // is the more semantic-locating axis (an author who
        // removes the `[` typically also drops the trailing
        // separator since both are paste-from-shell artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../[a-z]/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBracketExpansion { byte: b'[', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_bracket_expansion_diagnostic_carries_offending_dep_caminho_and_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_brace_expansion_diagnostic_carries_offending_dep_caminho_and_byte`
        // on the closest two-byte peer arm): the error's Display
        // surfaces the offending `:nome`, the offending `:caminho`
        // verbatim, the offending byte's hex / character form, and
        // names the shell-bracket-expansion / glob-character-class
        // footgun explicitly so a `feira lint` run can render the
        // diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-[a-z]/build".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-[a-z]/build"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x5b"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("bracket-expansion"),
            "diagnostic must name the shell-bracket-expansion footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("glob-character-class"),
            "diagnostic must reference the POSIX glob-character-class vocabulary: \
             {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_single_quote_grouping() {
        // The canonical paste-from-shell-history strong-quoted
        // sibling-workspace-path footgun: an author copies a
        // `cd '../caixa-teia'` shell-history one-liner whose strong-
        // quoting preserved the path across a whitespace paste
        // boundary and silently passed every prior arm
        // (`Path::is_absolute` false on `'..`, no control bytes, no
        // `\`, no `<` / `>`, no `|`, no `;`, no `&`, no backtick, no
        // `*` / `?`, no `(` / `)`, no `{` / `}`, no `[` / `]`,
        // doesn't end in `/`; the leading-`$` f4efe9c
        // `FonteCaminhoVarExpansion` arm doesn't fire because the
        // value starts with `'` not `$`). The lacre embedded the
        // value verbatim, the resolver folded it through
        // `Path::join` looking for a literal `./'../caixa-teia'`
        // subdirectory, and the failure surfaced at resolve time
        // with a non-self-locating `No such file or directory`
        // error. The new arm moves the rejection to validate time
        // and names the offending dep + caminho + byte verbatim.
        // The arm fires on the first `'` encountered.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "'../caixa-teia'".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellQuoteGrouping {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellQuoteGrouping, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "'../caixa-teia'");
        assert_eq!(byte, b'\'');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_double_quote_grouping() {
        // The symmetric weak-quoted paste shape (`"\"../caixa-teia\""`
        // — the canonical paste-from-JSON-config / paste-from-YAML-
        // flow-scalar / paste-from-TOML-basic-string / paste-from-
        // tatara-lisp-string-literal cross-idiom leak). Pinned
        // separately from the single-quote shape so the gate's
        // contract is "any `'` or `\"` anywhere", not single-byte
        // coverage. Mirrors the peer
        // `validate_rejects_path_fonte_with_caminho_carrying_close_bracket`
        // shape on the immediate-predecessor
        // `FonteCaminhoShellBracketExpansion` arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "\"../caixa-teia\"".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellQuoteGrouping { byte, .. } = err else {
            panic!("expected FonteCaminhoShellQuoteGrouping, got {err:?}");
        };
        assert_eq!(byte, b'"');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_double_quote() {
        // Embedded-position `"` shape (`"../\"caixa-teia\""` — the
        // canonical "I pasted a JSON key-value pair fragment into
        // the middle of the path" idiom). Pinned separately from
        // the leading-byte shape so the gate covers every position,
        // not only leading.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../\"caixa-teia\"".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellQuoteGrouping { byte: b'"', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_yaml_flow_scalar_paste() {
        // The canonical YAML double-quoted flow-scalar cross-idiom
        // leak shape (`"path: \"../caixa-teia\""` — the "I copied a
        // `path: \"...\"` YAML flow-scalar entry out of an aligned
        // values.yaml / K8s manifest and dropped it verbatim into
        // the `:caminho` slot including the `path: ` key prefix"
        // paste-idiom). The arm fires on the first `"` encountered;
        // pinned so the gate's coverage extends from the bare-quote
        // paste shape to the aligned-YAML-manifest cross-idiom-leak
        // shape.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "path: \"../caixa-teia\"".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellQuoteGrouping { byte: b'"', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_quote_grouping() {
        // The positive-control pin: the gate targets only `'` /
        // `"`, never adjacent printable ASCII or POSIX-valid bytes.
        // The canonical relative POSIX path (`"../caixa-teia"`) and
        // a nested deeply-pathed variant with adjacent printable
        // punctuation (`"../caixa-teia/sub-dir.v2"`) must continue
        // to validate cleanly so the gate doesn't widen to a "no
        // printable punctuation anywhere" sweep that would defeat
        // the entire path-fonte author surface. Peer with
        // `validate_accepts_path_fonte_with_caminho_carrying_no_bracket_expansion`
        // on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_bracket_expansion_fires_before_shell_quote_grouping() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both `[` and `'` (`"../[a-z]'x'"` — the canonical
        // "I pasted a glob-character-class followed by a strong-
        // quoted literal tail" footgun) routes through
        // `FonteCaminhoShellBracketExpansion` not
        // `FonteCaminhoShellQuoteGrouping`. The glob-character-class
        // expansion is the load-bearing root-cause edit on every
        // probe-as-both value; same cascade discipline every prior
        // `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../[a-z]'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBracketExpansion { byte: b'[', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_brace_expansion_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream shell-brace-expansion arm: a
        // value carrying both `{` and `'` (`"../{a,b}'x'"` — the
        // canonical "I pasted a brace-expansion fan followed by a
        // strong-quoted literal tail" footgun) routes through
        // `FonteCaminhoShellBraceExpansion` not
        // `FonteCaminhoShellQuoteGrouping`. The brace-expansion fan
        // is the load-bearing root-cause edit on every probe-as-
        // both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../{a,b}'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBraceExpansion { byte: b'{', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_subshell_grouping_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream shell-subshell-grouping arm:
        // a value carrying both `(` and `'` (`"../(cd foo)/'x'"` —
        // the canonical "I pasted a subshell-grouping followed by
        // a strong-quoted literal tail" footgun) routes through
        // `FonteCaminhoShellSubshellGrouping` not
        // `FonteCaminhoShellQuoteGrouping`. The modern Bourne
        // `$(<cmd>)` command-substitution boundary is the load-
        // bearing axis on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../(cd foo)/'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellSubshellGrouping { byte: b'(', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_glob_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream shell-glob arm: a value
        // carrying both `*` and `'` (`"../caixa-teia/*'x'"` — the
        // canonical "I pasted a `*` unbounded pathname-expansion
        // followed by a strong-quoted literal tail" footgun) routes
        // through `FonteCaminhoShellGlob` not
        // `FonteCaminhoShellQuoteGrouping`. The unbounded pathname-
        // expansion sentinel is the load-bearing root-cause edit
        // on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/*'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellGlob { byte: b'*', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_command_substitution_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream shell-command-substitution
        // arm: a value carrying both a backtick and `'`
        // (``"../`whoami`/'x'"`` — the canonical "I pasted a
        // legacy-backtick command-substitution followed by a
        // strong-quoted literal tail" footgun) routes through
        // `FonteCaminhoShellCommandSubstitution` not
        // `FonteCaminhoShellQuoteGrouping`. The CWE-78 shell-
        // command-injection vector is the load-bearing root-cause
        // edit on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../`whoami`/'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_background_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream shell-background arm: a value
        // carrying both `&` and `'` (`"../caixa-teia & 'x'"` — the
        // canonical "I pasted a `cmd & 'literal'` background-launch
        // + quote chain" footgun) routes through
        // `FonteCaminhoShellBackground` not
        // `FonteCaminhoShellQuoteGrouping`. The background-launch
        // tail is the load-bearing root-cause edit on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia & 'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_semicolon_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream shell-semicolon arm: a value
        // carrying both `;` and `'` (`"../caixa-teia; 'x'"` — the
        // canonical sequential-cleanup + quote paste idiom) routes
        // through `FonteCaminhoShellSemicolon` not
        // `FonteCaminhoShellQuoteGrouping`. The sequential-command-
        // separator paste is the load-bearing root-cause edit on
        // every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia; 'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream shell-pipe arm: a value
        // carrying both `|` and `'` (`"../caixa-teia | 'x'"` — the
        // canonical pipeline-to-quoted-literal paste idiom) routes
        // through `FonteCaminhoShellPipe` not
        // `FonteCaminhoShellQuoteGrouping`. The pipeline-tail paste
        // is the load-bearing root-cause edit on every probe-as-
        // both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia | 'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream shell-redirection arm: a
        // value carrying both `>` and `'` (`"../caixa-teia>log 'x'"`
        // — the canonical "I pasted a `cmd > log 'literal'`
        // redirect-plus-quote chain" footgun) routes through
        // `FonteCaminhoShellRedirection` not
        // `FonteCaminhoShellQuoteGrouping`. The input/output
        // redirection metachar carries the more self-locating
        // `byte` payload, so the prior arm wins on every probe-as-
        // both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>log 'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream backslash arm: a value
        // carrying both `\` and `'` (`"..\caixa-teia\'x'"` — the
        // canonical "I pasted a Windows-shell `cd ..\path\'literal'`
        // chain" footgun) routes through `FonteCaminhoBackslash`
        // not `FonteCaminhoShellQuoteGrouping`. The cross-host-OS-
        // separator divergence is the load-bearing axis on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia\\'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_quote_grouping() {
        // Cascade pin on the embedded-control-byte arm: a value
        // carrying both a control byte and `'` (`"../foo\n'x'"` —
        // the canonical paste-from-multiline-doc footgun where a
        // newline landed mid-caminho between two paste fragments)
        // routes through `FonteCaminhoControlChar` not
        // `FonteCaminhoShellQuoteGrouping`. The POSIX-syscall-
        // rejected-byte / NUL-`CString::new`-fail diagnostic is
        // the load-bearing axis on every value that probes
        // positive for both — mirrors the cascade discipline on
        // every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_quote_grouping() {
        // Cascade pin on the load-bearing leading-byte arm: a
        // leading `/` value with embedded `'` (`"/etc/'x'"`) routes
        // through `FonteCaminhoAbsolute` not
        // `FonteCaminhoShellQuoteGrouping` — the host-layout-leak
        // diagnostic is the load-bearing axis, the quote byte is
        // the secondary observation. Same precedence logic as every
        // prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_var_expansion_fires_before_shell_quote_grouping() {
        // Cascade pin on the upstream leading-`$` var-expansion
        // arm: a value carrying both a leading `$` and a `'`
        // (`"$DIR/'x'"` — the canonical "I pasted a `$DIR` shell-
        // variable + quoted literal at the head of a sibling-
        // workspace path" footgun) routes through
        // `FonteCaminhoVarExpansion` not
        // `FonteCaminhoShellQuoteGrouping`. The leading-byte
        // shell-variable-expansion is the more self-locating
        // diagnostic on values that probe as both — same
        // load-bearing-leading-byte cascade discipline every
        // prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$DIR/'x'".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_quote_grouping_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value
        // carrying both `'` and a trailing `/` (`"../'caixa-teia'/"`
        // — the canonical "I tab-completed a path whose strong-
        // quoted body already carried the quoting from a shell-
        // history paste" footgun) routes through
        // `FonteCaminhoShellQuoteGrouping` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-metachar
        // is the more semantic-locating axis (an author who removes
        // the `'` typically also drops the trailing separator since
        // both are paste-from-shell artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../'caixa-teia'/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellQuoteGrouping { byte: b'\'', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_quote_grouping_diagnostic_carries_offending_dep_caminho_and_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_bracket_expansion_diagnostic_carries_offending_dep_caminho_and_byte`
        // on the closest two-byte peer arm): the error's Display
        // surfaces the offending `:nome`, the offending `:caminho`
        // verbatim, the offending byte's hex / character form, and
        // names the shell-quote-grouping / cross-config-DSL-string-
        // literal-delimiter footgun explicitly so a `feira lint`
        // run can render the diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "'../caixa-teia'".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("'../caixa-teia'"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x27"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("quote-grouping"),
            "diagnostic must name the shell-quote-grouping footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("string-literal"),
            "diagnostic must reference the cross-config-DSL string-literal-delimiter \
             vocabulary: {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_shell_comment_lead() {
        // The canonical paste-from-shell-history-with-trailing-
        // annotation footgun: an author pastes a `cd ../caixa-teia
        // # legacy sibling` shell-history one-liner whose unquoted `#`
        // comment-lead separates the path from an inline annotation.
        // The POSIX shell trims the annotation to `../caixa-teia`
        // (POSIX.1-2017 §2.3 Token Recognition step 6), but
        // `Path::is_absolute` returns false on `..`, `#` is neither
        // a leading-byte sentinel nor a control byte nor `\` nor
        // `<` / `>` nor `|` nor `;` nor `&` nor backtick nor `*` /
        // `?` nor `(` / `)` nor `{` / `}` nor `[` / `]` nor `'` /
        // `"`, and the value's last byte isn't `/` — so the value
        // silently passed every prior arm. The resolver folded the
        // value through `Path::join` looking for a literal
        // `./../caixa-teia # legacy sibling` subdirectory and the
        // failure surfaced at resolve time with a non-self-locating
        // `No such file or directory` error. The new arm moves the
        // rejection to validate time and names the offending dep +
        // caminho + byte verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia # legacy sibling".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellComment {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellComment, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia # legacy sibling");
        assert_eq!(byte, b'#');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_yaml_comment_paste() {
        // The symmetric YAML flow-scalar / values.yaml / K8s-manifest
        // cross-idiom-leak shape (`"../caixa-teia  # pin"` — the
        // canonical "I copied a `path: ../caixa-teia  # pin` YAML
        // scalar-plus-comment entry out of an aligned values.yaml and
        // dropped it verbatim into the `:caminho` slot" paste-idiom).
        // Pinned separately from the shell-history shape so the
        // gate's coverage extends from the single-space `#` shape to
        // the YAML-canonical double-space `  #` shape. YAML 1.2 §6.6
        // requires the `#` to be preceded by whitespace to lex as a
        // comment (bare `foo#bar` is a single scalar); the double-
        // space paste from an aligned manifest is the canonical
        // shape.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia  # pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellComment { byte: b'#', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_url_fragment_anchor() {
        // The URL-fragment-identifier paste shape
        // (`"../caixa-teia#readme"` — the canonical
        // paste-from-browser-address-bar permalink shape where the
        // browser preserved the `#anchor` tail on the copy). Pinned
        // separately from the whitespace-separated shell / YAML
        // comment shapes so the gate covers the unpadded RFC 3986
        // §3.5 fragment-delimiter position too, not only positions
        // preceded by unquoted whitespace. Peer with the immediate-
        // sibling `is_git_repo_url` arm on the `:fonte :repo` axis
        // (a68f818) which closes the same byte under the same URL-
        // fragment-identifier banner.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia#readme".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellComment { byte: b'#', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_shell_comment() {
        // Leading-position `#` shape (`"#../caixa-teia"` — the
        // "I copied a shell-comment-out entry from a commented-out
        // dep row" footgun). Pinned separately from the embedded
        // shapes so the gate covers every position, not only
        // whitespace-preceded / mid-value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "#../caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellComment { byte: b'#', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_shell_comment() {
        // The positive-control pin: the gate targets only `#`,
        // never adjacent printable ASCII or POSIX-valid bytes. The
        // canonical relative POSIX path (`"../caixa-teia"`) and a
        // nested deeply-pathed variant with adjacent printable
        // punctuation (`"../caixa-teia/sub-dir.v2"`) must continue
        // to validate cleanly so the gate doesn't widen to a "no
        // printable punctuation anywhere" sweep that would defeat
        // the entire path-fonte author surface. Peer with
        // `validate_accepts_path_fonte_with_caminho_carrying_no_quote_grouping`
        // on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_quote_grouping_fires_before_shell_comment() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both `'` and `#` (`"../'x'#pin"` — the canonical
        // "I pasted a strong-quoted literal followed by a URL-
        // fragment permalink tail" footgun) routes through
        // `FonteCaminhoShellQuoteGrouping` not
        // `FonteCaminhoShellComment`. The shell-string-literal-
        // delimiter is the load-bearing root-cause edit on every
        // probe-as-both value; same cascade discipline every prior
        // `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../'x'#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellQuoteGrouping { byte: b'\'', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_bracket_expansion_fires_before_shell_comment() {
        // Cascade pin on the upstream shell-bracket-expansion arm:
        // a value carrying both `[` and `#` (`"../[a-z]#pin"` — the
        // canonical "I pasted a glob-character-class followed by a
        // URL-fragment tail" footgun) routes through
        // `FonteCaminhoShellBracketExpansion` not
        // `FonteCaminhoShellComment`. The glob-character-class
        // expansion is the load-bearing root-cause edit on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../[a-z]#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBracketExpansion { byte: b'[', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_brace_expansion_fires_before_shell_comment() {
        // Cascade pin on the upstream shell-brace-expansion arm: a
        // value carrying both `{` and `#` (`"../{a,b}#pin"` — the
        // canonical "I pasted a brace-expansion fan followed by a
        // URL-fragment tail" footgun) routes through
        // `FonteCaminhoShellBraceExpansion` not
        // `FonteCaminhoShellComment`. The brace-expansion fan is the
        // load-bearing root-cause edit on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../{a,b}#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBraceExpansion { byte: b'{', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_subshell_grouping_fires_before_shell_comment() {
        // Cascade pin on the upstream shell-subshell-grouping arm:
        // a value carrying both `(` and `#` (`"../(cd foo)#pin"` —
        // the canonical "I pasted a subshell-grouping followed by a
        // URL-fragment tail" footgun) routes through
        // `FonteCaminhoShellSubshellGrouping` not
        // `FonteCaminhoShellComment`. The modern Bourne `$(<cmd>)`
        // command-substitution boundary is the load-bearing axis on
        // every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../(cd foo)#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellSubshellGrouping { byte: b'(', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_glob_fires_before_shell_comment() {
        // Cascade pin on the upstream shell-glob arm: a value
        // carrying both `*` and `#` (`"../caixa-teia/*#pin"` — the
        // canonical "I pasted a `*` unbounded pathname-expansion
        // followed by a URL-fragment tail" footgun) routes through
        // `FonteCaminhoShellGlob` not `FonteCaminhoShellComment`.
        // The unbounded pathname-expansion sentinel is the load-
        // bearing root-cause edit on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/*#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellGlob { byte: b'*', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_command_substitution_fires_before_shell_comment() {
        // Cascade pin on the upstream shell-command-substitution
        // arm: a value carrying both a backtick and `#`
        // (``"../`whoami`#pin"`` — the canonical "I pasted a
        // legacy-backtick command-substitution followed by a URL-
        // fragment tail" footgun) routes through
        // `FonteCaminhoShellCommandSubstitution` not
        // `FonteCaminhoShellComment`. The CWE-78 shell-command-
        // injection vector is the load-bearing root-cause edit on
        // every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../`whoami`#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellCommandSubstitution { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_background_fires_before_shell_comment() {
        // Cascade pin on the upstream shell-background arm: a value
        // carrying both `&` and `#` (`"../caixa-teia&pin#tail"` —
        // the canonical "I pasted a `cmd &` background-launch
        // followed by a URL-fragment tail" footgun) routes through
        // `FonteCaminhoShellBackground` not
        // `FonteCaminhoShellComment`. The background-launch tail is
        // the load-bearing root-cause edit on every probe-as-both
        // value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia&pin#tail".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellBackground { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_semicolon_fires_before_shell_comment() {
        // Cascade pin on the upstream shell-semicolon arm: a value
        // carrying both `;` and `#` (`"../caixa-teia;pin#tail"` —
        // the canonical sequential-cleanup + URL-fragment paste
        // idiom) routes through `FonteCaminhoShellSemicolon` not
        // `FonteCaminhoShellComment`. The sequential-command-
        // separator paste is the load-bearing root-cause edit on
        // every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia;pin#tail".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellSemicolon { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_pipe_fires_before_shell_comment() {
        // Cascade pin on the upstream shell-pipe arm: a value
        // carrying both `|` and `#` (`"../caixa-teia|pin#tail"` —
        // the canonical pipeline-to-URL-fragment paste idiom) routes
        // through `FonteCaminhoShellPipe` not
        // `FonteCaminhoShellComment`. The pipeline-tail paste is
        // the load-bearing root-cause edit on every probe-as-both
        // value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia|pin#tail".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellPipe { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_redirection_fires_before_shell_comment() {
        // Cascade pin on the upstream shell-redirection arm: a
        // value carrying both `>` and `#` (`"../caixa-teia>log#pin"`
        // — the canonical "I pasted a `cmd > log` redirect followed
        // by a URL-fragment tail" footgun) routes through
        // `FonteCaminhoShellRedirection` not
        // `FonteCaminhoShellComment`. The input/output redirection
        // metachar carries the more self-locating `byte` payload,
        // so the prior arm wins on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia>log#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellRedirection { byte: b'>', .. }
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_shell_comment() {
        // Cascade pin on the upstream backslash arm: a value
        // carrying both `\` and `#` (`"..\caixa-teia#pin"` — the
        // canonical "I pasted a Windows-shell path followed by a
        // URL-fragment tail" footgun) routes through
        // `FonteCaminhoBackslash` not `FonteCaminhoShellComment`.
        // The cross-host-OS-separator divergence is the load-
        // bearing axis on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa-teia#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_shell_comment() {
        // Cascade pin on the embedded-control-byte arm: a value
        // carrying both a control byte and `#` (`"../foo\n#pin"` —
        // the canonical paste-from-multiline-doc footgun where a
        // newline landed mid-caminho between the path and an
        // annotation) routes through `FonteCaminhoControlChar` not
        // `FonteCaminhoShellComment`. The POSIX-syscall-rejected-
        // byte diagnostic is the load-bearing axis on every value
        // that probes positive for both — mirrors the cascade
        // discipline on every prior arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo\n#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_shell_comment() {
        // Cascade pin on the load-bearing leading-byte arm: a
        // leading `/` value with embedded `#` (`"/etc/foo#pin"`)
        // routes through `FonteCaminhoAbsolute` not
        // `FonteCaminhoShellComment` — the host-layout-leak
        // diagnostic is the load-bearing axis, the fragment byte is
        // the secondary observation. Same precedence logic as every
        // prior leading-byte arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/foo#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_var_expansion_fires_before_shell_comment() {
        // Cascade pin on the upstream leading-`$` var-expansion
        // arm: a value carrying both a leading `$` and a `#`
        // (`"$DIR/foo#pin"` — the canonical "I pasted a `$DIR`
        // shell-variable at the head of a sibling-workspace path
        // followed by a URL-fragment tail" footgun) routes through
        // `FonteCaminhoVarExpansion` not `FonteCaminhoShellComment`.
        // The leading-byte shell-variable-expansion is the more
        // self-locating diagnostic on values that probe as both.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$DIR/foo#pin".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_comment_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value
        // carrying both `#` and a trailing `/`
        // (`"../caixa-teia#pin/"` — the canonical "I tab-completed
        // a URL-fragment-carrying path" footgun) routes through
        // `FonteCaminhoShellComment` not
        // `FonteCaminhoTrailingSlash`. The embedded fragment /
        // comment-lead byte is the more semantic-locating axis (an
        // author who removes the `#pin` fragment typically also
        // drops the trailing separator since both are paste-from-
        // URL / paste-from-shell-tab-completion artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia#pin/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellComment { byte: b'#', .. },),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_comment_diagnostic_carries_offending_dep_caminho_and_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_quote_grouping_diagnostic_carries_offending_dep_caminho_and_byte`
        // on the immediate-predecessor arm): the error's Display
        // surfaces the offending `:nome`, the offending `:caminho`
        // verbatim, the offending byte's hex / character form, and
        // names the shell-comment / URL-fragment-identifier /
        // YAML-comment cross-config-DSL footgun explicitly so a
        // `feira lint` run can render the diagnostic without
        // re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia#readme".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia#readme"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x23"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("shell-comment") || rendered.contains("comment-lead"),
            "diagnostic must name the shell-comment footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("fragment") || rendered.contains("URL-fragment"),
            "diagnostic must reference the URL-fragment-identifier vocabulary: \
             {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_url_percent_encoded_space() {
        // The canonical paste-from-browser-address-bar percent-
        // encoded-space footgun: an author copies `../caixa%20teia`
        // out of a URL-encoded README hyperlink / browser address
        // bar / percent-encoded permalink expecting `%20` to decode
        // to a literal space at the filesystem layer. POSIX
        // `std::path::Path` treats `%` as a literal path-component
        // byte, so `Path::join` looks for a literal
        // `./../caixa%20teia` subdirectory. `Path::is_absolute`
        // returns false on `..`, `%` is neither a leading-byte
        // sentinel nor a control byte nor `\` nor `<` / `>` nor
        // `|` nor `;` nor `&` nor backtick nor `*` / `?` nor `(` /
        // `)` nor `{` / `}` nor `[` / `]` nor `'` / `"` nor `#`,
        // and the value's last byte isn't `/` — so the value
        // silently passed every prior arm. The new arm moves the
        // rejection to validate time and names the offending dep +
        // caminho + byte verbatim.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa%20teia".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoUrlPercentEncoding {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoUrlPercentEncoding, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa%20teia");
        assert_eq!(byte, b'%');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_url_percent_encoded_slash() {
        // The over-encoded path-separator shape (`"../caixa%2Fteia"`
        // intending the `%2F` as the URL encoding of `/`) locks a
        // `path:../caixa%2Fteia` BLAKE3 closure that diverges from
        // the byte-identical `path:../caixa/teia` form. Pinned
        // separately from the space-encoded shape so the gate's
        // coverage extends past the single canonical `%20` example
        // to any two-hex-digit percent-encoded sequence.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa%2Fteia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoUrlPercentEncoding { byte: b'%', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_lone_percent() {
        // The lone-`%` malformed-escape shape (`"../caixa-teia%foo"`
        // where `%` isn't followed by two hex digits) — every
        // WHATWG-conformant URL parser rejects the value at parse
        // time per RFC 3986 §2.1, but the byte would silently ride
        // into the lacre before the resolver subprocess crosses the
        // URL-parser boundary. Pinned separately from the well-
        // formed `%HH` shapes so the gate covers every percent-
        // occurrence, not only strictly-conformant escapes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia%foo".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoUrlPercentEncoding { byte: b'%', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_leading_yaml_directive() {
        // The YAML-directive-lead paste shape (`"%YAML/../caixa-teia"`
        // — the canonical paste-from-top-of-doc YAML directive
        // block cross-idiom leak per YAML 1.2 §6.8.1). Pinned
        // separately from embedded shapes so the gate covers the
        // leading-position `%` too, not only mid-value occurrences.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "%YAML/../caixa-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoUrlPercentEncoding { byte: b'%', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_printf_format_specifier() {
        // The printf-format-specifier paste shape
        // (`"../caixa-%s-teia"` — the canonical paste-from-shell-
        // diagnostic-one-liner `printf "path=%s\n" ...` idiom, CWE-
        // 134 format-string-injection vector). Pinned separately
        // from the URL-encoding shapes so the gate's rationale
        // extends past the RFC 3986 axis to the C / POSIX printf
        // format-directive-lead axis.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-%s-teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoUrlPercentEncoding { byte: b'%', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_percent() {
        // The positive-control pin: the gate targets only `%`,
        // never adjacent printable ASCII or POSIX-valid bytes. The
        // canonical relative POSIX path (`"../caixa-teia"`) and a
        // nested deeply-pathed variant with adjacent printable
        // punctuation (`"../caixa-teia/sub-dir.v2"`) must continue
        // to validate cleanly so the gate doesn't widen to a "no
        // printable punctuation anywhere" sweep that would defeat
        // the entire path-fonte author surface. Peer with
        // `validate_accepts_path_fonte_with_caminho_carrying_no_shell_comment`
        // on the immediate-predecessor arm.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_comment_fires_before_url_percent_encoding() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both `#` and `%` (`"../caixa-teia#pin%20"` — the
        // canonical "I pasted a URL-fragment permalink followed by a
        // percent-encoded space tail" footgun) routes through
        // `FonteCaminhoShellComment` not
        // `FonteCaminhoUrlPercentEncoding`. The URL-fragment-
        // identifier is the load-bearing downstream-truncation edit
        // on every probe-as-both value; same cascade discipline
        // every prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia#pin%20".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoShellComment { byte: b'#', .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_quote_grouping_fires_before_url_percent_encoding() {
        // Cascade pin on the upstream shell-quote-grouping arm: a
        // value carrying both `'` and `%` (`"../'x'%20teia"` — the
        // canonical "I pasted a strong-quoted literal followed by
        // a percent-encoded space" footgun) routes through
        // `FonteCaminhoShellQuoteGrouping` not
        // `FonteCaminhoUrlPercentEncoding`. The shell-string-
        // literal-delimiter is the load-bearing root-cause edit on
        // every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../'x'%20teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellQuoteGrouping { byte: b'\'', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_backslash_fires_before_url_percent_encoding() {
        // Cascade pin on the upstream backslash arm: a value
        // carrying both `\` and `%` (`"..\\caixa%20teia"` — the
        // canonical "I pasted a Windows-shell path followed by a
        // percent-encoded space" footgun) routes through
        // `FonteCaminhoBackslash` not
        // `FonteCaminhoUrlPercentEncoding`. The cross-host-OS-
        // separator divergence is the load-bearing root-cause edit
        // on every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "..\\caixa%20teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoBackslash { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_control_char_fires_before_url_percent_encoding() {
        // Cascade pin on the upstream control-char arm: a value
        // carrying both a NUL byte and `%` (`"../caixa\0%20teia"` —
        // the canonical "I pasted a paste-from-binary-blob path
        // followed by a percent-encoded space" footgun) routes
        // through `FonteCaminhoControlChar` not
        // `FonteCaminhoUrlPercentEncoding`. The POSIX-syscall-
        // rejected byte is the load-bearing root-cause edit on
        // every probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa\0%20teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoControlChar { byte: 0x00, .. },),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_absolute_fires_before_url_percent_encoding() {
        // Cascade pin on the upstream absolute-path arm: a value
        // that's both absolute and carries `%` (`"/etc/passwd%20"`
        // — the canonical "I pasted an absolute path with a
        // percent-encoded space tail" footgun) routes through
        // `FonteCaminhoAbsolute` not
        // `FonteCaminhoUrlPercentEncoding`. The host-layout-leak is
        // the load-bearing root-cause edit on every probe-as-both
        // value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "/etc/passwd%20".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoAbsolute { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_var_expansion_fires_before_url_percent_encoding() {
        // Cascade pin on the upstream var-expansion arm: a value
        // starting with `$` and carrying `%` (`"$HOME/caixa%20teia"`
        // — the canonical "I pasted a `$HOME`-rooted path with a
        // percent-encoded space" footgun) routes through
        // `FonteCaminhoVarExpansion` not
        // `FonteCaminhoUrlPercentEncoding`. The shell-variable-
        // expansion is the load-bearing root-cause edit on every
        // probe-as-both value.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$HOME/caixa%20teia".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_url_percent_encoding_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value
        // carrying both `%` and a trailing `/`
        // (`"../caixa%20teia/"` — the canonical "I tab-completed a
        // percent-encoded-space-carrying path" footgun) routes
        // through `FonteCaminhoUrlPercentEncoding` not
        // `FonteCaminhoTrailingSlash`. The embedded percent-
        // encoding-escape byte is the more semantic-locating axis
        // (an author who decodes the `%20` to a literal space is
        // likely to also tab-strip the trailing separator since
        // both are paste-from-URL / paste-from-shell-tab-completion
        // artifacts).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa%20teia/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoUrlPercentEncoding { byte: b'%', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_url_percent_encoding_diagnostic_carries_offending_dep_caminho_and_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_comment_diagnostic_carries_offending_dep_caminho_and_byte`
        // on the immediate-predecessor arm): the error's Display
        // surfaces the offending `:nome`, the offending `:caminho`
        // verbatim, the offending byte's hex / character form, and
        // names the URL-percent-encoding-escape / printf-format-
        // specifier footgun explicitly so a `feira lint` run can
        // render the diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa%20teia".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa%20teia"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x25"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("percent-encoding") || rendered.contains("percent-encoded"),
            "diagnostic must name the URL-percent-encoding-escape footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("printf") || rendered.contains("format-specifier"),
            "diagnostic must reference the printf-format-specifier vocabulary: \
             {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_var_expansion() {
        // The canonical embedded-`$` shell-variable-expansion paste
        // shape (`"../foo$HOME/bar"` — an author copies a partially-
        // substituted shell one-liner where the leading segment is a
        // literal `../foo` while the mid segment carries the un-
        // substituted `$HOME` template). The leading-`$` position is
        // already gated by the f4efe9c leading-byte arm which routes
        // through `FonteCaminhoVarExpansion`; this arm closes the
        // last positional gap on `$` — every position on the axis is
        // structurally rejected.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo$HOME/bar".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellVariableExpansion {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellVariableExpansion, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../foo$HOME/bar");
        assert_eq!(byte, b'$');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_braced_var_expansion() {
        // The symmetric braced-CI-manifest paste shape
        // (`"../foo${WORKSPACE}/bar"` — the canonical paste-from-
        // GitHub-Actions-workflow / paste-from-`.gitlab-ci.yml`
        // footgun). Pinned separately from the bare-`$VAR` shape so
        // the gate covers both POSIX shell §2.6 Parameter Expansion
        // syntactic forms, not only the unbraced variant. The
        // embedded `{` byte in `${...}` is also caught by the 598b770
        // shell-brace-expansion arm but that arm fires earlier in
        // the cascade — the `$` arm's coverage extends to `${...}`
        // structurally, so the diagnostic asserted here is the
        // brace-expansion one (which is a valid outcome; the point
        // of the pin is that the value never survives validation).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo${WORKSPACE}/bar".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellBraceExpansion { byte: b'{', .. }
                    | DepError::FonteCaminhoShellVariableExpansion { byte: b'$', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_command_substitution() {
        // The paste-from-shell-prompt command-substitution idiom
        // (`"../foo$(whoami)/bar"`). Pinned separately from the bare-
        // `$VAR` shape so the gate's rationale extends to POSIX shell
        // §2.6.3 Command Substitution (the modern `$(<cmd>)` form; the
        // legacy `` `<cmd>` `` form is already closed by the c370458
        // backtick arm). The embedded `(` byte in `$(...)` is also
        // caught structurally by the 0633c91 shell-subshell-grouping
        // arm which fires earlier in the cascade — the diagnostic
        // asserted here is either outcome, since both structurally
        // reject the value; the point of the pin is that the value
        // never survives validation.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo$(whoami)/bar".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellSubshellGrouping { byte: b'(', .. }
                    | DepError::FonteCaminhoShellVariableExpansion { byte: b'$', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_embedded_positional_parameter() {
        // The paste-from-`Makefile` / paste-from-SQL-migration bare-
        // `$1` positional-parameter shape (`"../foo$1/bar"` — a Make
        // automatic-variable `$1` or a PostgreSQL bind-parameter `$1`
        // idiom copied into a caminho template). None of the prior
        // shell-metachar arms cover this shape (`1` is a bare digit;
        // no `(` / `{` / letter follows the `$`), so the arm is the
        // sole gate on the shape.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo$1/bar".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellVariableExpansion { byte: b'$', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_dollar() {
        // The positive-control pin (peer with
        // `validate_accepts_path_fonte_with_caminho_carrying_no_percent`
        // on the immediate-predecessor arm): the gate targets only
        // `$`, never adjacent printable ASCII or POSIX-valid bytes.
        // A relative POSIX path carrying dashes / dots / slashes /
        // digits (`"../caixa-teia/sub-dir.v2"`) must continue to
        // validate cleanly so the gate doesn't widen to a "no
        // printable punctuation anywhere" sweep that would defeat
        // the entire path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_var_expansion_fires_before_shell_variable_expansion() {
        // Cascade pin on the leading-`$` sibling arm at line 540: a
        // value starting with `$` and carrying an embedded `$` too
        // (`"$HOME/foo$WORKSPACE/bar"` — the canonical "I pasted a
        // fully-templated CI path with two un-substituted variables")
        // routes through `FonteCaminhoVarExpansion` not
        // `FonteCaminhoShellVariableExpansion`. The leading-byte
        // host-layout-leak is the load-bearing self-locating axis
        // (the leading position dominates the semantic-locating
        // rationale on every probe-as-both value); the embedded
        // arm's positional-agnostic sweep catches only values whose
        // leading byte doesn't route through the earlier leading-
        // byte arms.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "$HOME/foo$WORKSPACE/bar".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteCaminhoVarExpansion { .. }),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_url_percent_encoding_fires_before_shell_variable_expansion() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both `%` and embedded `$` (`"../foo%20$HOME/bar"`
        // — the canonical "I pasted a percent-encoded space adjacent
        // to a `$HOME` template") routes through
        // `FonteCaminhoUrlPercentEncoding` not
        // `FonteCaminhoShellVariableExpansion`. The URL-percent-
        // encoding-escape byte is the more semantic-locating axis
        // (the paste-from-browser-address-bar shape is the load-
        // bearing self-locating edit); same cascade discipline every
        // prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo%20$HOME/bar".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoUrlPercentEncoding { byte: b'%', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_variable_expansion_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value
        // carrying both embedded `$` and a trailing `/`
        // (`"../foo$HOME/bar/"` — the canonical "I tab-completed a
        // `$HOME`-template-carrying path") routes through
        // `FonteCaminhoShellVariableExpansion` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-variable-
        // expansion byte is the more semantic-locating axis on
        // probe-as-both values (an author who substitutes the
        // `$HOME` template with a literal value is likely to also
        // tab-strip the trailing separator).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo$HOME/bar/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellVariableExpansion { byte: b'$', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_variable_expansion_diagnostic_carries_offending_dep_caminho_and_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_url_percent_encoding_diagnostic_carries_offending_dep_caminho_and_byte`
        // on the immediate-predecessor arm): the error's Display
        // surfaces the offending `:nome`, the offending `:caminho`
        // verbatim, the offending byte's hex / character form, and
        // names the shell-variable-expansion / command-substitution
        // footgun explicitly so a `feira lint` run can render the
        // diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo$HOME/bar".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../foo$HOME/bar"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x24"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("variable-expansion") || rendered.contains("variable expansion"),
            "diagnostic must name the shell-variable-expansion footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("command-substitution") || rendered.contains("command substitution"),
            "diagnostic must reference the command-substitution vocabulary: {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_shell_history_expansion() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // shell-history footgun on `:caminho`. An author copies a `cd
        // ../caixa-teia && !sudo make install` one-liner from a quick-
        // start README, intending the trailing `!sudo` as a shell-
        // history-expansion reference but the typed slot is itself a
        // byte-level string parser, not a shell context, so the byte
        // rides into the value verbatim. Until this arm landed the `!`
        // byte silently passed every prior `:caminho` cascade arm
        // (`!` isn't `\` / `<` / `>` / `|` / `;` / `&` / backtick /
        // `*` / `?` / `(` / `)` / `{` / `}` / `[` / `]` / `'` / `"` /
        // `#` / `%` / `$`); bash with the default `histexpand` mode
        // rewrites `!command` to the most recent history entry
        // beginning with `command`, the canonical RCE-class injection
        // vector when the byte rides into a shell argument executed
        // under `bash -i` (the operator-notebook interactive shell).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia!sudo".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellHistoryExpansion {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellHistoryExpansion, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../caixa-teia!sudo");
        assert_eq!(byte, b'!');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_double_bang_history_reference() {
        // The symmetric `!!` repeat-prior-command paste idiom (peer with
        // `validate_rejects_git_fonte_with_repo_carrying_double_bang_history_reference`
        // on `is_git_repo_url`). Pinned separately from the wrapped
        // `!command` shape so a future diagnostic-surface change that
        // only checked the leading or paired-bang position surfaces
        // here — the per-byte arm fires anywhere `!` appears in the
        // value, including at consecutive positions in the middle.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo!!/bar".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellHistoryExpansion { byte: b'!', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_trailing_enthusiasm_bang() {
        // The English-typography enthusiasm-form paste-from-prose
        // idiom: an author writes `:caminho "../caixa-teia!"`
        // expecting the substrate to coerce it to a kebab-case slug.
        // Pinned separately from the `!<word>` shell-history shape so
        // the gate's rationale extends to the paste-from-prose surface
        // (the same rationale the peer `is_git_repo_url` bang arm at
        // 7d53c68 covers). None of the prior shell-metachar arms cover
        // this shape (no `!<word>` reference and no `!!` repeat), so
        // the arm is the sole gate on the shape.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia!".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellHistoryExpansion { byte: b'!', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_bang() {
        // The positive-control pin (peer with
        // `validate_accepts_path_fonte_with_caminho_carrying_no_dollar`
        // on the immediate-predecessor arm): the gate targets only
        // `!`, never adjacent printable ASCII or POSIX-valid bytes.
        // A relative POSIX path carrying dashes / dots / slashes /
        // digits (`"../caixa-teia/sub-dir.v2"`) must continue to
        // validate cleanly so the gate doesn't widen to a "no
        // printable punctuation anywhere" sweep that would defeat
        // the entire path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub-dir.v2".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_variable_expansion_fires_before_shell_history_expansion() {
        // Cascade pin on the immediate-predecessor arm: a value
        // carrying both embedded `$` and `!` (`"../foo$HOME/bar!sudo"`
        // — the canonical "I pasted a `$HOME`-templated path adjacent
        // to a trailing `!sudo` history-expansion") routes through
        // `FonteCaminhoShellVariableExpansion` not
        // `FonteCaminhoShellHistoryExpansion`. The shell-variable-
        // expansion byte is the more semantic-locating axis on
        // probe-as-both values (the paste-from-CI-manifest-with-`$VAR`-
        // template shape is the load-bearing self-locating edit);
        // same cascade discipline every prior `:caminho` arm
        // establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo$HOME/bar!sudo".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellVariableExpansion { byte: b'$', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_history_expansion_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value carrying
        // both embedded `!` and a trailing `/` (`"../caixa-teia!sudo/"`
        // — the canonical "I tab-completed a `!sudo`-carrying path")
        // routes through `FonteCaminhoShellHistoryExpansion` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-history-
        // expansion byte is the more semantic-locating axis on probe-
        // as-both values (an author who removes the `!sudo` history
        // reference is likely to also tab-strip the trailing separator).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia!sudo/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellHistoryExpansion { byte: b'!', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_history_expansion_diagnostic_carries_offending_dep_caminho_and_byte() {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_variable_expansion_diagnostic_carries_offending_dep_caminho_and_byte`
        // on the immediate-predecessor arm): the error's Display
        // surfaces the offending `:nome`, the offending `:caminho`
        // verbatim, the offending byte's hex / character form, and
        // names the shell-history-expansion / bang-operator footgun
        // explicitly so a `feira lint` run can render the diagnostic
        // without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia!sudo".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../caixa-teia!sudo"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x21"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("history-expansion") || rendered.contains("history expansion"),
            "diagnostic must name the shell-history-expansion footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("bang"),
            "diagnostic must reference the bang-operator vocabulary: {rendered:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_shell_history_substitution() {
        // The fail-before-pass-after pin for the canonical paste-from-
        // shell-history-quick-substitution footgun on `:caminho`. An
        // author copies a `git clone <bad-url>` line from their terminal,
        // corrects it via bash's `^bad^good` quick-substitution history
        // operator (bash reference §9.3, `set -o histexpand` mode's
        // default for interactive sessions), and pastes the trailing
        // `^bad^good` substitution fragment into a `:caminho` value
        // without trimming the leading `git clone` prefix — the byte
        // rides into the manifest verbatim. Until this arm landed the
        // `^` byte silently passed every prior `:caminho` cascade arm
        // (`^` isn't `\` / `<` / `>` / `|` / `;` / `&` / backtick / `*`
        // / `?` / `(` / `)` / `{` / `}` / `[` / `]` / `'` / `"` / `#` /
        // `%` / `$` / `!`); bash with the default `histexpand` mode
        // rewrites the prior command's `bad` string to `good` and re-
        // executes it, the paired-operator half of the `set -o
        // histexpand` feature the peer `!` arm already closes the prefix
        // half of. The peer `is_git_repo_url` axis rejects the byte at
        // 49e142f under the same shell-history-substitution / RFC-3986-
        // unwise banner.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo^bad^good".into(),
        });
        let err = d.validate().unwrap_err();
        let DepError::FonteCaminhoShellHistorySubstitution {
            nome,
            caminho,
            byte,
        } = err
        else {
            panic!("expected FonteCaminhoShellHistorySubstitution, got {err:?}");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(caminho, "../foo^bad^good");
        assert_eq!(byte, b'^');
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_regex_negation_anchor() {
        // The symmetric paste-from-doc-grep-pipeline footgun (peer with
        // `validate_rejects_git_fonte_with_repo_carrying_caret_regex_anchor`
        // on `is_git_repo_url`). An author copies a `grep '^archived'`
        // regex-anchor / negation idiom from a doc snippet and the byte
        // rides in verbatim. Pinned separately from the `^old^new^`
        // quick-substitution shape so a future diagnostic-surface change
        // that only checked the paired-caret history-substitution
        // position surfaces here — the per-byte arm fires anywhere `^`
        // appears in the value, including at a solitary leading-of-
        // segment position.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo/^archived".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellHistorySubstitution { byte: b'^', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_rejects_path_fonte_with_caminho_carrying_trailing_history_substitution_open() {
        // The trailing-`^` history-substitution-open shape — an author
        // starts typing a `^bad^good` quick-substitution but pastes only
        // the leading `^` sentinel before context-switching (a bash-
        // reference §9.3 valid histexpand prefix on its own — even a
        // solitary `^` on the prior command's whole re-execution shape).
        // Pinned separately from the `^old^new^` full-form and the leading-
        // of-segment `^archived` regex-anchor shape so the gate's
        // rationale extends to the paste-from-shell-history-with-only-
        // the-first-byte-selected surface. None of the prior shell-
        // metachar arms cover this shape.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia^".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellHistorySubstitution { byte: b'^', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn validate_accepts_path_fonte_with_caminho_carrying_no_caret() {
        // The positive-control pin (peer with
        // `validate_accepts_path_fonte_with_caminho_carrying_no_bang`
        // on the immediate-predecessor arm): the gate targets only
        // `^`, never adjacent printable ASCII or POSIX-valid bytes.
        // A relative POSIX path carrying dashes / dots / slashes /
        // digits / underscore (`"../caixa-teia/sub_v2.rc"`) must
        // continue to validate cleanly so the gate doesn't widen to
        // a "no printable punctuation anywhere" sweep that would
        // defeat the entire path-fonte author surface.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../caixa-teia/sub_v2.rc".into(),
        });
        d.validate().unwrap();
    }

    #[test]
    fn fonte_caminho_shell_history_expansion_fires_before_shell_history_substitution() {
        // Cascade pin on the immediate-predecessor arm: a value carrying
        // both embedded `!` and `^` (`"../foo!sudo^bad^good"` — the
        // canonical "I pasted a `!sudo` history-reference next to a
        // `^bad^good` quick-substitution") routes through
        // `FonteCaminhoShellHistoryExpansion` not
        // `FonteCaminhoShellHistorySubstitution`. The `!` prefix form is
        // the more semantic-locating axis on probe-as-both values (an
        // author who removes the `!sudo` reference is likely to also
        // strip the paired `^` substitution fragment); same cascade
        // discipline every prior `:caminho` arm establishes.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo!sudo^bad^good".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellHistoryExpansion { byte: b'!', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_history_substitution_fires_before_trailing_slash() {
        // Cascade pin on the immediate-successor arm: a value carrying
        // both embedded `^` and a trailing `/` (`"../foo^bad^good/"` —
        // the canonical "I tab-completed a `^bad^good`-carrying path")
        // routes through `FonteCaminhoShellHistorySubstitution` not
        // `FonteCaminhoTrailingSlash`. The embedded shell-history-
        // substitution byte is the more semantic-locating axis on probe-
        // as-both values (an author who removes the `^bad^good`
        // substitution fragment is likely to also tab-strip the trailing
        // separator).
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo^bad^good/".into(),
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::FonteCaminhoShellHistorySubstitution { byte: b'^', .. },
            ),
            "got {err:?}",
        );
    }

    #[test]
    fn fonte_caminho_shell_history_substitution_diagnostic_carries_offending_dep_caminho_and_byte()
    {
        // Diagnostic-shape pin (peer with
        // `fonte_caminho_shell_history_expansion_diagnostic_carries_offending_dep_caminho_and_byte`
        // on the immediate-predecessor arm): the error's Display
        // surfaces the offending `:nome`, the offending `:caminho`
        // verbatim, the offending byte's hex form, and names the
        // shell-history-substitution / RFC-3986-'unwise' / regex-
        // negation footgun explicitly so a `feira lint` run can render
        // the diagnostic without re-parsing.
        let d = dep_with_fonte(DepSource::Path {
            caminho: "../foo^bad^good".into(),
        });
        let rendered = d.validate().unwrap_err().to_string();
        assert!(
            rendered.contains("caixa-teia"),
            "diagnostic must name the offending dep: {rendered}",
        );
        assert!(
            rendered.contains("../foo^bad^good"),
            "diagnostic must quote the offending caminho verbatim: {rendered:?}",
        );
        assert!(
            rendered.contains("0x5e") || rendered.contains("0x5E"),
            "diagnostic must surface the offending byte hex: {rendered:?}",
        );
        assert!(
            rendered.contains("history-substitution") || rendered.contains("history substitution"),
            "diagnostic must name the shell-history-substitution footgun: {rendered:?}",
        );
        assert!(
            rendered.contains("unwise"),
            "diagnostic must reference the RFC-3986 'unwise' set vocabulary: {rendered:?}",
        );
    }

    #[test]
    fn fonte_repo_empty_fires_before_pin_missing() {
        // Order pin: empty `:repo` is the more self-locating diagnostic
        // (every git source needs a repo; the pin discussion is
        // secondary), so it fires before the pin-missing arm even when
        // both are violated. Mirrors the
        // `nome_empty_takes_precedence_over_versao_invalid` ordering
        // discipline on the per-entry layer.
        let d = dep_with_fonte(DepSource::Git {
            repo: String::new(),
            tag: None,
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::FonteRepoEmpty { .. }),
            "got {err:?}"
        );
    }

    #[test]
    fn fonte_pin_missing_fires_before_pin_empty() {
        // Order pin: a fully-None pin set is structurally distinct from
        // a Some(empty) pin — the first surfaces as FontePinMissing
        // (no axis chosen), the second as FontePinEmpty (axis chosen
        // but value blank). Pin the disjoint relationship so a future
        // unification collapses to one variant only as a structural
        // decision.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: None,
            branch: None,
        });
        assert!(matches!(
            d.validate().unwrap_err(),
            DepError::FontePinMissing { .. }
        ));
    }

    #[test]
    fn nome_empty_takes_precedence_over_fonte_invalid() {
        // Order pin: a per-entry diagnostic without a non-empty :nome
        // can't be self-locating, so :nome "" fires first even when
        // :fonte is also malformed. Mirrors
        // `nome_empty_takes_precedence_over_versao_invalid` on the
        // adjacent axis.
        let mut d = dep_with_fonte(DepSource::Git {
            repo: String::new(),
            tag: None,
            rev: None,
            branch: None,
        });
        d.nome = String::new();
        assert_eq!(d.validate().unwrap_err(), DepError::NomeEmpty);
    }

    #[test]
    fn versao_invalid_takes_precedence_over_fonte_invalid() {
        // Order pin: the :versao parse-side diagnostic is narrower than
        // the :fonte shape diagnostic — a malformed :versao always names
        // the parser's reason, which is more actionable than the
        // :fonte gate's "the pins are wrong" wording. Pin the ordering
        // so a re-ordering surfaces here.
        let mut d = dep_with_fonte(DepSource::Git {
            repo: String::new(),
            tag: None,
            rev: None,
            branch: None,
        });
        d.versao = "v0.1".into();
        let err = d.validate().unwrap_err();
        assert!(
            matches!(err, DepError::VersaoInvalid { ref nome, .. } if nome == "caixa-teia"),
            "got {err:?}"
        );
    }

    #[test]
    fn fonte_invalid_diagnostic_carries_offending_nome() {
        // The diagnostic-shape pin: every :fonte error variant names
        // the offending dep's :nome verbatim, so the author can grep
        // caixa.lisp for the `:nome "<n>"` block and fix it in one
        // edit. Cover all seven variants so a future variant addition
        // forces a parallel diagnostic-shape decision.
        for (case, fonte) in [
            (
                "repo-empty",
                DepSource::Git {
                    repo: String::new(),
                    tag: Some("v1".into()),
                    rev: None,
                    branch: None,
                },
            ),
            (
                "repo-shape",
                DepSource::Git {
                    repo: "github:p/x ".into(),
                    tag: Some("v1".into()),
                    rev: None,
                    branch: None,
                },
            ),
            (
                "pin-missing",
                DepSource::Git {
                    repo: "github:p/x".into(),
                    tag: None,
                    rev: None,
                    branch: None,
                },
            ),
            (
                "pin-ambiguous",
                DepSource::Git {
                    repo: "github:p/x".into(),
                    tag: Some("v1".into()),
                    rev: None,
                    branch: Some("main".into()),
                },
            ),
            (
                "pin-empty",
                DepSource::Git {
                    repo: "github:p/x".into(),
                    tag: Some(String::new()),
                    rev: None,
                    branch: None,
                },
            ),
            (
                "caminho-empty",
                DepSource::Path {
                    caminho: String::new(),
                },
            ),
            (
                "caminho-absolute",
                DepSource::Path {
                    caminho: "/home/me/work/caixa-teia".into(),
                },
            ),
        ] {
            let d = dep_with_fonte(fonte);
            let msg = d
                .validate()
                .expect_err(&format!("{case}: expected fonte error"))
                .to_string();
            assert!(
                msg.contains("\"caixa-teia\""),
                "{case}: diagnostic must quote the offending :nome verbatim, got {msg:?}"
            );
        }
    }

    // -- :tag / :branch value-shape gate ----------------------------------

    #[test]
    fn validate_rejects_git_fonte_with_tag_carrying_trailing_space() {
        // The canonical paste-from-doc footgun on `:tag` — author
        // copies `"v0.1.0 "` (trailing space) out of a release-notes
        // paragraph. Until this gate landed the empty-pin arm passed
        // (the string isn't empty), the resolver issued
        // `git fetch <remote> tag 'v0.1.0 '`, and the failure
        // surfaced at clone time with a quoting-confused git error
        // far from the source caixa.lisp. The new gate moves the
        // check to caixa-build time and names the offending dep +
        // pin + value verbatim.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0 ".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            nome,
            pin,
            value,
            reason,
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(pin, ":tag");
        assert_eq!(value, "v0.1.0 ");
        assert!(
            reason.contains("whitespace"),
            "reason must surface the whitespace arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_tag_carrying_lock_suffix() {
        // The `.lock` suffix is git's atomic-rename guard for
        // in-flight ref updates — a refname ending in `.lock` is
        // unwritable on disk. Pinned separately from the whitespace
        // arm so a future relaxation that admits one but not the
        // other surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0.lock".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":tag");
        assert_eq!(value, "v0.1.0.lock");
        assert!(
            reason.contains(".lock"),
            "reason must surface the .lock arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_branch_carrying_embedded_space() {
        // The canonical "branch name with spaces" footgun (`feature
        // foo`, `release branch`) — git's refname parser rejects raw
        // whitespace, and the failure surfaces at `git checkout
        // 'feature foo'` time with a quoting-confused error far from
        // the source caixa.lisp. Pinned on the `:branch` axis so the
        // gate-applies-to-both-:tag-and-:branch contract is a build-
        // error to relax.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: None,
            branch: Some("feature/foo bar".into()),
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":branch");
        assert_eq!(value, "feature/foo bar");
        assert!(
            reason.contains("whitespace"),
            "reason must surface the whitespace arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_branch_carrying_qualified_prefix() {
        // The `refs/heads/main` shape — the canonical "I copied the
        // fully-qualified ref out of `git show-ref` instead of the
        // leaf" footgun. The caixa-resolver prepends `refs/heads/`
        // at clone time, so this resolves to a literal ref named
        // `refs/heads/refs/heads/main` on disk; the silent double-
        // prefix is the load-bearing reason to gate at validate.
        // The diagnostic must enumerate the leaf the author probably
        // meant (`"main"`) so the fix is one edit.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: None,
            branch: Some("refs/heads/main".into()),
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":branch");
        assert_eq!(value, "refs/heads/main");
        assert!(
            reason.contains("fully-qualified"),
            "reason must surface the qualified-prefix arm, got {reason:?}"
        );
        assert!(
            reason.contains("\"main\""),
            "reason must quote the leaf the author probably meant, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_tag_carrying_qualified_prefix() {
        // Sibling arm of the qualified-prefix gate on the `:tag`
        // axis (`refs/tags/v0.1.0` — same `git show-ref` output-leak
        // footgun). Pinned separately so a future relaxation that
        // only catches the `:branch` arm surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("refs/tags/v0.1.0".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":tag");
        assert_eq!(value, "refs/tags/v0.1.0");
        assert!(
            reason.contains("fully-qualified"),
            "reason must surface the qualified-prefix arm, got {reason:?}"
        );
        assert!(
            reason.contains("\"v0.1.0\""),
            "reason must quote the leaf the author probably meant, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_branch_named_at() {
        // The bare `@` is git's alias for `HEAD`; a `:branch "@"` is
        // unsourceable. Pinned so a future relaxation that admits
        // any single-character refname surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: None,
            branch: Some("@".into()),
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape { pin, value, .. } = err else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":branch");
        assert_eq!(value, "@");
    }

    #[test]
    fn validate_rejects_git_fonte_with_tag_carrying_double_dot() {
        // Git's `<rev1>..<rev2>` range grammar reserves `..` —
        // a `:tag "../escape"` (path-traversal-shaped slug) silently
        // passes parse and surfaces as a refname-parse error or, on
        // older git, a literal `../escape` checkout that escapes the
        // refs/ directory tree. Pinned separately from the
        // qualified-prefix arm so a future relaxation that catches
        // one but not the other surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("../escape".into()),
            rev: None,
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape { pin, value, .. } = err else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":tag");
        assert_eq!(value, "../escape");
    }

    #[test]
    fn validate_accepts_git_fonte_with_hierarchical_branch() {
        // The positive-control pin: hierarchical refnames with one or
        // more `/` separators (the `feature/foo` / `user/jdoe/feat`
        // canonical idiom) round-trip through the gate. Pinned
        // separately from the leaf-`"main"` positive control so a
        // future tightening that rejects all multi-component refnames
        // surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: None,
            branch: Some("feature/checkout-rewrite".into()),
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_accepts_git_fonte_with_prerelease_tag() {
        // The positive-control pin: semver pre-release shape
        // (`v0.1.0-alpha.1`) — the in-component dot is allowed
        // (only consecutive `..` and trailing `.` are rejected), the
        // mid-component hyphen is allowed. Pinned separately from
        // the bare-`"v0.1.0"` positive control so a future tightening
        // that rejects pre-release tags surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0-alpha.1".into()),
            rev: None,
            branch: None,
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_rejects_git_fonte_with_rev_carrying_refname_unfriendly_value() {
        // The `:rev` axis is routed through `crate::render::is_git_oid`
        // (a SHA's character set is `[0-9a-f]`, not a refname's), so a
        // value with refname-shape punctuation (here, a `:` mid-string
        // — would be a refname violation under `is_git_ref_name` too)
        // is rejected at the OID-shape gate. The two predicates
        // partition the `:fonte` pin axes structurally: an `:rev` value
        // that's a valid refname (`:rev "main"`, `:rev "v0.1.0"`) is
        // *still* rejected here because every refname character outside
        // `[0-9a-f]` fails the OID gate. Same shape as
        // `fonte_pin_shape_diagnostic_carries_offending_nome_pin_value`
        // on the refname-shaped axes — the diagnostic names the
        // offending dep + pin + value verbatim. The flip-from-accept
        // case the prior `:tag`/`:branch` gate left as a "future axis"
        // (e70d213) — now landed.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some("c0ffee:notarefname".into()),
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            nome,
            pin,
            value,
            reason,
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(nome, "caixa-teia");
        assert_eq!(pin, ":rev");
        assert_eq!(value, "c0ffee:notarefname");
        assert!(
            !reason.is_empty(),
            "FontePinShape `reason` must carry the predicate's wording verbatim"
        );
    }

    #[test]
    fn validate_accepts_git_fonte_with_rev_full_sha1() {
        // The positive-control pin on the SHA-1 OID width: exactly 40
        // lowercase hex characters — the canonical `git rev-parse HEAD`
        // emission on a SHA-1-hashed repository (the default on every
        // pre-2.42 git and the canonical pleme-io substrate hash).
        // Pinned separately from the SHA-256 positive control so a
        // future tightening that only admits one width surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some("0123456789abcdef0123456789abcdef01234567".into()),
            branch: None,
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_accepts_git_fonte_with_rev_full_sha256() {
        // The positive-control pin on the SHA-256 OID width: exactly
        // 64 lowercase hex characters — `git`'s
        // `extensions.objectFormat = sha256` emission (GA since Git
        // 2.42 / Oct 2023). The substrate admits either canonical
        // width so an `:rev` authored against a SHA-256-hashed
        // upstream round-trips through the gate without per-repo
        // configuration. Pinned separately from the SHA-1 positive
        // control so a future tightening that drops one width surfaces
        // here as a structural decision.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some("0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef".into()),
            branch: None,
        });
        d.validate().unwrap();
    }

    #[test]
    fn validate_rejects_git_fonte_with_rev_abbreviated_prefix() {
        // The canonical `git log --short` / `git rev-parse --short HEAD`
        // paste-from-release-notes footgun: a 7-char prefix (git's
        // default `core.abbrev`) silently passes string emptiness
        // checks and resolves to one commit today, but becomes ambiguous
        // tomorrow as the repo grows. Until this gate landed the empty-
        // pin arm passed (the string isn't empty) and the resolver
        // accepted the prefix through git's separate prefix-lookup pass
        // — defeating the reproducibility contract `:rev` carries vs.
        // `:tag` / `:branch`. The new gate moves the check to caixa-
        // build time and names the offending dep + pin + value verbatim.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some("c0ffee0".into()),
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":rev");
        assert_eq!(value, "c0ffee0");
        assert!(
            reason.contains("abbreviated") || reason.contains("ambiguous"),
            "reason must surface the abbreviation arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_rev_uppercase_hex() {
        // The canonical "I pasted the SHA in uppercase" footgun: `git
        // porcelain` emits OIDs lowercase exclusively, so an uppercase-
        // bearing `:rev` round-trips inconsistently across the
        // resolver's `git fetch <remote> <:rev>` ↔ `git rev-parse HEAD`
        // equality-check pipeline and fails the lacre's content-
        // addressing probe with a confusing case-only diff. Pinned
        // separately from the non-hex arm so a future relaxation that
        // admits one but not the other surfaces here.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some("DEADBEEFCAFEBABE0123456789ABCDEF01234567".into()),
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":rev");
        assert_eq!(value, "DEADBEEFCAFEBABE0123456789ABCDEF01234567");
        assert!(
            reason.contains("uppercase"),
            "reason must surface the uppercase arm, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_rev_refname_value() {
        // The cross-axis mis-slot footgun: `:rev "main"` — the author
        // conflated `:rev` (hex commit ID, immutable) and `:branch`
        // (mutable ref pointing at whatever HEAD is today). Until this
        // gate landed the resolver silently dispatched on the value
        // shape ("`main` doesn't look like a SHA, fall back to
        // refname"), defeating the `:rev` reproducibility contract.
        // The new gate rejects every non-hex value on the `:rev` axis,
        // so the `:rev`/`:branch` boundary is structurally enforced —
        // a refname in the `:rev` slot is a build error, not a
        // resolver-time silent reinterpretation.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some("main".into()),
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":rev");
        assert_eq!(value, "main");
        // 4 chars `main` fails the length arm before the character arm,
        // so the diagnostic surfaces the abbreviation wording (same
        // path the `c0ffee0` 7-char fixture lands on); the structural
        // assertion is just that the `:rev "main"` value is rejected.
        assert!(
            !reason.is_empty(),
            "FontePinShape reason must be non-empty for refname-shaped :rev"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_rev_tag_shaped_value() {
        // Sibling cross-axis mis-slot: `:rev "v0.1.0"` — the author
        // conflated `:rev` and `:tag`. Pinned separately from the
        // `:rev "main"` (`:branch` mis-slot) arm so a future relaxation
        // that catches one but not the other surfaces here. The
        // length arm fires first (6 chars ≠ 40 ≠ 64); the structural
        // assertion is just that the cross-axis mis-slot is a build
        // error, regardless of which sub-arm surfaces the diagnostic
        // (`is_git_oid` rejects at the first violation; longer
        // tag-shape values would hit the non-hex arm instead).
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some("v0.1.0".into()),
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":rev");
        assert_eq!(value, "v0.1.0");
        assert!(
            !reason.is_empty(),
            "FontePinShape reason must be non-empty for tag-shaped :rev"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_rev_too_long() {
        // Boundary case on the upper end: 41 hex chars — one past the
        // SHA-1 width, well below the SHA-256 width. Pin so a future
        // relaxation that admits "long enough to be a SHA" without
        // matching either canonical width surfaces here. The diagnostic
        // names the offending length verbatim so the author's grep
        // target is unambiguous (either trim one char or paste the
        // full SHA-256).
        let too_long: String = "0".repeat(41);
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some(too_long.clone()),
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":rev");
        assert_eq!(value, too_long);
        assert!(
            reason.contains("41"),
            "reason must surface the offending length verbatim, got {reason:?}"
        );
    }

    #[test]
    fn validate_rejects_git_fonte_with_rev_carrying_whitespace() {
        // The canonical paste-from-doc footgun on `:rev` — author
        // copies `"deadbeefcafe…0123 "` (trailing space) out of a
        // commit-message paragraph. Until this gate landed the empty-
        // pin arm passed (the string isn't empty), the resolver issued
        // `git fetch <remote> 'deadbeef… '` and the failure surfaced at
        // clone time with a quoting-confused git error far from the
        // source caixa.lisp. The new gate moves the check to caixa-
        // build time. Length is 41 (40 hex + space) so the length arm
        // fires first — pinned separately from the pure-length arm to
        // ensure the diagnostic surfaces *some* parser wording, not
        // silently pass through.
        let with_space = "0123456789abcdef0123456789abcdef01234567 ".to_string();
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: None,
            rev: Some(with_space.clone()),
            branch: None,
        });
        let err = d.validate().unwrap_err();
        let DepError::FontePinShape {
            pin, value, reason, ..
        } = err
        else {
            panic!("expected FontePinShape, got other variant");
        };
        assert_eq!(pin, ":rev");
        assert_eq!(value, with_space);
        assert!(
            !reason.is_empty(),
            "FontePinShape reason must be non-empty for whitespace-bearing :rev"
        );
    }

    #[test]
    fn fonte_pin_shape_diagnostic_carries_offending_nome_pin_value_for_rev() {
        // Diagnostic-shape pin on the `:rev` axis: every FontePinShape
        // variant on this axis names the offending dep's `:nome` + the
        // `:rev` axis + the offending value verbatim, so the author's
        // grep target is the literal `:rev "<value>"` block in
        // caixa.lisp. Sibling of the `fonte_pin_shape_diagnostic_
        // carries_offending_nome_pin_value` test on the refname-shaped
        // (`:tag` / `:branch`) axes.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:p/x".into(),
            tag: None,
            rev: Some("not-a-sha".into()),
            branch: None,
        });
        let msg = d
            .validate()
            .expect_err(":rev: expected FontePinShape")
            .to_string();
        assert!(
            msg.contains("\"caixa-teia\""),
            ":rev: diagnostic must quote the offending :nome verbatim, got {msg:?}"
        );
        assert!(
            msg.contains(":rev"),
            ":rev: diagnostic must name the offending pin axis, got {msg:?}"
        );
        assert!(
            msg.contains("not-a-sha"),
            ":rev: diagnostic must quote the offending value verbatim, got {msg:?}"
        );
    }

    #[test]
    fn fonte_pin_empty_fires_before_pin_shape() {
        // Order pin: a `Some("")` `:tag` is the more self-locating
        // diagnostic (the author chose an axis but left it blank;
        // grep is unambiguous), so it fires before the shape gate
        // even when both arms would match. Pinned so a future
        // reordering surfaces here. Mirrors the
        // `fonte_repo_empty_fires_before_pin_missing` ordering
        // discipline on the peer per-axis arms.
        let d = dep_with_fonte(DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some(String::new()),
            rev: None,
            branch: None,
        });
        assert!(matches!(
            d.validate().unwrap_err(),
            DepError::FontePinEmpty { ref pin, .. } if pin == ":tag"
        ));
    }

    #[test]
    fn fonte_pin_shape_fires_after_repo_empty() {
        // Order pin: `:repo ""` is the more self-locating axis
        // (every git source needs a repo; the per-pin shape gate is
        // secondary), so the repo-empty arm fires before the
        // per-pin shape arm even when both are violated. Pinned so
        // a future reordering surfaces here. Mirrors
        // `fonte_repo_empty_fires_before_pin_missing` on the
        // adjacent axis pair.
        let d = dep_with_fonte(DepSource::Git {
            repo: String::new(),
            tag: Some("v0.1.0 ".into()),
            rev: None,
            branch: None,
        });
        assert!(matches!(
            d.validate().unwrap_err(),
            DepError::FonteRepoEmpty { .. }
        ));
    }

    #[test]
    fn fonte_pin_shape_diagnostic_carries_offending_nome_pin_value() {
        // Diagnostic-shape pin across both refname-shaped axes
        // (`:tag` + `:branch`): every `FontePinShape` variant names
        // the offending dep's `:nome` + the offending pin axis + the
        // offending value verbatim, so the author's grep target is
        // unambiguous (the literal `:tag "<value>"` / `:branch
        // "<value>"` lands in caixa.lisp with quotes). Cover both
        // pin axes so a future variant addition forces a parallel
        // diagnostic-shape decision.
        for (pin_label, fonte) in [
            (
                ":tag",
                DepSource::Git {
                    repo: "github:p/x".into(),
                    tag: Some("v0.1.0~1".into()),
                    rev: None,
                    branch: None,
                },
            ),
            (
                ":branch",
                DepSource::Git {
                    repo: "github:p/x".into(),
                    tag: None,
                    rev: None,
                    branch: Some("feature/foo*".into()),
                },
            ),
        ] {
            let d = dep_with_fonte(fonte);
            let msg = d
                .validate()
                .expect_err(&format!("{pin_label}: expected FontePinShape"))
                .to_string();
            assert!(
                msg.contains("\"caixa-teia\""),
                "{pin_label}: diagnostic must quote the offending :nome verbatim, got {msg:?}"
            );
            assert!(
                msg.contains(pin_label),
                "{pin_label}: diagnostic must name the offending pin axis, got {msg:?}"
            );
        }
    }

    #[test]
    fn git_source_json_round_trip() {
        let src = DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        };
        let s = serde_json::to_string(&src).unwrap();
        assert!(s.contains(&format!(
            r#""{tipo}":"{git}""#,
            tipo = crate::render::DEP_SOURCE_KEY_TIPO,
            git = crate::render::DEP_SOURCE_TIPO_GIT,
        )));
        assert!(s.contains(r#""repo":"github:pleme-io/caixa-teia""#));
        assert!(s.contains(r#""tag":"v0.1.0""#));
        assert!(!s.contains("rev"));
        assert!(!s.contains("branch"));
        let round: DepSource = serde_json::from_str(&s).unwrap();
        assert_eq!(round, src);
    }

    // ── DEP_SOURCE_{KEY_TIPO,TIPO_GIT,TIPO_PATH} drift-detection ────────
    //
    // The `#[serde(tag = "tipo", rename_all = "lowercase")]` derive
    // attribute on [`DepSource`] pins three load-bearing byte-sequences
    // that flow into every serialized `Dep.fonte` block: the outer
    // discriminator-key `"tipo"` the `tag = "tipo"` attribute names, and
    // the two admitted variant-tag values `"git"` / `"path"` the
    // `rename_all = "lowercase"` attribute pins as the discriminator's
    // closed-set arms. The three pin tests below round-trip a
    // fully-populated variant of each arm through
    // [`serde_json::to_value`] and assert each canonical byte-sequence
    // appears at its axis — pins a hypothetical future
    // `tag = "type"` / `tag = "source_type"` typo, a `rename_all`
    // rebrand (`"UPPERCASE"` / `"snake_case"` / `"kebab-case"`), or a
    // Rust-side variant rename (`Git` → `Repository`, `Path` → `Local`)
    // at build time rather than at fetch time when the resolver's
    // `Dep.fonte` dispatch silently fails to match on the drifted
    // discriminator. Same "serialize-and-check" discipline the peer
    // `M2_LIMITS_KEY_*`, `M2_BEHAVIOR_KEY_ON_*`, `SUPERVISOR_KEY_*`,
    // and `MEMBRO_KEY_*` drift-detection pins carry — extended here
    // to the last `#[serde(tag = ..., rename_all = ...)]` discriminator
    // family in caixa-core lacking a lifted peer.

    #[test]
    fn dep_source_git_serde_keys_match_lifted_dep_source_key_consts() {
        // Fail-before-pass-after: a future `tag = "type"` at the derive
        // attribute would serialize under `"type":"git"`, and this test
        // would trip because `"tipo"` no longer appears at the emitted
        // discriminator key. A future `rename_all = "kebab-case"` /
        // `"snake_case"` (both no-ops on `Git` since it lacks internal
        // word boundaries) is caught by the sibling
        // `dep_source_path_serde_keys_match_lifted_dep_source_key_consts`
        // pin below (Path has no internal boundary either but the pair
        // catches any per-arm inconsistency). A future variant rename
        // `Git` → `Repository` would emit `"tipo":"repository"` and
        // trip this pin.
        let src = DepSource::Git {
            repo: "github:pleme-io/caixa-teia".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        };
        let json = serde_json::to_value(&src).unwrap();
        let obj = json.as_object().expect("Git serializes as a JSON object");
        assert_eq!(
            obj.get(crate::render::DEP_SOURCE_KEY_TIPO)
                .and_then(serde_json::Value::as_str),
            Some(crate::render::DEP_SOURCE_TIPO_GIT),
            "DepSource::Git must serialize the tipo discriminator at DEP_SOURCE_KEY_TIPO \
             with value DEP_SOURCE_TIPO_GIT — attribute drift or variant rename \
             detected in {json}"
        );
    }

    #[test]
    fn dep_source_path_serde_keys_match_lifted_dep_source_key_consts() {
        // Fail-before-pass-after: a future variant rename `Path` →
        // `Local` / `Filesystem` would emit `"tipo":"local"` and trip
        // this pin. A per-consumer disambiguation as the `defcaixa`
        // macro stabilizes ("caminho" → "path" for English-uniformity)
        // is scoped to the inner field key, not the discriminator; this
        // pin is orthogonal to that and catches only the outer
        // discriminator drift.
        let src = DepSource::Path {
            caminho: "../caixa-teia".into(),
        };
        let json = serde_json::to_value(&src).unwrap();
        let obj = json.as_object().expect("Path serializes as a JSON object");
        assert_eq!(
            obj.get(crate::render::DEP_SOURCE_KEY_TIPO)
                .and_then(serde_json::Value::as_str),
            Some(crate::render::DEP_SOURCE_TIPO_PATH),
            "DepSource::Path must serialize the tipo discriminator at DEP_SOURCE_KEY_TIPO \
             with value DEP_SOURCE_TIPO_PATH — attribute drift or variant rename \
             detected in {json}"
        );
    }

    #[test]
    fn dep_source_key_consts_are_pairwise_distinct() {
        // Cross-axis collapse detector: a hypothetical future edit that
        // accidentally set two of the three consts to the same byte
        // (`DEP_SOURCE_TIPO_GIT = "path"` typo matching a peer arm) would
        // pass every per-arm serialize pin above but silently collapse
        // the discriminator's closed-set arms onto one another; this pin
        // catches the collapse at build time.
        assert_ne!(
            crate::render::DEP_SOURCE_KEY_TIPO,
            crate::render::DEP_SOURCE_TIPO_GIT,
        );
        assert_ne!(
            crate::render::DEP_SOURCE_KEY_TIPO,
            crate::render::DEP_SOURCE_TIPO_PATH,
        );
        assert_ne!(
            crate::render::DEP_SOURCE_TIPO_GIT,
            crate::render::DEP_SOURCE_TIPO_PATH,
        );
    }

    #[test]
    fn dep_source_tipo_variant_consts_are_ascii_lowercase_shape() {
        // Shape pin against `rename_all` drift: the two variant-tag
        // consts must be ASCII-lowercase-only to match the
        // `rename_all = "lowercase"` attribute the derive uses; a future
        // rebrand to `"UPPERCASE"` / `"PascalCase"` at the attribute
        // would emit `"GIT"` / `"Git"` instead and trip this pin.
        for (label, s) in [
            ("DEP_SOURCE_TIPO_GIT", crate::render::DEP_SOURCE_TIPO_GIT),
            ("DEP_SOURCE_TIPO_PATH", crate::render::DEP_SOURCE_TIPO_PATH),
        ] {
            assert!(!s.is_empty(), "{label} must not be empty");
            assert!(
                s.bytes().all(|b| b.is_ascii_lowercase()),
                "{label} must be ASCII-lowercase-only (matching \
                 rename_all = \"lowercase\"), got {s:?}",
            );
        }
    }

    // ── per-entry :caracteristicas set-not-multiset gate ────────────
    //
    // Every Vec-keyed-by-name authoring surface on the typed Caixa
    // surface that identifies its entries by a name field now uniformly
    // closes the set-not-multiset discipline at build time (cite
    // `validate_caracteristicas`'s peer-axis enumeration). The
    // `:caracteristicas` axis is per-`Dep`: the feature-toggle slot is
    // set-shaped (a feature is either enabled or not — there is no
    // `feature × 2` semantic), so two entries naming the same feature
    // are a redundant declaration the caixa-resolver's lacre pipeline
    // would silently dedup at resolve time. The empty-feature arm
    // closes the parallel "operationally-meaningless value" axis on
    // the same slot. Same linear-walk + `HashSet` + first-collision
    // shape every peer set gate uses; same empty-first cascade every
    // peer per-entry shape + duplicate gate uses (the empty-feature
    // axis is the more-actionable defect since two `""` entries would
    // both report `caracteristica: ""` under a duplicate-first
    // ordering, with no way to distinguish the offending site).

    fn dep_with_features(features: &[&str]) -> Dep {
        Dep {
            nome: "caixa-teia".into(),
            versao: "^0.1".into(),
            fonte: None,
            opcional: false,
            caracteristicas: features.iter().map(|s| (*s).into()).collect(),
        }
    }

    #[test]
    fn validate_rejects_empty_caracteristica() {
        // Fail-before-pass-after pin: every pre-gate codebase accepted
        // `(:caracteristicas (""))` cleanly (the `Vec<String>` field
        // imposed no per-entry shape contract), the dep validated, and
        // the empty feature would have reached the future caixa-resolver
        // lacre pipeline as a no-op feature enable — silently dropping
        // the author's intent far from the source `caixa.lisp`. The new
        // gate surfaces the structural defect at the typed-validate
        // surface with a self-locating diagnostic naming the offending
        // dep's `:nome`.
        let d = dep_with_features(&[""]);
        assert!(
            matches!(d.validate().unwrap_err(), DepError::CaracteristicaEmpty { ref nome } if nome == "caixa-teia"),
            "expected CaracteristicaEmpty, got {:?}",
            d.validate(),
        );
    }

    #[test]
    fn validate_rejects_duplicate_caracteristica() {
        // Fail-before-pass-after pin on the set-not-multiset arm: the
        // feature-toggle slot is set-shaped, so `(:caracteristicas
        // ("http" "http"))` is a redundant declaration the lacre
        // pipeline dedupes silently at resolve time. The diagnostic
        // names the offending dep + the colliding feature verbatim so
        // the author can grep their caixa.lisp for `:caracteristicas`
        // and fix it in one edit. First-collision determinism is
        // pinned separately below.
        let d = dep_with_features(&["http", "http"]);
        assert!(
            matches!(
                d.validate().unwrap_err(),
                DepError::CaracteristicaDuplicate { ref nome, ref caracteristica }
                    if nome == "caixa-teia" && caracteristica == "http"
            ),
            "expected CaracteristicaDuplicate, got {:?}",
            d.validate(),
        );
    }

    #[test]
    fn validate_accepts_distinct_caracteristicas() {
        // The canonical authoring shape — every feature distinct — must
        // remain a clean pass (positive control sweep). Covers the
        // canonical kebab-case feature names a target caixa typically
        // declares.
        dep_with_features(&["http", "json", "tls"])
            .validate()
            .unwrap();
    }

    #[test]
    fn validate_accepts_single_caracteristica() {
        // Single-element list is the minimum non-empty shape; passes
        // the gate as the identity of the duplicate check (no second
        // entry to collide with).
        dep_with_features(&["http"]).validate().unwrap();
    }

    #[test]
    fn validate_accepts_empty_caracteristicas_list() {
        // The bare-dep authoring shape (`Dep::simple` / `Dep::git`)
        // produces `caracteristicas: Vec::new()`; the empty list is
        // the gate's empty-set identity and passes vacuously. Pin
        // this so a future tightening that requires ≥1 feature
        // surfaces here as a test failure rather than a silent
        // contract narrowing.
        Dep::simple("caixa-teia", "^0.1").validate().unwrap();
        assert!(dep_with_features(&[]).validate().is_ok());
    }

    #[test]
    fn validate_caracteristica_empty_fires_before_duplicate() {
        // Empty-first cascade: an entry with an empty feature *and*
        // duplicate entries surfaces the empty diagnostic first. The
        // empty-feature axis is the more-actionable defect since
        // `caracteristica: ""` is unambiguous; under duplicate-first
        // ordering the diagnostic could report the empty string from
        // either of two empty entries with no way to distinguish.
        // Mirrors the peer empty-before-duplicate ordering
        // discipline every per-entry shape + duplicate gate establishes
        // (`SupervisorSpec::validate`'s `EmptyChildName` arm before
        // `DuplicateChildCaixa`, `validate_membros`'s
        // `MembroCaixaEmpty` arm before `MembroDuplicate`).
        let d = dep_with_features(&["", "http", "http"]);
        assert!(matches!(
            d.validate().unwrap_err(),
            DepError::CaracteristicaEmpty { .. }
        ));
    }

    #[test]
    fn validate_caracteristica_duplicate_first_collision_determinism() {
        // Three matching entries: the second occurrence surfaces the
        // diagnostic (the second is the first *collision* — the first
        // entry is the establishing one, not a duplicate). Mirrors
        // every peer first-collision posture
        // (`SupervisorError::DuplicateChildCaixa` reports the second
        // collision, `AplicacaoError::MembroDuplicate` reports the
        // second, `DepError::DuplicateNome` reports the second).
        // Pinning this so a future shortcut that flips to last-
        // collision (or non-deterministic) surfaces here.
        let d = dep_with_features(&["http", "http", "http"]);
        assert!(matches!(
            d.validate().unwrap_err(),
            DepError::CaracteristicaDuplicate { ref caracteristica, .. } if caracteristica == "http"
        ));
    }

    #[test]
    fn validate_per_entry_shape_fires_before_caracteristicas() {
        // Per-entry shape precedence: a dep with a malformed `:nome`
        // (uppercase) AND duplicate `:caracteristicas` surfaces the
        // narrower `NomeInvalid` diagnostic first, not the set-gate
        // diagnostic. The `:nome` is the self-locating axis (every
        // diagnostic from the caracteristicas gate quotes the
        // offending dep's `:nome` to anchor the grep target —
        // surfacing the malformed name first keeps that anchor
        // valid). Same precedence shape every peer per-entry-shape
        // arm establishes against its peer set-gate
        // (`validate_deps_per_entry_validate_fires_before_duplicate_in_deps`
        // on the cross-entry `:nome` axis).
        let d = Dep {
            nome: "Caixa-Teia".into(), // uppercase — DNS-1123 violation
            versao: "^0.1".into(),
            fonte: None,
            opcional: false,
            caracteristicas: vec!["http".into(), "http".into()],
        };
        assert!(matches!(
            d.validate().unwrap_err(),
            DepError::NomeInvalid { .. }
        ));
    }

    // ── per-entry :caracteristicas value-shape gate ──────────────────
    //
    // Until this gate landed `:caracteristicas` only refused the empty
    // string and cross-entry duplicates: a non-empty distinct but
    // structurally invalid feature name silently passed validate and the
    // failure surfaced at `cargo metadata` time as Cargo's
    // `restricted_names::validate_feature_name` parser rejection, far from
    // the source `caixa.lisp` with no field naming which `:deps` entry's
    // `:caracteristicas` carried the typo. The lifted predicate makes the
    // Cargo-feature-name-grammar intersection-floor a substrate-level
    // invariant at validate time. Same trajectory as the eight peer
    // value-shape predicates each typed surface downstream of a structured
    // grammar already follows.

    #[test]
    fn validate_rejects_caracteristica_with_leading_plus() {
        // Fail-before-pass-after pin on the canonical Cargo
        // `+<feature>` activation-form-in-feature-name-slot footgun.
        // Cargo's `[dependencies.<dep>.features]` list grammar accepts
        // `+optional-feature` as an enablement of a previously-disabled
        // feature; pasting that activation form into `:caracteristicas`
        // (which names the feature itself) silently passed pre-gate and
        // failed at `cargo metadata` parse time.
        let d = dep_with_features(&["+http"]);
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::CaracteristicaInvalid { ref nome, ref caracteristica, .. }
                    if nome == "caixa-teia" && caracteristica == "+http"
            ),
            "expected CaracteristicaInvalid, got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_caracteristica_with_leading_hyphen() {
        // Fail-before-pass-after pin on the leading-hyphen footgun. `-`
        // is a legitimate continuation character (kebab-case feature
        // names like `runtime-tokio` pass) but Cargo rejects it at the
        // start; the structural defect — and its CLI-argument-injection
        // adjacency at any downstream Cargo subprocess invocation — is
        // closed at validate time, not at `cargo metadata` time.
        let d = dep_with_features(&["-json"]);
        let err = d.validate().unwrap_err();
        assert!(
            matches!(
                err,
                DepError::CaracteristicaInvalid { ref caracteristica, .. } if caracteristica == "-json"
            ),
            "expected CaracteristicaInvalid, got {err:?}"
        );
    }

    #[test]
    fn validate_rejects_caracteristica_with_leading_dot() {
        // Fail-before-pass-after pin on the leading-dot footgun. `.` is
        // a legitimate continuation character (version-suffix shapes
        // like `feat.v2` pass) but the leading-dot form is the
        // canonical dotted-version-suffix-as-feature-name confusion.
        let d = dep_with_features(&[".feat"]);
        let err = d.validate().unwrap_err();
        assert!(matches!(
            err,
            DepError::CaracteristicaInvalid { ref caracteristica, .. } if caracteristica == ".feat"
        ));
    }

    #[test]
    fn validate_rejects_caracteristica_with_whitespace() {
        // Fail-before-pass-after pin on the embedded-whitespace footgun:
        // a feature name with a space inside is structurally a multi-
        // token blob (the canonical paste-from-doc footgun, or an
        // accidental `"http server"` where the author meant
        // `"http-server"`).
        let d = dep_with_features(&["http feature"]);
        let err = d.validate().unwrap_err();
        assert!(matches!(
            err,
            DepError::CaracteristicaInvalid { ref caracteristica, .. } if caracteristica == "http feature"
        ));
    }

    #[test]
    fn validate_rejects_caracteristica_with_comma() {
        // Fail-before-pass-after pin on the embedded-comma footgun:
        // the list-separator-belongs-to-the-list-grammar
        // miscomprehension where the author writes
        // `:caracteristicas ("http,json")` intending two features but
        // the `Vec<String>` field consumes the bare token as one entry.
        let d = dep_with_features(&["http,json"]);
        let err = d.validate().unwrap_err();
        assert!(matches!(
            err,
            DepError::CaracteristicaInvalid { ref caracteristica, .. } if caracteristica == "http,json"
        ));
    }

    #[test]
    fn validate_rejects_caracteristica_with_slash() {
        // Fail-before-pass-after pin on the embedded-slash footgun:
        // Cargo's `dep/feat` namespaced-dep syntax applies inside
        // `[dependencies.<dep>.features]` list entries that already
        // name the parent dep (so the syntax says "enable feature
        // `feat` on a transitive dep `dep`"); `:caracteristicas` is
        // per-dep already (a sibling slot on the `Dep` itself), so the
        // segment separator within an entry must be `-`, `_`, `+`,
        // or `.`. The diagnostic remediation points at the canonical
        // Cargo namespaced-dep discipline.
        let d = dep_with_features(&["http/json"]);
        let err = d.validate().unwrap_err();
        assert!(matches!(
            err,
            DepError::CaracteristicaInvalid { ref caracteristica, .. } if caracteristica == "http/json"
        ));
    }

    #[test]
    fn validate_rejects_caracteristica_with_non_ascii() {
        // Fail-before-pass-after pin on the un-percent-encoded non-ASCII
        // byte footgun: NFC-vs-NFD normalization across filesystems
        // silently rewrites the feature-key, breaking the lacre's
        // content-addressing invariant. Pinned at a canonical
        // smart-quote-paste shape (`café`) where the raw `é` byte is the
        // documented APFS round-trip break.
        let d = dep_with_features(&["caf\u{e9}"]);
        let err = d.validate().unwrap_err();
        assert!(matches!(
            err,
            DepError::CaracteristicaInvalid { ref caracteristica, .. } if caracteristica == "caf\u{e9}"
        ));
    }

    #[test]
    fn validate_rejects_caracteristica_with_control_character() {
        // Fail-before-pass-after pin on the embedded-control-character
        // footgun: a CR/LF or any 0x00..0x1F / 0x7F byte landing in a
        // feature name is the canonical paste-from-multiline-doc
        // footgun the predicate's reason wording specifically calls out.
        let d = dep_with_features(&["http\njson"]);
        let err = d.validate().unwrap_err();
        assert!(matches!(err, DepError::CaracteristicaInvalid { .. }));
    }

    #[test]
    fn validate_accepts_canonical_caracteristicas_shapes() {
        // Positive control sweep: every canonical Cargo feature name
        // shape the pleme-io ecosystem uses must still pass. Mirrors
        // the substrate-side `cargo_feature_name_accepts_canonical_forms`
        // sweep — drift between either landing site and the predicate's
        // accepted set is a build error visible at this pair of tests,
        // not a per-renderer "this passed validate but failed at
        // cargo metadata time" surprise on the next acceptance.
        for s in [
            "http",
            "json",
            "derive",
            "serde_json",
            "runtime-tokio",
            "tokio.full",
            "v0.1",
            "http+json",
            "_internal",
            "__private",
            "default",
            "rt-multi-thread",
            "feat.v2",
        ] {
            let d = dep_with_features(&[s]);
            d.validate().unwrap_or_else(|e| {
                panic!("canonical Cargo feature name {s:?} must pass validate: {e:?}")
            });
        }
    }

    #[test]
    fn validate_caracteristica_empty_fires_before_invalid() {
        // Cascade precedence pin: an entry list with both an empty
        // feature AND an invalid-shape feature surfaces the
        // `CaracteristicaEmpty` arm first (the empty value carries no
        // self-locating data — `caracteristica: ""` is the diagnostic
        // with no way to anchor a grep target — so closing the empty
        // axis first preserves the per-entry-shape diagnostic's
        // self-locating discipline). Same empty-first cascade every
        // peer per-entry shape gate establishes
        // (`SupervisorSpec::validate`'s `EmptyChildName` before
        // `ChildCaixaInvalid`, `validate_membros`'s `MembroCaixaEmpty`
        // before `MembroCaixaInvalid`).
        let d = dep_with_features(&["", "+http"]);
        assert!(matches!(
            d.validate().unwrap_err(),
            DepError::CaracteristicaEmpty { .. }
        ));
    }

    #[test]
    fn validate_caracteristica_invalid_fires_before_duplicate() {
        // Per-entry-shape precedence pin: an entry list with the same
        // invalid feature shape declared twice surfaces the
        // `CaracteristicaInvalid` diagnostic on the first entry, not
        // the `CaracteristicaDuplicate` on the second collision. The
        // per-entry shape gate fires before the cross-entry set gate
        // — same precedence shape every peer two-arm-plus-set gate
        // establishes (`SupervisorSpec::validate`'s
        // `ChildCaixaInvalid` before `DuplicateChildCaixa`,
        // `validate_membros`'s `MembroCaixaInvalid` before
        // `MembroDuplicate`, `Dep::validate`'s `NomeInvalid` before
        // cross-list `DuplicateNome`).
        let d = dep_with_features(&["+http", "+http"]);
        assert!(matches!(
            d.validate().unwrap_err(),
            DepError::CaracteristicaInvalid { ref caracteristica, .. } if caracteristica == "+http"
        ));
    }

    #[test]
    fn validate_rejects_caracteristica_at_65_byte_boundary() {
        // Boundary pin on the 64-byte cap — both the boundary-accepting
        // case and the boundary-exceeding case in one place, so a
        // future cap shift surfaces both arms simultaneously, mirroring
        // the peer `cargo_feature_name_rejects_at_65_byte_boundary`
        // predicate-level pin at the dep-axis landing site.
        let max_ok = "a".repeat(64);
        dep_with_features(&[&max_ok])
            .validate()
            .unwrap_or_else(|e| panic!("64-byte feature name must pass: {e:?}"));
        let too_long = "a".repeat(65);
        let d = dep_with_features(&[&too_long]);
        assert!(matches!(
            d.validate().unwrap_err(),
            DepError::CaracteristicaInvalid { .. }
        ));
    }

    // ── self-dep cross-slot gate ─────────────────────────────────────

    #[test]
    fn validate_no_self_dep_rejects_self_in_deps() {
        // A caixa whose `:deps` lists its own `:nome` is a one-node
        // cycle in the lacre closure's dep-graph traversal — rejected,
        // naming the parent and the offending list tag.
        let deps = vec![
            Dep::simple("caixa-teia", "^0.1"),
            Dep::simple("orquestra", "^0.1"),
        ];
        let err = validate_no_self_dep(&deps, &[], "orquestra").unwrap_err();
        assert!(
            matches!(err, DepError::DepIsSelf { ref nome, list } if nome == "orquestra" && list == crate::render::DEP_AUTHOR_KEY_DEPS),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_no_self_dep_rejects_self_in_deps_dev() {
        // Same gate on the `:deps-dev` axis — neither dep list is a
        // second-class citizen on the self-edge invariant.
        let deps_dev = vec![Dep::simple("orquestra", "^0.1")];
        let err = validate_no_self_dep(&[], &deps_dev, "orquestra").unwrap_err();
        assert!(
            matches!(err, DepError::DepIsSelf { ref nome, list } if nome == "orquestra" && list == crate::render::DEP_AUTHOR_KEY_DEPS_DEV),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_no_self_dep_deps_fires_before_deps_dev() {
        // Walk order pin: a caixa that self-references on both lists
        // surfaces the `:deps` arm first — the load-bearing axis the
        // lacre closure resolves at every build. Mirrors the canonical
        // [`Caixa::validate_deps`] cascade (`:deps` → `:deps-dev`).
        let deps = vec![Dep::simple("orquestra", "^0.1")];
        let deps_dev = vec![Dep::simple("orquestra", "^0.2")];
        let err = validate_no_self_dep(&deps, &deps_dev, "orquestra").unwrap_err();
        assert!(
            matches!(err, DepError::DepIsSelf { ref nome, list } if nome == "orquestra" && list == crate::render::DEP_AUTHOR_KEY_DEPS),
            "got {err:?}"
        );
    }

    #[test]
    fn validate_no_self_dep_accepts_distinct_names() {
        // Positive control: every dep names a distinct caixa. The
        // canonical author surface — peer of
        // [`validate_no_self_supervision_accepts_distinct_children`].
        let deps = vec![
            Dep::simple("caixa-teia", "^0.1"),
            Dep::simple("caixa-arch", "^0.1"),
        ];
        let deps_dev = vec![Dep::simple("caixa-test", "^0.1")];
        validate_no_self_dep(&deps, &deps_dev, "orquestra").unwrap();
    }

    #[test]
    fn validate_no_self_dep_empty_lists_pass() {
        // A caixa with no declared deps has nothing to self-reference —
        // the gate is vacuously satisfied. Peer of
        // [`validate_no_self_supervision_empty_children_is_ok`].
        validate_no_self_dep(&[], &[], "orquestra").unwrap();
    }

    #[test]
    fn validate_no_self_dep_diagnostic_carries_offending_list_and_nome() {
        // Diagnostic-shape pin (peer with
        // [`validate_no_self_supervision`]'s diagnostic): the error's
        // Display surfaces both the offending list tag and the
        // parent's `:nome` verbatim, so the author can grep their
        // caixa.lisp for the offending block in one edit. Names
        // `:bibliotecas` / `:exe` / `:servicos` as the corrective
        // surface — every legitimate "I want to use code from this
        // caixa" intent routes through one of those three slots.
        let deps_dev = vec![Dep::simple("orquestra", "^0.1")];
        let rendered = validate_no_self_dep(&[], &deps_dev, "orquestra")
            .unwrap_err()
            .to_string();
        assert!(
            rendered.contains(crate::render::DEP_AUTHOR_KEY_DEPS_DEV),
            "diagnostic must name the offending list tag: {rendered}",
        );
        assert!(
            rendered.contains("orquestra"),
            "diagnostic must quote the parent caixa name: {rendered}",
        );
        assert!(
            rendered.contains(":bibliotecas"),
            "diagnostic must point at the corrective code-surface slot: {rendered}",
        );
    }

    #[test]
    fn validate_no_self_dep_accepts_coincidental_substring_match() {
        // Identity is exact-string equality, not substring — a dep
        // named `"orquestra-helper"` is a distinct caixa even when the
        // parent is `"orquestra"`. Pin the exact-match discipline so a
        // future relaxation that uses `contains` surfaces here, peer
        // with the supervision-tree and Aplicacao-membership gates
        // which all use exact-string equality on the typed identity.
        let deps = vec![Dep::simple("orquestra-helper", "^0.1")];
        validate_no_self_dep(&deps, &[], "orquestra").unwrap();
    }

    // ── drift-detection: DEP_AUTHOR_KEY_{DEPS,DEPS_DEV} pin ─────────────

    #[test]
    fn dep_author_key_consts_pin_canonical_kebab_case_labels() {
        // Scalar-value pin: the two author-facing kebab-case labels the
        // `(defcaixa … :deps ((…)) :deps-dev ((…)))` surface admits on
        // the two-list dep-graph slot axis, one arm per typed slot.
        // Mirrors the peer scalar-value pin the sibling
        // [`crate::M2_AUTHOR_KEY_LIMITS`] /
        // [`crate::M2_AUTHOR_KEY_BEHAVIOR`] /
        // [`crate::M2_AUTHOR_KEY_UPGRADE_FROM`] (f49c8b0) M2 top-level
        // author-labels, [`crate::M3_AUTHOR_KEY_MEMBROS`] etc.
        // (882f498) M3 top-level author-labels, and
        // [`crate::SUPERVISOR_AUTHOR_KEY_ESTRATEGIA`] etc. (be40492)
        // Supervisor top-level author-labels carry, so every kind-scoped
        // typed-slot-family axis routes through one canonical per-arm
        // declaration.
        //
        // A future rebrand (`:deps` → `:dependencies` matching Cargo's
        // verbatim key, `:deps-dev` → `:dev-dependencies` matching the
        // same, `:deps` / `:deps-dev` → `:runtime-deps` / `:dev-deps`
        // for symmetry) lands as an edit to exactly one const, and
        // every consumer that reaches for the label picks it up at
        // build time rather than at runtime as a downstream mismatch on
        // a `DepError::DuplicateNome { list: … }` diagnostic far from
        // the rename's commit.
        assert_eq!(crate::render::DEP_AUTHOR_KEY_DEPS, ":deps");
        assert_eq!(crate::render::DEP_AUTHOR_KEY_DEPS_DEV, ":deps-dev");
    }

    #[test]
    fn dep_author_key_consts_are_pairwise_distinct() {
        // Distinct-labels pin: the two `:deps` / `:deps-dev` labels
        // must not collapse onto one byte-string. A future copy-paste
        // slip that renamed both consts to the same value (or a rebrand
        // that dropped the `-dev` suffix from one but not the other)
        // would leave every `DepError::DuplicateNome { list: … }`
        // diagnostic naming an unattributable list — the linter would
        // route the author to the wrong caixa.lisp block, or the
        // cross-list precedence gate
        // (`validate_deps_duplicate_in_deps_fires_before_duplicate_in_deps_dev`)
        // would surface a `:deps`-tagged diagnostic on a `:deps-dev`
        // duplicate. Peer of the sibling
        // `m2_author_key_consts_are_pairwise_distinct`-shape gates the
        // other top-level kind-scoped slot-family axes carry
        // (implicitly held by their different byte-values today).
        assert_ne!(
            crate::render::DEP_AUTHOR_KEY_DEPS,
            crate::render::DEP_AUTHOR_KEY_DEPS_DEV,
            "DEP_AUTHOR_KEY_{{DEPS,DEPS_DEV}} consts must be pairwise-distinct \
             so a `DepError::DuplicateNome {{ list: … }}` diagnostic \
             self-locates the offending block in the author's caixa.lisp",
        );
    }

    #[test]
    fn validate_no_self_dep_routes_through_lifted_dep_author_key_consts() {
        // Production-through-const pin: the two per-arm list tags
        // [`validate_no_self_dep`] threads onto the `list:` field of a
        // returned [`DepError::DepIsSelf`] route through the lifted
        // [`crate::DEP_AUTHOR_KEY_DEPS`] /
        // [`crate::DEP_AUTHOR_KEY_DEPS_DEV`] consts. A future drift at
        // the walker (a rename that reaches one arm but not the const,
        // or vice versa) surfaces here at build time rather than at
        // runtime as a `feira lint` diagnostic naming the wrong list
        // tag. Mirror of the peer
        // [`crate::Caixa::declared_servico_slots`] production tagger
        // pin (f49c8b0) on the sibling M2 top-level slot axis, extended
        // onto the two-list dep-graph gate.
        let deps = vec![Dep::simple("orquestra", "^0.1")];
        let err = validate_no_self_dep(&deps, &[], "orquestra").unwrap_err();
        let DepError::DepIsSelf { list, .. } = err else {
            panic!("expected DepIsSelf from :deps walk");
        };
        assert_eq!(list, crate::render::DEP_AUTHOR_KEY_DEPS);

        let deps_dev = vec![Dep::simple("orquestra", "^0.1")];
        let err = validate_no_self_dep(&[], &deps_dev, "orquestra").unwrap_err();
        let DepError::DepIsSelf { list, .. } = err else {
            panic!("expected DepIsSelf from :deps-dev walk");
        };
        assert_eq!(list, crate::render::DEP_AUTHOR_KEY_DEPS_DEV);
    }

    // ── Dep::nome accessor pins ───────────────────────────────────────
    //
    // Three coherence pins on the lifted `Dep::nome` accessor: byte-equal
    // projection over the plain-shorthand / explicit-git / explicit-path
    // fixture triad the [`Dep`] docstring lists (so the accessor's
    // accept-set is exercised across every author-surface `:fonte`
    // shape); by-borrow pointer identity so the projection stays
    // zero-copy at every consumer site; and validate-composition through
    // the [`validate_no_self_dep`] cross-slot gate reading its
    // parent-name equality check through the lifted accessor rather than
    // the raw field.

    #[test]
    fn dep_nome_returns_declared_nome_across_fonte_shapes() {
        // Plain-shorthand form (`:fonte None`).
        assert_eq!(Dep::simple("caixa-teia", "^0.1").nome(), "caixa-teia");
        // Explicit git-source form with a tag pin — same accessor path.
        assert_eq!(
            Dep::git("caixa-teia", "^0.1", "github:pleme-io/caixa-teia", "v0.1.0").nome(),
            "caixa-teia",
        );
        // Explicit path-source form.
        assert_eq!(
            Dep {
                nome: "caixa-teia".to_string(),
                versao: "0.1.0".to_string(),
                fonte: Some(DepSource::Path {
                    caminho: "../caixa-teia".to_string(),
                }),
                opcional: false,
                caracteristicas: Vec::new(),
            }
            .nome(),
            "caixa-teia",
        );
        // The empty-string `:nome` sentinel (which [`Dep::validate`]
        // refuses through the [`DepError::NomeEmpty`] arm) still round-
        // trips as an empty `&str` through the accessor — the accessor is
        // a projection, not a gate; the gate is [`Dep::validate`].
        assert_eq!(Dep::simple("", "^0.1").nome(), "");
    }

    #[test]
    fn dep_nome_is_by_borrow_pointer_identity() {
        // Zero-copy pin: the accessor must borrow into the field's own
        // storage, not clone. If a future rewrite regresses to
        // `self.nome.clone().leak()` or an owned-buffer shape, the two
        // pointers diverge and this pin fails at build time.
        let d = Dep::simple("caixa-teia", "^0.1");
        assert!(std::ptr::eq(d.nome().as_ptr(), d.nome.as_ptr()));
    }

    // ── Dep::versao_requirement accessor pins ─────────────────────────
    //
    // Three coherence pins on the lifted `Dep::versao_requirement`
    // accessor: byte-equal projection over the plain-shorthand /
    // explicit-git / explicit-path fixture triad the [`Dep`] docstring
    // lists plus the empty-sentinel that round-trips as `""` (the accessor
    // is a projection, not a gate; the gate is [`Dep::validate`]); by-
    // borrow pointer identity so the projection stays zero-copy at every
    // consumer site; and validate-composition through the
    // [`crate::render::require_valid_versao_requirement`] cascade reading
    // its requirement-shape check through the lifted accessor rather than
    // the raw field.
    #[test]
    fn dep_versao_requirement_returns_declared_versao_across_fonte_shapes() {
        // Plain-shorthand form (`:fonte None`).
        assert_eq!(
            Dep::simple("caixa-teia", "^0.1").versao_requirement(),
            "^0.1",
        );
        // Explicit git-source form with a tag pin — same accessor path.
        assert_eq!(
            Dep::git(
                "caixa-teia",
                "~0.1.2",
                "github:pleme-io/caixa-teia",
                "v0.1.0"
            )
            .versao_requirement(),
            "~0.1.2",
        );
        // Explicit path-source form.
        assert_eq!(
            Dep {
                nome: "caixa-teia".to_string(),
                versao: "0.1.0".to_string(),
                fonte: Some(DepSource::Path {
                    caminho: "../caixa-teia".to_string(),
                }),
                opcional: false,
                caracteristicas: Vec::new(),
            }
            .versao_requirement(),
            "0.1.0",
        );
        // The wildcard requirement (`"*"`) — the shorthand
        // `parse_requirement` accepts as `VersionReq::STAR` — round-trips
        // verbatim through the accessor as `"*"`, same byte-shape the
        // author wrote.
        assert_eq!(Dep::simple("caixa-teia", "*").versao_requirement(), "*");
        // The empty-string `:versao` sentinel (which [`Dep::validate`]
        // refuses through the [`DepError::VersaoEmpty`] arm) still round-
        // trips as an empty `&str` through the accessor — the accessor is
        // a projection, not a gate; the gate is [`Dep::validate`]. Peer
        // of the sibling [`Dep::nome`] empty-sentinel round-trip pin.
        assert_eq!(Dep::simple("caixa-teia", "").versao_requirement(), "");
    }

    #[test]
    fn dep_versao_requirement_is_by_borrow_pointer_identity() {
        // Zero-copy pin: the accessor must borrow into the field's own
        // storage, not clone. If a future rewrite regresses to
        // `self.versao.clone().leak()` or an owned-buffer shape, the two
        // pointers diverge and this pin fails at build time. Peer of the
        // sibling [`Dep::nome`] pointer-identity pin — same by-borrow
        // discipline extended onto the requirement-carrying axis.
        let d = Dep::simple("caixa-teia", "^0.1");
        assert!(std::ptr::eq(
            d.versao_requirement().as_ptr(),
            d.versao.as_ptr(),
        ));
    }

    #[test]
    fn dep_validate_reads_requirement_through_accessor() {
        // Composition pin: the [`Dep::validate`]
        // [`crate::render::require_valid_versao_requirement`] cascade
        // consumes the requirement string through the lifted accessor —
        // both the requirement-gate input and the
        // [`DepError::VersaoInvalid`] error-body carrier route through
        // `self.versao_requirement()`. A valid requirement passes
        // (positive control); a malformed-but-non-empty requirement fails
        // and the diagnostic quotes the offending byte-string verbatim
        // (same shape the accessor projects), so a future regression that
        // detoured the requirement carrier through a different byte-
        // string (say the parsed `VersionReq`'s `Display`, or a
        // normalized rewrite) would surface here at build time. The
        // empty-`:versao` arm fires the [`DepError::VersaoEmpty`] variant
        // ahead of the parse arm, pinning the empty-first cascade the
        // accessor's `""` sentinel round-trip acknowledges.
        Dep::simple("caixa-teia", "^0.1").validate().unwrap();
        let err = Dep::simple("caixa-teia", "v0.1").validate().unwrap_err();
        assert!(
            matches!(
                &err,
                DepError::VersaoInvalid {
                    nome,
                    versao,
                    ..
                } if nome == "caixa-teia" && versao == "v0.1",
            ),
            "expected VersaoInvalid quoting the accessor-projected requirement, got {err:?}",
        );
        let err = Dep::simple("caixa-teia", "").validate().unwrap_err();
        assert!(
            matches!(
                &err,
                DepError::VersaoEmpty { nome } if nome == "caixa-teia",
            ),
            "expected VersaoEmpty from the empty-first arm, got {err:?}",
        );
    }

    // ── Dep::fonte accessor pins ──────────────────────────────────────
    //
    // Three coherence pins on the lifted `Dep::fonte` accessor: byte-
    // equal projection over the plain-shorthand (`:fonte None`) /
    // explicit-git-tag / explicit-path fixture triad the [`Dep`]
    // docstring lists (so the accessor's accept-set is exercised across
    // every author-surface `:fonte` shape and both `DepSource` variants);
    // pointer identity so the borrowed reference points into the field's
    // own `Option<DepSource>` storage (not a cloned side-buffer); and
    // validate-composition through the [`Dep::validate`] gate reading
    // its per-`:fonte` [`DepSource::validate`] delegation through the
    // lifted accessor rather than the raw `if let Some(ref fonte) =
    // self.fonte` bracket.

    #[test]
    fn dep_fonte_returns_declared_source_across_shapes() {
        // Plain-shorthand form — `:fonte` omitted, accessor projects
        // the `None` partition the resolver-side default-fill treats
        // as "resolve through `github:<default-org>/<nome>`".
        assert!(Dep::simple("caixa-teia", "^0.1").fonte().is_none());
        // Explicit git-source form with a tag pin — same accessor path.
        let git = Dep::git("caixa-teia", "^0.1", "github:pleme-io/caixa-teia", "v0.1.0");
        match git.fonte() {
            Some(DepSource::Git {
                repo,
                tag,
                rev,
                branch,
            }) => {
                assert_eq!(repo, "github:pleme-io/caixa-teia");
                assert_eq!(tag.as_deref(), Some("v0.1.0"));
                assert!(rev.is_none());
                assert!(branch.is_none());
            }
            other => panic!("expected explicit git :fonte, got {other:?}"),
        }
        // Explicit path-source form — the dev-only local-filesystem
        // arm the [`Dep`] docstring's third fixture carries.
        let path = Dep {
            nome: "caixa-teia".to_string(),
            versao: "0.1.0".to_string(),
            fonte: Some(DepSource::Path {
                caminho: "../caixa-teia".to_string(),
            }),
            opcional: false,
            caracteristicas: Vec::new(),
        };
        match path.fonte() {
            Some(DepSource::Path { caminho }) => {
                assert_eq!(caminho, "../caixa-teia");
            }
            other => panic!("expected explicit path :fonte, got {other:?}"),
        }
    }

    #[test]
    fn dep_fonte_is_by_borrow_pointer_identity() {
        // Zero-copy pin: the accessor must borrow into the field's own
        // `Option<DepSource>` storage, not clone into a side buffer. If
        // a future rewrite regresses to `self.fonte.clone()` or an
        // owned-buffer shape, the two pointers diverge and this pin
        // fails at build time. Peer of the sibling per-`Dep` [`Dep::nome`]
        // (eba2cde) / [`Dep::versao_requirement`] (05529b1) pointer-
        // identity pins — same by-borrow discipline extended onto the
        // outer-`Dep` `Option<&Composite>` composite-reference axis.
        let d = Dep::git("caixa-teia", "^0.1", "github:pleme-io/caixa-teia", "v0.1.0");
        let accessed = d.fonte().expect("git :fonte present") as *const DepSource;
        let raw = d.fonte.as_ref().expect("git :fonte present") as *const DepSource;
        assert!(std::ptr::eq(accessed, raw));
    }

    #[test]
    fn dep_validate_reads_fonte_through_accessor() {
        // Composition pin: [`Dep::validate`]'s per-`:fonte`
        // [`DepSource::validate`] delegation consumes the typed slot
        // through the lifted accessor — an author-omitted `:fonte`
        // still passes the outer gate (positive control), an explicit
        // well-formed git source with exactly one pin passes, and a
        // malformed git source (empty `:repo`) surfaces the
        // [`DepError::FonteRepoEmpty`] variant quoting the offending
        // dep's `:nome` verbatim so a future regression that detoured
        // the `:fonte` delegation through a different path (say a
        // per-scope override projector) would surface here at build
        // time. Peer of the sibling
        // `dep_validate_reads_requirement_through_accessor` composition
        // pin on the `:versao` axis.
        // Positive control 1: no `:fonte` at all.
        Dep::simple("caixa-teia", "^0.1").validate().unwrap();
        // Positive control 2: well-formed git source.
        Dep::git("caixa-teia", "^0.1", "github:pleme-io/caixa-teia", "v0.1.0")
            .validate()
            .unwrap();
        // Negative control: empty `:repo` — the accessor still returns
        // `Some(&DepSource::Git { repo: "", … })` and the delegated
        // `DepSource::validate` gate raises the typed carrier.
        let bad = Dep {
            nome: "caixa-teia".to_string(),
            versao: "^0.1".to_string(),
            fonte: Some(DepSource::Git {
                repo: String::new(),
                tag: Some("v0.1.0".to_string()),
                rev: None,
                branch: None,
            }),
            opcional: false,
            caracteristicas: Vec::new(),
        };
        let err = bad.validate().unwrap_err();
        assert!(
            matches!(
                &err,
                DepError::FonteRepoEmpty { nome } if nome == "caixa-teia",
            ),
            "expected FonteRepoEmpty from the accessor-routed :fonte gate, got {err:?}",
        );
    }

    #[test]
    fn validate_no_self_dep_reads_parent_equality_through_accessor() {
        // Composition pin: the cross-slot [`validate_no_self_dep`] gate
        // rejects a `:deps` entry whose `:nome` equals the parent caixa's
        // own `:nome` through the lifted accessor rather than the raw
        // field. Fails-before-passes-after: with the accessor lifted the
        // gate reads its equality check through `dep.nome() ==
        // parent_nome` on both the `:deps` and `:deps-dev` traversals, so
        // the diagnostic still names the offending list tag as expected.
        let deps = vec![Dep::simple("orquestra", "^0.1")];
        let err = validate_no_self_dep(&deps, &[], "orquestra").unwrap_err();
        assert!(matches!(
            err,
            DepError::DepIsSelf {
                ref nome,
                list,
            } if nome == "orquestra" && list == crate::render::DEP_AUTHOR_KEY_DEPS,
        ));
        let deps_dev = vec![Dep::simple("orquestra", "^0.1")];
        let err = validate_no_self_dep(&[], &deps_dev, "orquestra").unwrap_err();
        assert!(matches!(
            err,
            DepError::DepIsSelf {
                ref nome,
                list,
            } if nome == "orquestra" && list == crate::render::DEP_AUTHOR_KEY_DEPS_DEV,
        ));
        // A non-matching `:nome` passes through the accessor gate.
        let deps = vec![Dep::simple("caixa-teia", "^0.1")];
        validate_no_self_dep(&deps, &[], "orquestra").unwrap();
    }

    // ── Dep::caracteristicas accessor pins ────────────────────────────
    //
    // Three coherence pins on the lifted `Dep::caracteristicas` accessor:
    // byte-equal projection over the default-empty / single-entry /
    // multi-entry fixture triad (so the accessor's accept-set is
    // exercised across every author-surface `:caracteristicas` shape,
    // matching the peer sibling family's fixture-triad discipline); by-
    // borrow pointer identity so the projection stays zero-copy at every
    // consumer site; and validate-composition through the
    // [`Dep::validate_caracteristicas`] gate reading its per-entry
    // linear walk through the lifted accessor rather than the raw
    // `for c in &self.caracteristicas` bracket.

    #[test]
    fn dep_caracteristicas_returns_declared_features_across_shapes() {
        // Default-empty form — the [`Dep::simple`] constructor's
        // `Vec::new()` fill; the accessor projects the empty slice
        // verbatim (no `None` collapse).
        assert!(
            Dep::simple("caixa-teia", "^0.1")
                .caracteristicas()
                .is_empty(),
        );
        // Single-entry form — the canonical Cargo-shaped one-feature
        // enable ([`crate::render::is_cargo_feature_name`] accepts the
        // `"http"` byte-string as a valid feature name).
        let one = Dep {
            nome: "caixa-teia".to_string(),
            versao: "^0.1".to_string(),
            fonte: None,
            opcional: false,
            caracteristicas: vec!["http".to_string()],
        };
        assert_eq!(one.caracteristicas(), &["http".to_string()]);
        // Multi-entry form — the substrate's set-shaped multi-feature
        // enable, exercising the accessor over a length-two slice with
        // no duplicate collapse.
        let two = Dep {
            nome: "caixa-teia".to_string(),
            versao: "^0.1".to_string(),
            fonte: None,
            opcional: false,
            caracteristicas: vec!["http".to_string(), "json".to_string()],
        };
        assert_eq!(
            two.caracteristicas(),
            &["http".to_string(), "json".to_string()],
        );
    }

    #[test]
    fn dep_caracteristicas_is_by_borrow_pointer_identity() {
        // Zero-copy pin: the accessor must borrow into the field's own
        // `Vec<String>` storage, not clone into a side buffer. If a
        // future rewrite regresses to `self.caracteristicas.clone()` or
        // an owned-buffer shape, the two pointers diverge and this pin
        // fails at build time. Peer of the sibling per-`Dep`
        // [`Dep::nome`] (eba2cde) / [`Dep::versao_requirement`] (05529b1)
        // / [`Dep::fonte`] (d65d1bf) pointer-identity pins — same by-
        // borrow discipline extended onto the outer-`Dep` `&[String]`
        // slice-projection axis.
        let d = Dep {
            nome: "caixa-teia".to_string(),
            versao: "^0.1".to_string(),
            fonte: None,
            opcional: false,
            caracteristicas: vec!["http".to_string(), "json".to_string()],
        };
        assert!(std::ptr::eq(
            d.caracteristicas().as_ptr(),
            d.caracteristicas.as_ptr(),
        ));
    }

    #[test]
    fn dep_validate_reads_caracteristicas_through_accessor() {
        // Composition pin: [`Dep::validate_caracteristicas`]'s per-entry
        // linear walk consumes the feature-toggle list through the
        // lifted accessor — a well-formed `:caracteristicas` set passes
        // (positive control), an empty-string entry surfaces the
        // [`DepError::CaracteristicaEmpty`] variant quoting the offending
        // `Dep::nome`, and a within-list duplicate surfaces the
        // [`DepError::CaracteristicaDuplicate`] variant so a future
        // regression that detoured the walk through a different byte-
        // string list (say a per-scope override projector) would surface
        // here at build time. Peer of the sibling
        // `dep_validate_reads_fonte_through_accessor` /
        // `dep_validate_reads_requirement_through_accessor` composition
        // pins on the `:fonte` / `:versao` axes.
        // Positive control: two distinct well-formed feature names pass.
        Dep {
            nome: "caixa-teia".to_string(),
            versao: "^0.1".to_string(),
            fonte: None,
            opcional: false,
            caracteristicas: vec!["http".to_string(), "json".to_string()],
        }
        .validate()
        .unwrap();
        // Negative control 1: empty-string feature-name entry — the
        // accessor still returns `&[""]` and the walk raises the typed
        // empty-first carrier.
        let err = Dep {
            nome: "caixa-teia".to_string(),
            versao: "^0.1".to_string(),
            fonte: None,
            opcional: false,
            caracteristicas: vec![String::new()],
        }
        .validate()
        .unwrap_err();
        assert!(
            matches!(
                &err,
                DepError::CaracteristicaEmpty { nome } if nome == "caixa-teia",
            ),
            "expected CaracteristicaEmpty from the accessor-routed walk, got {err:?}",
        );
        // Negative control 2: within-list duplicate — the accessor's
        // slice view carries both entries, and the walk's dedup arm
        // raises the typed duplicate carrier quoting the offending
        // feature name verbatim.
        let err = Dep {
            nome: "caixa-teia".to_string(),
            versao: "^0.1".to_string(),
            fonte: None,
            opcional: false,
            caracteristicas: vec!["http".to_string(), "http".to_string()],
        }
        .validate()
        .unwrap_err();
        assert!(
            matches!(
                &err,
                DepError::CaracteristicaDuplicate {
                    nome,
                    caracteristica,
                } if nome == "caixa-teia" && caracteristica == "http",
            ),
            "expected CaracteristicaDuplicate from the accessor-routed dedup, got {err:?}",
        );
    }

    // ── Dep::opcional accessor pins ───────────────────────────────────
    //
    // Two coherence pins on the lifted `Dep::opcional` accessor: byte-
    // equal projection over the default-`false` / explicit-`true`
    // fixture pair across the plain-shorthand (`:fonte None`) / explicit-
    // git-tag / explicit-path fixture triad the [`Dep`] docstring lists,
    // exercising the accessor's accept-set over every author-surface
    // `:fonte` shape × every author-surface `:opcional` shape; and by-
    // `Copy` idempotency so the projection stays value-return (no
    // silent detour to a fresh `&bool` borrow that would introduce a
    // lifetime on the return type the plain-`Copy`-scalar axis's `bool`
    // shape elides). No composition pin — `:opcional` does not
    // participate in [`Dep::validate`] (an opcional dep with any bool
    // value is validate-accepted; the missing-source arm is a resolver-
    // side runtime dispatch, not a build-time refusal), so the axis
    // reduces to the value-shape + `Copy` pin pair the peer
    // [`crate::Caixa::max_restarts`] / [`crate::Caixa::estrategia`]
    // outer-`Option<Copy>` accessor pins already carry.

    #[test]
    fn dep_opcional_returns_declared_opcional_across_fonte_shapes() {
        // Default-`false` form via the [`Dep::simple`] constructor —
        // the accessor projects the `false` bit the default-fill sets.
        assert!(!Dep::simple("caixa-teia", "^0.1").opcional());
        // Default-`false` form via the [`Dep::git`] constructor — same
        // default fill; the accessor projects `false` regardless of the
        // `:fonte` arm.
        assert!(!Dep::git("caixa-teia", "^0.1", "github:pleme-io/caixa-teia", "v0.1.0").opcional(),);
        // Explicit-`true` form × plain-shorthand `:fonte` — the
        // canonical author-surface "this dep may be missing" shape.
        let plain_true = Dep {
            nome: "caixa-teia".to_string(),
            versao: "^0.1".to_string(),
            fonte: None,
            opcional: true,
            caracteristicas: Vec::new(),
        };
        assert!(plain_true.opcional());
        // Explicit-`true` form × explicit git-source — the accessor
        // projects the bit verbatim regardless of the `:fonte` arm.
        let git_true = Dep {
            nome: "caixa-teia".to_string(),
            versao: "^0.1".to_string(),
            fonte: Some(DepSource::Git {
                repo: "github:pleme-io/caixa-teia".to_string(),
                tag: Some("v0.1.0".to_string()),
                rev: None,
                branch: None,
            }),
            opcional: true,
            caracteristicas: Vec::new(),
        };
        assert!(git_true.opcional());
        // Explicit-`true` form × explicit path-source — the dev-only
        // local-filesystem arm the [`Dep`] docstring's third fixture
        // carries.
        let path_true = Dep {
            nome: "caixa-teia".to_string(),
            versao: "0.1.0".to_string(),
            fonte: Some(DepSource::Path {
                caminho: "../caixa-teia".to_string(),
            }),
            opcional: true,
            caracteristicas: Vec::new(),
        };
        assert!(path_true.opcional());
    }

    #[test]
    fn dep_opcional_projects_bool_by_copy() {
        // The by-`Copy` pin: [`Dep::opcional`] returns `bool` by value
        // (`bool: Copy`) — the accessor does not borrow `&self` past
        // the call (no lifetime on the return type), and calling the
        // accessor twice on the same [`Dep`] must yield discriminant-
        // equal values (idempotent, no side effects on `&self`). Peer
        // of the sibling outer-`Caixa` `Option<Copy>` by-`Copy`
        // `max_restarts_projects_option_by_copy` (eba5211) /
        // `estrategia_projects_option_by_copy` (ed04d3c) pins on the
        // outer-`Caixa` altitude — extended here to the outer-`Dep`
        // altitude's plain-`Copy` `bool` axis. The `Copy` discipline
        // replaces the pointer-equality claim the sibling per-`Dep`
        // by-borrow pins (`dep_nome_is_by_borrow_pointer_identity`
        // eba2cde, `dep_versao_requirement_is_by_borrow_pointer_identity`
        // 05529b1, `dep_fonte_is_by_borrow_pointer_identity` d65d1bf,
        // `dep_caracteristicas_is_by_borrow_pointer_identity` 9197944)
        // carry (a fresh `Copy` of a `Copy` discriminant is definitionally
        // the same discriminant, so the axis reduces to discriminant
        // equality).
        //
        // Pins against a future silent detour that returned a fresh
        // `&bool` reference (which would type-check but silently
        // introduce a borrow of `&self` past the call, collapsing the
        // load-bearing "no lifetime on the return type" `Copy`
        // projection the plain-`Copy`-scalar axis's `bool` shape
        // carries) or a stale-read side effect that flipped the outer
        // discriminant on successive calls.
        for opcional in [false, true] {
            let d = Dep {
                nome: "caixa-teia".to_string(),
                versao: "^0.1".to_string(),
                fonte: None,
                opcional,
                caracteristicas: Vec::new(),
            };
            let first = d.opcional();
            let second = d.opcional();
            assert_eq!(
                first, second,
                "Dep::opcional must be idempotent — two successive calls \
                 on the same &self must return the same bool",
            );
            assert_eq!(
                first, opcional,
                "Dep::opcional must return :opcional verbatim by Copy — \
                 got {first}, expected {opcional}",
            );
            assert_eq!(
                d.opcional(),
                d.opcional,
                "Dep::opcional accessor and self.opcional field access \
                 must byte-equal — a bit-flip drift would silently split \
                 the paired resolver-side drop-vs-error dispatch from \
                 the storage-side default-fill the [`Dep::simple`] / \
                 [`Dep::git`] constructor pair carries",
            );
        }
    }

    // ── DepSource::sole_pin — sole-set git-pin accessor ─────────────────

    #[test]
    fn sole_pin_returns_none_for_path_source() {
        // A path source carries no git-ref, so `sole_pin()` returns
        // `None` structurally — the sibling arm every git-fetching
        // consumer partitions off before reaching for a git-ref. Pins
        // the Path-arm branch of the accessor against a future silent
        // detour that treats a `Self::Path` as an unpinned-git source
        // and returns the wrong "no pin" signal (e.g. the empty string,
        // or a hard-coded `Some("HEAD")` matching the caixa-crd
        // path-arm `git_ref` fill).
        let s = DepSource::Path {
            caminho: "../local-caixa".to_string(),
        };
        assert_eq!(s.sole_pin(), None);
    }

    #[test]
    fn sole_pin_returns_none_for_unpinned_git_source() {
        // The [`DepSource::default_github`] shorthand shape carries no
        // pin — every `tag`/`rev`/`branch` is `None`, and `sole_pin()`
        // returns `None`. This is the shape caixa-resolver's `fetch_dep`
        // materializes when the author omits `:fonte` entirely, then
        // hands to `fetch_git` which raises `ResolveError::MissingPin`
        // on the `None` arm — the accessor's return matches the arm
        // the resolver's diagnostic keys off.
        let s = DepSource::default_github("pleme-io", "caixa-teia");
        assert_eq!(s.sole_pin(), None);
    }

    #[test]
    fn sole_pin_returns_rev_when_only_rev_is_set() {
        let s = DepSource::Git {
            repo: "github:o/x".into(),
            tag: None,
            rev: Some("deadbeefcafebabe1234567890abcdef12345678".into()),
            branch: None,
        };
        assert_eq!(
            s.sole_pin(),
            Some("deadbeefcafebabe1234567890abcdef12345678")
        );
    }

    #[test]
    fn sole_pin_returns_tag_when_only_tag_is_set() {
        let s = DepSource::Git {
            repo: "github:o/x".into(),
            tag: Some("v0.1.0".into()),
            rev: None,
            branch: None,
        };
        assert_eq!(s.sole_pin(), Some("v0.1.0"));
    }

    #[test]
    fn sole_pin_returns_branch_when_only_branch_is_set() {
        let s = DepSource::Git {
            repo: "github:o/x".into(),
            tag: None,
            rev: None,
            branch: Some("main".into()),
        };
        assert_eq!(s.sole_pin(), Some("main"));
    }

    #[test]
    fn sole_pin_precedence_rev_beats_tag_and_branch() {
        // Precedence: rev > tag > branch. Validate() rejects
        // multiple-pin shapes, but the accessor's precedence is defined
        // for pre-validate consumers (the resolver's `MissingPin`
        // diagnostic path, the caixa-crd round-trip's default `"main"`
        // fallback) and as defense-in-depth if the gate is ever
        // bypassed. Pins the same precedence caixa-resolver's
        // `fetch_git` and caixa-crd's `dep_into_ref` already apply
        // inline.
        let s = DepSource::Git {
            repo: "github:o/x".into(),
            tag: Some("v1".into()),
            rev: Some("deadbeefcafebabe1234567890abcdef12345678".into()),
            branch: Some("main".into()),
        };
        assert_eq!(
            s.sole_pin(),
            Some("deadbeefcafebabe1234567890abcdef12345678")
        );
    }

    #[test]
    fn sole_pin_precedence_tag_beats_branch_when_no_rev() {
        let s = DepSource::Git {
            repo: "github:o/x".into(),
            tag: Some("v1".into()),
            rev: None,
            branch: Some("main".into()),
        };
        assert_eq!(s.sole_pin(), Some("v1"));
    }

    #[test]
    fn sole_pin_byte_equals_inline_rev_or_tag_or_branch_cascade() {
        // Fail-before-pass-after byte-parity pin: the substrate accessor
        // must return byte-identical to the inline
        // `rev.as_deref().or(tag.as_deref()).or(branch.as_deref())`
        // cascade both caixa-resolver's `fetch_git` and caixa-crd's
        // `dep_into_ref` open-coded pre-lift. Trips at caixa-core build
        // time if the accessor's precedence silently drifts from the
        // consumer-side cascade — the exact drift this lift converges
        // to one substrate primitive to close structurally.
        //
        // Iterates through the 2^3 = 8 combinations of (tag, rev,
        // branch) each-either-`None`-or-`Some`, so every arm of the
        // precedence cascade lands under the pin. `validate()` refuses
        // the 4 multi-pin combinations, but the accessor's return is
        // defined on all 8.
        let vals = [Some("R".to_string()), None];
        for tag in &vals {
            for rev in &vals {
                for branch in &vals {
                    let s = DepSource::Git {
                        repo: "github:o/x".into(),
                        tag: tag.clone(),
                        rev: rev.clone(),
                        branch: branch.clone(),
                    };
                    // The exact inline cascade the two pre-lift
                    // consumer sites hand-rolled, byte-for-byte.
                    let expected = rev.as_deref().or(tag.as_deref()).or(branch.as_deref());
                    assert_eq!(
                        s.sole_pin(),
                        expected,
                        "sole_pin() must byte-equal \
                         rev.or(tag).or(branch) for \
                         (tag={tag:?}, rev={rev:?}, branch={branch:?}) — \
                         a drift would silently split caixa-resolver's \
                         fetch_git checkout target from caixa-crd's \
                         dep_into_ref git_ref fill",
                    );
                }
            }
        }
    }
}