registry.update

Registry.update automates skill manifest validation and registry updates by loading YAML manifests, enforcing organizational policies on naming and versioning, and atomically updating the registry file. This eliminates manual edits and ensures compliance across development and deployment workflows.

Yes. Registry.update applies policy enforcement to all skill manifests, validating naming conventions, required fields, and versioning rules automatically. Policy violations trigger structured responses that prevent non-compliant skills from entering the registry.

Registry.update handles concurrent access safely through thread-safe operations, preventing corruption when multiple skill manifests attempt simultaneous registry updates. Atomic writes to /registry/skills.json ensure data integrity across parallel validation and deployment workflows.

Registry.update emits a structured policy-violation response that halts the update. The skill is not added to the registry, and audit logging captures the failure. This ensures only compliant skills enter the registry and maintains an audit trail of all validation events.

Registry.update depends on skill.define and registry.diff to validate and compare manifests. These dependencies handle manifest preparation and change detection, so the validation pipeline is integrated into the registry update process.