Expand description
The user-scope skill record: what this tool last wrote outside an instance.
Skill destinations live under the invoking user’s home, where no instance manifest reaches, so without a record the installer’s only reference is the payload it currently carries. That makes a copy left by an older release indistinguishable from a file the user edited, and every release that touches a skill refuses on destinations nobody touched. This record closes that gap and nothing else: one digest per destination, written after a successful apply, read to answer one question — are these bytes ones we wrote?
It is not an instance manifest and never becomes one. No verification
reads it, and distribution:user-scope-files-stay-unrecorded keeps
these paths out of the manifest that does drive verification.
It is required state all the same. An apply that cannot write it fails and rolls back, because a landing this tool cannot vouch for is a landing it will refuse to take back. Reading is the forgiving half: a record that is absent, unreadable, or written by a schema this binary does not know reads as empty, and the caller loses the benefit of the doubt and nothing else.
Re-exports§
pub use crate::domain::paths::LEGACY_SKILL_RECEIPT_PATH as RECORD_PATH;
Structs§
- Skill
Record - The digests this tool last wrote to user-scope skill destinations.
Constants§
- SCHEMA_
VERSION - The record schema this binary writes.