chore(sync): regenerate from stark-skills@60f377c

[stark-claude-21s]

Automated regeneration from stark-skills@60f377c2172aada9a31982590cf5f47b8efae533 by the marketplace-sync workflow. Merges once this repo's CI is green.

[aryeh-stark]

Closing — superseded, and merging it now would regress main.

This auto-sync fired when stark-skills#810 merged, and its substantive content is already on main via #122. Verified byte-identical:

file	vs main
vendor/plugins/stark-gh/tools/lib/git.ts	same
vendor/plugins/stark-gh/tools/lib/types.ts	same
dist/claude/stark-gh/tools/lib/git.ts	same

The problem is the base. This branch predates #122 and #123, so git diff main..HEAD is 457 deletions — merging it would remove the plugin-asset version gate added in #123:

 engine/internal/digest/files.go   |  97 ---------
 engine/internal/index/index.go    |  33 +--
 engine/internal/build/build.go    |  12 +-
 index.json                        |  33 +--     (pluginAssets rows stripped)

That gate is what stops a change confined to vendor/plugins/<bundle>/tools/** from shipping under an unchanged bundle version — the exact failure that made this sync necessary in the first place (a lib/git.ts fix sat at 0.1.10 and would never have reached an installed machine).

It also bumps cleanup.md / pr-merge.md / pr-open.md artifact versions to 0.1.11. Those command bodies never changed — only the plugin's vendored tools did — so per the semver policy they should stay at 0.1.10, which is what main has. check-bumps and build --check are both clean there.

Nothing is lost by closing. If a future sync needs to re-run, it should branch from current main.