Use this guide when you want to refresh generated artifacts and control overwrite behavior.
Run a full idempotent refresh from project config:
vstack initUse --only to refresh a subset:
vstack init --only hook
vstack init --only hook agentUse prune mode to remove tracked artifacts that are no longer generated:
vstack init --pruneRun a preview first if needed:
vstack init --prune --dry-runWithout --prune, obsolete candidates are reported and preserved.
Force overwrite for selected type scope:
vstack init --only hook --forceForce overwrite for all managed artifacts:
vstack install --forceForce overwrite one named artifact:
vstack install --force-name hook/agent-call-audit
vstack install --force-name agent/engineerUse selectors as type/name.
Refresh hooks and verify hook state:
vstack init --only hook
vstack manifest status --target . --only hook
vstack manifest verify --target . --only hookRefresh agents and verify agent state:
vstack init --only agent
vstack manifest status --target . --only agent
vstack manifest verify --target . --only agent- A normal
vstack initpreserves locally modified managed artifacts. vstack manifest status --target .shows those files as modified.vstack manifest verify --target .reports checksum mismatch.- The file is overwritten only when you use an explicit force command.
- Run
vstack manifest status --target .to list modified managed files. - Run
vstack manifest verify --target .to confirm checksum mismatches. - Decide scope:
- one artifact:
vstack install --force-name <type>/<name> - one type:
vstack init --only <type> --force - all managed artifacts:
vstack install --force
- one artifact:
- Re-run
vstack manifest status --target .. - Re-run
vstack manifest verify --target ..