Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
The shipped Agent catalog as one owning artifact.
manifests/base/agents.yaml is the authored, kubectl-applied source of
truth for the deployed Agent custom resources (see that file's own
header, and docs/reference/declarative-catalog.md). Before this crate,
every consumer that needed the shipped catalog's content — the
installer, and three separate test suites — addressed the tree path by
hand and re-parsed it, and one of those consumers (the harness test
support) even carried its own partial copy of the Agent schema. A
catalog edit could then pass two of those readers and silently drift
against the third.
This crate embeds the shipped file at compile time and exposes it through
one typed decode path, [shipped], into polyc_controller::Agent — the
same type the apiserver and the reconciler use. Every other Rust
consumer of the catalog's content goes through this crate; the
installer's raw kubectl apply -f (which applies the file rather than
parsing it) instead names the tree path via [MANIFEST_PATH].
Parsing itself does not deep-validate references (a dangling
toolsEnabled or canHandoffTo entry is a reconciler .status concern,
not a decode concern) — see polyc_controller::agent's module doc.