[zzet]

Summary

publish-claude-plugin fails in "Regenerate plugin bundle" on every run since 2026-05-22, including the manual dispatch from main today after #1180:

go build ... -tags llama -o gortex ./cmd/gortex/
Package llama was not found in the pkg-config search path.
Package 'ggml' not found

make claude-plugin depends on build, and build has linked llama.cpp through -tags llama since c2ccbd4. The publish runner has no llama.cpp. The last successful publish was 2026-05-14, which is why gortexhq/claude-plugin is still on the v0.24.0 layout. The v0.53.1 release run failed at this same step.

Changes

• Makefile: claude-plugin no longer depends on build. It runs the emitter with go run and the same ldflags, with no build tags, because the emitter needs none of the optional backends. go run also leaves a developer's locally built ./gortex untouched.
• .github/workflows/skill-drift.yml: adds a make claude-plugin step. Nothing else ran this target, so a build change that broke it only showed up when a release tried to publish. The job already builds the pure-Go CLI on a stock runner, so the step adds little time. The job now also triggers on Makefile and publish-claude-plugin.yml changes.

Testing

• make claude-plugin on this branch: builds without the llama tag and writes the 32-file marketplace bundle (.claude-plugin/marketplace.json, plugins/gortex/, README, LICENSE) in about 16 s.
• The skill-drift job on this PR runs the new step on a stock ubuntu-latest runner.
• End to end: after merge, dispatch publish-claude-plugin with ref=main.

Checklist

• Code follows existing patterns in the codebase
• No unnecessary abstractions added