feat: Claude Code Hive plugin — native orchestration, 8 gate tools, 3 agents

[tctinh]

Summary

This branch rebases the Claude Code Hive work onto current main and tightens it around the current Hive / GitHub Copilot workflow instead of the earlier overengineered draft.

The main outcome is a publishable Claude Code delivery path:

• claude-code-hive ships the Claude-facing plugin assets
• hive-mcp ships the MCP runtime those assets launch
• the release pipeline now builds, validates, and publishes both packages alongside the existing packages

What Changed

Claude Code packaging

• Added packages/claude-code-hive as an npm package for the Claude plugin assets
• Shipped plugin.json, agents, commands, hooks, instructions, generated skills, and package-local launcher scripts
• Switched the plugin manifest to launch ./scripts/launch-hive-mcp.mjs instead of depending on a repo-local sibling path
• Added workspace/runtime preparation and asset verification scripts so local development and packed installs behave the same way

MCP runtime

• Added packages/hive-mcp as a publishable MCP server package
• Wired the server to accept an explicit project root and initialize services against that root
• Normalized the exposed Hive tool surface to the current canonical names such as hive_feature_create, hive_plan_write, and hive_feature_complete
• Added focused tests for service-root handling and tool-name coverage

Shared runtime cleanup

• Moved shared worker-prompt and prompt-budgeting utilities into hive-core
• Updated package dependencies to use release versions where the packaged consumers need them
• Fixed Bun-path handling in release artifact tests so packaging checks work in Node-driven environments too

CI / release / recovery

• Extended CI to build and test hive-mcp and claude-code-hive
• Expanded the release workflow to handle separate publish/recovery toggles for:
  • opencode-hive
  • hive-mcp
  • claude-code-hive
  • VS Code Marketplace
  • GitHub Release
• Enforced publish ordering so hive-mcp publishes before claude-code-hive
• Generalized npm publish-access preflight checks across all publishable npm packages
• Updated release contract tests to cover packed assets and install order

Docs

• Added Claude Code install guidance to the root README
• Added packages/claude-code-hive/README.md
• Updated docs/RELEASING.md to document multi-package publish and recovery behavior

Representative Files

• packages/claude-code-hive/plugin.json
• packages/claude-code-hive/scripts/launch-hive-mcp.mjs
• packages/claude-code-hive/scripts/prepare-workspace-hive-mcp.mjs
• packages/claude-code-hive/scripts/verify-plugin-assets.mjs
• packages/hive-mcp/src/index.ts
• packages/hive-mcp/src/server.ts
• packages/hive-mcp/src/services.ts
• .github/workflows/ci.yml
• .github/workflows/release.yml
• release-artifacts.test.mjs
• release-workflow.test.mjs

Validation

Ran successfully before push:

• node --test release-artifacts.test.mjs
• node --test release-workflow.test.mjs
• bun run build
• npm -ws --if-present run test
• git diff --check

[tctinh]

Merged and tagged v1.4.6, but the tagged Release workflow partially failed.

Observed state:

• PR merged on main at a80d93d
• tag v1.4.6 pushed successfully
• publish-opencode-hive succeeded
• publish-vscode succeeded
• publish-hive-mcp failed
• publish-claude-code-hive was skipped because hive-mcp failed first
• GitHub Release creation was skipped for the same reason

Authenticated Actions log for publish-hive-mcp shows the concrete failure:

• npm error code E403
• 403 Forbidden - PUT https://registry.npmjs.org/hive-mcp - You may not perform that action with these credentials.

This is not a repo build/package artifact failure. Local release checks were green, and local dry-run publish for hive-mcp succeeds. The blocker is the npm credential used by the workflow for hive-mcp publish.

Recovery path after fixing the npm credential or package publish permission:

• rerun Release with workflow_dispatch
• release_mode = recover
• recovery_tag = v1.4.6
• recover_hive_mcp = true
• recover_claude_code_hive = true
• recover_github_release = true
• leave recover_opencode_hive and recover_vscode disabled because those targets already succeeded

If the npm credential cannot be granted publish rights for hive-mcp under v1.4.6, cut a new patch release instead of retrying the same tag blindly.