chore: prepare githits 0.11.0 release

[jlitola]

Summary

• bump githits and @githits/mcp to the coordinated minor version 0.11.0
• consolidate all four pending fragments into separate dated changelog sections and remove the consumed files
• align server.json, bun.lock, and every generated version-bearing plugin, marketplace, and extension manifest
• document the hosted MCP rollout dependency and public MCP compatibility changes found during release review

Release scope

This minor release adds the portable quick_start MCP guidance flow, improves tool routing, makes onboarding setup/removal predictable, corrects changelog range and ordering contracts, and rejects canonical experimental resolve inputs locally.

The hosted endpoint must deploy @githits/mcp 0.11.0 before remote plugins and extensions rely on quick_start.

Validation

• bun run plugins:generate — generated 10 assets
• bun run plugins:check — validated 10 assets
• bun test — passed
• bun run typecheck — passed
• bun run lint — passed
• bun run format:check — 422 files checked, no fixes
• bun run build — passed
• bun run --cwd packages/mcp build — passed
• bun run validate:packages — passed
• bun run validate:packages:mcp-publish — passed
• bun run smoke:cli — authenticated stable and experimental cohorts passed, 89 steps
• bun run smoke:mcp — authenticated stable and experimental cohorts passed, 46 steps
• bun run smoke:cli:built — Node-built stable and experimental unauthenticated suite passed, 18 steps
• bun run smoke:mcp:built — Node-built stable and experimental registration suite passed, 7 steps
• bun test src/package-release-boundaries.test.ts after review changes — 7 passed, 0 failed, 41 assertions
• git diff --check — passed
• direct mcp-publisher validate server.json was not run because the pinned binary is unavailable locally; server.json changes only the two aligned SemVer strings on the previously accepted shape

Review

Claude Opus review loop completed in three rounds:

• round 1 found two valid artifact-accuracy gaps, both fixed; one category suggestion was rejected because categories derive from fragment suffixes
• round 2 verified those closures and found four minor compatibility/rollout note gaps through its one permitted fresh-context check; all were verified and fixed
• round 3 verified every closure and reported no findings
• internal Codex review was clean before every external round

The Claude reviewer remains retained for pre-merge follow-up.

Publishing behavior

Do not merge without separate explicit approval for this PR. After an approved merge, a successful Main workflow will trigger both release workflows: publish githits@0.11.0 and @githits/mcp@0.11.0, create their tags/releases, and publish com.githits/githits@0.11.0 to the MCP registry. Hosted MCP deployment remains a separate operator action.