Problem
After the migration squash (#837), test-upgrade is failing because volute mind upgrade conflicts on .claude/skills/volute-mind/.upstream.json.
The prior release (v0.55.0) installed skill volute-mind v1, which wrote .upstream.json with v1 metadata. HEAD has volute-mind v2 with different metadata. The upgrade merge conflicts on this file.
Root cause
.upstream.json files are runtime tracking files written by the skill sync system. They should not be part of the template merge comparison because:
- They are specific to when/how a skill was installed
- The skill sync will update them anyway after the upgrade
Suggested fix
Either:
- Add **/.upstream.json to the mind gitignore (changes existing behavior)
- Add **/.upstream.json merge=ours to .gitattributes so the mind version wins on conflict
- Explicitly exclude these files from the merge conflict list in upgrade.ts
Reproduction
Run npm run test:upgrade — the second test case fails.
Problem
After the migration squash (#837), test-upgrade is failing because volute mind upgrade conflicts on .claude/skills/volute-mind/.upstream.json.
The prior release (v0.55.0) installed skill volute-mind v1, which wrote .upstream.json with v1 metadata. HEAD has volute-mind v2 with different metadata. The upgrade merge conflicts on this file.
Root cause
.upstream.json files are runtime tracking files written by the skill sync system. They should not be part of the template merge comparison because:
Suggested fix
Either:
Reproduction
Run npm run test:upgrade — the second test case fails.