[Bug]: specify init writes speckit.manifest.json without the speckit-converge skill it just installed

[jabelk]

Version

spec-kit v1.0.1, specify init --here --integration claude --force

Description

After an in-place upgrade, .specify/integrations/speckit.manifest.json lists 9 speckit-* SKILL.md entries under files — but init also installed .claude/skills/speckit-converge/SKILL.md, which is absent from the manifest.

Any tooling that uses the manifest to classify vendored files (pristine / modified / missing / untracked — e.g. deciding whether the next specify init will clobber local work) sees converge as untracked: it cannot be classified at all, which is the worst of the four states for a file the installer itself owns.

Observed identically on two independent upgrades (a template repo and a workflows repo, both 0.5.0 → v1.0.1 in-place).

Expected behavior

The generated manifest includes every skill file the init run installs, converge included.

[Gambit-Checkmate]

Hi, I’d like to investigate the missing speckit-converge entry in the manifest generated by init. I can reproduce it with a clean installation, add a regression test for the generated manifest, and make the smallest fix that keeps existing manifests compatible. Is this issue open for an external PR?