Skip to main content

Crate metalcraft_packs

Crate metalcraft_packs 

Source
Expand description

§metalcraft-packs

The shared spec / protocol for Metalcraft integrations and agent packs — the pieces every part of the ecosystem must agree on, byte for byte:

  • IntegrationManifest — the integration.json shape.
  • canonical_sha256 — the one true content digest of a file-map. The registry computes it at publish time; the agent recomputes it on install to verify integrity. These must agree, which is the whole reason this lives in one crate rather than being copied into each repo.
  • is_valid_integration_id — the id/slug rule.
  • version_ge — semver “newer-or-equal”, used for latest-pointer and downgrade decisions.

Everything else — what a valid agent pack is, how it installs, what a registry must serve — lives in metalcraft-agent/specs/AGENT_PACK_FORMAT.md. Rules that can be checked independently on each side belong in prose that reaches the TypeScript clients too; only the digest has to be shared as code, because a hash that disagrees is unrecoverable in a way a validation rule is not.

This crate is pure: no I/O, no HTTP, no database. It is the integration equivalent of metalcraft-flows (the flow-graph spec).

Re-exports§

pub use hash::canonical_sha256;
pub use hash::canonical_sha256_text;
pub use manifest::ecosystem_ids;
pub use manifest::is_ecosystem;
pub use manifest::IntegrationManifest;
pub use manifest::ECOSYSTEM_TAG;
pub use version::version_ge;

Modules§

hash
The canonical content hash of a pack.
manifest
The integration.json manifest shape, shared by the registry and the agent.
version
Semver comparison helpers shared across the ecosystem.

Functions§

is_valid_integration_id
Whether an integration id / slug is well-formed: ^[a-z0-9][a-z0-9_-]{0,63}$.

Type Aliases§

PackManifestDeprecated
The pre-0.2 name for IntegrationManifest.