pub struct CapabilityLockEntry {
pub capability_type: CapabilityType,
pub version: String,
pub version_scheme: VersionScheme,
pub description: String,
pub source: CapabilitySource,
pub targets: BTreeMap<String, TargetLockEntry>,
pub implementation: Option<ImplementationConfig>,
pub parameters: Option<Value>,
pub workflow: Option<WorkflowConfig>,
pub server: Option<McpServerConfig>,
}Fields§
§capability_type: CapabilityType§version: StringThe capability’s own version: a declared manifest version, or the
commit that was installed when nothing better exists. Which one is
recorded in version_scheme, never guessed from the string.
version_scheme: VersionScheme§description: String§source: CapabilitySourceWhere this capability came from. One typed value, so every lifecycle
verb dispatches on match instead of comparing strings.
targets: BTreeMap<String, TargetLockEntry>§implementation: Option<ImplementationConfig>Cached from the manifest at install/update time, the same way
description is: after install, only the files a manifest declares
get copied to disk, tuff.toml itself does not, so this is the only
durable record of how a tool is invoked. Consumed by the generated
capability-index skill (RFC-103 tier 1).
parameters: Option<Value>§workflow: Option<WorkflowConfig>Same rationale as implementation/parameters: a workflow’s
requires list lives only in its manifest, which isn’t copied to the
installed target directory.
server: Option<McpServerConfig>Trait Implementations§
Source§impl Clone for CapabilityLockEntry
impl Clone for CapabilityLockEntry
Source§fn clone(&self) -> CapabilityLockEntry
fn clone(&self) -> CapabilityLockEntry
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more