agileflow.lock

The exact versions and hashes that agileflow sync reproduces.

agileflow.lock records resolution. It is generated; do not edit it. Commit it next to agileflow.yaml.

# Generated by AgileFlow. Do not edit by hand.
# Records the exact skill versions `agileflow sync` reproduces.
version: 1
resolved:
  diagnosing-bugs:
    source: "@agileflow/diagnosing-bugs"
    version: 1.0.1
    integrity: sha256-NPXz0qG+8Yj+Krt+03iGVnA2Q7FluotOZC/clkAKrGU=
    path: .agents/skills/diagnosing-bugs
    renderedHash: sha256-JUNeswhnIqtLFD20KesSozHF9cHeCN6NjK+EWQ8k2RQ=
    activation: auto
    ownership: managed
  filing-pr:
    source: .agents/skills/filing-pr
    version: local
    path: .agents/skills/filing-pr
    activation: auto
    ownership: local

Field	Meaning
`source`	Same as in `agileflow.yaml`.
`version`	Exact version: semver for registry skills, the package version or `0.0.0-git.<sha>` for git, the package version or `local` for paths.
`resolved`	The exact git commit, for git sources. `sync` checks out this commit.
`integrity`	Hash of the source package as published (every file's path, executable bit, and content). Checked before installing. Absent for locally owned skills.
`path`	Install location relative to the project (or home for personal skills).
`renderedHash`	Hash of the rendered skill directory exactly as AgileFlow installed it: the source plus render inputs (managed notice, question preference overlay, activation metadata). A different current hash means you modified the skill. The same `integrity` with a new `renderedHash` means only the render inputs changed, and `sync` re-renders clean skills. See Question preferences.
`activation`	Activation used when installing (default `auto`).
`ownership`	`managed` (AgileFlow owns the content) or `local` (you own it: forks and registered local skills).
`enabled`	`false` when the skill is disabled; omitted otherwise.

Keys are written in a stable order and skills are sorted by id, so lockfile diffs stay readable. The personal lockfile, ~/.config/agileflow/agileflow.lock, has the same format.

Ownership comes only from this file. AgileFlow never decides it owns a skill from its name.

The CLI version and skill versions are independent: a newer CLI does not change your locked skills, and skill updates do not need a new CLI.

agileflow.yaml